10 Aug

How to Secure Your Computer: A Practical Security Guide for Website Developers and Hosting Users

If you manage websites, hosting accounts, domains, email accounts, databases, or servers, your computer is more than just a personal device.

It is a key to your digital infrastructure.

If your computer becomes compromised, an attacker may not need to “hack” your hosting server directly. They may simply steal the credentials, cookies, SSH keys, API tokens, FTP passwords, cPanel credentials, or session information already available on your computer.

This is why securing your own computer is just as important as securing the server you manage.

Modern attacks increasingly focus on stealing identities rather than breaking into systems. Infostealer malware, phishing, malicious browser extensions, fake software installers, stolen session cookies, and credential leaks can give attackers everything they need to log in as you.

For website developers and hosting users, one compromised workstation can potentially lead to multiple compromised websites or hosting accounts.

Here is a practical security checklist for keeping your everyday computer safer.


1. Understand the Most Important Rule: Your Computer Is Part of Your Security Infrastructure

Many people think:

“My server is secure, so my websites are secure.”

That isn’t necessarily true.

Consider this situation:

You have access to:

  • WHM
  • cPanel
  • SSH
  • FTP/SFTP
  • Git repositories
  • Cloudflare
  • Domain registrars
  • DNS management
  • Email
  • Database servers
  • Hosting billing systems
  • Backup systems

Now imagine that malware running on your computer steals your browser cookies, saved credentials, or SSH keys.

The attacker may not need to exploit your server at all.

They can simply use the credentials you already have.

For administrators and developers, endpoint security is therefore part of server security.


2. Keep Your Operating System Updated

Operating system updates are one of the simplest and most effective security measures.

Enable automatic security updates whenever possible.

Keep updated:

  • Windows
  • macOS
  • Linux desktop distributions
  • Device drivers
  • System components
  • Security software

Do not continuously postpone security updates because they are inconvenient.

Security vulnerabilities are regularly discovered in operating systems and applications. Attackers actively look for machines that have not received available security fixes.

CISA recommends keeping software and operating systems up to date and enabling automatic updates where possible.

For Windows users

Make sure:

Windows Update ? Automatic Updates

is enabled.

Also make sure Microsoft Defender and its security intelligence updates are current.


3. Keep Your Browser Updated

Your browser is one of the most frequently used applications on your computer—and one of the most important security boundaries.

Keep Chrome, Edge, Firefox, Safari, or whichever browser you use updated.

Do not ignore:

“Restart to update”

for weeks.

Modern browsers contain security protections against malicious websites, phishing, dangerous downloads, exploit attempts, and other attacks.

A browser that is several versions behind can expose you to vulnerabilities that have already been fixed.


4. Be Careful About Browser Extensions

Browser extensions can have enormous access to your browsing environment.

A malicious or compromised extension may potentially access sensitive information depending on the permissions it receives.

For a developer or hosting administrator, this can be particularly dangerous.

You may be logged into:

  • WHM
  • cPanel
  • Cloudflare
  • GitHub
  • Google Workspace
  • Email
  • Domain registrar
  • Payment systems

Ask yourself:

Does this extension really need access to my websites and browsing data?

Remove extensions that you:

  • Don’t use
  • Don’t remember installing
  • No longer trust
  • Don’t recognize
  • Installed only temporarily

Install extensions only from reputable sources and periodically review your installed extensions.


5. Password Managers Are Not the Enemy

There is a common belief that:

“Never save passwords in your browser.”

That advice is understandable, but it is too simplistic for modern security.

A reputable password manager can be significantly safer than using the same password—or variations of the same password—across dozens of websites.

CISA recommends using long, random, unique passwords and a password manager to generate and store them.

The important question is not:

“Are my passwords stored?”

The more important question is:

“How are they protected?”

A good password manager should allow you to use:

  • Unique passwords for every service
  • Long randomly generated passwords
  • Strong encryption
  • MFA
  • Biometric or device authentication
  • Password breach detection
  • Secure synchronization

Modern browsers also protect stored credentials using operating-system security mechanisms. For example, Microsoft documents encryption protections for passwords stored in Edge.

But there is an important warning

A password manager does not protect you from an infected computer.

Infostealer malware can target browser credentials, cookies, session information and other sensitive data. Microsoft has documented malware campaigns specifically designed to steal browser credentials and session cookies.

Therefore:

Password manager + secure computer + MFA

is much stronger than simply refusing to save passwords.


6. Use Passkeys Whenever They Are Available

Passkeys are becoming an important replacement for traditional passwords.

Instead of typing a password, you authenticate using your device’s security mechanism, such as:

  • Fingerprint
  • Face recognition
  • Device PIN
  • Hardware security key

Passkeys are designed to resist many forms of phishing because the authentication credential is cryptographically tied to the legitimate website.

Google supports passkeys through Google Password Manager across major desktop and mobile platforms.

For important accounts, prefer:

Passkey > phishing-resistant MFA > traditional password alone

where supported.


7. Enable Multi-Factor Authentication Everywhere Possible

If an account supports MFA, enable it.

This is particularly important for:

  • Email
  • WHM
  • cPanel
  • Cloudflare
  • Domain registrar
  • GitHub/GitLab
  • Google Workspace
  • Microsoft accounts
  • Hosting billing systems
  • Server management systems
  • Banking and payment accounts

But not all MFA methods provide the same level of protection.

Where available, prefer:

  1. Passkeys
  2. Hardware security keys
  3. Authenticator applications
  4. SMS-based authentication

SMS is better than having no second factor, but it is generally not the strongest option.

Microsoft has reported that phishing-resistant MFA can prevent the overwhelming majority of password-based identity attacks, even when an attacker knows the username and password.


8. Never Reuse Your Hosting Password

This deserves its own section.

Your hosting password should not be the same password you use for:

  • Gmail
  • Facebook
  • WordPress
  • Your domain registrar
  • Another hosting company
  • Your personal email
  • Your computer

If another website suffers a data breach and your password is reused there, attackers may try the same credentials against your hosting account.

This is called credential stuffing.

Your WHM/cPanel/hosting password should be:

Unique and used nowhere else.

The same principle applies to your email and domain registrar accounts.


9. Protect Your Email Account Like a Master Key

Your primary email account is often more important than your hosting account.

Why?

Because an attacker who gains access to your email may be able to reset passwords for:

  • Hosting
  • Domain registrar
  • Cloudflare
  • GitHub
  • Social media
  • Payment services
  • Other email accounts

Your primary email should therefore have:

  • A unique password
  • MFA or a passkey
  • Recovery information
  • Security alerts enabled
  • Regular login/activity monitoring

Think of your email account as the master key to your digital life.


10. Do Not Trust Emails Just Because They Look Professional

Modern phishing emails can look extremely convincing.

An email can contain:

  • Company logos
  • Correct branding
  • Professional formatting
  • Realistic signatures
  • Fake support tickets
  • Fake invoices
  • Security warnings
  • Password expiration notices
  • Domain renewal notices
  • “Your account has been suspended” messages

Never assume:

“It has a company logo, therefore it is legitimate.”

Instead, verify the request independently.

For example, if you receive:

“Your Cloudflare account has been suspended. Click here to restore access.”

Do not immediately click the link.

Open your browser and manually visit the official website.

The same applies to:

  • Hosting companies
  • Domain registrars
  • Banks
  • Google
  • Microsoft
  • GitHub
  • Payment providers

11. Check the Website Address Before Logging In

Phishing websites can look almost identical to legitimate websites.

Before entering credentials, check the domain carefully.

For example:

example.com

is completely different from:

example-login.com

or:

example.com.some-random-domain.com

or:

examp1e.com

Attackers frequently use domains that visually resemble legitimate websites.

For highly sensitive services, consider using bookmarks or manually entering the known official address rather than following login links from emails.


12. Do Not Install Random “Tools” From the Internet

This is one of the biggest risks for developers.

You may search for:

  • PDF converters
  • Video converters
  • Cracked software
  • Windows activators
  • Drivers
  • WordPress tools
  • SEO software
  • FTP clients
  • SSH utilities
  • “Free” premium plugins
  • Theme generators
  • AI tools
  • Browser utilities

and download software from an unknown website.

This is dangerous.

A program can appear to work normally while silently installing an infostealer or remote-access malware.

Download software from:

  • The vendor’s official website
  • Microsoft Store
  • Apple App Store
  • Trusted package repositories
  • Official GitHub/GitLab repositories when appropriate

Be particularly suspicious of:

“Disable antivirus before installing.”

That is an enormous red flag.


13. Avoid Pirated and Cracked Software

Cracked software is one of the easiest ways for attackers to distribute malware.

A “free” application may contain:

  • Password stealers
  • Remote access trojans
  • Cryptominers
  • Ransomware
  • Browser stealers
  • Keyloggers

For someone who manages hosting accounts, the risk is much greater because the computer may contain highly valuable credentials.

Saving money on a software license is not worth losing control of your hosting infrastructure.


14. Treat Unexpected Browser Pop-ups as Suspicious

If a website suddenly displays:

“Your computer is infected!”

or:

“Your Windows license has expired!”

or:

“Your browser is outdated!”

or:

“Click Allow to verify you are human.”

Stop.

Do not panic.

Do not install anything.

Do not call a phone number displayed by the website.

Do not grant remote access.

Close the tab/window and investigate using a trusted source.

Websites cannot normally determine that your computer has a virus simply because a pop-up says so.


15. Be Careful With “Allow Notifications”

Many websites ask:

“Allow notifications?”

Users often click Allow without thinking.

A malicious website can abuse browser notifications to display fake:

  • Antivirus warnings
  • Security alerts
  • Cryptocurrency scams
  • Fake Microsoft warnings
  • Fake Google warnings
  • Fake update notifications

Only allow notifications for websites that genuinely need them.

Periodically review browser notification permissions and remove suspicious sites.


16. Do Not Install Unknown Remote-Access Software

Applications such as remote-support tools can be legitimate and useful.

But if someone contacts you unexpectedly and says:

“Please install this software so I can fix your computer.”

be extremely careful.

Never provide remote access to an unknown person simply because they claim to be:

  • Microsoft support
  • Google support
  • Your hosting provider
  • Your bank
  • Your ISP
  • Your antivirus company

If remote access is genuinely required, initiate the support request yourself and verify the support provider independently.


17. Use Antivirus and Endpoint Protection

Modern operating systems already include security protection.

For Windows users, Microsoft Defender provides built-in protection against many common threats.

Keep it enabled and updated.

Do not install multiple antivirus products simply because you think:

“More antivirus = more security.”

Multiple security products can conflict with each other and do not necessarily provide better protection.

More importantly, antivirus is only one layer.

You still need:

  • Updated software
  • MFA
  • Safe browsing
  • Secure passwords
  • Good download habits
  • Regular monitoring

18. Use a Separate Computer for High-Value Administration

If you manage significant hosting infrastructure, consider separating everyday activities from administrative activities.

For example:

Everyday computer

Used for:

  • Social media
  • YouTube
  • General browsing
  • Downloads
  • Personal email
  • Entertainment

Administrative computer

Used primarily for:

  • WHM
  • SSH
  • Server administration
  • Domain management
  • Cloudflare
  • Git repositories
  • Production systems

The idea is simple:

The fewer risky activities performed on your administrative computer, the smaller the attack surface.

Microsoft also recommends dedicated PCs for users with access to high-value assets as part of its credential-protection guidance.

For larger organizations, dedicated privileged-access workstations can be an extremely effective security measure.


19. Do Not Use an Administrator Account for Everything

On your everyday computer, avoid running everything with administrator privileges.

Use a standard user account for normal activities where practical.

When administrator privileges are genuinely required, elevate the operation.

This makes it harder for certain types of malware to immediately obtain system-level privileges.


20. Secure Your Computer’s Login

Your Windows/macOS login itself should be protected.

Use:

  • Strong device password/PIN
  • Fingerprint
  • Face authentication
  • Automatic screen locking

Never leave your workstation unlocked when you walk away.

This is especially important in offices.

Someone does not need sophisticated malware if they can simply sit at your unlocked computer and access your browser, email, hosting panel, or password manager.


21. Secure Your SSH Keys

Developers and server administrators frequently use SSH keys.

Treat SSH private keys like passwords—but potentially even more carefully.

Never:

  • Send private keys through chat
  • Upload them to public repositories
  • Put them inside website files
  • Store them in publicly accessible directories
  • Commit them to Git
  • Share them with customers

Use encrypted key storage and strong passphrases.

Remember:

Private key = authentication credential.

If someone steals it, they may be able to authenticate without knowing your traditional password.


22. Never Put Production Credentials in Source Code

This is extremely important for developers.

Do not put credentials directly inside:

config.php
.env
database.php
settings.php
Git repositories
JavaScript files
public HTML

depending on the application and deployment architecture.

Never commit:

  • Database passwords
  • API keys
  • SMTP passwords
  • Cloud credentials
  • SSH private keys
  • Hosting passwords

to a public Git repository.

Microsoft specifically warns developers not to hardcode passwords, API keys, connection strings, or other secrets in source code.

Use appropriate secret-management and environment/configuration mechanisms instead.


23. Be Careful With Git Repositories

Before pushing a project to GitHub or another Git server, check what you are committing.

A common mistake is accidentally committing:

.env
config.php
backup.sql
database credentials
SSH keys
API keys

Once a secret has been pushed to a repository, simply deleting the file may not be enough because the secret may remain in Git history.

If a secret is exposed:

Treat it as compromised and rotate it immediately.

Do not merely delete the file.


24. Be Careful With FTP

If you manage websites, avoid plain FTP whenever possible.

Prefer:

  • SFTP
  • SSH
  • FTPS where appropriate

Plain FTP transmits credentials without the protection provided by encrypted transport.

Also avoid storing FTP passwords unnecessarily in multiple applications.


25. Be Careful With cPanel and WHM Sessions

For hosting administrators and resellers, browser sessions themselves can be valuable to attackers.

Do not assume:

“I have MFA, therefore I’m completely protected.”

If malware steals an active session cookie, the attacker may potentially use the existing authenticated session without needing the password.

This is one reason endpoint security is so important.

Log out of sensitive systems when they are no longer needed, particularly on shared or untrusted computers.


26. Monitor Your Important Accounts

Security isn’t only about prevention.

Monitor for unusual activity.

Look for:

  • Unknown login locations
  • Unknown devices
  • Password reset emails you did not request
  • New MFA devices
  • New SSH keys
  • New API tokens
  • Unexpected forwarding rules
  • New email filters
  • Unknown administrators
  • Unexpected hosting account changes
  • New FTP accounts
  • New cPanel users
  • Unexpected DNS changes

If something looks suspicious, investigate immediately.


27. Never Ignore Security Notifications

If Google, Microsoft, Cloudflare, GitHub, your hosting provider, or another service tells you:

“A new login was detected.”

Do not simply dismiss it.

Ask:

Was this me?

If the answer is no:

  1. Change the password.
  2. Revoke active sessions.
  3. Remove unknown devices.
  4. Review MFA settings.
  5. Review recovery information.
  6. Check API keys/tokens.
  7. Investigate the computer from which you normally log in.

28. If You Suspect Your Computer Is Infected, Stop Using It for Administration

This is especially important for hosting users.

Suppose several websites suddenly become compromised and you suspect your hosting credentials were stolen.

Do not immediately log into WHM from the same computer and start changing every password.

If the computer is infected, the attacker may simply capture the new passwords as you type them.

Instead:

Use a known-clean device to change critical credentials.

Then:

  1. Change the hosting/reseller password.
  2. Revoke active sessions where possible.
  3. Enable MFA.
  4. Rotate SSH keys if necessary.
  5. Rotate API tokens.
  6. Change email credentials.
  7. Review account activity.
  8. Scan and investigate the original computer.
  9. Check all websites for backdoors and unauthorized accounts.
  10. Re-secure the workstation before using it for administration again.

29. Remember: Malware Can Steal More Than Passwords

This is one of the most important security lessons today.

People often think:

“I don’t save my passwords, so malware can’t steal them.”

Unfortunately, that’s not necessarily true.

Modern infostealers may target:

  • Browser passwords
  • Cookies
  • Session tokens
  • Autofill information
  • Cryptocurrency wallets
  • Browser profiles
  • Email credentials
  • Authentication data
  • Files
  • Application data

Microsoft has documented attacks where malware specifically targeted browser profile data and session cookies, allowing attackers to impersonate users without necessarily needing their password.

Therefore:

Typing your password manually is not a substitute for having a clean computer.


30. Keep Your Browser Profile Clean

Periodically review:

  • Saved passwords
  • Saved payment methods
  • Extensions
  • Notification permissions
  • Download history
  • Unknown browser profiles
  • Signed-in devices
  • Synced data

Remove anything you don’t recognize.

If you suddenly discover an extension you don’t remember installing, don’t simply ignore it.

Investigate how it got there.


31. Be Suspicious of Urgency

Attackers love urgency.

Messages such as:

“Your account will be deleted in 30 minutes.”

“Your domain expires today.”

“Your server has been suspended.”

“Payment failed—click immediately.”

“Your mailbox is full.”

“Your SSL certificate has expired.”

are designed to make you act before thinking.

Slow down.

Verify independently.

A few extra seconds can prevent a major security incident.


32. Back Up Your Important Data

Security is not only about preventing unauthorized access.

You also need to be able to recover from:

  • Ransomware
  • Hardware failure
  • Accidental deletion
  • Malware
  • Lost devices

Keep important files backed up.

For critical business data, maintain backups that cannot simply be deleted by the same account that is compromised.

And periodically test whether your backups can actually be restored.

A backup that has never been tested is only a backup in theory.


33. Secure Your Wi-Fi and Home/Office Network

Your computer is not the only thing that needs protection.

Secure your router:

  • Change the default administrator password.
  • Keep router firmware updated.
  • Use WPA2/WPA3.
  • Disable unnecessary remote administration.
  • Use a strong Wi-Fi password.
  • Review connected devices.
  • Replace old routers that no longer receive security updates.

If you work from public Wi-Fi, be particularly careful with administrative activities.


34. Don’t Trust USB Devices

Avoid connecting unknown USB drives to your computer.

A USB device can contain malicious files or exploit vulnerabilities.

If someone gives you a USB drive containing:

“Important website backup”

don’t automatically plug it into the computer you use to administer your servers.

Use appropriate security controls and scan files before opening them.


35. Security Is About Layers

There is no single magic security setting.

Good security looks more like this:

Secure device

?

Updated OS

?

Updated browser

?

Endpoint protection

?

Strong unique credentials

?

Password manager/passkeys

?

MFA

?

Safe browsing habits

?

Limited privileges

?

Secure server access

?

Monitoring

?

Backups

Each layer reduces the chance that one mistake becomes a disaster.


A Practical Security Checklist for Website Developers

If you develop websites or manage hosting accounts, your minimum checklist should look something like this:

Computer

  • Operating system automatically updated
  • Browser automatically updated
  • Antivirus/endpoint protection enabled
  • Firewall enabled
  • Screen automatically locks
  • Strong device authentication
  • Unnecessary applications removed
  • Unknown browser extensions removed
  • No pirated/cracked software

Accounts

  • Unique password for every important account
  • Password manager or secure credential management
  • Passkeys enabled where available
  • MFA enabled
  • Primary email strongly protected
  • Recovery options secured
  • Old sessions reviewed
  • Unknown devices removed

Hosting

  • WHM/cPanel MFA enabled
  • Unique reseller/hosting password
  • SSH keys protected
  • SFTP/SSH preferred over FTP
  • API keys protected
  • Hosting login activity monitored
  • Unused accounts removed
  • Unused FTP accounts removed
  • Backups available and tested

Development

  • No passwords inside source code
  • No API keys in Git repositories
  • .env and secret files excluded where appropriate
  • Production credentials separated from development credentials
  • Dependencies kept updated
  • Unused plugins/themes/scripts removed
  • Git repositories reviewed before publishing

Email

  • MFA/passkey enabled
  • Suspicious emails independently verified
  • Unexpected attachments avoided
  • Links checked before logging in
  • Security alerts monitored
  • Unknown forwarding rules investigated

The Most Important Lesson

You don’t need to become paranoid about every click on the internet.

But you should become deliberate about what you trust.

The modern attack isn’t always:

“A hacker broke through my server.”

Very often it is:

“Someone stole the administrator’s identity.”

The attacker may obtain that identity through phishing, credential reuse, malware, browser data theft, malicious software, leaked credentials, stolen session cookies, or compromised devices.

For website developers, hosting customers, system administrators, and resellers, the computer sitting on your desk can therefore be one of the most important security boundaries in your entire infrastructure.

Protect the computer. Protect the identity. Protect the accounts. Then protect the server.

Security is not a single product, browser setting, or antivirus application.

It is a habit.

And the best security habit is simple:

Stop assuming that something is safe until you have a reason to trust it.

13 May

Temporary Restriction of cPanel & WHM Access Due to Critical Security Vulnerabilities

We have been alerted to several critical cPanel vulnerabilities that may allow elevated access to affected hosting infrastructure:

  • CVE-2026-29205
  • CVE-2026-29206
  • CVE-2026-32991
  • CVE-2026-32992
  • CVE-2026-32993

As a precautionary security measure, we have temporarily restricted access to the following services:

  • cPanel
  • WHM

We are currently awaiting official security patches from cPanel and expect further updates within the next 24 hours. Once the patches are released, applied, and all security checks are completed, access restrictions will be lifted accordingly.

If you require any urgent account or service-related changes during this period, please contact our support team by opening a support ticket.

We appreciate your patience and understanding as we work to ensure the continued security and stability of all services.

30 Mar

Default browser protocol for Chrome – HTTPS

Chrome is the most popular browser for its simplicity, fast and secure browsing experience. In a recent blog post, We came to learn that chrome will make HTTPS as default protocol for website having SSL enabled. This new feature will be applied with the upcoming version 90. As per blog post, this changes will improve privacy and website loading speed along with security for those website which supports HTTPS.

For example, users usually type example.com or www.example.com and browser takes to http://example.com or http://www.example.com as http:// is set as default protocol. With the latest chrome update, default protocol will be set to https and it will work as https://example.com or https://www.example.com

For sites that doesn’t have SSL certificate installed yet or has some kind of certificate related error, chrome will automatically fall back to http protocol.

TetraHost offers hosting service including SSL certificate provided by Let’s Encrypt SSL and client can install certificate for their domains by login to cPanel >> Lets Encrypt SSL. Following blog post have the instruction on installing SSL: https://www.tetrahostbd.com/blog/ssl-googles-not-secure-warning-and-your-website/

HTTPS protects website users by encrypting traffic sent over the user machine to Web Server. This process provide extra layer of security to users data they submit while browsing website.

Chrome is set to release the update by 13th April, 2021.

We highly recommend our users to enable/install SSL certificate. If you want our assistance with installing/enabling SSL certificate to your website, please submit a support ticket to support [at] tetrahostbd.com with the domain name.

30 Jul

WordPress Security: Tips To Secure A WordPress Website

WordPress, the most popular Content Management System(CMS) in the market, which powers almost 42.4% of all the websites on the Internet. This popularity also brings some problems to your room making it the most targeted CMS by hacker to get benefited using a site. If you are serious about your website, then you need to pay proper attention to your site and WordPress security best practices. Keeping your WordPress site secure takes a little effort but should be top of the agenda for anyone serious about their website.

Hacker uses two approaches to hack WordPress websites. They target individual sites as well as large clusters. Nothing in this world is hack-proof but what We can try is make this as difficult as possible, so they go elsewhere.

In this tutorial, We will share our Best Tips to keep your WordPress website secure.

1. Update your WordPress

WordPress is an open source software which is regularly maintained and updated. By default, WordPress automatically installs minor updates. For major releases, you need to manually initiate the update. Not updating your themes and plugins can mean trouble. In most cases, WordPress-powered sites are compromised because their core software, files, themes, and plugins are outdated making them traceable. WordPress also comes with thousands of plugins and themes that you can install on your website. These plugins and themes are maintained by third-party developers which regularly release updates as well. Every WordPress site administrator should regularly check for update and keep WordPress including plugin and theme files up-to-date.

How to configure automatic updates

You can configure automatic updates as well. To auto-upgrade WordPress core, insert this code into your wp-config.php file:

define( 'WP_AUTO_UPDATE_CORE', true );

For plugins, use:

add_filter( 'auto_update_plugin', '__return_true' );

For themes, use:

add_filter( 'auto_update_theme', '__return_true' );

2. Install a WordPress Security Plugin

Many users find it easier to rely on a one-stop security solution. If that is the case with you, one of the following WordPress security plugins might be suitable:

iThemes Security – available in both a free and premium version, iThemes provides over 30 different ways to improve the security of your website.

WordFence – is another security plugin that offers both a free and premium version. With just over 11 million downloads, WordFence has a strong user base who depend on this plugin for their security needs.

Sucuri – While Sucuri maintains a free plugin in the WordPress repository, they also provide a more comprehensive service that includes: malware and blacklist scanning, DDoS protection, malware cleanup, firewall protection and more. One of the great features of the Sucuri service is that it includes cleanup in the event that you site is compromised.

3. Install SSL Certificate

SSL (Secure Sockets Layer) is a protocol which encrypts data transfer between your website and users browser. This encryption makes it harder for someone to sniff around and steal information. For instance, our hosting service comes with free SSL on all plans which customer can avail from cPanel >> Let’s Encrypt SSL.

4. Use a Strong Password

The most common WordPress hacking attempts use stolen passwords. You can make that difficult by using stronger passwords that are unique for your website. Not just for WordPress admin account, but also for database user, WordPress hosting account.

5. Disable File Editing

If a user has admin access to your WordPress dashboard they can edit any files that are part of your WordPress installation. This includes all plugins and themes. It can be accessed by going to Appearance >> Editor. Another way you can find the plugin editor is by going under Plugins >> Editor. If you disallow file editing, no one will be able to modify any of the files – even if a hacker obtains admin access to your WordPress dashboard.

To make this work, add the following to the wp-config.php file (at the very end):

define('DISALLOW_FILE_EDIT', true);

6. Change your WP-login URL

By default, the URL We use to log into our dashboard is either wp-login.php or wp-admin, added after your site’s main URL. For instance, YOURSITE.com/wp-login.php and guess what, those two are also the most accessed URLs by hackers who want to get into your database. If you change that URL, you reduce the chances of finding yourself in trouble. Guessing a custom login URL is way harder for hackers.

The iThemes Security plugin does this trick. For instance, your login URL can turn into something like YOURSITE.com/my_site.

7. Securing wp-includes Folder

The wp-includes folder contains only the files that are strictly necessary to run the core version of WordPress, one without any plugins or themes. Remember, the default theme still resides in the wp-content/theme directory. Thus, no visitor (including you) should require access to content of the wp-include folder. You can disable access using this following code snippet by updating your default .htaccess file:

# Block the include-only files.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^wp-admin/includes/ - [F,L]
RewriteRule !^wp-includes/ - [S=3]
RewriteRule ^wp-includes/[^/]+\.php$ - [F,L]
RewriteRule ^wp-includes/js/tinymce/langs/.+\.php - [F,L]
RewriteRule ^wp-includes/theme-compat/ - [F,L]
</IfModule>

8. Hide wp-config.php and .htaccess files

While this is an advanced process for improving your site’s security, if you’re serious about your security it’s a good practice to hide your site’s .htaccess and wp-config.php files to prevent hackers from accessing them. We strongly recommend this to be done by an experience developer because a slight mistake can take down your site. You should start by taking backup of the files as well. To hide the files, there are two things you need to do:

Go to your .htaccess file and add the following code,

<Files wp-config.php>
order allow,deny
deny from all
</Files>

<Files .htaccess>
order allow,deny
deny from all
</Files>

Another security measure that you can take is to restrict wp-config.php file permission. Set the file permissions to 600 so that only true owners can edit the wp-config file. To change the file permission of wp-config, select the file from cPanel >> File Manager and then choose the option ‘Permission’.

9. Disable PHP File Execution in Certain WordPress Directories

Another way to harden your WordPress security is by disabling PHP file execution in directories where it’s not needed such as /wp-content/uploads/.

You can do this by opening a text editor like Notepad and paste this code:

<Files *.php>
deny from all
</Files>

Next, you need to save this file as .htaccess and upload it to /wp-content/uploads/ folders on your website using File Manager or FTP Client.

10. Change Security Keys

It is recommended that you change the WordPress Secuity key periodically so that if someone/something got login credentials, resetting the security keys will log them out immediately. You can generate a new set of security keys and place them in the ‘wp-config.php’ file and here is the URL where you can generate new set of keys. It’ll help secure your WordPress site. Its generate new keys every time someone browse the URL.

11. Choose a Good Hosting Company

You should find/choose a good hosting provider who has up-to-date security system deployed on their servers. You might look for Cloudlinux, Litespeed, Imunify360 Scanner etc. A company with good support and daily backup system will help you to run your WordPress site properly.

12. Don’t Use Nulled Themes

We have seen, people are using nulled theme for their website which is one of the main reason for security breach of a site. You should try to get the premium theme by paying the charges to actual seller. Nulled themes contain hidden malicious codes, which could destroy your website and database or log your admin credentials very easily.

13. Monitor your site – to find any unusual activity.

14. Back up your site regularly – in-case of emergency.

15. Use Latest PHP Version – PHP is used for backend coding and using latest version of PHP will enhance the site security parameter.

16. Use Clever Usernames and Passwords – do not go with the common ones, think and use harder.

17. Captcha Protection – Protecting your site with google captcha protection.

That’s all, we hope this article helped you learn the top WordPress security best practices as well as discover the best WordPress security plugins for your website.

23 Feb

WordPress Update Released v5.1, Update Your WordPress NOW!


WordPress has released an update on Thursday, 21 February, 2019. We urges all our client to update their WordPress developed site to latest released version.

In order to update, please login to your WordPress Admin Panel >> Dashboard >> Updates >> here you should find with an option to update WordPress to latest Version or you can use “Re-install Now” button to have latest version installed for your account. Sites that support automatic background updates are already beginning to update automatically.

More information on the latest update is available on the following URLs:

Version 5.1

WordPress 5.1 Release Candidate

If you face any trouble updating your WordPress to latest version feel free to contact us. If you want us to update your WordPress, please create an support ticket with your WordPress Admin login details and We will update them for you.

Thank you for choosing TetraHost

Support Desk, TetraHost
M: +880 191 3377417 | E: support@tetrahostbd.com
https://www.tetrahostbd.com

13 Dec

WordPress Update Released v5.0, Update Your WordPress NOW!

WordPress has released an update on 6th December, 2018. We urges all our client to update their WordPress developed site to latest released version.

In order to update, please login to your WordPress Admin Panel >> Dashboard >> Updates >> here you should find with an option to update WordPress to latest Version or you can use “Re-install Now” button to have latest version installed for your account. Sites that support automatic background updates are already beginning to update automatically.

More information on the latest update is available on the following URLs:

Version 5.0

WordPress 5.0.1 Security Release

If you face any trouble updating your WordPress to latest version feel free to contact us. If you want us to update your WordPress, please create an support ticket with your WordPress Admin login details and We will update them for you.

Thank you for choosing TetraHost

Support Desk, TetraHost
M: +880 191 3377417 | E: support@tetrahostbd.com
https://www.tetrahostbd.com

04 Aug

WordPress Update Released v4.9.8, Update Your WordPress!

WordPress has released an update on 2nd August, 2018. We urges all our WordPress client to update their WordPress to latest released version.

In order to update, please login to your WordPress Admin Panel >> Dashboard >> Updates >> here you should find with an option to update WordPress to latest Version or you can use “Re-install Now” button to have latest version installed for your account. Sites that support automatic background updates are already beginning to update automatically.

More information on the latest update is available on the following URLs:
https://codex.wordpress.org/Version_4.9.8
https://wordpress.org/news/2018/08/wordpress-4-9-8-maintenance-release/

If you face any trouble updating your WordPress to latest version feel free to contact us. If you want us to update your WordPress, please create an support ticket with your WordPress Admin login details and We will update them for you.

Thank you for choosing TetraHost

Support Desk, TetraHost
M: +880 191 3377417 | E: support@tetrahostbd.com
https://www.tetrahostbd.com

07 Jul

WordPress Update Released v4.9.7, Update Your WordPress!

WordPress has released an update on 5th July, 2018. We urges all our WordPress client to update their WordPress to latest released version.

In order to update, please login to your WordPress Admin Panel >> Dashboard >> Updates >> here you should find with an option to update WordPress to latest Version or you can use “Re-install Now” button to have latest version installed for your account. Sites that support automatic background updates are already beginning to update automatically.

More information on the latest update is available on the following URLs:
https://codex.wordpress.org/Version_4.9.7
https://wordpress.org/news/2018/07/wordpress-4-9-7-security-and-maintenance-release/

If you face any trouble updating your WordPress to latest version feel free to contact us. If you want us to update your WordPress, please create an support ticket with your WordPress Admin login details and We will update them for you.

Thank you for choosing TetraHost

Support Desk, TetraHost
M: +880 191 3377417 | E: support@tetrahostbd.com
https://www.tetrahostbd.com

04 Jul

SSL, Google’s ‘Not Secure’ warning and your website

Starting from July, 2018 Chrome Browser will mark a website without SSL certificate or HTTPS as “NOT SECURE“. This means that when potential customers visit a website without the HTTPS in the address bar, they will see that their website is not secure. So what can you do? You can simply install SSL certificate and have your site secured.

We at TetraHost offers free SSL certificate with our hosting service and to install SSL for your website, simply login to your cPanel >> Security >> Let’s Encrypt SSL >> here you will find option to install SSL certificate.

For assistance, please check following article:

Announcement: Free Let’s Encrypt SSL With Hosting

More about the Google Announcement:
https://security.googleblog.com/2018/02/a-secure-web-is-here-to-stay.html

If you are having any issue with SSL install or want us to install the certificates for you, please submit a ticket to support [at] tetrahostbd.com