An Introduction to WordPress Security

Recent statistics show that over 28% of website administrators across the web use WordPress. With its popularity comes a price - it is often targeted by malicious hackers and spammers, who seek to leverage insecure websites to their advantage. WordPress security is about risk reduction, not risk elimination. There is always risk, and security is a continuous process requiring frequent assessment of these attack vectors.

This guide is intended to educate WordPress administrators on basic security techniques and actionable steps that will help to improve your security posture and reduce the risk of a compromise.

In This Guide

x
1
Software Vulnerabilities

The WordPress security team works diligently to provide important security updates and vulnerability patches. However, the use of third-party plugins and themes exposes users to additional security threats.

By regularly installing the latest versions of core WordPress files and extensions, you can ensure that your website possesses all of the prevailing security patches.

1.1 - Auditing Plugins & Themes

Plugins and themes can become deprecated, obsolete, or include bugs that pose serious security risks to your website.

To protect your WordPress installation, we recommend that you audit your plugins and themes on a regular basis.

Assess Your Plugin Security

You can assess the security of WordPress plugins and themes by reviewing a couple of important indicators:

  • Does the plugin or theme have a large install base?
  • Are there a lot of user reviews, and is the average rating high?
  • Are the developers actively supporting their plugin and pushing frequent updates or security patches?
  • Does the vendor list terms of service or a privacy policy?
  • Does the vendor include a physical contact address in the ToS or from a contact page?

Carefully read the Terms of Service - it may include unwanted extras that the authors didn’t advertise on their homepage. If the plugin or theme doesn’t meet any of these requirements or has recently changed owners before the latest update, you may want to look for a more secure solution.

Note

Sometimes bad actors will purchase a plugin to add malicious or unwanted functionality. Exercise caution when installing plugins that have recently changed owners before the latest update.

Remove Unused Plugins & Themes

When it comes to unused plugins, less is more. Storing unwanted plugins in your WordPress installation increases the chance of a compromise, even if they are disabled and not actively being used in your installation.

Not using that WordPress plugin? Remove it from your installation.

1.2 - Updates

Updating WordPress

When a new update is available, you’ll be notified in the Dashboard > Updates menu.

You should always apply updates as soon as possible. Logging into your site on a frequent basis will ensure that you’re aware of updates as they are released. If you cannot update your site for any reason, consider using a website firewall to virtually patch the problem and minimize the risk.

To set up automatic updates in WordPress:

  1. Log into your server via SFTP or SSH.
  2. Locate the wp-config.php file, normally located in the document root folder public_html.
  3. Add the following snippet to the file: define( 'WP_AUTO_UPDATE_CORE', true );

Note

Some updates can break your website, so be sure to verify your site is fully operational after an update is applied.

Advanced users can refer to the WordPress Codex’s guide to updates using subversion.

To manually apply updates in WordPress:

  1. Log into your server via SFTP or SSH.
  2. Manually remove the wp-admin and wp-includes directories
  3. Replace the core files from the root directory, /wp-admin/ and /wp-includes/ using copies from the official WordPress repository.
  4. Log into WordPress as an admin - you may see a prompt to update the database.
  5. Click on Update WordPress Database.
  6. Once the database has updated, navigate to Dashboard > Updates.
  7. Apply any missing updates.
  8. Open your website to verify it is operational.

Caution

    Before updating your website to the latest version of WordPress, we recommend taking the following precautionary steps:

    1. Back up your website, especially any customized content.
    2. Review the release notes to identify if changes will have any negative impacts to your website.
    3. Test the update on a development site to verify that your themes, plugins and other extensions are compatible with the latest version.

Database Update Required

Database Update Required

Updating Plugins

WordPress may not be able to update the extension if it has been downloaded from a third party website. If this is the case, you may need to manually update the plugin using FTP or use an included updater.

To manually apply updates for plugins in WordPress:

  1. Verify compatibility between the plugin and your current WordPress version.
  2. Download the latest version of the plugin from an official source and save it on your local machine.
  3. Check for special update instructions from the plugin developer or vendor. If none exist, proceed with steps 4-9.
  4. Log into your server via SFTP or SSH.
  5. Navigate to /wp-content/plugins/ and download this folder to your computer to serve as a backup.
  6. Locate the directory of the plugin you want to update and delete it from FTP.
  7. Upload the latest version to the same location.
  8. Log into WordPress as an admin and click Dashboard > Plugins.
  9. Locate the plugin you just updated from the list and click Activate.

Updating Themes

If you are not using a child/parent theme for customizations, you’ll need to copy your modifications to a new theme folder, then update it to FTP.

To manually update themes in WordPress:

  1. Connect to your website using FTP and go to /wp-content/themes/, then download the current theme folder to your computer.
  2. Visit the theme’s website to download the latest version of the theme and save it on your local machine - you will now have two copies of the theme folder.
  3. Copy any customizations and code changes from your old theme and add them to the new theme files.
  4. Upload the newest version of the theme directory, complete with customizations to WordPress using FTP.

Note

If you are using a customized child theme that is inheriting functionality from a parent theme, then updating your theme is fairly straight-forward. Simply overwrite your copy of the parent theme with the latest version from the official source. Your customizations will remain intact in the child theme.

2
Access Control

Attackers frequently exploit weak user credentials to obtain access to WordPress websites.

By utilizing strong, unique passwords on your website, restricting the privileges available to users through assigned roles, enabling two-step or multi-factor authentication and limiting user sessions, you can reduce the risk of a website compromise by a bad actor.

2.1 - User Accounts

Admin

A large majority of attacks target the wp-admin, wp-login.php, and xmlrpc.php access points by using a combination of common usernames and passwords.

By using a unique username and removing the default admin account in your WordPress installation, you make it much more difficult for attackers to guess (brute force) their way into your website.

Replace the default “admin” account:

  1. Log into WordPress as an administrator.
  2. From the Dashboard, select Users > Add New.
  3. Using a new email address, create a new account and set the Role to Administrator.
  4. Save the new user, then log out and log back in with your new Administrator account.
  5. From the Dashboard, select Users > All Users.
  6. Hover your mouse over the username admin, then select Delete.
  7. Attribute old posts to the new Administrator account.

Tip

Create a nickname that’s different from your existing username and set it as your public display name. This will make it more difficult for attackers to brute force your login credentials.

Roles & the Principle of Least Privilege

The principle of least privilege is composed of two very simple steps:

  • Use the minimal set of privileges on a system in order to perform an action.
  • Grant privileges only for the exact duration that an action is necessary.

With this concept in mind, WordPress includes built-in roles for Administrators, Authors, Editors, Contributors and Subscribers. These roles specify what can and cannot be accomplished by a user.

Follow these access control recommendations to reduce your security risks:

  • Create new user accounts at the lowest level of permission.
  • Grant temporary permissions and revoke access when they are no longer needed.
  • Delete accounts that are no longer being used.
  • Ensure that the default user role is set to Subscriber:
    1. Log into WordPress as an Administrator.
    2. Verify that your Subscriber permissions include only the ability to log in and update a profile
    3. From the Dashboard, select Settings > General.
    4. Set the New User Default Role to Subscriber.

2.2 - Passwords

Password lists are often used by attackers to brute force WordPress websites. This is why you should always use strong, unique passwords for all of your accounts.

Strong passwords should meet the following standards:

  • At least 1 uppercase character
  • At least 1 lowercase character
  • At least 1 digit
  • At least 1 special character
  • At least 10 characters, with no more than two identical characters in a row

Note

Using a password generator to generate a randomized string of letters and numbers is one of the simplest ways to create a secure password.

Password Generation Options

Password Generation Options

2FA / MFA

Two-factor authentication provides a second level of protection for your account. This feature requires a user to approve a login via an app, and protects your account in the event that someone is able to guess your password.

To add 2FA to WordPress using Google Authenticator:

  1. Download and install Google Authenticator for your iPhone or Android.
  2. Install and activate a 2FA plugin for WordPress like miniOrange’s 2FA.
  3. Select miniOrange 2-Factor from the left menu and follow the instructions
  4. Once you have obtained your QR code, open Google Authenticator and click on the Add button at the bottom-right hand side of the application.
  5. Scan the QR code displayed by the plugin using your phone’s camera.
  6. Verify the code on the plugin page.

Sucuri’s Website Security Platform includes a feature that helps you easily password protect or implement 2FA on any page of your website.

To add 2FA to any page on your website using Sucuri:

  1. Download and install Google Authenticator for your iPhone or Android.
  2. Log into the Sucuri Dashboard and navigate to Website Firewall.
  3. Click on the website you would like to protect, then select Access Control from the top navigation.
  4. Enter the page name that you would like to protect (ie. /wp-login.php), then select 2FA with Google Auth from the drop-down menu.
  5. Click Protect Page and scan the QR code with your mobile device using Google Authenticator.

Add 2FA with Sucuri

Add 2FA from the Sucuri dashboard

2.3 - Limit Login Attempts

WordPress allows users to attempt a login unlimited times by default, but this leaves your site vulnerable to brute force attacks as hackers attempt different password combinations.

You can add an extra layer of security by limiting the number of login attempts against an account through a plugin, or by using a Web Application Firewall (WAF).

Some popular plugins that provide you with this feature include Limit Login Attempts, WP Limit Login Attempts and Loginizer.

2.4 - Pre-Login Captchas

The acronym stands for Completely Automated Public Turing Test To Tell Computers and Humans Apart. This feature is extremely useful at stopping automated bots from accessing your WordPress dashboard, as well as submitting unwanted spam through forms.

Popular plugins that add a CAPTCHA to your WordPress login page include Captcha and Really Simple Captcha.

Pre-Login Captchas

Pre-Login Captchas

2.5 - Restrict Access to Authenticated URLs

Limiting the access to your login page to only authorized IP’s will prevent unauthorized entries.

There are plugins available that can do this. If you are using a cloud-based WAF like the Sucuri Firewall, you can restrict access to these URL’s via your dashboard without having to mess around with .htaccess files.

Whitelist IP Addresses

Whitelist IP Addresses from the Sucuri dashboard
3
Proactive WordPress Security

In the field of Information Security (InfoSec) we like to use the phrase defense in depth.

To appreciate this ideology, you have to subscribe to a very simple principle: There is no 100% complete solution capable of protecting any environment.

In this section, we’ve listed a number of solutions you can employ on your website to provide an effective defense in depth strategy. By layering these defensive controls, you’ll be able to identify and mitigate attacks against your website.

3.1 - Security Plugins

If you go to the official WordPress repository and do a quick search for Security, you will find over 4,298 plugins with distinct categorizations and feature sets.

We’ll break down the categories and explain their importance so you can find the right solutions for your needs.

WordPress Security Plugin – Prevention Category

These plugins look to provide some level of prevention, otherwise known as a perimeter defense for your website. Their objective is to stop hacks from happening by filtering incoming traffic.

Prevention plugins are often limited to working at the application layer, meaning the attack has to hit the WordPress application for them to respond. Attacks against server software cannot be prevented with security plugins, which is why we recommend considering a cloud-based WAF instead.

WordPress Security Plugin – Detection Category

Protection is great for known issues, but not so great for the unknown. Being able to detect anything that gets past your perimeter defense is extremely valuable, which is where detection comes into play.

These plugins will attempt to identify intruders through File Integrity Checks, scanning for indicators of compromise, or a combination of the two mechanisms.

The effectiveness of these plugins is strictly determined by the order in which they are installed. For instance, if the plugin is based on integrity checks, then it needs to be installed on a fresh, known-good environment so that it can create a baseline to check from.

Some plugins may compare known third-party themes and plugins to their own repository in order to work with websites that have already been compromised, but these are not compatible with customized or little-known files.

Tip

Detection plugins are important in identifying if something has gone wrong on your website. These tools ensure that you’re informed when a security incident occurs.

WordPress Security Plugin – Auditing Category

Contrary to popular belief, security is not a set it and forget it undertaking. You have to invest time into the process and get acclimated with what is going on, who is logging in, what is changing, and when the changes are being made.

Auditing plugins can help you answer the questions above by offering basic administration features that help you identify, thwart, or respond to a compromise.

WordPress Security Plugin – Utility Category

This is perhaps the most diverse bucket of the entire WordPress Security Plugin ecosystem. Some plugins are those we consider to be the Swiss Army knives of the security landscape. These utility plugins have a much smaller set of functionality.

These plugins can be exhaustive in their security configuration options. They have every possible configuration you could or might ever want to employ, and are best suited for users who like to tinker or want the ability to configure specific options to meet their needs. For example, some security plugins simply disable XML-RPC, or move your login page.

We also reserve this category for toolsets like backups or maintenance plugins that address specific security functions.

3.2 - Hosting

Website hosting security has matured in recent years, and it’s a complex topic.

Most hosts provide the security you require at various levels in the stack, but not for the website itself. There are a number of hosting providers that provide security for an additional fee but, unless you’ve purchased a security product from them, it’s unlikely that they’ll resolve a compromise for you.

There are four main hosting environments that can be used for your WordPress installation:

  • Shared Hosting Environments
  • Virtual Private Server (VPS) Environments
  • Managed Hosting Environments
  • Dedicated Servers

In theory, the environments that remove the most dependency from the user will offer the most security. If you have the time and skill to secure your own environment, then you have more options but also more responsibility.

In reality however, the type of hosting environment you choose should be dictated by your needs and expertise:

  • If you’re someone that has little understanding of how websites work, then it’s in your best interest to go with a managed environment.
  • If you’re an organization with your own network operations center (NOC), information security operations center (SOC), or dedicated sysadmins, then a VPS or dedicated server provides better isolation of your environment (assuming it’s properly configured).

You can also initiate a conversation with your hosting provider to identify what their stance is on security. Some key points should be addressed:

  • What security precautions are they taking to protect your website (not just their server)?
  • What actions will they take if they identify malware on one of your websites?
  • How often do they look for malware?
  • Do they offer incident response services?
  • Will you need to reach out to a third-party if your site is hacked?

Note

Use carefully isolated FTP and user accounts on Shared Server environments to prevent cross-site contamination.

SFTP/SSH Connections

Secure file transfer to and from your server is an important facet of website security in your hosting environment. Encryption ensures that any data sent is protected from prying eyes who may be sniffing your network traffic.

We recommend using one of the following methods to connect to your server:

SSH: Secure Socket Shell is a secure network protocol and the most common way of safely administering remote servers. With Secure Socket Shell, any kind of authentication, including password authentication and file transfers, is completely encrypted.

SFTP: SSH File Transfer Protocol is an extension of SSH and allows authentication over a secure channel. If you are using FileZilla or some other FTP client, you can often select SFTP instead - the default port for SFTP in most FTP services is 22.

3.3 - Backups

Maintaining website backups should be one of the most important recurring tasks for a website administrator.

A good set of backups can save your website when absolutely everything else has gone wrong. If a malicious attacker decides they want to wipe all your site files, or corrupts your site files with their buggy scripts, the damage can be undone by restoring your site from your backups.

There are four key requirements to employing a successful backup solution:

  1. Offsite Location: Your backups should be stored offsite and not on the same server as your website. Backups stored on your web server pose a serious security risk because they often contain old unpatched software with vulnerabilities, and due to their publicly-accessible location, anyone can exploit them to attack your live website. Off-site backups also help protect against hardware failure. If your web server hard drive fails, you can easily lose all your data - the live site, and the backups.
  2. Automatic: Backup systems should be completely automated to ensure that backups are made on a regular basis. Humans are lazy and forgetful, so you can mitigate user error through automation. If a manual solution is your only option, then make sure you schedule a time to perform the backups regularly.
  3. Redundant: Schofield’s Second Law of Computing states that data doesn’t exist unless there are at least two copies of it. This means that your backup strategy has to include redundancy, or backups of your backups.
  4. Tested & True: Make sure that the restore process actually works. Start with an empty web directory and then make sure you can use those backups to get all your data back and the website back online with a test domain using nothing but the backup file.

3.4 - Detection

There are a number of tools you can use to help identify when something has gone wrong on your website. To help you respond quickly to a security breach, employ a tool that includes the following services.

Integrity Monitoring

Integrity checks are an important aspect of auditing your WordPress installation and can give you an early warning of an intrusion on your website.

File Integrity Monitoring tools are normally installed on a server where they create a baseline cryptographic checksum of the critical files and registry entries. If a file or record is modified in any way, you’ll receive a notification of the changes.

You can install the free Sucuri Scanner plugin for WordPress to use our core file integrity monitoring system.

Auditing / Alerts

Auditing tools give you visibility into user activity on the website.

As the administrator of your website you should be asking questions like:

  1. Who is logging in?
  2. Should they be logging in?
  3. Why are they changing that post?
  4. Why are they logging in when they should be sleeping?
  5. Who installed that plugin?

We cannot stress enough the importance of logging activity. Use a tool that logs and alerts you of any actions taken on your website, including:

  1. User authentication success and failures
  2. User creation/removal
  3. File uploads
  4. Post and page creation
  5. Post and page publishing
  6. Widget modification/activation
  7. Plugin installation
  8. Theme modifications
  9. Settings modifications

WordPress Integrity Monitoring Alerts

Integrity alerts with the Sucuri Plugin

Response and Recovery Plan

Response and recovery isn’t just about responding to a compromise or incident; it’s about analyzing the impacts of an attack to understand what happened, and implementing controls to prevent it from happening again.

Secure & Clean WordPress

4
Hardening Recommendations

Caution: The following recommendations are for server administrators with knowledge of how these files work. If you do not feel comfortable with these suggestions, we recommend using a website firewall that includes virtual hardening instead.

4.1 - Basic .htaccess Configurations

The .htaccess file is what most vendors will modify when they say they are hardening your environment.

This critical configuration file is specific for web servers running on Apache. If you’re running your WordPress instance on a LAMP stack using Apache, then we recommend hardening your site by updating your .htaccess file with the following rules.

Note

Some of the rules below are dependant on the version of Apache you are running. In those cases, we have included instructions for both versions 2.2 and 2.4 of Apache Server.

/.HTACCESS

Rule Explanation

  1. # BEGIN WordPress
  2. # Rewrite rule
  3. <IfModule mod_rewrite.c>
  4. RewriteEngine On
  5. RewriteBase /
  6. RewriteRule ^index\.php$ - [L]
  7. RewriteCond %{REQUEST_FILENAME} !-f
  8. RewriteCond %{REQUEST_FILENAME} !-d
  9. RewriteRule . /index.php [L]
  10. </IfModule>
  11. # END WordPress

Rewrite Rule:

This rule is generated by WordPress if it has write access to your server, most notably to fix issues with pretty permalinks.

If it isn’t at the top of your file, place at the the top of your .htaccess file. Any other rules should go after the # BEGIN WordPress and # END WordPress statements.

  1. # Block IPs for login Apache 2.2
  2. <files /wp-login.php>
  3. order deny,allow
  4. allow from MYIP
  5. allow from MYIP2
  6. deny from all
  7. </files>
  8. # Block IPS for login Apache 2.4
  9. <Files "wp-login.php">
  10. Require all denied
  11. </Files>

Restrict Logins to IP Range

This rule restricts access to wp-login.php to an IP, protecting you from unauthorized login attempts in other locations. Even if you do not have a static IP, you can still restrict logins to your ISP common range.

Use this same entry on other authenticated URLs that you’d like to restrict, including /wp-admin. If you are using a dynamic IP, you can refer to our instructions: How to lock down WordPress Admin Panel with a dynamic IP

  1. # Protect wp-config Apache 2.2
  2. <files wp-config.php>
  3. order allow,deny
  4. deny from all
  5. </files>
  6. #Protect wp-config Apache 2.4
  7. <Files "wp-config.php">
  8. Require all denied
  9. Require ip 1.1.1.1
  10. </Files>

Protect wp-config.php

This rule restricts visitors from accessing your wp-config.php file, which contains sensitive information about the database, including name, host, username and password. This file is also used to define advanced settings, security keys and developer options.

  1. # Prevent directory browsing
  2. Options All -Indexes

Prevent Directory Browsing

This rule prevents attackers from viewing the folder contents of your website, restricting the information they have to exploit your website.

  1. # Prevent image hotlinking
  2. RewriteEngine on
  3. RewriteCond %{HTTP_REFERER} !^$
  4. RewriteCond %{HTTP_REFERER} \
  5. !^http://(www\.)example.com/.*$ [NC]
  6. RewriteRule \.(gif|jpg|jpeg|bmp|png)$ - [NC,F,L]

Prevent Image Hotlinking

This rule prevents other websites from using images hosted on your website. While hotlinking won’t get your site hacked, it can result in a damaging exploitation of your server resources. Change example.com to your website.

  1. # Protect htaccess Apache 2.2
  2. <files ~ "^.*\.([Hh][Tt][Aa])">
  3. order allow, deny
  4. deny from all
  5. satisfy all
  6. </files>
  7. # Protect htaccess Apache 2.4
  8. <FilesMatch "^.*\.([Hh][Tt][Aa])">
  9. Require all denied
  10. </FilesMatch>

Protect .htaccess

This rule prevents attackers from accessing any files that start with “hta” - this ensures that .htaccess files are protected in all of the directories of your server.

  1. # Block Includes
  2. <IfModule mod_rewrite.c>
  3. RewriteEngine On
  4. RewriteBase /
  5. RewriteRule ^wp-admin/includes/ - [F,L]
  6. RewriteRule !^wp-includes/ - [S=3]
  7. RewriteRule ^wp-includes/[^/]+\.php$ - [F,L]
  8. RewriteRule ^wp-includes/js/tinymce/langs/.+\.php \
  9. - [F,L]
  10. RewriteRule ^wp-includes/theme-compat/ - [F,L]
  11. </IfModule>

Block Includes

This rule blocks hackers from inserting malicious files into any of the four primary folders used for includes:

  • /wp-admin/includes/
  • /wp-includes
  • /wp-includes/js/tinymce/langs/
  • /wp-includes/theme-compat/

/WP-INCLUDES/.HTACCESS
/WP-CONTENT/UPLOADS/.HTACCESS

Rule Explanation

  1. # Backdoor Protection Apache 2.2
  2. <Files *.php>
  3. deny from all
  4. </Files>
  5. # Backdoor Protection Apache 2.4
  6. <FilesMatch ".+\.php$">
  7. Require all denied
  8. </FilesMatch>

Prevent PHP Backdoors

This rule prevents hackers from placing PHP backdoors in the /wp-includes/ and /wp-content/uploads/ folders, two popular locations for malicious file uploads.

4.2 - Application Configurations

WP-Config

The wp-config.php file is a very important configuration file containing sensitive information about your WordPress site, including database connections.

If the wp-config.php file does not exist in the root folder, WordPress will automatically look for this file in the folder above the root directory. Moving this file out of the root folder prevents wp-config.php from being accessible from the Internet.

Salts & Keys

The wp-config file includes a section dedicated to authentication salts and keys. These salts and keys improve the security of cookies and passwords that are in transit between your browser and the web server.

You can set up your keys by including or editing these lines after the other define statements in your wp-config.php file:

define('AUTH_KEY', 'include salt here');
define('SECURE_AUTH_KEY', 'include salt here');
define('LOGGED_IN_KEY', 'include salt here');
define('NONCE_KEY', 'include salt here');

You can easily generate your salts by navigating to the wordpress.org salt generator or using the reset salts + keys option in our WordPress Plugin.

Important

    If you suspect that the secret keys have been compromised, regenerate them as soon as possible. All users will need to re-authenticate.

Disable File Editing

By default, file changes can be made through Appearance > Editor from the WordPress dashboard.

You can increase your security by disabling file editing from the dashboard. This prevents an attacker from changing your files through the backend or wp-admin. You will still be able to make changes via SFTP/SSH.

To disable file editing from the dashboard, include the following two lines of code at the end of your wp-config.php file:

## Disable Editing in Dashboard
define('DISALLOW_FILE_EDIT', true);

Note

    Some plugins disable file editing as part of their hardening process, or as an extra setting.

5
Security Services

There are a number of professional services that take care of your website security needs for you. Not all services are the same – some charge more to fix complex hacks, and others provide different tiered feature sets. You should choose the one that best fits your needs.

If your host provides security services, take some time to research exactly what features they include. They’re normally happy to advise you on ways you can complement their baseline feature sets with additional services.

The benefit to employing a cloud-based security service like Sucuri is that it provides complete end-to-end website security. This means protection, detection, and response services are included with an all-in-one platform and no hidden fees.

Our high availability Globally Distributed Anycast Network (GDAN) ensures that websites can efficiently service their global audiences, while mitigating DDoS attacks.

6
Implementing SSL & HTTPS

SSL has become increasingly important in the past couple of years, not only for securely transmitting information to and from your website, but also to increase visibility and lower the chances of being penalized.

SSL allows a website to be accessed over HTTPS, which encrypts the data sent between visitors and web servers. Since 2014, SSL has been a ranking signal for SEO and Google has now started to flag non-HTTPS websites that transmit password and credit card data.

We’ve put together a free guide on how to implement SSL on your website. If you need assistance, you can reach out to us and learn how we can help you activate SSL/HTTPS via our cloud-based WAF.