+V4 API and Web Service
---+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.2 HTTP Message Structure Validation
------+V4.2.1 Verify that all application components (including load balancers, firewalls, and application …
------+V4.2.2 Verify that when generating HTTP messages, the Content-Length header field does not conflict with …
------+V4.2.3 Verify that the application does not send nor accept HTTP/2 or HTTP/3 messages with …
------+V4.2.4 Verify that the application only accepts HTTP/2 and HTTP/3 requests where the header fields and …
------+V4.2.5 Verify that, if the application (backend or frontend) builds and sends requests, it uses …
---+V4.3 GraphQL
------+V4.3.1 Verify that a query allowlist, depth limiting, amount limiting, or query cost analysis is used to …
------+V4.3.2 Verify that GraphQL introspection queries are disabled in the production environment unless the …
---+V4.4 WebSocket
------+V4.4.1 Verify that WebSocket over TLS (WSS) is used for all WebSocket connections.
------+V4.4.2 Verify that, during the initial HTTP WebSocket handshake, the Origin header field is checked …
------+V4.4.3 Verify that, if the application's standard session management cannot be used, dedicated tokens are …
------+V4.4.4 Verify that dedicated WebSocket session management tokens are initially obtained or validated …

V4 API and Web Service

Control Objective

Several considerations apply specifically to applications that expose APIs for use by web browsers or other consumers (commonly using JSON, XML, or GraphQL). This chapter covers the relevant security configurations and mechanisms that should be applied.

Note that authentication, session management, and input validation concerns from other chapters also apply to APIs, so this chapter cannot be taken out of context or tested in isolation.

References

For more information, see also:

1. Pārskats

Nosaukums Standarts
V4.1 Generic Web Service Security

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

V4.2 HTTP Message Structure Validation

This section explains how the structure and header fields of an HTTP message should be validated to prevent attacks such as request smuggling, response splitting, header injection, and denial of service via overly long HTTP messages.

These requirements are relevant for general HTTP message processing and generation, but are especially important when converting HTTP messages between different HTTP versions.

V4.3 GraphQL

GraphQL is becoming more common as a way of creating data-rich clients that are not tightly coupled to a variety of backend services. This section covers security considerations for GraphQL.

V4.4 WebSocket

WebSocket is a communications protocol that provides a simultaneous two-way communication channel over a single TCP connection. It was standardized by the IETF as RFC 6455 in 2011 and is distinct from HTTP, even though it is designed to work over HTTP ports 443 and 80.

This section provides key security requirements to prevent attacks related to communication security and session management that specifically exploit this real-time communication channel.

1.1 Atsauces

1.2 Identificētās prasības

1.3 Saistītie tiesību akti

2. Identificētās prasības

Prasības
Avots Prasība

3. Saistītie tiesību akti

Tiesību akti
Avots Regulējums
  • 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.