SI-1 Policy and procedures
The system and information integrity policy and procedures: ownership, scope, review frequency and how this -1 control governs patching, malware protection, monitoring and integrity controls in the SI family.

System and information integrity family: flaw remediation, malicious code protection, system monitoring, security alerts, integrity verification, input validation, error handling, information retention and PII quality and de-identification.
The system and information integrity policy and procedures: ownership, scope, review frequency and how this -1 control governs patching, malware protection, monitoring and integrity controls in the SI family.
Flaw remediation: finding, testing and installing patches within defined timeframes, automated flaw remediation status, and the root cause analysis enhancement added in Release 5.2.0.
Malicious code protection: anti-malware at endpoints and network entry and exit points, update cadence, scan configuration, response actions and false positive handling. A FedRAMP annual assessment control.
System monitoring: intrusion detection, monitoring objectives, sensor placement, event analysis and alerting. It has the most enhancements in the SI family and is mapped to many FedRAMP 20x Key Security Indicators.
Security alerts, advisories and directives: subscribing to sources such as CISA, distributing alerts internally and acting on binding directives within required timeframes.
Security and privacy function verification: automated self-tests that confirm security functions work, with alerting and defined responses to failures. High baseline under NIST, but required by FedRAMP at Classes C and D.
Software, firmware and information integrity: integrity checking, file integrity monitoring, code signing and boot verification, including the SI-7(12) enhancement revised in Release 5.2.0.
Spam protection: filtering unsolicited email at entry and exit points and keeping filters updated, plus FedRAMP's DMARC expectation for providers that send email on behalf of the government.
Information input validation: checking syntax and semantics of inputs to prevent injection and similar attacks, with enhancements for manual override, review of errors and predictable behavior. A FedRAMP annual assessment control at Classes C and D.
Error handling: error messages that help users and administrators without leaking stack traces, credentials or system details to attackers. In the moderate and high baselines.
Information management and retention: keeping and disposing of information according to legal and operational requirements, with enhancements to limit PII elements and minimize PII in testing.
Predictable failure prevention: tracking mean time to failure and preparing standby components so failures are replaced before they cause outages. Not in any SP 800-53B baseline.
Non-persistence: rebuilding components from a known state on a schedule or per session, for example by reimaging or using virtualization, so attackers cannot persist. Not in any baseline.
Information output filtering: checking application output for unexpected content that could indicate compromise or data leakage. Not in any SP 800-53B baseline.
Memory protection: data execution prevention, address space layout randomization and similar protections against code execution in memory. In the moderate and high baselines.
Fail-safe procedures: predefined responses to failure conditions, such as alerting operators or shutting down safely, distinct from SC-24's known-state failure. Not in any SP 800-53B baseline.
PII quality operations: checking and correcting the accuracy, relevance, timeliness and completeness of personal data. Assigned only to the SP 800-53B privacy baseline.
De-identification: removing identifiers from datasets and testing that the result cannot be re-identified, with enhancements for statistical disclosure control and differential privacy. Privacy baseline only.
Tainting: embedding markers or capabilities in data so exfiltration or improper removal can be detected. Not in any SP 800-53B baseline.
Information refresh: regenerating or deleting information on a schedule to limit how long stale or compromised information can be exploited. Not in any SP 800-53B baseline.
Information diversity: alternative information sources that essential functions can switch to when the primary source is corrupted or unavailable. Not in any SP 800-53B baseline.
Information fragmentation: splitting sensitive information across systems so compromise of one component does not expose it all. Not in any SP 800-53B baseline.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.