si-10-5-restrict-inputs-to-trusted-sources-and-approved-formats

name	SI-10(5)_restrict-inputs-to-trusted-sources-and-approved-formats
description	Restrict the use of information inputs to [organization-defined] and/or [organization-defined].
category	input-validation
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","si-10-5","si","enhancement"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-20"]
chains_with	["AC-3","AC-6"]
prerequisites	["SI-10"]
severity_boost	{"AC-3":"Chain with AC-3 for comprehensive security coverage","AC-6":"Chain with AC-6 for comprehensive security coverage"}

SI-10(5) Restrict Inputs to Trusted Sources and Approved Formats

Enhancement of: SI-10

High-Level Description

Family: System and Information Integrity (SI) Framework: NIST SP 800-53 Rev 5

Restricting the use of inputs to trusted sources and in trusted formats applies the concept of authorized or permitted software to information inputs. Specifying known trusted sources for information inputs and acceptable formats for such inputs can reduce the probability of malicious activity. The information inputs are those defined by the organization in the base control ( SI-10).

What to Check

• Verify SI-10(5) Restrict Inputs to Trusted Sources and Approved Formats is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for SI-10(5)
• Verify enhancement builds upon base control SI-10

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for SI-10(5) implementation details. Verify the organization has documented how this control is satisfied.

Step 2: Validate Implementation

# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null

Step 3: Test Operating Effectiveness

Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.

Tools

Tool	Purpose	Usage
cloud-audit-mcp	Check integrity monitoring	cloud_audit_monitoring
AWS CLI	Review GuardDuty/Inspector	aws guardduty list-detectors

Remediation Guide

Control Statement

Restrict the use of information inputs to [organization-defined] and/or [organization-defined].

Implementation Guidance

Restricting the use of inputs to trusted sources and in trusted formats applies the concept of authorized or permitted software to information inputs. Specifying known trusted sources for information inputs and acceptable formats for such inputs can reduce the probability of malicious activity. The information inputs are those defined by the organization in the base control ( ).