DE.CM-09.288

Does your organization have a process to monitor hardware and software for signs of tampering?

Explanation

Hardware and software tampering can introduce unauthorized modifications, backdoors, or malicious code that compromise system integrity and security. Effective monitoring includes regular physical inspections of hardware seals/chassis, verification of firmware/software checksums, and automated tools that detect unexpected changes to system configurations or files. Evidence could include documented monitoring procedures, logs from tamper-detection systems, results from integrity verification tools (like Tripwire or AIDE), hardware inspection checklists, or reports from security information and event management (SIEM) systems that flag potential tampering events.

Implementation Example

Monitor hardware and software for signs of tampering

ID: DE.CM-09.288

Context

Function: DE: DETECT
Category: DE.CM: Continuous Monitoring
Sub-Category: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events

ResponseHub is the product I wish I had when I was a CTO

Previously I was co-founder and CTO of Progression, a VC backed HR-tech startup used by some of the biggest names in tech.

As our sales grew, security questionnaires quickly became one of my biggest pain-points. They were confusing, hard to delegate and arrived like London busses - 3 at a time!

I'm building ResponseHub so that other teams don't have to go through this. Leave the security questionnaires to us so you can get back to closing deals, shipping product and building your team.

Neil Cameron

Founder, ResponseHub