-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
WSTG-CONF-XX - Security Header Misconfiguration #1172
Comments
I'd be fine with this. Just give me a few days to consider if it belong amongst an existing section |
Sure, take your time. |
Another one to add to the list would be headers in places where they're not valid - such as a |
I'm really sorry, I'm not ignoring this but I might not get to sit and look at it until after the holidays. |
No problem, take your time buddy. I'll also be a bit busy until a few weeks into 2025 anyways. |
Okay I finally found a few mins to look at this. Here's my proposal:
@ThunderSon @rbsec thoughts/complaints? 😄 |
Seems reasonable, and gives us a catch-all for any future header checks we want to add. |
I'll review it a bit better when I get back from holidays, but so far it sounds fair. Thank you! |
Can i submit a pull request for a content update for a new CONF item for "Security Header Misconfiguration"
There doesnt seem to be anyone which covers these scenarios yet. Please do let me know if I am wrong.
Otherwise, what do you guys think?
The text was updated successfully, but these errors were encountered: