Requirement
Implement policies and procedures to protect electronic protected health information from improper alteration or destruction, with mechanisms to authenticate ePHI as an addressable specification.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Required element 1 — any one of
integrityalterationtamperunauthorised changeunauthorized change
Supporting terms — specificity signals
checksumhashversionimmutableaudit trailfile integrity monitoringdigital signature
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| GDPR | Art.5(1)(d) | Accuracy | integrity |
| SOC 2 | PI1.1 | Quality information about processing objectives and specifications | integrity |
| GDPR | Art.16 | Right to rectification | integrity |
| CCPA/CPRA | 1798.106 | Right to correct | integrity |
| PCI DSS 4.0.1 | 6.4.3 | Payment page scripts are authorised, inventoried and integrity-checked | integrity |
| PCI DSS 4.0.1 | 9.5 | Point-of-interaction devices are protected from tampering | integrity |
| PCI DSS 4.0.1 | 10.6 | Time synchronisation | integrity |
| PCI DSS 4.0.1 | 11.5 | Intrusion detection and change detection | integrity |