HITRUST CSF healthcare security with i1/r2 assessments

version
0.1.0
GitHub stars
436

Install

/plugin install hitrust@grc-engineering-suite

Run it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.

Contents

Discovered from source

Skills 1

HITRUST Expert

Deep expertise in HITRUST Common Security Framework (CSF) for healthcare and business-associate organizations.

Important — normative text. HITRUST CSF is proprietary and subscription-required. This skill provides implementation guidance, assessment workflow, and evidence patterns — phrased in the author's own words. All normative control statements, scoring rubrics, and MyCSF-specific requirement language must be read from your licensed CSF. When a command in this plugin quotes a control description, it is a paraphrased summary; consult the CSF for authoritative text.

Expertise Areas

HITRUST Alliance Overview

Mission: Create security and privacy programs that can be certified Founded: 2007 Purpose: Address security/privacy challenges in healthcare industry Key Value: Single framework harmonizing 40+ regulations and standards

HITRUST CSF (Common Security Framework)

Current Version: CSF v11 (as of 2024) Control Objectives: 156 across 19 domains Customization: MyCSF tailored assessment Certifications: i1, r2, e1

Assessment Types

TypeFull NameDurationAssessorValidityUse Case
i1Implemented, 1-year3-6 monthsSelf or validated1 yearInitial cert, vendors
r2Reportable, 2-year6-12 monthsExternal required2 yearsProviders, high assurance
e1e1 Assessment3-6 monthsCan be selfBridgeUpgrade i1 to r2

i1 Assessment:

  • Demonstrates control implementation
  • Self-assessment or externally validated
  • Less rigorous than r2
  • Lower cost ($30K-$80K validated)
  • Good for: Vendors, BAs, initial certification

r2 Assessment:

  • Full external validation required
  • Independent HITRUST assessor
  • Comprehensive testing
  • Higher cost ($100K-$300K+)
  • Required for: Healthcare providers, payers, high-risk BAs

e1 Assessment:

  • Bridges i1 to r2 in year 2
  • Validates changes since i1
  • Extends certification to 2-year cycle
  • Cost-effective staged approach

MyCSF Customization

HITRUST CSF requirements tailored based on:

Organization Factors:

  1. Type: Provider, payer, clearinghouse, BA, vendor, other
  2. Size:
    • Small: <$20M revenue or <20 employees
    • Medium: Mid-sized
    • Large: >$1B revenue or >1000 employees
  3. System Type: SaaS, on-premise, hybrid, mobile
  4. Regulatory Factors: HIPAA, state laws, international regs

Customization Result:

  • Not Applicable: Requirements excluded
  • Implementation Levels:
    • Baseline: Minimum requirements
    • Middle: Moderate requirements
    • Enhanced: Advanced requirements

19 Control Domains

  1. Information Security Management Program (01) - 12 controls

    • Security governance
    • Risk management program
    • Compliance management
  2. Access Control (02) - 14 controls

    • User access management
    • Privileged access
    • Access reviews
    • Remote access
  3. Human Resources Security (03) - 8 controls

    • Background screening
    • Terms of employment
    • Termination procedures
  4. Risk Management (04) - 5 controls

    • Risk assessment methodology
    • Risk treatment
    • Acceptance criteria
  5. Security Policy (05) - 3 controls

    • Information security policy
    • Review and updates
  6. Organization of Information Security (06) - 8 controls

    • Management commitment
    • Security roles
    • Contact with authorities
  7. Compliance (07) - 6 controls

    • Legal requirements
    • Privacy obligations
    • Intellectual property
  8. Asset Management (08) - 7 controls

    • Asset inventory
    • Information classification
    • Media handling
  9. Physical and Environmental Security (09) - 11 controls

    • Secure areas
    • Physical entry controls
    • Equipment security
    • Disposal
  10. Communications and Operations Management (10) - 23 controls

    • Change management
    • Capacity management
    • Malware protection
    • Backup
    • Network security
  11. Information Systems Acquisition, Development and Maintenance (11) - 15 controls

    • Security requirements
    • Secure development
    • Cryptographic controls
  12. Information Security Incident Management (12) - 6 controls

    • Incident response plan
    • Reporting procedures
    • Collection of evidence
  13. Business Continuity Management (13) - 5 controls

    • BCM process
    • Continuity planning
    • Testing
  14. Network Protection (14) - 7 controls

    • Network architecture
    • Segmentation
    • Firewall management
  15. Password Management (15) - 6 controls

    • Password policies
    • Storage and transmission
    • Multi-factor authentication
  16. Education, Training and Awareness (16) - 4 controls

    • Security awareness
    • Role-based training
  17. Third Party Assurance (17) - 6 controls

    • Business associate agreements
    • Vendor risk management
    • Cloud service provider oversight
  18. Mobile Device Security (18) - 5 controls

    • Mobile device policy
    • BYOD management
    • Mobile application security
  19. Incident Detection and Response (19) - 5 controls

    • Monitoring and detection
    • Security information and event management (SIEM)
    • Threat intelligence

Framework Harmonization

HITRUST CSF maps to 40+ frameworks including:

Primary Frameworks:

  • HIPAA Security and Privacy Rules
  • NIST 800-53, Cybersecurity Framework
  • ISO/IEC 27001:2013, 27002
  • PCI DSS v3.2.1
  • FedRAMP Moderate Baseline

Additional Frameworks:

  • AICPA Trust Services Criteria (SOC 2)
  • COBIT 5
  • GDPR
  • FISMA
  • FDA Medical Device Guidance
  • CMS MARS-E
  • State breach notification laws
  • Canadian PIPEDA
  • UK Data Protection Act

Benefits of Harmonization:

  • Single assessment covers multiple requirements
  • Reduced audit fatigue
  • Streamlined compliance
  • Consistent control language

Certification Process

Phase 1: Preparation (2-4 months)

  1. Gap assessment
  2. Remediation planning
  3. Control implementation
  4. Documentation
  5. Self-assessment

Phase 2: Assessment (1-3 months)

  1. Assessor selection (for validated/r2)
  2. Scoping and kickoff
  3. Evidence collection
  4. Interviews and testing
  5. Assessor review

Phase 3: Certification (1-2 months)

  1. Corrective action (if needed)
  2. Final review
  3. Certification decision
  4. Certificate issuance

Ongoing: Surveillance

  • Continuous monitoring
  • Interim assessments
  • Change notifications
  • Annual recertification (i1) or biennial (r2)

Common Implementation Challenges

  1. Scope Definition:

    • System boundaries unclear
    • Data flows not documented
    • Inherited controls from cloud providers
  2. Resource Constraints:

    • Limited security staff
    • Budget limitations
    • Competing priorities
  3. Documentation Gaps:

    • Policies outdated or missing
    • Procedures not formalized
    • Evidence not collected systematically
  4. Technical Deficiencies:

    • MFA not fully deployed
    • Encryption gaps
    • Logging/monitoring insufficient
    • Vulnerability management immature
  5. Organizational:

    • Lack of executive support
    • Unclear roles and responsibilities
    • Change management resistance

Critical Controls (High Failure Rate)

  1. 09.ab - Encryption of ePHI at Rest
  2. 10.k - Encryption in Transit
  3. 15.d - Multi-Factor Authentication
  4. 10.j - Audit Logging
  5. 12.a - Incident Response Plan
  6. 13.a - Business Continuity Plan
  7. 17.a - Business Associate Agreements
  8. 04.a - Risk Assessment

Evidence Requirements

Common Artifacts Needed:

  • Information security policies
  • Risk assessment reports
  • Business impact analysis
  • System security plans
  • Network diagrams
  • Data flow diagrams
  • Asset inventories
  • Access control matrices
  • Audit logs
  • Vulnerability scan reports
  • Penetration test reports
  • Security awareness training records
  • Incident response plans and tests
  • Business continuity/disaster recovery plans
  • Business associate agreements
  • Vendor risk assessments
  • Change management records

Cost Considerations

i1 Validated Assessment:

  • Assessor fees: $30K-$80K
  • Remediation: $50K-$150K
  • Tools/tech: $20K-$50K
  • Internal effort: 500-1000 hours
  • Total: $100K-$280K

r2 Assessment:

  • Assessor fees: $100K-$300K
  • Remediation: $150K-$500K
  • Tools/tech: $50K-$150K
  • Internal effort: 1000-2000 hours
  • Total: $300K-$950K+

Costs vary by scope, readiness, and organization size

Certification Benefits

Regulatory:

  • Demonstrates HIPAA compliance
  • Satisfies breach safe harbor (some states)
  • Shows due diligence

Business:

  • Competitive differentiator
  • Customer confidence
  • BAA credibility
  • Reduced audit burden
  • Streamlined vendor assessments

Operational:

  • Improved security posture
  • Standardized processes
  • Better risk visibility
  • Incident readiness

Capabilities

  • HITRUST CSF assessment planning (i1, r2, e1)
  • MyCSF scoping and customization
  • Gap analysis and remediation roadmaps
  • Control implementation guidance (156 controls)
  • Evidence collection and documentation
  • Assessor selection and management
  • Framework mapping (HIPAA, NIST, ISO, PCI-DSS)
  • Business associate agreement review
  • Vendor risk assessment (HITRUST CSF perspective)
  • Continuous monitoring and surveillance
  • Certification maintenance

Commands 5

HITRUST Assessment

Evaluates organizational readiness for HITRUST Common Security Framework (CSF) certification.

Arguments

  • $1 - Assessment type (required: i1, r2, e1)
  • $2 - Scope (optional: full, self-assessment, validated)

HITRUST Assessment Types

TypeNameDurationAssessorRecertification
i1Implemented, 1-yearFasterSelf or 3rd partyAnnual
r2Reportable, 2-yearComprehensiveExternal assessor requiredBiennial
e1e1 AssessmentBridges i1 to r2Can be selfN/A - transition

i1 Assessment (Implemented, 1-year)

  • Purpose: Demonstrate control implementation
  • Rigor: Self-attestation or validated
  • Validity: 1 year
  • Use Case: Initial certification, vendor assessments, lower-risk orgs
  • Effort: 3-6 months typically

r2 Assessment (Reportable, 2-year)

  • Purpose: Full independent validation
  • Rigor: External assessor required
  • Validity: 2 years
  • Use Case: Healthcare providers, BAAs, regulatory compliance
  • Effort: 6-12 months typically

e1 Assessment

  • Purpose: Bridge from i1 to r2 in year 2
  • Rigor: Validates implementation since i1
  • Validity: Extends to 2-year r2 cycle
  • Use Case: Organizations wanting staged approach

HITRUST CSF Structure

156 Control Objectives across 19 domains:

  1. Information Security Management Program
  2. Access Control
  3. Human Resources Security
  4. Risk Management
  5. Security Policy
  6. Organization of Information Security
  7. Compliance
  8. Asset Management
  9. Physical and Environmental Security
  10. Communications and Operations Management
  11. Information Systems Acquisition, Development and Maintenance
  12. Information Security Incident Management
  13. Business Continuity Management
  14. Network Protection
  15. Password Management
  16. Education, Training and Awareness
  17. Third Party Assurance
  18. Mobile Device Security
  19. Incident Detection and Response

MyCSF (Customization)

HITRUST MyCSF tailors requirements based on:

  • Organization type: Healthcare provider, payer, vendor, etc.
  • Organization size: Small, medium, large
  • System type: SaaS, on-premise, hybrid
  • Regulatory factors: HIPAA, state laws, international

Customization Result:

  • Some requirements "Not Applicable"
  • Implementation levels adjusted (baseline, enhanced, advanced)
  • Scope tailored to risk profile

Assessment Output

  1. Readiness Score: Overall CSF compliance percentage
  2. Control Status by Domain: 19-domain breakdown
  3. Implementation Levels: Which controls at baseline/enhanced/advanced
  4. Inherited Controls: From cloud providers, managed services
  5. Gap Analysis: Controls not yet implemented or mature
  6. Remediation Roadmap: Prioritized plan to close gaps
  7. Assessment Timeline: Projected certification timeline
  8. Estimated Cost: Assessment and remediation budget

Source Framework Mapping

HITRUST CSF harmonizes multiple frameworks:

  • HIPAA: Health Insurance Portability and Accountability Act
  • NIST: 800-53, Cybersecurity Framework
  • ISO: 27001/27002
  • PCI DSS: Payment Card Industry
  • FedRAMP: Federal Risk and Authorization Management Program
  • GDPR: General Data Protection Regulation
  • And 40+ other frameworks

Examples

# Full r2 assessment for healthcare provider
/hitrust:assess r2 full

# i1 self-assessment readiness check
/hitrust:assess i1 self-assessment

# Validated i1 assessment scope
/hitrust:assess i1 validated

HITRUST Control Mapping

Maps HITRUST CSF control requirements to underlying source frameworks (HIPAA, NIST, ISO, PCI-DSS, etc.).

Arguments

  • $1 - HITRUST control ID (required, e.g., 01.a, 09.ab)
  • $2 - Target framework (optional: HIPAA, NIST, ISO27001, PCIDSS, all)

HITRUST Control ID Format

Structure: [Domain].[Control][Subcontrol]

  • Domain: 01-19 (two digits)
  • Control: Single letter (a-z)
  • Subcontrol: Optional second letter or number

Examples:

  • 01.a - Information Security Management Program, control (a)
  • 09.ab - Physical and Environmental Security, subcontrol (ab)
  • 02.d - Access Control, control (d)

19 HITRUST Domains

DomainNameControl Count
01Information Security Management Program12
02Access Control14
03Human Resources Security8
04Risk Management5
05Security Policy3
06Organization of Information Security8
07Compliance6
08Asset Management7
09Physical and Environmental Security11
10Communications and Operations Management23
11Information Systems Acquisition, Development and Maintenance15
12Information Security Incident Management6
13Business Continuity Management5
14Network Protection7
15Password Management6
16Education, Training and Awareness4
17Third Party Assurance6
18Mobile Device Security5
19Incident Detection and Response5

Source Framework Mappings

HITRUST CSF harmonizes 40+ frameworks including:

Primary Frameworks

  • HIPAA Security Rule, Privacy Rule
  • NIST 800-53, Cybersecurity Framework
  • ISO/IEC 27001:2013, 27002
  • PCI DSS v3.2.1
  • FedRAMP Moderate Baseline

Additional Frameworks

  • COBIT 5
  • AICPA Trust Services Criteria (SOC 2)
  • GDPR
  • FISMA
  • State breach notification laws
  • FDA guidance for medical devices
  • MARS-E (CMS)

Common Control Examples

Access Control (Domain 02)

02.d: Automated Central Audit Log

  • HIPAA: 164.308(a)(1)(ii)(D), 164.312(b)
  • NIST 800-53: AU-2, AU-3, AU-6
  • ISO 27001: A.12.4.1
  • PCI DSS: 10.1, 10.2, 10.3

Encryption (Domain 10)

10.k: Encryption of ePHI at Rest

  • HIPAA: 164.312(a)(2)(iv)
  • NIST 800-53: SC-28
  • ISO 27001: A.10.1.1
  • PCI DSS: 3.4

Incident Response (Domain 12)

12.a: Incident Response Plan

  • HIPAA: 164.308(a)(6)
  • NIST 800-53: IR-1, IR-8
  • ISO 27001: A.16.1.1
  • PCI DSS: 12.10

Business Associate Management (Domain 17)

17.a: Business Associate Agreements

  • HIPAA: 164.308(b)(1), 164.314(a)
  • NIST 800-53: SA-9
  • ISO 27001: A.15.1.2

MyCSF Implementation Levels

Controls have different implementation requirements based on:

Baseline Level

  • Minimum required implementation
  • Small/low-risk organizations
  • Basic security posture

Enhanced Level (Middle)

  • Moderate implementation
  • Medium organizations
  • Standard security posture

Advanced Level

  • Comprehensive implementation
  • Large/high-risk organizations
  • Mature security programs

Output

  1. Control Definition: What HITRUST requires
  2. Framework Mappings: Shows alignment to:
    • HIPAA sections
    • NIST 800-53 controls
    • ISO 27001 controls
    • PCI DSS requirements
    • Other relevant frameworks
  3. Implementation Guidance: How to satisfy the control
  4. Evidence Examples: What assessors look for
  5. Common Gaps: Typical deficiencies

Examples

# Map encryption control to all frameworks
/hitrust:control-map 10.k all

# Show HIPAA mapping for access control
/hitrust:control-map 02.d HIPAA

# View incident response NIST alignment
/hitrust:control-map 12.a NIST

# Check BAA requirements against ISO
/hitrust:control-map 17.a ISO27001

HITRUST CSF Evidence Checklist

Generates comprehensive evidence collection checklists for HITRUST Common Security Framework (CSF) certification with focus on healthcare and HIPAA alignment (implementation levels 1-3).

Never commit evidence artifacts to source control. The outputs below include real usernames, credential reports, MFA device states, and privileged-account inventories. .gitignore covers evidence/ by default so git add -A will not sweep it up, but durable storage is your responsibility. Use an encrypted, access-controlled evidence locker (encrypted S3 with least-privilege IAM, a GRC platform, or a shared drive with full-disk encryption and MFA-gated access).

Usage

/hitrust:evidence-checklist <control-id> [--implementation-level <1|2|3>] [--export <format>]

Arguments

  • <control-id>: HITRUST CSF control (e.g., "01.a", "09.ab", "10.h") or category (e.g., "Access Control", "Encryption")
  • --implementation-level: Target implementation level (1, 2, or 3). Default: 2 (most common)
  • --export: Export format (json, csv, markdown). Default: markdown

Example: Access Control Evidence (Level 2 - HIPAA Aligned)

/hitrust:evidence-checklist "01.a" --implementation-level 2

Output:

HITRUST CSF Evidence Checklist
Control: 01.a - User Registration
Implementation Level: Level 2 (HIPAA-aligned)
Mapped Frameworks: HIPAA §164.312(a)(2)(i), NIST 800-53 AC-2, ISO 27001 A.9.2.1
Assessment Type: Validated (third-party)
Certification Validity: 2 years

## Control Description (paraphrased)

The organization should operate a formal user onboarding and offboarding process so that access rights are granted, tracked, and revoked consistently. See your licensed HITRUST CSF for the authoritative control text.

## Implementation Level Requirements

### Level 1 (Basic)
- User registration process documented
- Access approval required
- User de-registration process exists

### Level 2 (HIPAA-aligned) - TARGET
- Level 1 + automated user provisioning/de-provisioning
- Access rights based on role
- Quarterly access reviews
- Integration with HR systems

### Level 3 (Advanced)
- Level 2 + real-time provisioning/de-provisioning
- Continuous access monitoring
- Automated access reviews
- Advanced analytics and reporting

## Evidence Requirements (Level 2)

### Required Documentation

□ **Access Control Policy**
  - Scope: All systems processing PHI (Protected Health Information)
  - Required elements:
    - User registration procedures
    - Role-based access control (RBAC) framework
    - Access approval workflow
    - De-registration procedures (within 24 hours of termination)
    - Quarterly access reviews
  - Update frequency: Annually
  - Approver: CISO and Privacy Officer
  - Evidence: Signed Access Control Policy v1.x

□ **Role-Based Access Control (RBAC) Matrix**
  - Definition of all roles (Physician, Nurse, Admin, Billing, etc.)
  - Permissions for each role
  - Systems/applications accessible by role
  - Evidence: RBAC matrix (Excel/documentation)
  - Frequency: Annual review, update when roles change

□ **User Access Request Form/Workflow**
  - Standard request form or ticketing system workflow
  - Required fields: Name, role, manager approval, HR verification
  - Evidence: Sample access request forms (10-25 samples)
  - Frequency: Quarterly review of samples

□ **Quarterly Access Review Procedure**
  - Documented procedure for quarterly access reviews
  - Manager sign-off on continued access need
  - Remediation process for inappropriate access
  - Evidence: Quarterly access review procedure document
  - Frequency: Quarterly execution

### Automated Evidence Collection

✓ **User Access Inventory**
```bash
# AWS IAM users accessing PHI systems
aws iam list-users --output json > evidence/hitrust-01a-iam-users-$(date +%Y%m%d).json

# IAM credential report (shows creation dates, last access)
aws iam generate-credential-report
aws iam get-credential-report --output text | base64 -d \
  > evidence/hitrust-01a-credential-report-$(date +%Y%m%d).csv

# Filter for PHI system access (based on tags)
aws iam list-users | jq -r '.Users[].UserName' | while read user; do
  tags=$(aws iam list-user-tags --user-name "$user" --query 'Tags[?Key==`PHI-Access`].Value' --output text)
  if [ ! -z "$tags" ]; then
    echo "$user,$tags" >> evidence/hitrust-01a-phi-access-users-$(date +%Y%m%d).csv
  fi
done

# Azure AD users (healthcare organizations)
az ad user list --output json > evidence/hitrust-01a-azure-users-$(date +%Y%m%d).json

# Filter guest users (external access to PHI requires scrutiny)
az ad user list --filter "userType eq 'Guest'" --output json \
  > evidence/hitrust-01a-guest-users-$(date +%Y%m%d).json

Collection Frequency: Monthly Retention: 6 years (HIPAA record retention requirement) Purpose: User registration inventory per HITRUST 01.a

✓ User Provisioning/De-provisioning Logs

# AWS CloudTrail - User creation events (last 90 days)
aws cloudtrail lookup-events \
  --lookup-attributes AttributeKey=EventName,AttributeValue=CreateUser \
  --start-time $(date -u -d '90 days ago' +%Y-%m-%dT%H:%M:%S) \
  --max-items 1000 \
  --output json > evidence/hitrust-01a-user-creation-$(date +%Y%m).json

# User deletion events (last 90 days)
aws cloudtrail lookup-events \
  --lookup-attributes AttributeKey=EventName,AttributeValue=DeleteUser \
  --start-time $(date -u -d '90 days ago' +%Y-%m-%dT%H:%M:%S) \
  --max-items 1000 \
  --output json > evidence/hitrust-01a-user-deletion-$(date +%Y%m).json

# Permission changes (AttachUserPolicy, DetachUserPolicy)
for event in AttachUserPolicy DetachUserPolicy; do
  aws cloudtrail lookup-events \
    --lookup-attributes AttributeKey=EventName,AttributeValue=$event \
    --start-time $(date -u -d '90 days ago' +%Y-%m-%dT%H:%M:%S) \
    --max-items 1000 \
    --output json >> evidence/hitrust-01a-permission-changes-$(date +%Y%m).json
done

# Azure AD audit logs
az monitor activity-log list \
  --caller 'Microsoft.Authorization' \
  --start-time $(date -u -d '90 days ago' +%Y-%m-%dT%H:%M:%S) \
  --output json > evidence/hitrust-01a-azure-audit-$(date +%Y%m).json

Collection Frequency: Monthly Retention: 6 years Purpose: Audit trail of user registration/de-registration

✓ Role Assignments

# AWS IAM - Users and their attached policies (roles)
for user in $(aws iam list-users --query 'Users[].UserName' --output text); do
  echo "=== $user ===" >> evidence/hitrust-01a-user-roles-$(date +%Y%m%d).txt
  aws iam list-attached-user-policies --user-name "$user" >> evidence/hitrust-01a-user-roles-$(date +%Y%m%d).txt
  aws iam list-user-policies --user-name "$user" >> evidence/hitrust-01a-user-roles-$(date +%Y%m%d).txt
  aws iam list-groups-for-user --user-name "$user" >> evidence/hitrust-01a-user-roles-$(date +%Y%m%d).txt
done

# AWS SSO permission sets (role assignments)
aws sso-admin list-permission-sets --instance-arn <INSTANCE-ARN> \
  --output json > evidence/hitrust-01a-sso-permission-sets-$(date +%Y%m%d).json

# Azure AD role assignments
az role assignment list --all --output json \
  > evidence/hitrust-01a-azure-role-assignments-$(date +%Y%m%d).json

Collection Frequency: Monthly Retention: 6 years Purpose: Role-based access control evidence

✓ Access Review Evidence (Quarterly)

# Generate access review report for managers
# This is typically a manual process, but can export current access for review

# Export all users with their roles for quarterly review
aws iam list-users | jq -r '.Users[] | .UserName' | while read user; do
  created=$(aws iam get-user --user-name "$user" --query 'User.CreateDate' --output text)
  groups=$(aws iam list-groups-for-user --user-name "$user" --query 'Groups[].GroupName' --output text)
  echo "$user,$created,$groups" >> evidence/hitrust-01a-access-review-Q$(date +%q)-$(date +%Y).csv
done

# Add header
sed -i '1i Username,CreatedDate,Groups' evidence/hitrust-01a-access-review-Q$(date +%q)-$(date +%Y).csv

Collection Frequency: Quarterly (Q1, Q2, Q3, Q4) Retention: 6 years Purpose: Quarterly access review requirement

Manual Evidence Collection

□ Quarterly Access Review Reports

  • Complete review of all user access every 90 days
  • Required elements:
    • List of all users with PHI access at review start date
    • Manager certification of continued need for access
    • Identified inappropriate access
    • Remediation actions taken (within 30 days)
    • Senior management sign-off
  • Evidence: 4 quarterly access review reports per year
  • Frequency: Quarterly (Q1, Q2, Q3, Q4)
  • CRITICAL: HITRUST Level 2 requires 4 consecutive quarters for i1 certification

□ Access Request Approvals (Sample)

  • Sample size: 25 access requests from last quarter
  • Required elements:
    • User name and role requested
    • Business justification
    • Manager approval (email/ticket)
    • HR verification (employee status)
    • Security team approval (for PHI access)
    • Access granted date (within 5 business days of approval)
    • Appropriate role assigned (matches RBAC matrix)
  • Evidence: Folder of 25 approval tickets/emails
  • Frequency: Quarterly review

□ Termination Access Revocation (Sample)

  • Sample size: All terminations in last quarter (or 25 if >25)
  • Required elements:
    • HR termination notice
    • Access revoked within 24 hours (HIPAA requirement)
    • Confirmation from IT (screenshot/log)
    • No subsequent access after termination (audit logs)
  • Evidence: HR notices + revocation tickets + audit logs
  • Frequency: Quarterly review

□ HR System Integration Evidence

  • Integration between HR system (Workday, BambooHR, etc.) and IAM
  • Automated provisioning workflow (hire → create account)
  • Automated de-provisioning workflow (termination → disable/delete account)
  • Evidence: Integration configuration screenshots, workflow diagrams
  • Frequency: Annual review

□ Emergency Access Procedures

  • Break-glass / emergency access procedures for PHI
  • Required elements:
    • When emergency access is permitted
    • Approval process (or post-hoc review)
    • Audit logging of emergency access
    • Review frequency (within 24 hours)
  • Evidence: Emergency access procedure document + usage logs (if any)
  • Frequency: Annual review

HITRUST Assessment Expectations

HITRUST Validated Assessors will verify:

Documentation Review

✓ Access control policy comprehensive and approved ✓ RBAC matrix defined and current ✓ User registration procedures documented ✓ De-registration procedures documented (24-hour requirement for PHI) ✓ Quarterly access review procedures documented

Implementation Review

✓ User provisioning automated (integration with HR) ✓ De-provisioning automated (<24 hours for PHI access) ✓ RBAC implemented (not everyone has admin access) ✓ Access approvals documented (samples reviewed) ✓ Quarterly access reviews performed (4 consecutive quarters)

Testing Requirements

✓ Sample 25 access requests (test approval process) ✓ Sample 25 terminations (test <24hr revocation) ✓ Review 4 quarterly access review reports ✓ Test emergency access procedures

Audit Trail

✓ CloudTrail/Azure AD logs show all access changes ✓ Logs retained for 6 years (HIPAA requirement) ✓ Logs centrally stored and protected from tampering

Common HITRUST Assessment Findings

Critical (Likely to fail i1 certification)

❌ No access control policy ❌ No quarterly access reviews (must show 4 consecutive quarters) ❌ De-provisioning >24 hours after termination ❌ No approval process for access requests ❌ No RBAC - everyone has same access level ❌ Audit logs not retained for 6 years

Moderate (Corrective Action Plan required)

⚠️ Access review missing manager sign-offs ⚠️ Access request samples show unapproved access ⚠️ RBAC matrix not current (roles changed, matrix not updated) ⚠️ De-provisioning automated but >24 hours ⚠️ Some access not role-based (ad-hoc permissions)

Minor (Observations)

⚠️ Access review documentation could be more detailed ⚠️ Emergency access procedures not tested ⚠️ HR integration manual (not automated)

Remediation Guidance

If No Quarterly Access Reviews

  1. Immediate (Week 1): Export all user access from all PHI systems
  2. Week 2: Send access lists to managers for validation
  3. Week 3: Collect manager sign-offs, identify inappropriate access
  4. Week 4: Remediate identified access issues
  5. Ongoing: Schedule quarterly (every 90 days) reviews

Timeline: Establish process immediately, but need 4 consecutive quarters for certification Priority: 🔴 CRITICAL (required for i1 certification)

If De-Provisioning >24 Hours

  1. Week 1: Identify manual steps causing delay
  2. Week 2: Automate HR → IAM integration (use Workday/BambooHR APIs)
  3. Weeks 3-4: Test automated de-provisioning in non-prod
  4. Week 5: Deploy to production
  5. Week 6: Monitor and validate <24hr revocation

Timeline: 6-8 weeks Priority: 🔴 CRITICAL (HIPAA requirement)

If No RBAC

  1. Week 1: Define standard roles (Physician, Nurse, Billing, Admin, etc.)
  2. Week 2: Map current permissions to roles (create RBAC matrix)
  3. Weeks 3-4: Assign users to roles (remove ad-hoc permissions)
  4. Week 5: Test role assignments in non-prod
  5. Week 6: Deploy to production, remove individual permissions

Timeline: 6-8 weeks Priority: 🔴 CRITICAL (foundational control)

Cross-References

Related HITRUST CSF Controls

  • 01.b - Privilege Management
  • 01.c - User Password Management
  • 01.f - Segregation of Duties
  • 01.k - User Identification and Authentication
  • 01.m - Teleworking (remote access for PHI)

Maps to Other Frameworks

  • HIPAA: §164.312(a)(2)(i) - Unique User Identification, §164.308(a)(3)(i) - Workforce security
  • NIST 800-53: AC-2 (Account Management), AC-5 (Separation of Duties), AC-6 (Least Privilege)
  • ISO 27001:2022: A.5.15 (Access control), A.5.16 (Identity management), A.5.18 (Access rights)
  • SOC 2: CC6.1, CC6.2 (Logical and physical access controls)
  • PCI-DSS: 8.1, 8.2 (User identification and authentication)

Cost Estimates

HITRUST CSF i1 Certification (Level 2, Small-Medium Healthcare Org)

  • HITRUST readiness assessment: 80 hours ($8,000)
  • Access control implementation (01.a + related): 120 hours ($12,000)
  • RBAC matrix development: 40 hours ($4,000)
  • HR system integration (automated provisioning): 80 hours ($8,000)
  • Quarterly access reviews: 40 hours/quarter ($4,000/quarter)
  • Validated assessment (external): $40k-$80k (depends on org size)
  • Total Year 1: ~$72k-$112k (one-time) + $16k/year (quarterly reviews)

HITRUST i1 Certification Ongoing

  • Annual assessment: $40k-$80k/year
  • Quarterly access reviews: $16k/year
  • RBAC matrix updates: $2k/year
  • Ongoing: ~$58k-$98k/year

Tools

  • Identity governance platform: $10k-$50k/year
  • HR system integration: $5k-$15k/year
  • GRC platform with HITRUST MyCSF: $15k-$40k/year

Evidence Package Structure

evidence/
└── hitrust-csf-01a-access-control/
    ├── policies/
    │   ├── access-control-policy-v1.2-signed.pdf
    │   ├── rbac-matrix-2024.xlsx
    │   └── emergency-access-procedure.pdf
    ├── automated/
    │   ├── 2024-01/
    │   │   ├── iam-users-20240131.json
    │   │   ├── credential-report-20240131.csv
    │   │   ├── role-assignments-20240131.txt
    │   │   └── provision-deprovision-logs-202401.json
    │   └── ... (monthly)
    ├── quarterly-reviews/
    │   ├── Q1-2024-access-review.pdf
    │   ├── Q1-2024-manager-signoffs.pdf
    │   ├── Q2-2024-access-review.pdf
    │   ├── Q2-2024-manager-signoffs.pdf
    │   ├── Q3-2024-access-review.pdf
    │   ├── Q3-2024-manager-signoffs.pdf
    │   ├── Q4-2024-access-review.pdf
    │   └── Q4-2024-manager-signoffs.pdf (4 REQUIRED)
    ├── access-request-samples/
    │   ├── Q1-2024/
    │   │   ├── request-001-dr-smith.pdf
    │   │   ├── request-002-nurse-jones.pdf
    │   │   └── ... (25 samples)
    │   └── ... (quarterly)
    ├── termination-samples/
    │   ├── Q1-2024/
    │   │   ├── termination-001-revocation.pdf
    │   │   └── ... (all terminations)
    │   └── ... (quarterly)
    ├── hr-integration/
    │   ├── integration-architecture-diagram.pdf
    │   ├── provisioning-workflow-screenshots.pdf
    │   └── deprovisioning-workflow-screenshots.pdf
    └── README.md (evidence index, 6-year retention)

Automation Script

#!/usr/bin/env python3
"""
HITRUST CSF 01.a - User Registration Evidence Collection
For healthcare organizations pursuing HITRUST i1 certification
"""
import boto3
import json
import csv
from datetime import datetime
import os

class HITRUSTAccessControlEvidence:
    def __init__(self, output_dir="evidence/hitrust-csf-01a-access-control"):
        self.output_dir = f"{output_dir}/automated/{datetime.now().strftime('%Y-%m')}"
        self.timestamp = datetime.now().strftime("%Y%m%d")
        self.quarter = f"Q{(datetime.now().month-1)//3+1}-{datetime.now().year}"
        os.makedirs(self.output_dir, exist_ok=True)

    def collect_user_inventory(self):
        """Collect IAM user inventory"""
        print("Collecting user inventory (PHI access)...")
        iam = boto3.client('iam')

        users = iam.list_users()['Users']

        # Filter for PHI access (based on tags)
        phi_users = []
        for user in users:
            username = user['UserName']
            tags = iam.list_user_tags(UserName=username).get('Tags', [])
            if any(tag.get('Key') == 'PHI-Access' and tag.get('Value') == 'true' for tag in tags):
                phi_users.append({
                    'username': username,
                    'created': user['CreateDate'].isoformat(),
                    'arn': user['Arn'],
                    'tags': tags
                })

        # Save evidence
        output_file = f"{self.output_dir}/phi-access-users-{self.timestamp}.json"
        with open(output_file, 'w') as f:
            json.dump(phi_users, f, indent=2)

        print(f"✓ Total IAM users: {len(users)}")
        print(f"✓ PHI access users: {len(phi_users)}")

        return phi_users

    def collect_access_changes(self):
        """Collect user creation/deletion logs (last 90 days)"""
        print("Collecting access change logs (last 90 days)...")
        cloudtrail = boto3.client('cloudtrail')

        from datetime import datetime, timedelta
        start_time = datetime.now() - timedelta(days=90)
        end_time = datetime.now()

        # Track user lifecycle events
        events = ['CreateUser', 'DeleteUser', 'AttachUserPolicy', 'DetachUserPolicy']

        all_events = []
        for event_name in events:
            response = cloudtrail.lookup_events(
                LookupAttributes=[{
                    'AttributeKey': 'EventName',
                    'AttributeValue': event_name
                }],
                StartTime=start_time,
                EndTime=end_time,
                MaxResults=1000
            )
            all_events.extend(response.get('Events', []))

        # Save evidence
        output_file = f"{self.output_dir}/access-changes-{self.timestamp}.json"
        with open(output_file, 'w') as f:
            json.dump(all_events, f, indent=2, default=str)

        print(f"✓ Access change events: {len(all_events)}")

        return all_events

    def generate_quarterly_review_template(self, phi_users):
        """Generate template for quarterly access review"""
        review_file = f"evidence/hitrust-csf-01a-access-control/quarterly-reviews/{self.quarter}-access-review-template.txt"
        os.makedirs(os.path.dirname(review_file), exist_ok=True)

        template = f"""
HITRUST CSF 01.a - Quarterly Access Review
Review Period: {self.quarter}
Review Date: {datetime.now().strftime("%Y-%m-%d")}
Reviewer: [Name/Title of Qualified Individual]

INSTRUCTIONS FOR MANAGERS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Review each user with PHI access and certify:
1. User still requires access to PHI for job duties
2. Access level is appropriate (least privilege)
3. User has completed annual HIPAA training

For each user, mark:
  ✓ = Access approved (continue)
  ✗ = Access should be revoked
  ↓ = Access should be reduced

USERS WITH PHI ACCESS ({len(phi_users)} total)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

"""
        for idx, user in enumerate(phi_users, 1):
            template += f"""
{idx}. {user['username']}
   Created: {user['created']}
   Role/Tags: {', '.join(tag['Value'] for tag in user.get('tags', []))}

   Manager Decision: [ ] ✓ Approve  [ ] ✗ Revoke  [ ] ↓ Reduce
   Manager Name: _________________ Date: ___/___/___

"""

        template += """
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

SUMMARY
Total Users Reviewed: ______
Approved: ______
Revoked: ______
Reduced: ______

Qualified Individual Sign-Off:

Name: _________________________ Title: _________________

Signature: _____________________ Date: ___/___/___

Actions Required:
□ Revoke access for users marked ✗ (within 30 days)
□ Reduce access for users marked ↓ (within 30 days)
□ File this review in evidence folder (retain 6 years per HIPAA)
"""

        with open(review_file, 'w') as f:
            f.write(template)

        print(f"✓ Quarterly review template generated: {review_file}")
        print(f"  ACTION REQUIRED: Complete manager reviews for {self.quarter}")

        return review_file

    def generate_compliance_report(self, phi_users, access_changes):
        """Generate HITRUST 01.a compliance summary"""
        report = f"""
HITRUST CSF 01.a - User Registration Evidence Summary
Generated: {datetime.now().strftime("%Y-%m-%d %H:%M:%S")}
Implementation Level: Level 2 (HIPAA-aligned)

USER INVENTORY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Users with PHI Access: {len(phi_users)}

ACCESS CHANGES (Last 90 days)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Total Access Changes:   {len(access_changes)}

QUARTERLY ACCESS REVIEW STATUS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Current Quarter: {self.quarter}
Template Generated: ✓
Manager Reviews: ⏳ PENDING
Required for i1: 4 consecutive quarterly reviews

REQUIRED ACTIONS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
□ Complete manager reviews for {self.quarter} (within 15 days)
□ Remediate inappropriate access (within 30 days)
□ Obtain Qualified Individual sign-off
□ File completed review (6-year retention)

Evidence Location: {self.output_dir}
Retention: 6 years (HIPAA §164.316(b)(2))
"""

        report_file = f"{self.output_dir}/compliance-summary-{self.timestamp}.txt"
        with open(report_file, 'w') as f:
            f.write(report)

        print(f"\n{report}")
        return report_file

if __name__ == "__main__":
    print("HITRUST CSF 01.a - User Registration Evidence Collection")
    print("=" * 70)
    print("Implementation Level: Level 2 (HIPAA-aligned)")
    print("=" * 70)

    collector = HITRUSTAccessControlEvidence()

    phi_users = collector.collect_user_inventory()
    access_changes = collector.collect_access_changes()
    collector.generate_quarterly_review_template(phi_users)
    collector.generate_compliance_report(phi_users, access_changes)

    print("\n✓ HITRUST 01.a evidence collection complete")
    print("⚠️  CRITICAL: Complete quarterly access review for certification")

HITRUST CSF Version: v11 (current) Implementation Level: Level 2 (HIPAA-aligned) - Most common Certification Type: i1 (Interim), r2 (Validated) Certification Validity: 2 years Evidence Retention: 6 years (HIPAA requirement) Priority: 🔴 CRITICAL (Healthcare industry standard)

HITRUST Gap Analysis

Analyzes current security posture against HITRUST CSF requirements and identifies control gaps.

Arguments

  • $1 - Assessment type target (required: i1, r2)
  • $2 - Analysis depth (optional: high-level, detailed, by-domain)

Gap Analysis Process

1. Current State Assessment

Reviews existing security controls and documentation:

  • Policies and procedures
  • Technical configurations
  • Audit logs and monitoring
  • Training and awareness programs
  • Incident response capabilities
  • Business continuity plans

2. HITRUST Requirement Mapping

Maps current controls to HITRUST CSF requirements:

  • 156 control objectives
  • MyCSF customization (org type, size, system)
  • Implementation levels (baseline, enhanced, advanced)
  • Authoritative source references

3. Gap Identification

Identifies three types of gaps:

  • Missing Controls: No implementation exists
  • Partial Controls: Implemented but incomplete
  • Documentation Gaps: Control exists but not documented

4. Risk Prioritization

Ranks gaps by:

  • Critical: High-risk, assessor will flag
  • High: Important for certification
  • Medium: Should address before assessment
  • Low: Nice-to-have or lower risk

Common Gap Categories

Policy & Documentation Gaps

  • Missing or outdated information security policies
  • Incomplete risk assessments
  • No business impact analysis (BIA)
  • Lack of system security plans
  • Missing business associate agreements

Impact: Easy to fix, high assessor focus

Technical Control Gaps

  • Multi-factor authentication not implemented
  • Encryption at rest/in transit incomplete
  • Insufficient logging and monitoring
  • Vulnerability management gaps
  • Patch management deficiencies

Impact: Moderate to fix, critical for compliance

Process & Procedure Gaps

  • Incident response plan not tested
  • No formal change management
  • Access reviews not performed
  • Security awareness training lacking
  • Vendor risk assessments missing

Impact: Moderate to fix, ongoing effort required

Organizational Gaps

  • No designated security officer (CISO/CSO)
  • Unclear roles and responsibilities
  • Lack of security governance structure
  • Insufficient resources/budget
  • No security steering committee

Impact: Strategic, requires executive commitment

MyCSF Scoping Impact

Gaps vary based on MyCSF customization:

Organization Size

  • Small: Fewer requirements, focused gaps
  • Medium: Standard requirements, typical gaps
  • Large: Enhanced requirements, complex gaps

Organization Type

  • Provider: HIPAA-heavy gaps common
  • Payer: Privacy/claims gaps typical
  • Vendor: Third-party assurance gaps
  • Business Associate: BAA-related gaps

System Type

  • SaaS: Inherited controls reduce gaps
  • On-Premise: More infrastructure gaps
  • Hybrid: Complex scoping, varied gaps

Output

  1. Executive Summary: High-level gap overview
  2. Gap Count by Severity:
    • Critical: X gaps
    • High: Y gaps
    • Medium: Z gaps
    • Low: W gaps
  3. Gap Details by Domain: 19-domain breakdown
  4. Remediation Effort Estimates:
    • Quick wins (<1 month)
    • Short-term (1-3 months)
    • Medium-term (3-6 months)
    • Long-term (6-12 months)
  5. Budget Estimates: Tooling, consulting, staff time
  6. Prioritized Roadmap: Phased remediation plan
  7. Timeline to Certification: Based on gap closure

Gap Analysis Report Sections

1. Current Maturity Assessment

  • Initial: Ad-hoc, inconsistent controls
  • Developing: Some processes defined
  • Defined: Documented and followed
  • Managed: Measured and monitored
  • Optimized: Continuously improving

2. Control Status Summary

  • Implemented: Meets HITRUST requirements
  • Partially Implemented: Needs enhancement
  • Planned: On roadmap but not started
  • Not Implemented: Critical gap
  • Not Applicable: MyCSF excluded

3. Quick Wins

Controls that can be addressed rapidly:

  • Policy updates
  • Documentation creation
  • Simple technical configs
  • Training completion

4. Critical Path Items

Gaps that block certification:

  • Missing MFA
  • No encryption at rest
  • Incomplete audit logging
  • Lack of incident response plan

Examples

# High-level gap analysis for r2 assessment
/hitrust:gap-analysis r2 high-level

# Detailed gap analysis for i1
/hitrust:gap-analysis i1 detailed

# Domain-specific gap analysis
/hitrust:gap-analysis r2 by-domain

HITRUST Scope Selection

Helps determine whether to pursue i1, r2, or e1 HITRUST CSF assessment based on organizational needs and constraints.

Arguments

  • $1 - Organization type (optional: provider, payer, vendor, business-associate)
  • $2 - Primary driver (optional: hipaa, baa-requirement, vendor-requirement, competitive)

Decision Factors

i1 Assessment (Implemented, 1-year)

Choose i1 when:

  • First-time HITRUST certification
  • Vendor/supplier requirement (not provider)
  • Annual recertification acceptable
  • Budget constraints (<$100K for assessment)
  • Want to test readiness before r2
  • Self-attestation preferred (validated optional)

i1 Validated vs Self-Assessment:

  • Validated: External assessor reviews and validates
    • More credible to customers
    • ~$30K-$80K assessment cost
    • Recommended for BAAs, vendors
  • Self-Assessment: Internal team completes
    • Lower cost (~$10K-$30K tools/training)
    • Less third-party credibility
    • Good for internal readiness

r2 Assessment (Reportable, 2-year)

Choose r2 when:

  • Healthcare provider or payer
  • BAA partners require r2
  • Regulatory compliance driver (OCR, state regs)
  • 2-year validity needed
  • Higher assurance level required
  • Competitive differentiation
  • External assessor mandatory

r2 Requirements:

  • External HITRUST assessor required
  • More rigorous testing and validation
  • Higher cost ($100K-$300K+ assessment)
  • Longer timeline (6-12 months)
  • Greater ongoing maintenance

e1 Assessment (Bridge)

Choose e1 when:

  • Currently have i1, want to upgrade to r2
  • Year 2 of certification cycle
  • Incremental approach to r2
  • Budget spreading across 2 years
  • Want to maintain continuous certification

Organization Type Guidance

Healthcare Providers (Hospitals, Clinics)

Recommendation: r2

  • Regulatory scrutiny highest
  • Patient trust critical
  • OCR expectations
  • BAA requirements from partners

Health Plans/Payers

Recommendation: r2

  • Large member populations
  • Regulatory requirements
  • Vendor management
  • Public reporting often required

Business Associates

Recommendation: i1 validated or r2

  • BAA requirements dictate
  • Customer expectations
  • Competitive landscape
  • Risk profile of data

Technology Vendors (SaaS, Cloud)

Recommendation: i1 validated minimum, r2 preferred

  • Customer requirements vary
  • Inherited controls from infrastructure
  • Velocity of product changes
  • Certification as sales enabler

Smaller Organizations (<50 employees)

Recommendation: i1 self-assessment or validated

  • Resource constraints
  • Cost sensitivity
  • Risk-appropriate
  • Can upgrade to r2 later

Cost Comparison

Assessment TypeAssessment CostRemediation CostTimelineValidity
i1 Self$10K-$30K$50K-$150K3-6 months1 year
i1 Validated$30K-$80K$50K-$150K3-6 months1 year
r2$100K-$300K+$150K-$500K+6-12 months2 years
e1$40K-$100KVariable3-6 monthsExtends to 2yr

Costs vary by scope, assessor, and readiness level

Output

  1. Recommended Assessment Type: i1, r2, or e1
  2. Justification: Why this type fits
  3. Timeline Projection: Expected duration
  4. Budget Estimate: Assessment + remediation
  5. Alternative Paths: e.g., "Start with i1, plan for r2"
  6. Key Considerations: Org-specific factors

Examples

# Vendor needing BAA compliance
/hitrust:scope-select business-associate baa-requirement

# Healthcare provider evaluating options
/hitrust:scope-select provider hipaa

# Determine best path for SaaS vendor
/hitrust:scope-select vendor competitive

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/frameworks/hitrust
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70