Does WAF comply with PCI DSS 6.6 requirements?

Yes.

If my Adobe Commerce on cloud infrastructure account manages sites on multiple domains, is the WAF profile tuned for each domain, or collectively for all domains?

The WAF is tuned collectively for all domains under a single cloud account.

What rules are used for the WAF?

The rule set in the WAF profile applied to your Adobe Commerce on cloud infrastructure production environment is based on the OWASP Top 10 Threat Protection rule set, which covers common exploits to web services. It also contains Adobe Commerce-specific rules developed by TrustWave SpiderLabs. Fastly’s Security Research team has also added rules which protect your site and network from commonly known attacks: bad IP addresses, bad user agents, and known botnet command and control nodes. We enable rules at OWASP Paranoia Level 3 or less, which provides high-security coverage.

How do I access logs?

To have the logs sent to your logging tool, please work with your Technical Account Manager (TAM) to add a logging endpoint in Fastly.

What does a block request look like?

A blocked request returns a 403 page with a request identifier.

You can customize this page as long as the customization includes the request identifier. Contact your technical account manager for details.

How do we update WAF rule sets? How quickly can a WAF rule be changed or updated and applied globally in production?

As a part of the cloud WAF service, Fastly manages rule updates from commercial third parties, Fastly research, and open sources. They update published rules into a policy as needed or when changes to the rules are available from their respective sources. New rules that match the published classes of rules are also inserted into the WAF instance of any service once it is enabled. This helps ensure immediate coverage for new or evolving exploits. You can review information about rule updates and maintenance on the Fastly documentation site.

How is Adobe Commerce’s cloud WAF different from the WAF solution Fastly offers to its direct customers?

The WAF solution that is sold directly by Fastly is a paid offering that includes broader rule sets and additional features like rule customization and malware protection. Adobe Commerce’s cloud WAF solution includes a subset of rules targeted at the Adobe Commerce application and includes only one rule set for each customer’s Production environment.

What types of security threats does WAF protect against?

ThreatWAF protection
SQL injection attacksBoth the OWASP ModSecurity Core Rule Set and the TrustWave commercial rule set include specific filters for SQL injection attacks and its variants.
Cross-site injectionThe OWASP rule set protects against cross-site injection attacks. Fastly leverages a scoring mechanism for each request looking for cross-site injection and other threats to the origin. We score every request against the entire core rule set and validate that the request score is below a configurable threshold in order for it to pass.
Brute force attacksCovered by the OWASP rule set. Fastly also blocks brute force activity by using VCL code that recognizes specific sources, requests, or attempts to brute force or overwhelm security controls prior to any traffic reaching the origin datacenter.
Network attacksNetwork attacks, or attacks targeting network infrastructure, are managed automatically by Fastly. Fastly does not pass DNS to origin, and traffic that does not match a narrow HTTP, HTTPS or DNS profile is discarded at the edge of the network. Attacks targeting control protocols are defended against through authentication of endpoints throughout the network. Additionally, network protocols used within the Fastly network are hardened to ensure that they cannot be leveraged as a means of amplification or reflection. Customers are responsible for protecting against attacks that bypass the Fastly network by leveraging the Fastly Cache IP address space, published to our customers as a component of our CDN service. It's recommended that origin IP address space not be published in public DNS to ensure bypass attacks cannot use these addresses as targets.
JavaScript injection attacksWAF rules protect against malicious JavaScript code being inserted into client communications with web services. Common exploit patterns or scores are filtered through the WAF to ensure the integrity of the origin service.

Are additional features and functionality offered?

Adobe Commerce’s WAF offering includes protection against OWASP Top-10 threats as part of PCI requirements, 24x7 support, including triage for false positives, and version upgrades. The following features are not supported in the standard offer:

  • rate limiting
  • rule customizations
  • bot mitigation
  • malware protection

How is my site performance affected by the WAF?

An estimated 1.5 milliseconds (ms) to 20 ms of latency is introduced to every non-cached request.

Can customers create and modify IP blacklists to block traffic?

Yes, customers can enable blocking by country and access control list (ACL) from the Adobe Commerce on cloud infrastructure’s Admin UI. Use these features in cases where you want to block access for visitors coming from specific countries or certain IPs or IP ranges. If you want blocked visitors to see a custom page rather than an error code, you can create a custom error page by uploading HTML in the Fastly Configuration menu. See Create a custom error/maintenance page in our developer documentation.

Where can I check the operational status of my WAF service?

Overall WAF service availability is reported on the Fastly Status page. Availability reporting for individual customers’ WAF is not provided.

Does Adobe Commerce provide Incident Management for the WAF service?

At this time, Incident Management is not offered.