Requirement
Implement hardware, software and procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information.
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
audit controlaudit logloggingrecord activitylog
Required element 2 — any one of
ephiphisystemaccess to records
Supporting terms — specificity signals
who accessedwhenretained6 yearstamperexaminesiembreak-the-glass alert
Contradiction markers
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
access to records is not logged
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| CCPA/CPRA | Regs (cybersecurity audits) | Annual independent cybersecurity audit | audit |
| SOC 2 | CC2.1 | Quality information for internal control | logging |
| SOC 2 | CC4.1 | Ongoing and separate evaluations | audit |
| SOC 2 | CC4.2 | Communication of deficiencies | audit |
| ISO 27001 | A.8.15 | Logging | logging |
| ISO 27001 | A.8.34 | Protection of information systems during audit testing | audit |
| PCI DSS 4.0.1 | 10.2 | Audit logs capture user activity and security events | logging |
| PCI DSS 4.0.1 | 10.5.1 | Audit log history retained for 12 months | logging |