STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to CA API Gateway ALG Security Technical Implementation Guide

V-237402

CAT II (Medium)

The CA API Gateway must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.

Rule ID

SV-237402r831427_rule

STIG

CA API Gateway ALG Security Technical Implementation Guide

Version

V1R3

CCIs

CCI-002754

Discussion

A common vulnerability of network elements is unpredictable behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state. The behavior will be derived from the organizational and system requirements and includes, but is not limited to, notification of the appropriate personnel, creating an audit record, and rejecting invalid input. The CA API Gateway must validate both XML and JSON schemas to verify valid inputs from a client requesting Registered Services. This helps to prevent XDoS attacks and parameter tampering, which in turn helps to prevent the injection of malicious scripts or content into the request.

Check Content

Open the CA API Gateway - Policy Manager and double-click all Registered Services required to validate inputs. 

Verify that either the "Validate XML Schema" or "Validate JSON Schema" Assertions have been added to the policies and that they have been configured in accordance with organizational requirements. 

If they have not, this is a finding.

Fix Text

Open the CA API Gateway - Policy Manager and double-click each of the Registered Services required to validate inputs that do not include a "Validate XML Schema" or Validate JSON Schema" Assertion. 

Add either the "Validate XML Schema" or "Validate JSON Schema" Assertion and configure in accordance with organizational requirements.