Skip to content
Back to skills

Si 10 5 Restrict Inputs To Trusted

ASecurity

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

  • 3,518 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 3, 2026
securityrustgoawsgcpazuresecuritydocumentation

Works with

  • cli
  • mcp

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill si-10-5-restrict-inputs-to-trusted --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Si 10 5 Restrict Inputs To Trusted?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Si 10 5 Restrict Inputs To Trusted
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-si-10-5-restrict-inputs-to-trusted/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-si-10-5-restrict-inputs-to-trusted)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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](#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 ( [SI-10](#si-10)).

## Risk Assessment

| Finding                                                                          | Severity | Impact                                      |
| -------------------------------------------------------------------------------- | -------- | ------------------------------------------- |
| SI-10(5) Restrict Inputs to Trusted Sources and Approved Formats not implemented | High     | System and Information Integrity            |
| SI-10(5) partially implemented                                                   | Medium   | Incomplete System and Information Integrity |

## CWE Categories

| CWE ID | Title                     |
| ------ | ------------------------- |
| CWE-20 | Improper Input Validation |

## References

- [NIST SP 800-53 Rev 5 - SI-10(5)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=si-10.5)
- [NIST SP 800-53A Rev 5 (Assessment Procedures)](https://csrc.nist.gov/pubs/sp/800/53/a/r5/final)
- [NIST SP 800-53 Rev 5 Full Catalog](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final)

## Checklist

- [ ] Control documented in SSP
- [ ] Implementation evidence collected
- [ ] Operating effectiveness validated
- [ ] Continuous monitoring in place
- [ ] Related controls (AC-3, AC-6) reviewed

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in security →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.