{"data":{"id":"SI-10","name":"Information Input Validation","family":"SI","family_name":"System and Information Integrity","withdrawn":false,"description":"Check the validity of the following information inputs: [Assignment: organization-defined information inputs to the system].","supplemental_guidance":"Checking the valid syntax and semantics of system inputs—including character set, length, numerical range, and acceptable values—verifies that inputs match specified definitions for format and content. For example, if the organization specifies that numerical values between 1-100 are the only acceptable inputs for a field in a given application, inputs of \"387,\"\"abc,\" or \"%K%\" are invalid inputs and are not accepted as input to the system. Valid inputs are likely to vary from field to field within a software application. Applications typically follow well-defined protocols that use structured messages (i.e., commands or queries) to communicate between software modules or system components. Structured messages can contain raw or unstructured data interspersed with metadata or control information. If software applications use attacker-supplied inputs to construct structured messages without properly encoding such messages, then the attacker could insert malicious commands or special characters that can cause the data to be interpreted as control information or metadata. Consequently, the module or component that receives the corrupted output will perform the wrong operations or otherwise interpret the data incorrectly. Prescreening inputs prior to passing them to interpreters prevents the content from being unintentionally interpreted as commands. Input validation ensures accurate and correct inputs and prevents attacks such as cross-site scripting and a variety of injection attacks.","enhancements":[{"id":"SI-10(01)","name":"Manual Override Capability","statement":"a. Provide a manual override capability for input validation of the following information inputs: [Assignment: organization-defined inputs defined in the base control (SI-10)];\nb. Restrict the use of the manual override capability to only [Assignment: organization-defined authorized individuals]; and\nc. Audit the use of the manual override capability.","baselines":[]},{"id":"SI-10(02)","name":"Review and Resolve Errors","statement":"Review and resolve input validation errors within [Assignment: organization-defined time period].","baselines":[]},{"id":"SI-10(03)","name":"Predictable Behavior","statement":"Verify that the system behaves in a predictable and documented manner when invalid inputs are received.","baselines":[]},{"id":"SI-10(04)","name":"Timing Interactions","statement":"Account for timing interactions among system components in determining appropriate responses for invalid inputs.","baselines":[]},{"id":"SI-10(05)","name":"Restrict Inputs to Trusted Sources and Approved Formats","statement":"Restrict the use of information inputs to [Assignment: organization-defined trusted sources] and/or [Assignment: organization-defined formats].","baselines":[]},{"id":"SI-10(06)","name":"Injection Prevention","statement":"Prevent untrusted data injections.","baselines":[]}],"baseline_low":false,"baseline_moderate":true,"baseline_high":true,"nist_800_53":{"rev5":{"id":"SI-10","name":"Information Input Validation","description":"Check the validity of the following information inputs: [Assignment: organization-defined information inputs to the system].","discussion":"Checking the valid syntax and semantics of system inputs—including character set, length, numerical range, and acceptable values—verifies that inputs match specified definitions for format and content. For example, if the organization specifies that numerical values between 1-100 are the only acceptable inputs for a field in a given application, inputs of \"387,\"\"abc,\" or \"%K%\" are invalid inputs and are not accepted as input to the system. Valid inputs are likely to vary from field to field within a software application. Applications typically follow well-defined protocols that use structured messages (i.e., commands or queries) to communicate between software modules or system components. Structured messages can contain raw or unstructured data interspersed with metadata or control information. If software applications use attacker-supplied inputs to construct structured messages without properly encoding such messages, then the attacker could insert malicious commands or special characters that can cause the data to be interpreted as control information or metadata. Consequently, the module or component that receives the corrupted output will perform the wrong operations or otherwise interpret the data incorrectly. Prescreening inputs prior to passing them to interpreters prevents the content from being unintentionally interpreted as commands. Input validation ensures accurate and correct inputs and prevents attacks such as cross-site scripting and a variety of injection attacks.","related_controls":[],"baseline_low":false,"baseline_moderate":true,"baseline_high":true,"baseline_privacy":false,"new_in_rev5":false,"changes_from_rev4":""}},"compliance_mappings":{"iso_27001_2022":[],"iso_27002_2022":[],"cobit_2019":["DSS06"],"pci_dss_v4":[],"nist_csf_2":["PR.DS-10"],"cis_controls_v8":[],"soc2_tsc":["CC6.6","CC6.6-POF2"],"finos_ccc":[],"iso_42001_2023":["A.7.2","A.7.4"],"iec_62443":["3-3 SR 3.5"],"asd_e8":[],"nis2":[],"apra_cps_234":[],"mas_trm":[],"pra_op_resilience":[],"bsi_grundschutz":["APP.3.1"],"anssi":["Hygiene.33","SecNumCloud.15.3"],"osfi_b13":["B-13.3.2"],"finma_circular":["IV.D(78)","IV.D(80)","IV.E(84)"],"gdpr":["Art.5(1)(d)"],"dora":["Art.9(4)(e)"],"bio2":[],"rbi_csf":["Annex1.6"],"fisc":["FISC.T5","FISC.T6","FISC.T8","FISC.T12"],"lgpd_bcb":["BCB.PIX"],"hkma_tme1":["TME1.3.2","TME1.10.1"],"mlps_2":[],"dnb_good_practice":[],"cra":["CRA.I.2f"],"swift_cscf":[],"cbb_tm":["TM-7"],"cbuae":["CR-6"],"nca_ecc":["2-14"],"sama_csf":["3.2"],"uae_ia":["T7"],"bog_cisd":["CISD-IX","CISD-SDLC"],"bom_ctrm":["3.13"],"cbe_csf":["CTO-4","CTO-5"],"cbn_csf":["Part5.2"],"popia":["s16"],"sa_js2":["JS2-SA"],"bcbs_239":["Principle 3","Principle 7"],"bot_cyber":["Ch2.5"],"ffiec_is":["II.C.17"],"hipaa_sr":["§164.312(c)(1)"],"iosco_cyber":["PROT-3","RR-3"],"sebi_cscrf":["PR.AS"],"cmmc_2":["SI"],"nerc_cip":[],"nrc_73_54":[],"tsa_psd":[],"ieee_1686":[],"ferc_cip":[],"doe_c2m2":[],"api_1164":[],"awia":[],"iaea_nss":[],"pci_pts":[],"fips_140":[],"cbest":[],"tiber_eu":[],"pci_hsm":[],"common_criteria":[],"isae_3402":["Clause 4"],"fca_sysc_13":["SYSC 13.7.1"],"fda_21_cfr_11":["§11.10(f)"],"fda_cyber":["ST-3"],"hitrust_csf":["10.b"],"iso_27799":[],"lloyds_ms":["BP2.2","MS1.1","MS2.1","MS5.1","MS6.1","MS13.2"],"naic_ds":[],"nhs_dspt":[],"pra_ss1_23":["P3.2","P4.3"],"solvency_ii":["Pillar3-Reporting"],"owasp_masvs_v2":["MASVS-CODE-4","MASVS-PLATFORM-1"],"csa_ccm_v4":[],"csa_aicm":[],"ccss_v9":[],"mica":["Art.68(1)","Art.69(1)","Art.76(1)"],"basel_sco60":["SCO60.66"],"bssc":[],"sec_custody_digital":[],"dpdpa":[],"nist_ai_rmf_1":["MAP 3.5","MEASURE 2.6"],"eu_ai_act":["Art.10(3)-(4)","Art.14(4)","Art.15(1)-(4)","Art.15(5)","Art.26(4)"]},"metadata":{"last_reviewed":"2026-10-03","review_notes":"2026-10-03: nist_csf_2 PR.DS-10 added from NIST's CSF 2.0 to SP 800-53 Rev 5.2.0 crosswalk (OLIR entry 186), which OSA's mapping now takes as its base. 2026-10-03: baselines LMH to -MH, from NIST SP 800-53B Release 5.2.0.","mapping_status":"complete"},"function":"preventative","used_by_patterns":["SP-002","SP-005","SP-012","SP-013","SP-023","SP-027","SP-028","SP-030","SP-041","SP-045","SP-047","SP-048","SP-049","SP-050","SP-051","SP-053","SP-054"],"attack":{"techniques":101,"route":"/api/v1/controls/SI-10?fields=attack"}}}