+V3 Web Frontend Security
---+V3.1 Web Frontend Security Documentation
------+V3.1.1 Verify that application documentation states the expected security features that browsers using the …
---+V3.2 Unintended Content Interpretation
------+V3.2.1 Verify that security controls are in place to prevent browsers from rendering content or …
------+V3.2.2 Verify that content intended to be displayed as text, rather than rendered as HTML, is handled …
------+V3.2.3 Verify that the application avoids DOM clobbering when using client-side JavaScript by employing …
---+V3.3 Cookie Setup
------+V3.3.1 Verify that cookies have the 'Secure' attribute set, and if the '__Host-' prefix is not used for …
------+V3.3.2 Verify that each cookie's 'SameSite' attribute value is set according to the purpose of the cookie …
------+V3.3.3 Verify that cookies have the '__Host-' prefix for the cookie name unless they are explicitly …
------+V3.3.4 Verify that if the value of a cookie is not meant to be accessible to client-side scripts (such as …
------+V3.3.5 Verify that when the application writes a cookie, the cookie name and value length combined are not …
---+V3.4 Browser Security Mechanism Headers
------+V3.4.1 Verify that a Strict-Transport-Security header field is included on all responses to enforce an …
------+V3.4.2 Verify that the Cross-Origin Resource Sharing (CORS) Access-Control-Allow-Origin header field is a …
------+V3.4.3 Verify that HTTP responses include a Content-Security-Policy response header field which defines …
------+V3.4.4 Verify that all HTTP responses contain an 'X-Content-Type-Options: nosniff' header field. This …
------+V3.4.5 Verify that the application sets a referrer policy to prevent leakage of technically sensitive data …
------+V3.4.6 Verify that the web application uses the frame-ancestors directive of the Content-Security-Policy …
------+V3.4.7 Verify that the Content-Security-Policy header field specifies a location to report violations.
------+V3.4.8 Verify that all HTTP responses that initiate a document rendering (such as responses with …
---+V3.5 Browser Origin Separation
------+V3.5.1 Verify that, if the application does not rely on the CORS preflight mechanism to prevent disallowed …
------+V3.5.2 Verify that, if the application relies on the CORS preflight mechanism to prevent disallowed …
------+V3.5.3 Verify that HTTP requests to sensitive functionality use appropriate HTTP methods such as POST …
------+V3.5.4 Verify that separate applications are hosted on different hostnames to leverage the restrictions …
------+V3.5.5 Verify that messages received by the postMessage interface are discarded if the origin of the …
------+V3.5.6 Verify that JSONP functionality is not enabled anywhere across the application to avoid Cross-Site …
------+V3.5.7 Verify that data requiring authorization is not included in script resource responses, like …
------+V3.5.8 Verify that authenticated resources (such as images, videos, scripts, and other documents) can be …
---+V3.6 External Resource Integrity
------+V3.6.1 Verify that client-side assets, such as JavaScript libraries, CSS, or web fonts, are only hosted …
---+V3.7 Other Browser Security Considerations
------+V3.7.1 Verify that the application only uses client-side technologies which are still supported and …
------+V3.7.2 Verify that the application will only automatically redirect the user to a different hostname or …
------+V3.7.3 Verify that the application shows a notification when the user is being redirected to a URL outside …
------+V3.7.4 Verify that the application's top-level domain (e.g., site.tld) is added to the public preload list …
------+V3.7.5 Verify that the application behaves as documented (such as warning the user or blocking access) if …
|
V3 Web Frontend Security
Control ObjectiveThis category focuses on requirements designed to protect against attacks executed via a web frontend. These requirements do not apply to machine-to-machine solutions. ReferencesFor more information, see also:
1. Ħarsa ġenerali
| Titlu |
Standard |
|
V3.1 Web Frontend Security Documentation
|
This section outlines the browser security features that should be specified in the application's documentation.
|
|
V3.2 Unintended Content Interpretation
|
Rendering content or functionality in an incorrect context can result in malicious content being executed or displayed.
|
|
V3.3 Cookie Setup
|
This section outlines requirements for securely configuring sensitive cookies to provide a higher level of assurance that they were created by the application itself and to prevent their contents from leaking or being inappropriately modified.
|
|
V3.4 Browser Security Mechanism Headers
|
This section describes which security headers should be set on HTTP responses to enable browser security features and restrictions when handling responses from the application.
|
|
V3.5 Browser Origin Separation
|
When accepting a request to sensitive functionality on the server side, the application needs to ensure the request is initiated by the application itself or by a trusted party and has not been forged by an attacker. Sensitive functionality in this context could include accepting form posts for authenticated and non-authenticated users (such as an authentication request), state-changing operations, or resource-demanding functionality (such as data export). The key protections here are browser security policies like Same Origin Policy for JavaScript and also SameSite logic for cookies. Another common protection is the CORS preflight mechanism. This mechanism will be critical for endpoints designed to be called from a different origin, but it can also be a useful request forgery prevention mechanism for endpoints which are not designed to be called from a different origin.
|
|
V3.6 External Resource Integrity
|
This section provides guidance for the safe hosting of content on third-party sites.
|
|
V3.7 Other Browser Security Considerations
|
This section includes various other security controls and modern browser security features required for client-side browser security.
|
1.1 Referenzi
1.2 Rekwiżiti identifikati
1.3 Regolamenti relatati
2. Rekwiżiti identifikati
3. Regolamenti relatati
Regolamenti
| Sors |
Regolamentazzjoni |
- OWASP -
EN: Publications of the OWASP Foundation, https://owasp.org/. OWASP® is a registered trademark of the OWASP Foundation, Inc.; GRCA is not affiliated with, nor endorsed by, the OWASP Foundation. Only the versions published by OWASP are authoritative. - OWASP Application Security Verification Standard (ASVS) 5.0.0, May 2025, from OWASP/ASVS: © 2008-2025 The OWASP Foundation, licensed under CC BY-SA 4.0. Changes: divided into sections and converted into the GRCA format, the wording unchanged. These adaptations are shared under CC BY-SA 4.0 as well.
- OWASP Mobile Application Security Verification Standard (MASVS) v2.1.0, January 2024, from OWASP/masvs: © The OWASP Foundation, licensed under CC BY-SA 4.0. Changes: converted into the GRCA format, the wording unchanged. These adaptations are shared under CC BY-SA 4.0 as well.
- OWASP Mobile Application Security Weakness Enumeration (MASWE) v1.0.0, August 2026, from OWASP/maswe: © The OWASP Foundation, licensed under CC BY-SA 4.0. Changes: converted into the GRCA format, the wording unchanged, linked to the MASVS controls they map to. These adaptations are shared under CC BY-SA 4.0 as well.
- OWASP Mobile Application Security Testing Guide (MASTG) v2.0.0, June 2026, from OWASP/mastg: © The OWASP Foundation, licensed under CC BY-SA 4.0. The tests and best practices only, without code samples, images, tools or apps. Changes: converted into the GRCA format, the wording unchanged; references to other pages of the MASTG as links to mas.owasp.org; the weakness of each test in the numbering of MASWE v1 and linked to it. These adaptations are shared under CC BY-SA 4.0 as well.
- OWASP Software Assurance Maturity Model (SAMM) v2.2.0, July 2026, from owaspsamm/core: © The OWASP Foundation, licensed under CC BY-SA 4.0. Changes: converted into the GRCA format, the wording unchanged; short codes (G-SM-1-A) built from the model, the assessment questions as assessment procedures of their activities. These adaptations are shared under CC BY-SA 4.0 as well.
- OWASP Top 10:2025, from OWASP/Top10: © 2003-2025 The OWASP® Foundation, Inc., licensed under CC BY-SA 4.0. The ten categories, without the icons. Changes: converted into the GRCA format, the wording unchanged. These adaptations are shared under CC BY-SA 4.0 as well. The names of the mapped CWEs (Common Weakness Enumeration): © 2006–2026 The MITRE Corporation. License: The MITRE Corporation hereby grants you a non-exclusive, royalty-free license to use CWE for research, development, and commercial purposes. Any copy you make for such purposes is authorized on the condition that you reproduce MITRE’s copyright designation and this license in any such copy. See the CWE Terms of Use. CWE™ is a trademark of The MITRE Corporation.
DE: Veröffentlichungen der OWASP Foundation, https://owasp.org/. OWASP® ist eine eingetragene Marke der OWASP Foundation, Inc.; GRCA steht in keiner Verbindung zur OWASP Foundation und wird von ihr nicht unterstützt. Maßgeblich sind allein die von OWASP veröffentlichten Fassungen. - OWASP Application Security Verification Standard (ASVS) 5.0.0, Mai 2025, aus OWASP/ASVS: © 2008-2025 The OWASP Foundation, lizenziert unter CC BY-SA 4.0. Änderungen: in Abschnitte aufgeteilt und in das GRCA-Format umgewandelt, der Wortlaut unverändert. Diese Bearbeitungen stehen ebenfalls unter CC BY-SA 4.0.
- OWASP Mobile Application Security Verification Standard (MASVS) v2.1.0, Januar 2024, aus OWASP/masvs: © The OWASP Foundation, lizenziert unter CC BY-SA 4.0. Änderungen: in das GRCA-Format umgewandelt, der Wortlaut unverändert. Diese Bearbeitungen stehen ebenfalls unter CC BY-SA 4.0.
- OWASP Mobile Application Security Weakness Enumeration (MASWE) v1.0.0, August 2026, aus OWASP/maswe: © The OWASP Foundation, lizenziert unter CC BY-SA 4.0. Änderungen: in das GRCA-Format umgewandelt, der Wortlaut unverändert, mit den MASVS-Controls verknüpft, denen sie zugeordnet sind. Diese Bearbeitungen stehen ebenfalls unter CC BY-SA 4.0.
- OWASP Mobile Application Security Testing Guide (MASTG) v2.0.0, Juni 2026, aus OWASP/mastg: © The OWASP Foundation, lizenziert unter CC BY-SA 4.0. Nur die Tests und Best Practices, ohne Codebeispiele, Bilder, Werkzeuge und Apps. Änderungen: in das GRCA-Format umgewandelt, der Wortlaut unverändert; Verweise auf andere Seiten des MASTG als Links zu mas.owasp.org; die Schwachstelle jedes Tests in der Nummerierung der MASWE v1 und mit ihr verknüpft. Diese Bearbeitungen stehen ebenfalls unter CC BY-SA 4.0.
- OWASP Software Assurance Maturity Model (SAMM) v2.2.0, Juli 2026, aus owaspsamm/core: © The OWASP Foundation, lizenziert unter CC BY-SA 4.0. Änderungen: in das GRCA-Format umgewandelt, der Wortlaut unverändert; Kürzel (G-SM-1-A) aus dem Modell gebildet, die Assessment-Fragen als Prüfverfahren ihrer Aktivitäten. Diese Bearbeitungen stehen ebenfalls unter CC BY-SA 4.0.
- OWASP Top 10:2025, aus OWASP/Top10: © 2003-2025 The OWASP® Foundation, Inc., lizenziert unter CC BY-SA 4.0. Die zehn Kategorien, ohne die Symbole. Änderungen: in das GRCA-Format umgewandelt, der Wortlaut unverändert. Diese Bearbeitungen stehen ebenfalls unter CC BY-SA 4.0. Die Namen der zugeordneten CWEs (Common Weakness Enumeration): © 2006–2026 The MITRE Corporation. MITRE erlaubt die Nutzung für Forschung, Entwicklung und kommerzielle Zwecke, wenn jede Kopie den Urheberrechtsvermerk und die Lizenz enthält; maßgeblich ist der englische Wortlaut der Lizenz oben und die CWE Terms of Use. CWE™ ist eine Marke der MITRE Corporation.
|