We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In order to take all measures to prevent XSS attacks, datagovteam wants to implement a Content Security Policy.
18F recommends CSPs https://guides.18f.gov/engineering/security/content-security-policy/
AND we get a ding on ScanGov score for not having one on data.gov specifically: https://scangov.org/profile/?domain=data.gov#security
Despite data.gov and resources.data.gov being static sites, it would help us maintain better "scores" to have a CSP in place.
Will improve security posture from data injection and XSS attacks
meta-tag
The text was updated successfully, but these errors were encountered:
No branches or pull requests
User Story
In order to take all measures to prevent XSS attacks, datagovteam wants to implement a Content Security Policy.
Acceptance Criteria
AND having CSPs is an accepted web best practice
WHEN a page loads
THEN a CSP is present in the header
Background
18F recommends CSPs https://guides.18f.gov/engineering/security/content-security-policy/
AND we get a ding on ScanGov score for not having one on data.gov specifically: https://scangov.org/profile/?domain=data.gov#security
Despite data.gov and resources.data.gov being static sites, it would help us maintain better "scores" to have a CSP in place.
Security Considerations (required)
Will improve security posture from data injection and XSS attacks
Sketch
meta-tag
meta-tag
meta-tag
The text was updated successfully, but these errors were encountered: