+V4.1 Generic Web Service Security
---+V4.1.1 Verify that every HTTP response with a message body contains a Content-Type header field that …
---+V4.1.2 Verify that only user-facing endpoints (intended for manual web-browser access) automatically …
---+V4.1.3 Verify that any HTTP header field used by the application and set by an intermediary layer, such as …
---+V4.1.4 Verify that only HTTP methods that are explicitly supported by the application or its API …
---+V4.1.5 Verify that per-message digital signatures are used to provide additional assurance on top of …

V4.1 Generic Web Service Security

This section addresses general web service security considerations and, consequently, basic web service hygiene practices.

1. Oversigt

Titel Standard
V4.1.1 Verify that every HTTP response with a message body contains a Content-Type header field that …

Verify that every HTTP response with a message body contains a Content-Type header field that matches the actual content of the response, including the charset parameter to specify safe character encoding (e.g., UTF-8, ISO-8859-1) according to IANA Media Types, such as "text/", "/+xml" and "/xml".

V4.1.2 Verify that only user-facing endpoints (intended for manual web-browser access) automatically …

Verify that only user-facing endpoints (intended for manual web-browser access) automatically redirect from HTTP to HTTPS, while other services or endpoints do not implement transparent redirects. This is to avoid a situation where a client is erroneously sending unencrypted HTTP requests, but since the requests are being automatically redirected to HTTPS, the leakage of sensitive data goes undiscovered.

V4.1.3 Verify that any HTTP header field used by the application and set by an intermediary layer, such as …

Verify that any HTTP header field used by the application and set by an intermediary layer, such as a load balancer, a web proxy, or a backend-for-frontend service, cannot be overridden by the end-user. Example headers might include X-Real-IP, X-Forwarded-*, or X-User-ID.

V4.1.4 Verify that only HTTP methods that are explicitly supported by the application or its API …

Verify that only HTTP methods that are explicitly supported by the application or its API (including OPTIONS during preflight requests) can be used and that unused methods are blocked.

V4.1.5 Verify that per-message digital signatures are used to provide additional assurance on top of …

Verify that per-message digital signatures are used to provide additional assurance on top of transport protections for requests or transactions which are highly sensitive or which traverse a number of systems.

1.1 Referencer

1.2 Identificerede krav

1.3 Relaterede reguleringer

2. Identificerede krav

Krav
Kilde Krav

3. Relaterede reguleringer

Reguleringer
Kilde Regulering
  • 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.