Adobe Commerce on cloud infrastructure has a protective blocking feature that, under certain circumstances, restricts access to websites with security vulnerabilities. We use this partial blocking method to prevent exploitation of known security vulnerabilities.
Outdated software often contains exploits we protect against by partially blocking access to these sites.
How the protective block works
Adobe Commerce maintains a database of signatures of known security vulnerabilities in open-source software that are commonly deployed on our infrastructure. The security check analyzes only known vulnerabilities in open-source projects; it cannot examine customizations you write.
We analyze the code of your application:
- When you push new code to Git
- When new vulnerabilities are added to our database
If a critical vulnerability is detected in your application, it rejects the Git push.
We run two types of blocks:
For development websites, we run complete blocks.
The error message accompanying
git pushprovides detailed information about the vulnerability.
For production websites, we run a “partial block” that allows the site to stay mostly online.
Depending on the nature of the vulnerability, parts of a request, such as a query string, cookies or any additional headers, might be removed from GET requests. All other requests may be blocked entirely—this could apply to logging in, form submission, or product checkout.
Unblocking is automated upon resolution of the security risk. The block is removed soon after you apply a security upgrade that removes the vulnerability.
Opt out of the protective block
The protective block is there to protect you against known vulnerabilities in the software you deploy Adobe Commerce on cloud infrastructure.
However, you can opt out of the protective block by adding the following to
preflight: enabled: false
You can also explicitly opt-out of some specific check as follows:
preflight: enabled: true ignore_rules: [ “drupal:SA-CORE-2014-005” ]