si-7-1-integrity-checks

name	SI-7(1)_integrity-checks
description	Perform an integrity check of [organization-defined] [organization-defined].
category	input-validation
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","si-7-1","si","enhancement"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-20"]
chains_with	[]
prerequisites	["SI-7"]
severity_boost	{}

SI-7(1) Integrity Checks

Enhancement of: SI-7

High-Level Description

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

Security-relevant events include the identification of new threats to which organizational systems are susceptible and the installation of new hardware, software, or firmware. Transitional states include system startup, restart, shutdown, and abort.

What to Check

• Verify SI-7(1) Integrity Checks is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for SI-7(1)
• Verify enhancement builds upon base control SI-7

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for SI-7(1) 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

Perform an integrity check of [organization-defined] [organization-defined].

Implementation Guidance

Security-relevant events include the identification of new threats to which organizational systems are susceptible and the installation of new hardware, software, or firmware. Transitional states include system startup, restart, shutdown, and abort.

Risk Assessment