Bobcares

Whitelist IP for ModSecurity in Plesk and Windows

by | Oct 25, 2023

Learn how to Whitelist IP  for ModSecurity in Plesk and Windows. Our Plesk Support team is here to help you with your questions and concerns.

Whitelist IP for ModSecurity in Plesk and Windows

With the increasing threat of hackers and malicious attacks, we need to have strong defenses in place. This is where ModSecurity steps in, It helps protect our website from potential threats.

Whitelist IP for ModSecurity in Plesk and Windows

Today, we are going to take a look at how to whitelist IP addresses in ModSecurity, so that trusted sources can access our site and keep malicious attacks at bay.

How to Whitelist IP Addresses in ModSecurity

For Debian-based systems (Ubuntu/Debian)

  1. To begin with, connect to the server via SSH.
  2. Then, create or open the ModSecurity file used for IP whitelisting.
  3. Next, add the following rule in a single line:

    SecRule REMOTE_ADDR "@ipMatch 203.0.113.0/24,192.0.2.2" "id:3,phase:1,t:none,log,pass,ctl:ruleRemoveById=52333"

    Here, we have to replace `52333` with the rule ID and `203.0.113.0/24` with the IP addresses we want to whitelist. We can mention multiple addresses, separated by commas.

  4. Now, it is time to check the Apache syntax

    apache2ctl -t

  5. If the syntax check is successful, we can apply the new configuration:

    service apache2 reload

RHEL-based systems (CentOS/CloudLinux):

  1. First, connect to the server via SSH.
  2. Then, create or open the ModSecurity file used for IP whitelisting.
  3. Next, we have to add the IP whitelisting rule as seen in the Debian-based system section.
  4. Now, check the Apache syntax as seen here:

    httpd -t

  5. If the syntax check is successful, we can apply the new configuration:

    service httpd reload

For OWASP Ruleset on Windows

  1. First, log into the Plesk control panel.
  2. Then, head to Web Application Firewall (ModSecurity)” under Tools & Settings and click Settings.
  3. Now, add this IP whitelisting rule in the Custom directives field.

    SecRule REMOTE_ADDR "@ipMatch 203.0.113.0/24,192.0.2.2" "id:3,phase:1,t:none,log,pass,ctl:ruleRemoveById=52333"

    Here, we have to replace `52333` with the rule ID and `203.0.113.0/24` with the IP addresses we want to whitelist. We can mention multiple addresses, separated by commas.

  4. Finally, click the OK button to apply the changes.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to Whitelist IP  for ModSecurity in Plesk and Windows.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF