STIGhubSTIGhub
STIGsRMF ControlsCompare

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
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← SI-10 (3) — Information Input Validation

CCI-002754

Definition

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

Parent Control

SI-10 (3)Information Input ValidationSystem and Information Integrity

Linked STIG Checks (43)

V-279050CAT IIColdFusion must be configured with secure and approved server settings to enforce application hardening, input validation, error handling, and protection against common web vulnerabilities.Adobe ColdFusion Security Technical Implementation GuideV-205011CAT IIThe ALG must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.Application Layer Gateway Security Requirements GuideV-274714CAT IIThe API must use parameterized queries.Application Programming Interface (API) Security Requirements GuideV-274715CAT IIThe API must provide input validation.Application Programming Interface (API) Security Requirements GuideV-222609CAT IThe application must not be subject to input handling vulnerabilities.Application Security and Development Security Technical Implementation GuideV-204821CAT IIThe application server must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.Application Server Security Requirements GuideV-237402CAT IIThe CA API Gateway must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.CA API Gateway ALG Security Technical Implementation GuideV-251649CAT IIIDMS must check for invalid data and behave in a predictable manner when encountered.CA IDMS Security Technical Implementation GuideV-233228CAT IIThe container platform must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.Container Platform Security Requirements GuideV-233544CAT IIWhen invalid inputs are received, PostgreSQL must behave in a predictable and documented manner that reflects organizational and system objectives.Crunchy Data PostgreSQL Security Technical Implementation GuideV-261934CAT IIWhen invalid inputs are received, PostgreSQL must behave in a predictable and documented manner that reflects organizational and system objectives.Crunchy Data Postgres 16 Security Technical Implementation GuideV-206609CAT IIWhen invalid inputs are received, the DBMS must behave in a predictable and documented manner that reflects organizational and system objectives.Database Security Requirements GuideV-235778CAT IIThe audit log configuration level must be set to request in the Universal Control Plane (UCP) component of Docker Enterprise.Docker Enterprise 2.x Linux/UNIX Security Technical Implementation GuideV-235779CAT IIThe host operating systems auditing policies for the Docker Engine - Enterprise component of Docker Enterprise must be set.Docker Enterprise 2.x Linux/UNIX Security Technical Implementation GuideV-205220CAT IIThe DNS server implementation must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.Domain Name System (DNS) Security Requirements GuideV-224210CAT IIWhen invalid inputs are received, the EDB Postgres Advanced Server must behave in a predictable and documented manner that reflects organizational and system objectives.EDB Postgres Advanced Server v11 on Windows Security Technical Implementation GuideV-213635CAT IIWhen invalid inputs are received, the EDB Postgres Advanced Server must behave in a predictable and documented manner that reflects organizational and system objectives.EDB Postgres Advanced Server v9.6 Security Technical Implementation GuideV-259294CAT IIWhen invalid inputs are received, the EDB Postgres Advanced Server must behave in a predictable and documented manner that reflects organizational and system objectives.EnterpriseDB Postgres Advanced Server (EPAS) Security Technical Implementation GuideV-215736CAT IIThe BIG-IP APM module must be configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.F5 BIG-IP Access Policy Manager Security Technical Implementation GuideV-214502CAT IIThe BIG-IP AFM module must be configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.F5 BIG-IP Advanced Firewall Manager Security Technical Implementation GuideV-214514CAT IIThe BIG-IP ASM module must be configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.F5 BIG-IP Application Security Manager Security Technical Implementation GuideV-215795CAT IIThe BIG-IP Core implementation must be configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.F5 BIG-IP Local Traffic Manager Security Technical Implementation GuideV-203752CAT IIThe operating system must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.General Purpose Operating System Security Requirements GuideV-213733CAT IIWhen invalid inputs are received, DB2 must behave in a predictable and documented manner that reflects organizational and system objectives.IBM DB2 V10.5 LUW Security Technical Implementation GuideV-65281CAT IIThe DataPower Gateway must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.IBM DataPower ALG Security Technical Implementation GuideV-213789CAT IIWhen invalid inputs are received, SQL Server must behave in a predictable and documented manner that reflects organizational and system objectives.MS SQL Server 2014 Database Security Technical Implementation GuideV-205587CAT IIThe Mainframe Product must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.Mainframe Product Security Requirements GuideV-253743CAT IIWhen invalid inputs are received, MariaDB must behave in a predictable and documented manner that reflects organizational and system objectives.MariaDB Enterprise 10.x Security Technical Implementation GuideV-255323CAT IIWhen invalid inputs are received, the Azure SQL Database must behave in a predictable and documented manner that reflects organizational and system objectives.Microsoft Azure SQL Database Security Technical Implementation GuideV-276239CAT IIWhen invalid inputs are received, the Azure SQL Managed Instance must behave in a predictable and documented manner that reflects organizational and system objectives.Microsoft Azure SQL Managed Instance Security Technical Implementation GuideV-271362CAT IIWhen invalid inputs are received, the SQL Server must behave in a predictable and documented manner that reflects organizational and system objectives.Microsoft SQL Server 2022 Instance Security Technical Implementation GuideV-215639CAT IIThe Windows 2012 DNS Server must follow procedures to re-role a secondary name server as the master name server should the master name server permanently lose functionality.Microsoft Windows 2012 Server Domain Name System Security Technical Implementation GuideV-221199CAT IIWhen invalid inputs are received, MongoDB must behave in a predictable and documented manner that reflects organizational and system objectives.MongoDB Enterprise Advanced 3.x Security Technical Implementation GuideV-252181CAT IIWhen invalid inputs are received, MongoDB must behave in a predictable and documented manner that reflects organizational and system objectives.MongoDB Enterprise Advanced 4.x Security Technical Implementation GuideV-265950CAT IIWhen invalid inputs are received, MongoDB must behave in a predictable and documented manner that reflects organizational and system objectives.MongoDB Enterprise Advanced 7.x Security Technical Implementation GuideV-279390CAT IIWhen invalid inputs are received, MongoDB must behave in a predictable and documented manner that reflects organizational and system objectives.MongoDB Enterprise Advanced 8.x Security Technical Implementation GuideV-235195CAT IIWhen invalid inputs are received, the MySQL Database Server 8.0 must behave in a predictable and documented manner that reflects organizational and system objectives.Oracle MySQL 8.0 Security Technical Implementation GuideV-253529CAT IThe configuration integrity of the container platform must be ensured and runtime policies must be configured.Palo Alto Networks Prisma Cloud Compute Security Technical Implementation GuideV-214079CAT IIWhen invalid inputs are received, PostgreSQL must behave in a predictable and documented manner that reflects organizational and system objectives.PostgreSQL 9.x Security Technical Implementation GuideV-234596CAT IIThe UEM server must be configured to write to the server event log when invalid inputs are received.Unified Endpoint Management Server Security Requirements GuideV-240310CAT IIvRA PostgreSQL database must be configured to validate character encoding to UTF-8.VMW vRealize Automation 7.x PostgreSQL Security Technical Implementation GuideV-239811CAT IIWhen invalid inputs are received, the vROps PostgreSQL DB must behave in a predictable and documented manner that reflects organizational and system objectives.VMW vRealize Operations Manager 6.x PostgreSQL Security Technical Implementation GuideV-207502CAT IIThe VMM must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.Virtual Machine Manager Security Requirements Guide