Advanced Search
Search Results
395 total results found
Remediation Steps
Follow the steps below to remediate this finding on Apache webserver. Replace the self-signed certificate with a CA-issued certificate.For Let's Encrypt:sudo certbot --apache -d yourdomain.comUpdate the Apache SSL VirtualHost configuration to reference the new...
Plesk
Remediation Steps
Follow the steps below to remediate this finding on Plesk. In the Plesk control panel, navigate to Domains > your domain > SSL/TLS Certificates.Click the Let's Encrypt button to replace the self-signed certificate with a trusted one.Assign the new certificate ...
Generic / Developer guidance
Remediation Steps
Follow the steps below to remediate this finding on Generic / Developer guidance. Subresource Integrity (SRI) allows browsers to verify that third-party files (scripts, stylesheets) have not been tampered with.For each externally hosted resource, generate a ha...
WordPress
Remediation Steps
Follow the steps below to remediate this finding on WordPress. Use the wp_enqueue_script() and wp_enqueue_style() functions with a src_integrity parameter, or hook into script_loader_tag to add integrity attributes:add_filter('script_loader_tag', function($tag...
Joomla
Remediation Steps
Follow the steps below to remediate this finding on Joomla. In your template's index.php, add integrity and crossorigin attributes to any third-party <script> or <link> tags that load external resources.For Joomla 4+, use the WebAssetManager to register assets...
Drupal
Remediation Steps
Follow the steps below to remediate this finding on Drupal. In your module's *.libraries.yml, add the integrity key for external assets:my_library:js:https://cdn.example.com/lib.js:type: external attributes: integrity: sha384-<hash> crossorigin: anonymous
Microsoft IIS webserver
Remediation Steps
Follow the steps below to remediate this finding on Microsoft IIS webserver. Audit application responses for Unix timestamps in JSON, HTML, or HTTP headers and ensure sensitive timestamps (file modification dates, user IDs encoded as timestamps) are not expose...
Nginx webserver
Remediation Steps
Follow the steps below to remediate this finding on Nginx webserver. To suppress Last-Modified and ETag headers:add_header Last-Modified ""; etag off;Review application-generated responses and ensure raw Unix timestamps are not returned in API responses unless...
Apache webserver
Remediation Steps
Follow the steps below to remediate this finding on Apache webserver. Suppress file-based timestamp headers:Header unset Last-Modified FileETag NoneReview application code that returns raw Unix timestamps in API or HTML responses.