Use the Security Rules tab on the Configure Zone screen to protect a B2C Commerce embedded CDN (eCDN) zone with web application firewall (WAF) managed rulesets, realm and zone security rules, custom firewall rules, and rate limiting. Learn what each control does, which zone types are eligible, and how traffic from trusted sources bypasses security checks.
Which Salesforce Commerce Product Do I Have?
What the Security Rules Tab Covers in B2C Commerce
The Security Rules tab on the B2C Commerce Configure Zone screen groups the controls that decide which requests reach your storefront and how suspicious traffic is handled. Page Shield policies and host header override rules appear on their own tabs in the Configure Zone screen but are part of the same zone-security workflow.
| Control | What it does | For more information |
|---|---|---|
| WAF managed rulesets | Enable Salesforce-managed rule packages (the eCDN WAFv2 Managed Ruleset and the OWASP WAFv2 Managed Ruleset) that block common attack patterns. | Configure WAF Settings for an eCDN Zone |
| Realm Security Rules | Manage IP address lists and custom firewall rules that apply across all eligible zones in your realm. Replaces the legacy Trusted IP configuration. | Realm Security Rules for eCDN Zones |
| Custom firewall rules | Match requests by IP, geography, header, or other criteria and choose an action, such as block, challenge, or skip. | Create a Custom Firewall Rule for an eCDN Zone |
| Rate limiting rules | Throttle or block clients that exceed a request threshold in a time window. | Create a Rate Limiting Rule for an eCDN Zone |
| Page Shield policies | Monitor and control the client-side scripts and connections that run on your storefront. | Configure a Page Shield Policy for an eCDN Zone |
| Host header override rules | Rewrite the Host header for matching requests so they route to the correct origin. | Configure a Host Header Override Rule for an eCDN Zone |
Example: Rate Limit Logins That Use Leaked Credentials
Exposed Credentials Check was removed from WAF Rules in B2C Commerce 26.10. To act on leaked
credentials, use Leaked Credentials Detection fields in a custom firewall rule or a rate-limiting
rule. This rate-limiting rule issues a Managed Challenge for 1 hour to
every /Account-Login POST request from an IP address that submitted two leaked
username and password pairs in the last minute.
- Rule Name: Rate Limit Leaked Credentials
- Set Rate Limit: 2 requests per minute
- Use Custom Counting Expression: selected
- Matching Characteristics: IP with NAT support
- Choose action: Managed Challenge
- Action for Selected Duration: 1 hour
Rule expression:
(ends_with(http.request.uri.path, "/Account-Login") and http.request.method eq "POST")
Counting expression:
(ends_with(http.request.uri.path, "/Account-Login") and http.request.method eq "POST" and cf.waf.credential_check.username_and_password_leaked)
For the Leaked Credentials Detection fields and a custom firewall rule example, see Create a Custom Firewall Rule for an eCDN Zone and Create a Rate Limiting Rule for an eCDN Zone.
Behavior: What Traffic Is Bypassed
When a request comes from an IP address in a trusted (Managed IP Address) list and matches a skip rule, the eCDN for B2C Commerce bypasses selected security checks. The core purpose, making sure that traffic from trusted IP addresses isn't blocked, is preserved from the legacy Trusted IP model. The new model implements it more precisely.
| Security check | Legacy behavior (Trusted IP groups) | New behavior (WAF custom rules + skip actions) |
|---|---|---|
| Custom firewall rules | Bypassed | Bypassed |
| WAF managed rules | Bypassed | Bypassed |
| Rate limiting rules | Bypassed | Bypassed |
| DDoS Layer 7 protections | Bypassed | Automatically adjusted (sensitivity reduced for trusted sources). No additional configuration required. |
| Bot management | Bypassed | Not bypassed by default. Evaluate whether your use case requires this and configure accordingly. |
DDoS Layer 7 Override Details
When an account has account-level (realm-level) trusted IP lists configured, B2C Commerce
automatically applies DDoS Layer 7 overrides on all eligible zones. These overrides are separate
from the skip rule applied to custom firewall rules, WAF rules, and rate limiting rules. They're
set to sensitivity_level: off and action: log to prevent
false-positive challenges on legitimate high-volume traffic from trusted sources.
The following Cloudflare DDoS managed rules are automatically overridden:
| Rule ID | Description |
|---|---|
0b1e17bd25c74e38834f19043486aee1 |
Unusual headers/URI path signature #1 |
466d6c2e8ba74459a2670e91e269dfd6 |
Unusual headers/URI path signature #56 |
12b9aecf1f6245b29d7e842bf35a42a0 |
Unusual headers/URI path signature #57 |
6e3ccc23900c428e8ec0fb8a3a679c52 |
Requests from known bad sources |
d38bbe6dc925461ca4e47e4cecd68c61 |
High request rate to search endpoints |
0a07c24f3cd44a57a5c19b73d2f294d7 |
Requests trying to impersonate browsers |
Zone Type Eligibility
The following zone types for B2C Commerce support Realm Security Rules (same as legacy Trusted IP support):
- Proxy zones
- Legacy zones (custom domains)
- Default Domain zones
Feature Switch
Realm Security Rules are controlled by a feature switch in B2C Commerce Business Manager. When the Enable eCDN Trusted IP Migration feature switch is enabled, the Security Rules tab with the Managed IP Address Lists and Custom Firewall Rules functionality becomes available in the Configure Zones interface. Contact your Salesforce account team if this tab isn't visible in your organization.
- Configure WAF Settings for an eCDN Zone
Configure web application firewall (WAF) managed rulesets for an eCDN zone for B2C Commerce by using the Security Rules tab in Configure Zones in Business Manager. - Realm Security Rules for eCDN Zones
Realm Security Rules let you define Managed IP Address Lists and custom firewall rules that control how trusted IP traffic is handled across all your eCDN zones for B2C Commerce. These rules replace the legacy Trusted IP configuration. - Create a Custom Firewall Rule for an eCDN Zone
Configure a custom firewall rule to control incoming traffic to your B2C Commerce storefront based on specified request parameters. - Create a Rate Limiting Rule for an eCDN Zone
Configure a rate limiting rule to specify rate limits for requests that match a particular expression and then perform an action when requests reach those rate limits. Rate limiting rules improve B2C Commerce storefront availability, target specific traffic patterns and combat threats, such as bots.