Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a content security policy at the application level #493

Open
1 of 9 tasks
sandbergja opened this issue Oct 1, 2024 · 0 comments
Open
1 of 9 tasks

Add a content security policy at the application level #493

sandbergja opened this issue Oct 1, 2024 · 0 comments

Comments

@sandbergja
Copy link
Member

What maintenance needs to be done?

Add a content security policy header in addition to the current header that comes from nginx.

Level of urgency

  • High
  • Moderate
  • Low

Why is this maintenance needed?

It would provide XSS and Clickjacking protections to users of this application.

Acceptance criteria

  • DSS responses include a Content-Security-Policy header set at the application level
  • The CSP has object-src 'none';
  • The CSP has base-uri 'none';
  • The CSP is as restrictive as possible
  • The CSP still allows libwizard to embed DSS in iframes
  • The UIs still work

Implementation notes, if any

See this documentation about a Strict CSP and MDN's general documentation about CSPs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant