STIGQter: STIG Summary: Application Programming Interface (API) Security Requirements Guide Version: 1 Release: 1 Benchmark Date: 11 Sep 2025:

The API must provide input validation.

DISA Rule

SV-274715r1143753_rule

Vulnerability Number

V-274715

Group Title

SRG-APP-000447

Rule Version

SRG-APP-000447-API-001035

Severity

CAT II

CCI(s)

• CCI-002754 - Verify that the system behaves in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.

Weight

10

Fix Recommendation

Follow best practice when accepting user input and verify all input is validated before the API processes the input.

Remediate identified vulnerabilities and obtain documented risk acceptance for those issues that cannot be remediated immediately.

Check Contents

Verify the API provides input validation.

Review the API documentation and interview the API administrator.
Review the API's input handling mechanisms at all exposed endpoints.

Identify all points where user input is accepted, including query parameters, headers, body content, and path variables.

Verify that input validation is implemented to enforce expected formats, data types, ranges, and lengths.

Ensure validation occurs on the server side, regardless of any client-side checks.

Check for validation against known-safe patterns or whitelists (e.g., regex, enumerated values) and proper rejection of malformed or unexpected input.

If input validation is missing, insufficient, or only enforced on the client side, this is a finding.is is a finding.

Vulnerability Number

V-274715

Documentable

False

Rule Version

SRG-APP-000447-API-001035

Severity Override Guidance

Verify the API provides input validation.

Review the API documentation and interview the API administrator.
Review the API's input handling mechanisms at all exposed endpoints.

Identify all points where user input is accepted, including query parameters, headers, body content, and path variables.

Verify that input validation is implemented to enforce expected formats, data types, ranges, and lengths.

Ensure validation occurs on the server side, regardless of any client-side checks.

Check for validation against known-safe patterns or whitelists (e.g., regex, enumerated values) and proper rejection of malformed or unexpected input.

If input validation is missing, insufficient, or only enforced on the client side, this is a finding.is is a finding.

Check Content Reference

M

Target Key

5703