Skip to content

refactor: add a reference to Security Headers on "How to Prevent" section #106

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Apr 27, 2023
Merged

refactor: add a reference to Security Headers on "How to Prevent" section #106

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions 2023/en/src/0xa7-security-misconfiguration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,8 +80,10 @@ Furthermore:
(TLS), regardless of whether it is an internal or public-facing API.
* Be specific about which HTTP verbs each API can be accessed by: all other
HTTP verbs should be disabled (e.g. HEAD).
* Implement a proper Cross-Origin Resource Sharing (CORS) policy on APIs
expected to be accessed from browser-based clients (e.g. web app front-ends).
* APIs expecting to be accessed from browser-based clients (e.g., WebApp
front-end) should, at least:
* implement a proper Cross-Origin Resource Sharing (CORS) policy
* include applicable Security Headers
* Ensure all servers in the HTTP server chain (e.g. load balancers, reverse
and forward proxies, and back-end servers) process incoming requests in a
uniform manner to avoid desync issues.
Expand Down