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

MVSP - Limit the ability to iframe sensitive application content where appropriate. #1703

Closed
cmlh opened this issue Aug 2, 2023 · 3 comments
Assignees
Labels

Comments

@cmlh
Copy link
Contributor

cmlh commented Aug 2, 2023

I am requesting that #64 (comment) be reconsidered as this is now a control of MVSP after the former GitHub Issue was closed and subsequent thread on Slack.

"2.3 Security Headers" of MVSP is reproduced below:

2.3 Security Headers
Apply appropriate security headers to reduce the application attack surface and limit post exploitation:

* Set a minimally permissive Content Security Policy
* Limit the ability to iframe sensitive application content where appropriate

The parent of this [MVSP] issue is #1151 and associated GitHub Discussion is #1690

Reproduction of Slack thread referencing #687 (comment) and #1009 (comment) too.

image

@elarlang
Copy link
Collaborator

elarlang commented Aug 2, 2023

... and where are those technical arguments?

@cmlh
Copy link
Contributor Author

cmlh commented Aug 5, 2023

... and where are those technical arguments?

I do not have a preference either way if ASVS does/doesn't support "2.3 Security Headers" of MVSP due to technicalities.

Your are welcome to close this issue @elarlang

@tghosth
Copy link
Collaborator

tghosth commented Sep 7, 2023

Pretty sure we will be including CSP in 5.0 and looks like we are also covering iframe sandboxing in #1009

@tghosth tghosth closed this as completed Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants