
us-hipaa-security
HIPAA Security Rule (45 CFR Part 164, Subpart C) for ePHI protection with Administrative, Physical, and Technical Safeguards
- version
- 0.1.0
- GitHub stars
- 436
Install
/plugin install us-hipaa-security@grc-engineering-suiteRun it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.
Contents
Discovered from sourceSkills 1
HIPAA Security Rule Expert
Deep expertise in the Health Insurance Portability and Accountability Act (HIPAA) Security Rule - the U.S. federal regulation governing the protection of electronic Protected Health Information (ePHI).
Expertise Areas
HIPAA Security Rule Overview
Regulatory Citation: 45 CFR Part 164, Subpart C (Security Standards for the Protection of Electronic Protected Health Information) Effective Date: April 21, 2003 (Compliance Date: April 20, 2005) Enforcement: U.S. Department of Health and Human Services (HHS) - Office for Civil Rights (OCR) Guidance Document: NIST SP 800-66 Rev. 2 (An Introductory Resource Guide for Implementing the HIPAA Security Rule)
Scope:
- Applies to electronic PHI (ePHI) only - not paper records or oral communications
- Covered Entities (CEs): Healthcare providers, health plans, healthcare clearinghouses that transmit ePHI
- Business Associates (BAs): Vendors/contractors who create, receive, maintain, or transmit ePHI on behalf of CEs (e.g., cloud providers, EHR vendors, billing companies, data analytics firms)
- Subcontractors: BAs must have contracts with their own subcontractors
What is ePHI?
- Individually identifiable health information in electronic form
- Includes any demographic information collected from an individual that:
- Relates to physical/mental health condition
- Relates to provision of healthcare
- Relates to payment for healthcare
- 18 HIPAA identifiers (names, dates, medical record numbers, etc.) + health information
Enforcement and Penalties
OCR Enforcement Triggers:
- Breach Reports: Unsecured ePHI affecting 500+ individuals (must report to OCR within 60 days)
- Complaints: Patients/employees filing complaints with OCR
- Desk Audits: OCR requests documentation remotely
- On-Site Audits: Comprehensive compliance reviews
- Media Reports: News of breaches or violations
Penalty Tiers (per violation category per year):
- Tier 1: Lack of knowledge (reasonable diligence would not have known) - Minimum $100 per violation, max $25,000
- Tier 2: Reasonable cause (not willful neglect) - Minimum $1,000 per violation, max $100,000
- Tier 3: Willful neglect corrected within 30 days - Minimum $10,000 per violation, max $250,000
- Tier 4: Willful neglect not corrected - Minimum $50,000 per violation, max $1.9 million
Note: "Per violation category" means penalties are capped annually, not per individual breach event.
The Five Safeguard Categories
1. Administrative Safeguards (45 CFR §164.308)
What It Governs: Administrative actions, policies, and procedures to manage the selection, development, implementation, and maintenance of security measures.
Key Standards/Implementation Specifications:
- Security Management Process (§164.308(a)(1)): Risk analysis, risk management, sanction policy, information system activity review
- Assigned Security Responsibility (§164.308(a)(2)): Designated security official with authority and responsibility
- Workforce Security (§164.308(a)(3)): Clearance procedures, termination procedures
- Information Access Management (§164.308(a)(4)): Access authorization, access establishment/modification, access termination/suspension
- Security Awareness and Training (§164.308(a)(5)): Reminders, protection from malicious software, login monitoring, password management
- Security Incident Procedures (§164.308(a)(6)): Response and reporting, documented incident responses
- Contingency Plan (§164.308(a)(7)): Data backup, disaster recovery, emergency mode operation, testing and revision
- Evaluation (§164.308(a)(8)): Periodic technical and non-technical evaluation
- Business Associate Contracts and Other Arrangements (§164.308(b)(1)): Written contracts or other arrangements with BAs
Typical Evidence: Security policies, risk analysis documentation, training records, incident response logs, disaster recovery plans, BAAs
2. Physical Safeguards (45 CFR §164.310)
What It Governs: Physical measures to protect electronic information systems and related buildings and equipment from natural and environmental hazards, and unauthorized intrusion.
Key Standards/Implementation Specifications:
- Facility Access Controls (§164.310(a)(1)): Contingency operations, facility security plan, access control and validation, maintenance records
- Workstation Use (§164.310(b)): Policies specifying proper workstation use for ePHI
- Workstation Security (§164.310(c)): Physical safeguards for workstations that access ePHI
- Device and Media Controls (§164.310(d)(1)): Disposal, media re-use, accountability, data backup and storage
Typical Evidence: Facility access logs, visitor logs, workstation security policies, media disposal records, backup storage documentation
3. Technical Safeguards (45 CFR §164.312)
What It Governs: Technology and related policies/procedures that protect ePHI and control access to it.
Key Standards/Implementation Specifications:
- Access Control (§164.312(a)(1)): Unique user identification, emergency access procedure, automatic logoff, encryption and decryption
- Audit Controls (§164.312(b)): Hardware/software/ procedural mechanisms that record and examine activity in information systems
- Integrity (§164.312(c)(1)): Mechanisms to protect ePHI from improper alteration or destruction
- Person or Entity Authentication (§164.312(d)): Verify identity of person/entity seeking access to ePHI
- Transmission Security (§164.312(e)(1)): Encryption of ePHI whenever appropriate over electronic networks
Typical Evidence: Access control logs, audit logs/reports, encryption configuration evidence, authentication documentation
4. Organizational Requirements (45 CFR §164.314)
What It Governs: Business Associate Agreements and group health plan requirements.
Key Standards/Implementation Specifications:
- Business Associate Agreements (§164.314(a)(1)): Written contract between CE and BA specifying permitted/required uses, safeguards, reporting, and BA obligations to subcontractors
- Business Associate Agreements - Group Health Plans (§164.314(b)(1)): Plan documents must provide that the plan sponsor will adequately safeguard ePHI
Typical Evidence: Executed BAAs, BAA templates, subcontractor agreements
5. Policies, Procedures, and Documentation (45 CFR §164.316)
What It Governs: Reasonable and appropriate policies, procedures, and documentation to comply with the Security Rule.
Key Standards/Implementation Specifications:
- Policies and Procedures (§164.316(a)(1)): Comply with standards, implementation specifications, and other requirements
- Documentation (§164.316(b)(1)-(2)): Maintain policies and procedures for 6 years from date of creation or last effective date, whichever is later
Typical Evidence: Written security policies, policy review/approval records, documentation retention evidence
Required vs. Addressable Implementation Specifications
Understanding the Distinction:
HIPAA Security Rule implementation specifications are categorized as either Required or Addressable. This distinction is critical for compliance.
Required Specifications:
- Must be implemented exactly as stated in the regulation
- No alternative options available
- Non-compliance is a direct violation
Addressable Specifications:
- Must implement UNLESS:
- The specification is not reasonable and appropriate for your organization, AND
- You document why it is not reasonable and appropriate, AND
- You implement an equivalent alternative measure, OR
- Document why nothing is appropriate and implement nothing
Important: "Addressable" does NOT mean "optional." It means you must assess whether it applies and justify your decision.
Examples of Addressable Specifications:
-
Encryption/Decryption of ePHI at Rest (§164.312(a)(2)(iv))
- Why addressable: Legacy systems may not support encryption
- Alternative: Compensating controls like strong access controls, physical security, or network segmentation
- Documentation must explain why encryption is not reasonable/appropriate
-
Automatic Logoff (§164.312(a)(2)(iii))
- Why addressable: May interfere with clinical workflows
- Alternative: Manual session timeout policies, physical workstation controls
- Documentation must explain why automatic logoff disrupts operations
-
Encryption in Transmission (§164.312(e)(2)(ii))
- Why addressable: Some legacy healthcare systems don't support TLS
- Alternative: VPN tunnels, dedicated circuits, or network segmentation
- Documentation must explain why transmission encryption is not feasible
-
Workstation Security (§164.310(c))
- Why addressable: Some clinical areas require mobile workstations
- Alternative: Privacy screens, workstation positioning policies, cable locks
- Documentation must explain environmental constraints
-
Media Disposal (§164.310(d)(2)(i))
- Why addressable: Some media cannot be destroyed (e.g., records on legal hold)
- Alternative: Purging/sanitization (NIST SP 800-88 guidelines), secure storage
- Documentation must explain why destruction is not appropriate
-
Password Management (§164.308(a)(5)(ii)(D))
- Why addressable: Some organizations use alternative authentication
- Alternative: Biometrics, smart cards, certificates, or other multi-factor methods
- Documentation must explain why passwords are not used
Best Practice for Addressable Specs:
- Conduct an organization-wide assessment
- For each addressable spec, document:
- Whether you implement it as-is
- If not, why it is not reasonable/appropriate (cost, technical feasibility, operational impact)
- What alternative you implemented instead
- How the alternative provides equivalent protection
- Review annually as technology and operations evolve
Risk Analysis (§164.308(a)(1)(ii)(A)) - The Linchpin
Why It's Critical:
The risk analysis is the foundation of every HIPAA Security Rule compliance program. It is the most frequently cited requirement in OCR Resolution Agreements and enforcement actions.
What a Defensible Risk Analysis Includes:
-
ePHI Scope and Data Flow Inventory:
- Map all systems that create, receive, maintain, or transmit ePHI
- Document data flows between systems
- Identify all external connections (internet-facing systems, VPNs, BAs)
- Catalog storage locations (databases, file servers, cloud storage, mobile devices)
-
Threat and Vulnerability Identification:
- External threats (hackers, malware, ransomware)
- Internal threats (insider misuse, accidental disclosure)
- Environmental threats (natural disasters, power outages)
- System vulnerabilities (unpatched software, weak configurations)
-
Likelihood and Impact Assessment:
- Rate likelihood of each threat materializing (high/medium/low)
- Assess potential impact (e.g., number of patients affected, clinical disruption, financial harm)
- Combine to determine risk level (critical/high/medium/low)
-
Current Control Evaluation:
- Document existing safeguards for each identified risk
- Assess whether controls are adequate or need improvement
- Identify gaps where controls are missing or insufficient
-
Risk Level Determination:
- Assign final risk ratings based on likelihood × impact × existing controls
- Prioritize risks for remediation
-
Risk Management/Mitigation Plan:
- Document remediation actions for high/critical risks
- Assign timelines, owners, and resources
- Implement mitigation measures
- Reassess residual risk after mitigation
Common OCR Findings:
- "Failure to conduct an adequate risk analysis" - Most common enforcement finding
- Risk analysis limited to certain systems or locations (not "organization-wide")
- Risk analysis not updated after significant changes (new systems, mergers, breaches)
- Risk analysis not documented or lacks specificity
- Risk analysis does not address all threats to ePHI
Best Practices:
- Use NIST SP 800-30 (Risk Assessment) as a methodology guide
- Update annually or after significant changes
- Maintain documentation for 6 years
- Obtain senior management sign-off
- Use risk analysis results to inform security policies and budget
Business Associate Agreements (BAAs)
When a BAA is Required:
A BAA is required when a Covered Entity or Business Associate:
- Creates, receives, maintains, or transmits ePHI on behalf of another CE or BA
- Provides services that involve access to ePHI
Common Examples Requiring BAAs:
- Cloud service providers (AWS, Azure, GCP, Salesforce, etc.)
- EHR/EMR software vendors (Epic, Cerner, etc.)
- Medical billing/claims clearinghouses
- Data analytics firms
- IT managed service providers
- Shredding/document disposal companies
- Email/calendar/office productivity services (Microsoft 365, Google Workspace)
- Fax/telecommunications services
- Transcription/medical scribe services
- Health information exchanges
What a BAA Must Obligate the BA to Do (§164.314(a)(2)(i)):
- Implement Appropriate Safeguards: Ensure ePHI is protected per Security Rule requirements
- Report Breaches: Notify CE of any security incident or breach (within 60 days for 500+ individuals)
- Report Security Violations: Inform CE of any Security Rule violations by subcontractors
- Authorize CE Access: Allow CE or OCR to access BAA and related records
- Ensure Subcontractor Compliance: Require subcontractors to agree to same restrictions (via BAAs)
Common BAA Failure Modes:
- Missing BAAs: Cloud services or SaaS vendors used without signed BAAs
- Incomplete BAAs: BAA lacks required provisions or is outdated
- Subcontractor Chains: BA's subcontractors don't have their own BAAs
- Oral Agreements: BAAs must be in writing
- Vendor-Provided Templates: Using vendor templates that don't meet HIPAA requirements
BAA vs. Other Agreements:
- Data Use Agreement (DUA): Often separate from BAA, covers specific research uses
- Non-Disclosure Agreement (NDA): Not sufficient - does not cover HIPAA Security Rule requirements
- Service Level Agreement (SLA): Covers uptime/performance, not ePHI protection
SCF Crosswalk Context
Framework Mapping: This HIPAA Security Rule plugin maps to SCF ID usa-federal-law-hipaa-security-rule-2013.
The /grc-engineer:gap-assessment command supports this framework via SCF crosswalk.
Key SCF Domain Overlaps:
- PRI (Data Privacy): ePHI handling, minimum necessary, disclosure prohibitions
- IAC (Identity and Access Control): Unique user IDs, access authorization, least privilege
- IRO (Incident Response Operations): Security incident procedures, breach notification
- CPL (Contingency Planning): Data backup, disaster recovery, emergency mode operation
- RSK (Risk Management): Risk analysis, risk management, evaluation
- CFG (Configuration Management): System configuration, change management, security settings
- PES (Physical Environment Security): Facility access controls, workstation security, media controls
When Using /grc-engineer:gap-assessment:
/grc-engineer:gap-assessment HIPAA
This will map HIPAA Security Rule requirements to SCF controls and generate findings grouped by safeguard category.
Assessment Approach Guidance
When performing a HIPAA Security Rule assessment:
a. Confirm Entity Type:
- Covered Entity: Healthcare provider, health plan, or healthcare clearinghouse
- Business Associate: Vendor that handles ePHI on behalf of a CE
- Hybrid Organization: Single legal entity that is both a CE and a BA (must designate which components are which)
- Associate Subcontractor: BA's subcontractor handling ePHI
b. Confirm ePHI Systems in Scope:
- Clinical Systems: EHR/EMR, electronic prescribing, telehealth platforms
- Administrative Systems: Claims processing, billing, revenue cycle management
- Patient-Facing Systems: Patient portals, mobile health apps, remote monitoring devices
- Data Platforms: Data warehouses, health information exchanges, analytics platforms
- Infrastructure: Cloud storage (S3, Azure Blob, GCS), databases, file servers
- Endpoints: Workstations, laptops, mobile devices, tablets
- Communication: Email systems, fax servers, secure messaging platforms
c. Ask for Recent Risk Analysis:
- Date of last organization-wide risk analysis
- Whether it covers all ePHI systems and locations
- Whether it's been updated since major changes (new systems, mergers, breaches)
- Whether senior management has approved it
- Whether high/critical risks have been addressed
d. Identify Breach History or OCR Investigations:
- Any past ePHI breaches (investigation findings, remediation completed)
- Any OCR complaints or investigations (findings, corrective action plans)
- Any state attorney general actions
- Lessons learned and improvements implemented
e. Surface Addressable Specification Implementation Status:
- For each addressable spec, check:
- Is it implemented as-is?
- If not, is there documented rationale explaining why it's not reasonable/appropriate?
- Is there an equivalent alternative measure?
- Is the documentation up-to-date and signed off?
Common Addressable Spec Gaps:
- Encryption at rest not enabled for databases or cloud storage
- Automatic logoff not configured for workstations
- Encryption in transit not enforced for all external connections
- Media disposal procedures not documented or followed
- Password management not formalized (written policy)
f. Flag Missing Business Associate Agreements:
- Cloud providers (AWS, Azure, GCP) - check for BAA addendum
- SaaS applications (Office 365, Google Workspace, Salesforce, etc.)
- EHR/EMR vendors
- IT service providers (MSPs, managed security, help desk)
- Billing/clearinghouse services
- Data analytics/analytics vendors
- Email/fax/telecommunication services
- Shredding/disposal vendors
- Health information exchanges
- Mobile app/telehealth platforms
Note: Even vendors that claim HIPAA compliance often require you to execute their BAA separately - check each vendor's process.
Capabilities
- HIPAA Security Rule gap assessments and analysis
- Risk analysis evaluation (§164.308(a)(1)(ii)(A))
- Required vs. addressable specification assessment
- Administrative, Physical, and Technical Safeguard evaluation
- Business Associate Agreement readiness review
- ePHI system scope identification
- Security incident and breach response evaluation
- Contingency plan review (backup/disaster recovery)
- Security awareness and training assessment
- Access control and authentication evaluation
- Encryption at rest and in transit review
- Audit control implementation validation
- Physical security measures assessment
- Policy and procedure documentation review
- OCR enforcement and penalty guidance
- HHS OCR audit preparation
- NIST SP 800-66 implementation guidance
- SCF crosswalk mapping (usa-federal-law-hipaa-security-rule-2013)
- Multi-framework compliance analysis (HIPAA + PCI-DSS, NIST, etc.)
Evidence Checklist Command
The /us-hipaa-security:evidence-checklist command generates comprehensive evidence request lists organized by safeguard category:
Category Short Codes (use with --category flag):
admin- Administrative Safeguards (§164.308)physical- Physical Safeguards (§164.310)technical- Technical Safeguards (§164.312)org- Organizational Requirements (§164.314)policies- Policies and Documentation (§164.316)
Usage Examples:
/us-hipaa-security:evidence-checklist # All categories (default)
/us-hipaa-security:evidence-checklist --category=admin # Administrative only
/us-hipaa-security:evidence-checklist --format=csv # Export to spreadsheet
/us-hipaa-security:evidence-checklist --audience=internal # Simplified checklist
Output Formats: table (default Markdown table), markdown (detailed list), csv (spreadsheet)
Audience Options: auditor (external/OCR with CFR references), internal (simplified readiness check)
Commands 2
HIPAA Security Rule Assessment
Run a comprehensive gap assessment of the HIPAA Security Rule (45 CFR Part 164, Subpart C) against the SCF crosswalk for usa-federal-law-hipaa-security-rule-2013.
Usage
/us-hipaa-security:assess [--scope=<category>]
Arguments
--scope: Optional safeguard category to limit assessment scopeadministrative- Administrative Safeguards only (§164.308)physical- Physical Safeguards only (§164.310)technical- Technical Safeguards only (§164.312)organizational- Organizational Requirements only (§164.314)policies- Policies & Documentation only (§164.316)- Default: All five categories
Pre-Assessment Confirmation
Before starting the assessment, confirm the following with the user:
-
Entity Type: Are you a Covered Entity (healthcare provider, health plan, clearinghouse) or Business Associate (vendor handling ePHI on behalf of a CE)?
-
ePHI Systems in Scope: What systems handle electronic Protected Health Information?
- Clinical systems (EHR/EMR, e-prescribing)
- Administrative systems (billing, claims, RCM)
- Patient-facing systems (portals, telehealth, mobile apps)
- Data platforms (warehouses, HIEs, analytics)
- Cloud infrastructure (AWS, Azure, GCP)
- Endpoints (workstations, laptops, mobile devices)
-
Risk Analysis Status: When was your last organization-wide risk analysis conducted (required under §164.308(a)(1)(ii)(A))? Does it cover all ePHI systems?
-
Enforcement History: Any prior OCR investigations, breaches, or enforcement actions?
How It Works
This command routes to /grc-engineer:gap-assessment HIPAA and leverages the SCF crosswalk to map HIPAA Security Rule implementation specifications to standardized compliance controls.
Assessment Output
The assessment generates findings grouped by safeguard category:
Administrative Safeguards (§164.308)
| Control Reference | CFR Section | SCF Control ID | Current Status | Risk Level | Recommended Remediation | Req/Addr |
|---|---|---|---|---|---|---|
| Example: Risk Analysis | §164.308(a)(1)(ii)(A) | PRI-01 | Gap | Critical | Conduct organization-wide risk analysis covering all ePHI systems | Required |
| Example: Security Awareness Training | §164.308(a)(5)(i) | CFG-02 | Partially | High | Implement formal training program with completion tracking | Required |
| Example: Encryption at Rest | §164.312(a)(2)(iv) | IAC-08 | Implemented | Low | Continue current implementation | Addressable |
Status Categories:
- Implemented: Fully compliant with no identified gaps
- Partially: Partially compliant but requires improvement
- Gap: Not implemented - non-compliant
- N/A: Not applicable to organization's scope
Risk Levels:
- Critical: Immediate violation, blocks audit, high likelihood of OCR enforcement
- High: Serious gap, should remediate before audit
- Medium: Important improvement
- Low: Best practice recommendation
Req/Addr Column:
- Required: Must implement exactly as stated
- Addressable: Must implement, document equivalent alternative, or document rationale
Physical Safeguards (§164.310)
Same format as Administrative Safeguards, covering:
- Facility Access Controls
- Workstation Use
- Workstation Security
- Device and Media Controls
Technical Safeguards (§164.312)
Same format, covering:
- Access Control (unique user IDs, emergency access, automatic logoff, encryption)
- Audit Controls
- Integrity
- Authentication
- Transmission Security
Organizational Requirements (§164.314)
Same format, covering:
- Business Associate Agreements
- Group Health Plan requirements
Policies & Documentation (§164.316)
Same format, covering:
- Written policies and procedures
- Documentation retention (6 years)
Remediating Addressable Specifications
For any Addressable implementation specifications marked as "Gap" or "Partially":
-
Document Rationale: Explain why the specification is not reasonable and appropriate for your organization
- Cost considerations
- Technical feasibility issues
- Operational impact on clinical workflows
- Environmental constraints
-
Implement Equivalent Alternative (if applicable):
- Identify alternative control providing equivalent protection
- Document how alternative achieves same security objective
- Implement and test the alternative
-
Maintain Documentation:
- Keep assessment and rationale for 6 years
- Review annually as technology and operations evolve
- Update if circumstances change
Examples
# Full HIPAA Security Rule assessment (all categories)
/us-hipaa-security:assess
# Assessment limited to Administrative Safeguards only
/us-hipaa-security:assess --scope=administrative
# Assessment focused on Technical Safeguards
/us-hipaa-security:assess --scope=technical
SCF Crosswalk
This assessment leverages the Secure Controls Framework (SCF) crosswalk for usa-federal-law-hipaa-security-rule-2013, which maps HIPAA Security Rule implementation specifications to standardized SCF controls.
SCF ID: usa-federal-law-hipaa-security-rule-2013 Regulator: US HHS OCR Region: Americas Depth: Reference (tier 2 of 3)
Related Commands
/us-hipaa-security:evidence-checklist- Generate evidence request list for audits/grc-engineer:gap-assessment- Direct access to gap assessment with framework options
Common Findings
Based on OCR enforcement actions and Resolution Agreements, the most common HIPAA Security Rule gaps include:
- Inadequate Risk Analysis (§164.308(a)(1)(ii)(A)) - Not organization-wide, not updated, lacks specificity
- Missing Business Associate Agreements (§164.308(b)(1)) - Cloud providers, SaaS vendors without BAAs
- Insufficient Access Controls (§164.312(a)(1)) - Shared accounts, lack of unique user IDs
- Incomplete ePHI Inventory - Systems handling ePHI not identified or documented
- Missing or Outdated Policies (§164.316(a)) - No written policies, policies not updated
- Lack of Encryption (§164.312(a)(2)(iv)) - Addressable but not implemented or documented
- Insufficient Audit Controls (§164.312(b)) - No audit logging or review procedures
- Incomplete Contingency Planning (§164.308(a)(7)) - No disaster recovery plan, untested backups
Enforcement Context
OCR Audit Priorities (based on publicly available information):
- Risk analysis and risk management (most frequent finding)
- Business Associate Agreements
- Access controls and audit trails
- Encryption and transmission security
- Breach notification compliance
- Security incident response procedures
Penalty Tiers (per violation category per year)
As of January 28, 2026 (45 CFR 102.3 / Federal Register annual inflation adjustment)
- Tier 1: $145 – $73,011 (lack of knowledge)
- Tier 2: $1,461 – $73,011 (reasonable cause)
- Tier 3: $14,602 – $73,011 (willful neglect, corrected)
- Tier 4: $73,011 – $2,190,294 (willful neglect, not corrected)
Annual cap: $2,190,294 per violation category.
Applicability: Covered Entities and Business Associates handling ePHI Citation: 45 CFR Part 164, Subpart C Enforcement: US Department of Health and Human Services (HHS) - Office for Civil Rights (OCR) Guidance: NIST SP 800-66 Rev. 2
HIPAA Security Rule Evidence Checklist
Generate a comprehensive evidence request list for HIPAA Security Rule compliance, organized by safeguard category. Suitable for audits, readiness assessments, or OCR desk audit preparation.
Never commit evidence artifacts to source control. Evidence outputs may include real patient information, access logs, and security configurations that contain or reference ePHI.
.gitignorecoversevidence/by default sogit add -Awill not sweep it up, but durable storage is your responsibility. Use an encrypted, access-controlled evidence locker with appropriate safeguards per §164.312(a)(2)(iv).
Usage
/us-hipaa-security:evidence-checklist [--category=<cat>] [--format=<fmt>] [--audience=<aud>]
Arguments
--category: Safeguard category to includeadmin- Administrative Safeguards (§164.308)physical- Physical Safeguards (§164.310)technical- Technical Safeguards (§164.312)org- Organizational Requirements (§164.314)policies- Policies and Documentation (§164.316)- Default: All categories
--format: Output formattable- Markdown table (default)markdown- Detailed Markdown listcsv- Comma-separated values (for spreadsheets)
--audience: Target audienceauditor- External auditor or OCR (detailed, with CFR references)internal- Internal readiness check (simplified)
Evidence Checklist
Administrative Safeguards (§164.308)
| Evidence Item | CFR Reference | Required/Addressable | Common Format | Notes/Gotchas |
|---|---|---|---|---|
| Documented risk analysis covering all ePHI systems | §164.308(a)(1)(ii)(A) | Required | Risk analysis report, updated within last 12 months | Must be organization-wide, not just certain systems. Most common OCR finding. |
| Written risk management plan with remediation timelines | §164.308(a)(1)(ii)(B) | Required | Risk management plan document | Must prioritize high/critical risks and assign owners and due dates |
| Sanction policy for workforce member security violations | §164.308(a)(1)(ii)(C) | Required | Written policy signed by management | Must specify sanctions for improper access/disclosure of ePHI |
| Information system activity review logs and reports | §164.308(a)(1)(ii)(D) | Required | Audit log review reports, quarterly or more frequent | Must demonstrate regular review of access logs and security events |
| Assigned security official designation documentation | §164.308(a)(2) | Required | Organizational chart, job description, delegation of authority | Single point of accountability with authority to implement Security Rule |
| Workforce clearance procedure records | §164.308(a)(3)(ii)(B) | Addressable | Background check records, clearance forms | If not implemented, document why it's not reasonable/appropriate |
| Access authorization policies and approval records | §164.308(a)(4)(ii)(A) | Required | Access authorization form, approval workflow | Formal process for granting/reviewing access to ePHI |
| Security awareness training records with completion dates | §164.308(a)(5)(i) | Required | Training completion report, sign-in sheets | All workforce members with ePHI access must be trained upon hire and periodically thereafter |
| Malware/phishing awareness training materials | §164.308(a)(5)(ii)(B) | Addressable | Training presentations, phishing simulation reports | If not implemented, document alternative protection mechanisms |
| Login monitoring procedures and evidence | §164.308(a)(5)(ii)(C) | Addressable | Login monitoring policy, anomalous login review logs | May be part of broader SIEM/security monitoring program |
| Password management policy | §164.308(a)(5)(ii)(D) | Addressable | Password policy document, MFA configuration evidence | If passwords not used, document alternative authentication method |
| Security incident response procedure documentation | §164.308(a)(6)(i) | Required | Incident response plan with roles and responsibilities | Must cover detection, response, reporting, and recovery |
| Security incident log and documented response records | §164.308(a)(6)(ii) | Required | Incident log, investigation reports | Log all incidents, even those not requiring breach notification |
| Contingency/disaster recovery plan, tested within last 12 months | §164.308(a)(7)(i) | Required | Disaster recovery plan, test report | Testing must include backups and emergency mode operations |
| Data backup procedures and recent backup test results | §164.308(a)(7)(ii)(A) | Required | Backup policy, backup verification logs | Backups must be tested periodically to ensure restoration capability |
| Emergency mode operation plan | §164.308(a)(7)(ii)(B) | Required | Emergency mode procedures, access documentation | How to access ePHI during emergency (e.g., power outage, natural disaster) |
| Annual or event-triggered security evaluation report | §164.308(a)(8) | Required | Security evaluation report, gap analysis | Must evaluate technical and non-technical safeguards |
| Executed BAAs for all relevant vendors and subcontractors | §164.308(b)(1) | Required | Signed Business Associate Agreements | Include cloud providers, SaaS vendors, billing companies, IT service providers |
Physical Safeguards (§164.310)
| Evidence Item | CFR Reference | Required/Addressable | Common Format | Notes/Gotchas |
|---|---|---|---|---|
| Facility access control policy and physical access logs | §164.310(a)(1) | Required | Access control policy, badge access logs | Must restrict unauthorized physical access to ePHI systems |
| Contingency operations plan for facility emergencies | §164.310(a)(2)(i) | Addressable | Emergency access procedures | How to access ePHI during facility emergency (fire, flood, etc.) |
| Facility security plan | §164.310(a)(2)(ii) | Addressable | Security plan document, security guard procedures | Must address facility access controls |
| Access control and validation procedures | §164.310(a)(2)(iii) | Addressable | Visitor log, badge issuance procedures | Visitors must be escorted and access logged |
| Maintenance records for physical safeguards | §164.310(a)(2)(iv) | Addressable | Maintenance logs for security systems | Document maintenance of locks, alarms, badge readers |
| Workstation use policy specifying acceptable ePHI handling | §164.310(b) | Required | Workstation use policy, signed acknowledgments | Covers acceptable use, locking screens, no eating/drinking near computers |
| Physical workstation security controls | §164.310(c) | Addressable | Screen locks, cable locks, privacy screens, positioning | May include workstation placement away from public areas |
| Media disposal and destruction records for drives containing ePHI | §164.310(d)(2)(i) | Addressable | Disposal log, certificate of destruction | Must follow NIST SP 800-88 guidelines for sanitization |
| Media re-use and sanitization records before reuse | §164.310(d)(2)(ii) | Addressable | Sanitization log, sanitization procedure documentation | Must verify no ePHI remains before reusing media |
| Hardware and media movement/transfer tracking log | §164.310(d)(2)(iii) | Addressable | Media transfer log, chain of custody form | Track movement of ePHI-containing media between locations |
| Data backup and storage documentation | §164.310(d)(2)(iv) | Addressable | Backup storage location, access controls | Backup media must be securely stored |
| Hardware/electronics disposal records | §164.310(d)(2)(i) | Addressable | Equipment disposal log, destruction certificate | Must ensure ePHI cannot be recovered |
Technical Safeguards (§164.312)
| Evidence Item | CFR Reference | Required/Addressable | Common Format | Notes/Gotchas |
|---|---|---|---|---|
| Unique user ID assignment policy and provisioning evidence | §164.312(a)(2)(i) | Required | Account management policy, user provisioning logs | No shared accounts allowed for ePHI access |
| Emergency access procedure documentation | §164.312(a)(2)(ii) | Required | Emergency access procedures, access logs | How to access ePHI during emergency when normal authentication unavailable |
| Automatic logoff configuration evidence (or documented alternative) | §164.312(a)(2)(iii) | Addressable | Session timeout policy, screen lock settings | If not implemented, document why it's not reasonable (e.g., clinical workflow) |
| Encryption/decryption of ePHI at rest — implementation evidence or documented rationale | §164.312(a)(2)(iv) | Addressable | Encryption configuration, or documented alternative | Most common addressable spec. If not encrypted, document compensating controls |
| Audit log configuration and sample audit logs from ePHI systems | §164.312(b) | Required | Audit log configuration report, sample logs | Must record accesses, disclosures, modifications, deletions |
| Audit log review procedures and evidence of regular review | §164.312(b) | Required | Audit review schedule, review sign-off logs | Logs must be reviewed regularly (quarterly or more frequent) |
| Data integrity controls evidence | §164.312(c)(1) | Addressable | Checksum verification, hash validation, digital signatures | Protect ePHI from improper alteration or destruction |
| Authentication mechanism documentation (MFA evidence preferred) | §164.312(d) | Required | Authentication policy, MFA configuration | Verify identity of persons/entities accessing ePHI |
| Encryption in transit for ePHI — TLS configuration evidence or documented alternative | §164.312(e)(2)(ii) | Addressable | TLS configuration, network encryption evidence | All external ePHI transmissions should be encrypted |
| Authentication for ePHI transmission | §164.312(e)(1) | Required | Authentication policy for network access | Verify identity of entities receiving ePHI electronically |
Organizational Requirements (§164.314)
| Evidence Item | CFR Reference | Required/Addressable | Common Format | Notes/Gotchas |
|---|---|---|---|---|
| BAA template with required contractual provisions checklist | §164.314(a)(1) | Required | BAA template document, provisions checklist | Must include all required provisions per §164.314(a)(2)(i) |
| Executed BAAs for all Business Associates | §164.314(a)(1) | Required | Signed BAAs, BAA tracking log | Include subcontractor BAAs |
| BAA subcontractor agreement evidence | §164.314(a)(2)(ii) | Required | Subcontractor BAAs, BAA amendment notices | BAs must require subcontractors to comply with same restrictions |
| Group health plan amendment documentation | §164.314(b)(1) | Required (if applicable) | Plan document amendment, sponsor certification | Required only if organization is a group health plan with plan sponsor |
| Plan sponsor certification of ePHI safeguards | §164.314(b)(2)(iii) | Required (if applicable) | Sponsor certification, compliance statement | Plan sponsor must certify compliance with Security Rule |
| Restriction on uses/disclosures by plan sponsor | §164.314(b)(2)(iv) | Required (if applicable) | Plan document restrictions, disclosure logs | Plan sponsor cannot use/disclosed ePHI beyond plan administration |
Policies, Procedures, and Documentation (§164.316)
| Evidence Item | CFR Reference | Required/Addressable | Common Format | Notes/Gotchas |
|---|---|---|---|---|
| Written policies and procedures for Security Rule compliance | §164.316(a) | Required | Complete set of security policies and procedures | Must be reasonable and appropriate for organization's size and complexity |
| Policy version history and review/update dates | §164.316(b)(1) | Required | Policy version control, review log, approval signatures | Policies must be reviewed and updated periodically |
| Documentation retention evidence demonstrating 6-year retention | §164.316(b)(2) | Required | Document retention schedule, archive access logs | Policies must be retained 6 years from creation or last effective date |
| Security policy documentation for all required implementation specifications | §164.316(a) | Required | Policy manual covering all applicable safeguards | Must address each required and implemented addressable specification |
| Written procedures for addressable specification decisions | §164.316(a) | Required | Addressable spec assessment documentation | Must document rationale for each addressable spec decision |
Evidence Collection by Format
For Auditors (External/OCR)
Provide organized evidence package with:
- Cover Letter: Organization overview, assessment scope, point of contact
- Table of Contents: Evidence index with CFR references
- Executive Summary: Security Rule compliance status, key gaps, remediation timeline
- Detailed Evidence Sections: Grouped by safeguard category
- Gap Analysis: Findings with CFR section, severity, remediation plan
- Attachments: All supporting documentation
For Internal Readiness
Simplified checklist format:
- Risk analysis completed and updated
- All BAAs signed and current
- Security training current for all staff
- Access controls implemented (unique IDs, least privilege)
- Audit logging enabled and reviewed regularly
- Contingency plan tested in last 12 months
- Encryption implemented where addressable and reasonable
- Policies reviewed and updated
- Incident response procedures documented
- Physical security controls in place
Automated Evidence Collection
Cloud Infrastructure Evidence
AWS - S3 Bucket Encryption Check:
# Check if S3 buckets containing ePHI have encryption enabled
aws s3api list-buckets --output json | jq -r '.Buckets[].Name' | while read bucket; do
encryption=$(aws s3api get-bucket-encryption --bucket "$bucket" 2>&1)
if echo "$encryption" | grep -q "ServerSideEncryptionConfigurationNotFoundError"; then
echo "$bucket,NOT ENCRYPTED" >> evidence/hipaa-s3-encryption-$(date +%Y%m%d).csv
else
echo "$bucket,ENCRYPTED" >> evidence/hipaa-s3-encryption-$(date +%Y%m%d).csv
fi
done
AWS - RDS Encryption Check:
# Check if RDS databases containing ePHI are encrypted
aws rds describe-db-instances --query 'DBInstances[].[DBInstanceIdentifier,StorageEncrypted]' \
--output json > evidence/hipaa-rds-encryption-$(date +%Y%m%d).json
AWS - CloudTrail Logging Check:
# Verify CloudTrail is logging ePHI-affecting AWS account activity
aws cloudtrail describe-trails --query 'trailList[?IsMultiRegionTrail==`true`]' \
--output json > evidence/hipaa-cloudtrail-$(date +%Y%m%d).json
On-Premises Evidence
Active Directory - User Account Review:
# Export Active Directory users with ePHI system access
Get-ADUser -Filter * -Properties LastLogonDate,Enabled |
Where-Object {$_.MemberOf -like "*ePHI-Access*"} |
Select-Object Name,Enabled,LastLogonDate |
Export-Csv -Path "evidence/hipaa-ad-users-$(Get-Date -Format yyyyMMdd).csv" -NoTypeInformation
SQL Server - Audit Log Export:
-- Export audit logs from SQL Server databases containing ePHI
SELECT * FROM sys.dm_audit_log
WHERE event_time > DATEADD(day, -90, GETDATE())
ORDER BY event_time DESC;
Evidence Retention Requirements
6-Year Retention (§164.316(b)(2)):
- Retain from date of creation OR date last in effect (whichever is later)
- Applies to all Security Rule policies and procedures
- Includes risk analyses, BAAs, incident logs, training records, evaluation reports
- Must be accessible for OCR reviews
Recommended Evidence Archive Structure:
evidence/
└── hipaa-security/
├── administrative/
│ ├── risk-analysis/
│ ├── training-records/
│ ├── incident-logs/
│ └── policies/
├── physical/
│ ├── facility-access-logs/
│ ├── workstation-security/
│ └── media-disposal/
├── technical/
│ ├── access-control/
│ ├── audit-logs/
│ └── encryption-evidence/
├── organizational/
│ └── baas/
└── policies/
├── security-policies/
└── procedures/
Examples
# Generate full evidence checklist (all categories)
/us-hipaa-security:evidence-checklist
# Generate Administrative Safeguards checklist only
/us-hipaa-security:evidence-checklist --category=admin
# Generate checklist in CSV format for spreadsheet import
/us-hipaa-security:evidence-checklist --format=csv
# Generate simplified internal readiness checklist
/us-hipaa-security:evidence-checklist --audience=internal
Related Commands
/us-hipaa-security:assess- Run gap assessment before collecting evidence/grc-engineer:gap-assessment HIPAA- Direct SCF crosswalk assessment
Applicability: Covered Entities and Business Associates Citation: 45 CFR Part 164, Subpart C Enforcement: US HHS Office for Civil Rights (OCR) Evidence Retention: 6 years (§164.316(b)(2))
Sponsors
Details
- Marketplace
- GRCEngClub/claude-grc-engineering
- Source
- plugins/frameworks/us-hipaa-security
- Category
- Community
More from GRCEngClub/claude-grc-engineering
All 70- us-nerc-cipv0.1.0
- us-soxv0.1.0
- vault-kvv0.1.0
- wiz-inspectorv0.1.0
- academic-research-companionv0.1.0
- au-apra-cps-234v0.1.0
- aws-inspectorv0.1.0
- aws-secrets-inspectorv0.1.0
- azure-inspectorv0.1.0
- ch-fadpv0.1.0
- cis-controlsv0.1.0
- cmmcv0.1.0
- compliance-posture-dashboardv0.1.0
- crowdstrike-inspectorv0.1.0
- csa-ccmv0.1.0
- cyber-essentials-plusv0.1.0
- datadog-inspectorv0.1.0
- dorav0.1.0
- drata-inspectorv0.1.0
- essential8v0.1.0
- eu-nis2v0.1.0
- fedramp-20xv0.1.0
- fedramp-rev5v0.1.0
- fedramp-sspv0.1.0