You are configuring the FortiWeb client-side protection feature to defend against browser-based attacks.

The layered browser-protection model separates prevention, runtime detection, and post-compromise mitigation. CORS protection belongs in the first stage because it restricts which origins can interact with protected resources, helping prevent unauthorized cross-origin access before exploitation occurs. Subresource integrity belongs in the second stage because it detects whether externally loaded scripts or resources have been modified at runtime by comparing them against expected integrity values. HTTP header-based protection belongs in the mitigation stage because security headers can limit the impact of browser-side compromise by controlling browser behavior, enforcing restrictions, and reducing exploit capability. The correct sequence is therefore CORS first, subresource integrity second, and HTTP header request last.

================