# NIST SP 800-53 Rev. 5 SI-15 — Information Output Filtering

- Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-15-information-output-filtering
- Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › SI — System and Information Integrity
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**NIST SP 800-53 Rev. 5**·Control `SI-15`·high·Component: **System and Information Integrity**

## What this control requires

> Validate information output from specified software programs or applications to ensure it aligns with expected content, preventing attacks like SQL injections that can lead to unexpected output. This validation helps detect and filter out extraneous content, alerting monitoring tools to any anomalies. This control supports the Output Filtering, Threat Detection capability within the System and Information Integrity family.
> 
> — NIST SP 800-53 Rev. 5, Control SI-15

### In plain English

Validate information output from specified software programs or applications to ensure it aligns with expected content, preventing attacks like SQL injections that can lead to unexpected output. In practice, this means you can prove you information information-level controls on a defined cadence.

## Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

## What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within **System and Information Integrity**, the assessor will trace your implementation back to the catalogue reference (Control SI-15) and look for objective evidence on the latest two assessment cycles.

## How to implement

#### Endpoint Protection

**MDM.** Make MDM enrollment a hard gate for device access (Intune compliance + Conditional Access, or Jamf + Okta device trust). Unmanaged devices simply don't get a session token.

**EDR.** Deploy CrowdStrike / SentinelOne / Defender for Endpoint to every server and laptop; alert on any host that stops sending telemetry for >24h.

### Operational checklist

-   **Information.** Document the trigger, the owner and the cadence.
-   **Security.** Document the trigger, the owner and the cadence.
-   **Detection.** Document the trigger, the owner and the cadence.
-   **Validation.** Document the trigger, the owner and the cadence.
-   **Filter.** Document the trigger, the owner and the cadence.
-   **Scope:** information, system, application, threat, protection, software, capability, applications.

## Evidence to collect

-   **Edr Scan.** `edr_scan` evidence

EDR telemetry (CrowdStrike, Defender for Endpoint) confirms threat detection. Focus: Information Output Filtering.

## Common pitfalls

-   Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure.

## Related controls in NIST SP 800-53 Rev. 5

-   [**Control SI-4(13)** — Analyze Traffic And Event Patterns](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-4-13-analyze-traffic-and-event-patterns)
-   [**Control SI-4(14)** — Wireless Intrusion Detection](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-4-14-wireless-intrusion-detection)
-   [**Control SI-7(17)** — Runtime Application Self-Protection](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-7-17-runtime-application-self-protection)
-   [**Control SC-3(2)** — Access And Flow Control Functions](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-3-2-access-and-flow-control-functions)
-   [**Control SI-4(16)** — Correlate Monitoring Information](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-4-16-correlate-monitoring-information)
-   [**Control SI-7** — Software, Firmware, And Information Integrity](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-7-software-firmware-and-information-integrity)

## References

-   [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls)
-   Catalogue identifier: `Control SI-15`

Topics: application securitylogging monitoringedr xdrendpoint protectioncontinuous monitoringthreat intelligence

## Related compliance guidance

- [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs.
- [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement.
- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.