+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.7 Other Browser Security Considerations

This section includes various other security controls and modern browser security features required for client-side browser security.

1. Yleiskatsaus

Otsikko Standardi
V3.7.1 Verify that the application only uses client-side technologies which are still supported and …

Verify that the application only uses client-side technologies which are still supported and considered secure. Examples of technologies which do not meet this requirement include NSAPI plugins, Flash, Shockwave, ActiveX, Silverlight, NACL, or client-side Java applets.

V3.7.2 Verify that the application will only automatically redirect the user to a different hostname or …

Verify that the application will only automatically redirect the user to a different hostname or domain (which is not controlled by the application) where the destination appears on an allowlist.

V3.7.3 Verify that the application shows a notification when the user is being redirected to a URL outside …

Verify that the application shows a notification when the user is being redirected to a URL outside of the application's control, with an option to cancel the navigation.

V3.7.4 Verify that the application's top-level domain (e.g., site.tld) is added to the public preload list …

Verify that the application's top-level domain (e.g., site.tld) is added to the public preload list for HTTP Strict Transport Security (HSTS). This ensures that the use of TLS for the application is built directly into the main browsers, rather than relying only on the Strict-Transport-Security response header field.

V3.7.5 Verify that the application behaves as documented (such as warning the user or blocking access) if …

Verify that the application behaves as documented (such as warning the user or blocking access) if the browser used to access the application does not support the expected security features.

1.1 Viittaukset

1.2 Tunnistetut vaatimukset

1.3 Liittyvät säädökset

2. Tunnistetut vaatimukset

Vaatimukset
Lähde Vaatimus

3. Liittyvät säädökset

Säädökset
Lähde Sääntely
  • 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.

    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.