The Server Side Scanner (SSS) adds to the included remote malware and blocklist scans by checking your website’s files directly on the server. It runs once a day and looks for: backdoors, phishing, and other security issues.
You can learn how to enable the Server Side Scanner here. It is not required, but we recommend all our users enable it whenever possible.
File Audits
The Server Side Scanner also tracks changes to your files, so you have an audit trail of what changed on your site and when.
The SSS monitors your site’s files across three states:
• New: files detected for the first time since scanning was enabled.
• Changed: files that existed in a previous scan but have been modified since.
• Deleted: files that were present in a previous scan but are no longer on the server.
Note
File changes will be available to view within the Server Side Scanner results in the monitoring dashboard. You can find a visual reference in this article. You will not be alerted to file changes via email.
File Types Scanned
The Server Side Scanner checks server-side scripts and executable file types where backdoors, phishing pages, and other security issues are most commonly found. The following extensions are included:
.php, .htm, .phtml, .shtml, .js, .pl, .py, .sh, .cgi, .asp, .asa, .module, and others
Static files such as images, PDFs, and media files are not scanned and neither is the database.
Server-Side Scan – Host Server Requirements
1. PHP runtime
•PHP 7.1 or higher has to be installed and able to serve .php requests without being blocked. Servers without PHP (IIS, ColdFusion, .NET or Node-only) will not be able to make use of the Server Side Scanner (SSS).
•PHP memory and time limits have to fit the site‘s file count. The following settings are general guidelines:
|
Files |
|
|
|---|---|---|
|
< 10k |
256M |
180 |
|
10k–50k |
512M |
180 |
|
50k–100k |
1024M |
300 |
|
100k+ |
2048M |
300 |
2. File system and permissions
• The document root has to be writable by the PHP/web server user. If not, the scan will not be able to complete (this mostly affects hosting servers such as WP Engine).
If your site’s root is read-only, we have a workaround. Please open a support ticket for further assistance.
• PHP needs a usable temp directory for /tmp/filesToUpload-*.zip. The SSS creates a zip archive in the server’s temp directory which the scanning infrastructure uses for analysis. The archive is removed after the scan completes, but the scan will fail if PHP cannot write to the temp directory.
3. Network and security layers
The Server Side Scan will need to be allowed on any security plugin or firewall enabled.
•IPs: 54.184.226.94 and 35.162.140.124
•User-agent: Sucuri Server Side Scanner
The scanner can‘t run JavaScript or solve CAPTCHAs, so any challenge page counts as a block.
4. Request size and timeouts
• The request body limit has to allow scan POSTs bigger than 1 MB. General guidelines are listed below:
◦nginx: client_max_body_size 20M
◦Apache: LimitRequestBody 20971520
◦ModSecurity: SecRequestBodyLimit / SecRequestBodyNoFilesLimit 20971520
• The server has to respond within the scanner‘s 180-second window.
If your server doesn’t meet these requirements, you will still be able to make full use of our remote scans which will provide detection for most attacks.