Referrer-Policy shows it can work. When the header is missing, browsers fall back to strict-origin-when-cross-origin. 86.6% of the sites we scanned don't send it, and we didn't count that as a failure for that reason. The other headers don't have a safe default like that yet.
And if any of the websites use .NET, they can get almost all of the recommended security headers in one line by using a NuGet package I created: https://gaprogman.github.io/OwaspHeaders.Core/
So.. you've written up what you checked, and what didn't match what ever criteria you had.
But.. what does it mean? Why enforce certain headers? Why enforce certain options? There is a section which kinda looks at this, but not really.
You have a bunch of links at the end for resources, but why not just provide the rationale for each rule or option inclusion in the article as well? What does each prevent or allow and why?
No, not for a VPS. They are configured at the web server. If you mean CDN, you might be able to use a _headers file or similar to add. Cloudflare can definitely do it.
for static sites... it's not that I would call them useless, but most are just not very critical. Clickjacking and any cookie attacks on a site without cookies is pretty useless most of the time.
19 comments
[ 0.29 ms ] story [ 20.6 ms ] threadBut.. what does it mean? Why enforce certain headers? Why enforce certain options? There is a section which kinda looks at this, but not really.
You have a bunch of links at the end for resources, but why not just provide the rationale for each rule or option inclusion in the article as well? What does each prevent or allow and why?