To enable COEP and CORP headers, send Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp on your HTML documents, and Cross-Origin-Resource-Policy on the resources you serve. Trial the report-only variants first, because every cross-origin subresource must opt in. Then verify with curl -I and a re-scan.
Cross-origin isolation is a browser state that puts a page in its own browsing context group and blocks it from loading cross-origin resources unless those resources opt in.
What triggers this finding?
The scanner requests your site over HTTPS and reads the response headers of the main document. It looks for three headers:
- Cross-Origin-Opener-Policy (COOP) decides whether windows you open, or that open you, keep a script reference to your page.
- Cross-Origin-Embedder-Policy (COEP) decides whether your page may load cross-origin resources that have not opted in. The values are
unsafe-none,require-corpandcredentialless. - Cross-Origin-Resource-Policy (CORP) is set on a resource. It tells the browser which origins may load it:
same-origin,same-siteorcross-origin. It is defined in the Fetch Standard.
The finding fires when one or more of these are absent or set to their permissive defaults. The COOP and COEP processing rules are in the HTML Standard. MDN has a readable summary in its COEP reference.
Why does it matter, and why is it only info?
Same-origin policy stops a page from reading another origin's responses directly. It does not stop a page from loading those responses into its own process. That leaves two problems:
- Reference leaks. A page that opens a cross-origin popup, or is opened by one, can keep a
windowreference. That reference exposes some cross-window signals, such as frame counts and navigation timing, which attackers use for cross-site leak techniques. - Side channels. Speculative-execution attacks such as Spectre can read memory in the same process. If an attacker's page shares a process with data from your origin, that data may be readable. Browsers respond with process isolation, but they can only apply it fully when the page opts into the isolation headers.
An auditor flags this because the cost of a leak lands on you. A hijacked session page or a leaked account detail can mean a breach notification and a lost customer. The scanner rates the finding as info because the headers are defence in depth, and a missing header is not a vulnerability by itself. Setting them blindly can also break embeds, ads and third-party widgets. So the rating asks you to decide deliberately rather than treat the finding as an incident.
How do I fix it? Enable COEP and CORP headers safely
Roll out in this order so nothing breaks in production.
Step 1: Set COOP and report-only COEP
Start with a policy that reports violations without blocking anything.
add_header Cross-Origin-Opener-Policy "same-origin" always;
add_header Cross-Origin-Embedder-Policy-Report-Only "require-corp" always;
The Apache equivalent:
Header always set Cross-Origin-Opener-Policy "same-origin"
Header always set Cross-Origin-Embedder-Policy-Report-Only "require-corp"
COOP same-origin severs the window relationship with cross-origin popups. If you rely on OAuth or payment popups that call back with window.opener, test them now. same-origin-allow-popups is a softer COOP value for that case.
Step 2: Mark your own assets with CORP
Add CORP to the files you serve. Use same-site for assets only your own subdomains load. Use cross-origin for assets that partners or CDNs legitimately embed.
location /static/ {
add_header Cross-Origin-Resource-Policy "same-site" always;
}
Step 3: Fix third-party resources
Under require-corp, a cross-origin image, script or font loads only if its server sends CORP or CORS headers allowing it. For third parties you do not control, you have three choices:
- Ask the vendor to send CORP or CORS headers.
- Load the resource with the
crossoriginattribute, if the server supports CORS. - Use
credentiallessinstead ofrequire-corp. It lets no-CORS cross-origin requests through without credentials. Browser support differs, so check current compatibility before relying on it.
Also check that every subresource is served over HTTPS, since insecure loads are a separate problem. Fixing mixed active content covers that.
Step 4: Enforce
When the report-only window shows no violations, switch to the enforcing header.
add_header Cross-Origin-Embedder-Policy "require-corp" always;
Send the headers from every host that serves HTML. A policy on the apex but not on www still leaves one entry point open, as host variant header mismatches explains.
How does the scanner rate it and how do I confirm the fix?
The check reads the response headers from the main document. It records the observed value of each header as evidence and rates the result info. The rating is the same whether one header or all three are missing, so the evidence is what shows which of the three need work.
Confirm the fix yourself before re-scanning:
curl -sI https://example.com/ | grep -i -E '^cross-origin-(opener|embedder|resource)'
You should see COOP same-origin and COEP require-corp or credentialless. In the browser console, window.crossOriginIsolated should return true. Then trigger a re-scan. The finding clears once the headers are present on the scanned host. If the old headers keep appearing, allow for CDN cache expiry.
Common questions
Do I need COEP and CORP if I do not use SharedArrayBuffer?
No site is forced to. Cross-origin isolation is required to use SharedArrayBuffer and some high-resolution timers, but it also hardens any page against reference leaks and side channels. Sites with sensitive logged-in pages gain the most. Static brochure sites with many third-party embeds may reasonably accept the info finding.
Will require-corp break my site?
It can. Under require-corp, any cross-origin image, script, font or iframe lacking CORP or CORS headers is blocked. That is why the report-only header exists. Run it for a period, review the reported violations, fix or replace each resource, and only then enforce.
What is the difference between CORP and CORS?
CORP is a response header that tells the browser which origins may load a resource in no-CORS mode, such as a plain <img> tag. CORS governs whether scripts may read a cross-origin response. They solve different problems, and under require-corp a resource can satisfy the policy with either one.
Key takeaways
- Cross-origin isolation needs COOP
same-originplus COEPrequire-corporcredentialless, with CORP on resources others embed. - The finding is rated info because the headers are hardening, and enabling them can break third-party content.
- Deploy report-only COEP first, fix violations, then enforce on every host that serves HTML.
- Verify with
curl -Iandwindow.crossOriginIsolated, then re-scan. - SetEnforce checks the main document's response headers for these three policies and records the values it saw as evidence.