164.312(c)(2) Mechanism to Authenticate ePHI (Addressable)
164.312(c)(2) in HIPAA Security Rule (the HIPAA Security Rule as it currently stands). All HIPAA Security Rule controls held. Open HIPAA Security Rule on the standards site.
The control as we hold it
Mechanism to Authenticate ePHI (Addressable). Implement electronic mechanisms to corroborate that ePHI has not been altered or destroyed in an unauthorized manner. NIST recommends hash-based or signed integrity verification.
Reviewed and closest counterparts in the other frameworks
Reviewed rows come from a released pair; a closest match is the nearest held text and is not a reviewed row.
SOC 2
- SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11) (closest match)
- SOC2-CC6.1 CC6.1 Logical access security over protected information assets (closest match)
- SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary (closest match)
- SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software (closest match)
- SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities (closest match)
- SOC2-PI1.3 PI1.3 Controls over system processing (closest match)
NIST SP 800-53 Rev 5
- NIST800-SI-7 SI-7 Software, Firmware, and Information Integrity (closest match)
What an auditor commonly asks for
General guidance for this control area (domain: Technical), in our words, not a statement of the standard and not binding on an assessor.
- the unique-user and access-control records
- the audit-log configuration and review records
- the integrity and encryption records for ePHI in transit