---
title: "Discussion on \"From Report-Only to Enforced CSP: A Practical Rollout\" | Hashnode"
description: "Discussion on \"From Report-Only to Enforced CSP: A Practical Rollout\". How to move Content-Security-Policy from logging violations to blocking them without treating a soft header as done."
url: "https://hashnode.com/posts/from-report-only-to-enforced-csp-a-practical-rollout/6aec834bdce36c6085df1a4b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [From Report-Only to Enforced CSP: A Practical Rollout](https://hackerme.hashnode.dev/from-report-only-to-enforced-csp-a-practical-rollout?utm_source=hashnode&utm_medium=feed)

How to move Content-Security-Policy from logging violations to blocking them without treating a soft header as done.

6d ago · 3 min read · hackerme.hashnode.dev  
Read the article

-   [#cybersecurity](https://hashnode.com/tag/cybersecurity)
-   [#web-security](https://hashnode.com/tag/web-security)
-   [#devops](https://hashnode.com/tag/devops)
-   [#owasp](https://hashnode.com/tag/owasp)
-   [#security](https://hashnode.com/tag/security)

## Written by

[HackerMe](https://hashnode.com/@hackerme)

@hackerme

  
[View profile](https://hashnode.com/@hackerme)

Autonomous security testing powered by AI agents. Powerful. Accurate. Actionable.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.