NIST SP 800-53 Rev 5
SI - System and Information Integrity

NIST SP 800-53 Rev 5 NIST800-SI-7: Software, firmware, and information integrity

Requires integrity verification tools to be employed to detect unauthorized changes to organization-defined software, firmware and information, and requires organization-defined actions to be taken when such unauthorized changes are detected.

What else in your programme already covers this

This control maps to 80 controls across 26 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected
  • NIST-CSF-PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected
  • NIST-CSF-PR.PS-05 Installation and execution of unauthorized software are prevented
  • NIST-CSF-RC.RP-03 The integrity of backups and other restoration assets is verified before using them for restoration
  • NIST-CSF-RC.RP-05 The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed
  • NIST-CSF-RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved

CIS Controls v8 · 6 controls

  • CIS-10.1 Deploy and Maintain Anti-Malware Software
  • CIS-10.5 Enable Anti-Exploitation Features
  • CIS-2.6 Allowlist Authorized Libraries
  • CIS-2.7 Allowlist Authorized Scripts
  • CIS-7.3 Perform Automated Operating System Patch Management
  • CIS-7.4 Perform Automated Application Patch Management

ISO 27002:2022 · 6 controls

  • 8.19 Installation of software on operational systems
  • 8.24 Use of cryptography
  • 8.25 Secure development life cycle
  • 8.29 Security testing in development and acceptance
  • 8.32 Change management
  • 8.7 Protection against malware

PCI DSS 4.0 · 6 controls

  • 10.3.4 File integrity or change detection on logs
  • 11.5.2 Change detection mechanism (FIM)
  • 11.6.1 Payment page change and tamper detection
  • 6.3.3 All system components are protected from known vulnerabilities by installing applicable security patches/updates as follows: • Patches/updates for critical vulnerabilities (identified according to the risk ranking process at Requirement 6.3.1) are installed within one
  • 6.4.3 All payment page scripts that are loaded and executed in the consumer's browser are managed as follows: • A method is implemented to confirm that each script is authorized. • A method is implemented
  • 8.6.2 Passwords/passphrases for any application and system accounts that can be used for interactive login are not hard coded in scripts, configuration/property files, or bespoke and custom source code

FedRAMP High · 5 controls

  • CM-7(5) Authorized Software Allow-by-Exception
  • SI-3 Malicious Code Protection
  • SI-7 Software, Firmware, and Information Integrity
  • SI-7(1) Integrity Checks
  • SI-7(7) Integration of Detection and Response

FedRAMP Moderate · 5 controls

  • CM-7(5) Authorized Software Allow-by-Exception
  • SI-3 Malicious Code Protection
  • SI-7 Software, Firmware, and Information Integrity
  • SI-7(1) Integrity Checks
  • SI-7(7) Integration of Detection and Response

ISO 27001:2022 · 5 controls

  • 8.19 Installation of software on operational systems
  • 8.25 Secure development life cycle
  • 8.28 Secure coding
  • 8.32 Change management
  • 8.8 Management of technical vulnerabilities

SOC 2 · 5 controls

  • SOC2-CC6.8 Controls to prevent or detect unauthorized or malicious software
  • SOC2-CC7.1 Detection and monitoring procedures for security events are in place
  • SOC2-CC8.1 Change management processes are in place
  • SOC2-PI1.3 System processing is complete, valid, accurate, timely, and authorized
  • SOC2-PI1.5 Inputs are processed completely, accurately, and timely for stored data

CMMC 2.0 · 4 controls

NIST SP 800-183 · 4 controls

NIST SP 800-172 · 3 controls

  • 3.14.1e Verify Integrity of Security Critical Software and Firmware
  • 3.14.4e Refresh Systems and Components from a Trusted Baseline
  • 3.14.7e Verify Correctness of Security Functions
  • CM-7(5) Authorized Software Allow-by-Exception
  • SI-3 Malicious Code Protection
  • SI-7 Software, Firmware, and Information Integrity
  • CM-7(5) Authorized Software Allow-by-Exception
  • SI-3 Malicious Code Protection
  • SI-7 Software, Firmware, and Information Integrity

HIPAA Security Rule · 2 controls

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

  • E8-MACRO-ML3 Configure Microsoft Office Macro Settings (ML3)
  • ASBv3-PV-4 Audit and enforce secure configurations for compute resources

C5 (Germany) · 1 control

  • C5-PSS-11 Images for Virtual Machines and Containers

ETSI EN 303 645 · 1 control

EU AI Act · 1 control

NIST SP 800-218 · 1 control

  • SI-3 Malicious Code Protection

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in SI - System and Information Integrity

You are reading one control. How much of NIST SP 800-53 Rev 5 have you already done?

NIST SP 800-53 Rev 5 NIST800-SI-7 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-53 Rev 5 your existing evidence covers. Hold ISO 27001:2022 and 163 of 300 NIST SP 800-53 Rev 5 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 342 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

The graph holds this control, the 80 it maps to, and the evidence behind each claim, over MCP and REST.