Advanced Search
Search Results
176 total results found
Remediation Steps
Follow the steps below to remediate this finding on WordPress. Add the following to your theme's functions.php:add_action('send_headers', function() { header('Strict-Transport-Security: max-age=31536000; includeSubDomains; preload'); });Alternatively, if using...
Remediation Steps
Follow the steps below to remediate this finding on Joomla. Edit the .htaccess file in the Joomla root directory and add:<IfModule mod_headers.c> Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" </IfModule>Alternativel...
Remediation Steps
Follow the steps below to remediate this finding on Drupal. Install and enable the Security Kit (SecKit) module:composer require drupal/seckit drush en seckitNavigate to Admin > Configuration > System > Security Kit.Under the "HTTP Strict Transport Security" s...
Remediation Steps
Follow the steps below to remediate this finding on Apache webserver. Prevent direct access to .htaccess files by adding the following to your main Apache configuration (apache2.conf or httpd.conf):<Files ".ht*"> Require all denied </Files>This blocks access t...
Remediation Steps
Follow the steps below to remediate this finding on Nginx webserver. Nginx does not use .htaccess files. If .htaccess files exist on the server, deny access in your server block:location ~ /\.ht {deny all;}Reload Nginx:sudo systemctl reload nginx
Remediation Steps
Follow the steps below to remediate this finding on Plesk. Log in to the Plesk control panel.Navigate to Domains > your domain > Apache & nginx Settings.Under "Additional Apache directives", add:<Files ".ht*"> Require all denied </Files>Click Apply.
Remediation Steps
Follow the steps below to remediate this finding on Linux (Debian/Ubuntu). Block ICMP timestamp requests using iptables or nftables.With iptables:sudo iptables -A INPUT -p icmp --icmp-type timestamp-request -j DROP sudo iptables -A OUTPUT -p icmp --icmp-type t...
Remediation Steps
Follow the steps below to remediate this finding on Linux (RHEL/CentOS/AlmaLinux). Block ICMP timestamp requests using firewalld or iptables.With firewalld:sudo firewall-cmd --permanent --add-rich-rule='rule protocol value="icmp" icmp-type name="timestamp-requ...
Remediation Steps
Follow the steps below to remediate this finding on Windows. Block ICMP timestamp requests using Windows Firewall.Open Windows Firewall with Advanced Security.Create a new Inbound Rule:Rule Type: CustomProtocol and Ports: ICMPv4, Specific types: Timestamp Requ...
Remediation Steps
Follow the steps below to remediate this finding on Microsoft IIS webserver. In IIS Manager, select your site and open Error Pages.For each error code (especially 500), set the error response to a custom static HTML page that does not reveal internal details.I...
Remediation Steps
Follow the steps below to remediate this finding on Nginx webserver. Disable PHP error display in php.ini:display_errors = Offdisplay_startup_errors = Offlog_errors = Onerror_log = /var/log/php_errors.logConfigure custom error pages in nginx.conf:error_page 50...
Remediation Steps
Follow the steps below to remediate this finding on Apache webserver. Disable PHP error display in php.ini or via .htaccess:php_flag display_errors off php_flag log_errors on php_value error_log /var/log/php_errors.logConfigure custom error pages:ErrorDocument...
Remediation Steps
Follow the steps below to remediate this finding on WordPress. In wp-config.php, disable debug output:define('WP_DEBUG', false); define('WP_DEBUG_DISPLAY', false); define('WP_DEBUG_LOG', false);Ensure no error output plugins (e.g., Debug Bar) are active in pro...
Remediation Steps
Follow the steps below to remediate this finding on Joomla. In the Joomla Administrator panel, go to System > Global Configuration > Server tab.Set Error Reporting to None.Click Save.
Remediation Steps
Follow the steps below to remediate this finding on Drupal. Go to Administration > Configuration > Development > Logging and errors.Set "Error messages to display" to None.Save the configuration.
Remediation Steps
Follow the steps below to remediate this finding on Linux (Debian/Ubuntu). For Postfix, restrict relay access in /etc/postfix/main.cf:smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destinationSet your trusted network:myn...
Remediation Steps
Follow the steps below to remediate this finding on Linux (RHEL/CentOS/AlmaLinux). For Postfix on RHEL/CentOS, edit /etc/postfix/main.cf:smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destinationRestart Postfix:sudo syst...
Remediation Steps
Follow the steps below to remediate this finding on Windows. For Microsoft Exchange, open the Exchange Admin Center.Go to Mail flow > Receive connectors.Select each connector and verify the Permission groups do not include Anonymous users for relay.For IIS SMT...