Essentials · 1-year
A foundational set of cybersecurity requirements (44 under CSF v11).
Usually fitsLower-risk vendors, or a first step.
Texas, U.S. · 22 weeksInterbank Messaging and Resilience Program
U.S. Southwest · 18 weeksPCI DSS 4.0.1 Transition for a Payments Processor
Austin, Texas · 14 weeksSOC 2 Type II Readiness for an HR PlatformPick the right assessment, scope it tightly and reach validation with evidence that clears HITRUST quality assurance the first time.
Choose an r2 because it sounds complete and you can spend a year on evidence nobody asked for. Choose an e1 and you may find your customer wanted an r2 all along.
We start from the requirement in your buyer’s contract. Then we scope in MyCSF, claim every piece of cloud inheritance available and remediate to the standard HITRUST quality assurance expects.
A documented choice, grounded in what your customers require.
Systems, data flows and r2 risk factors applied correctly.
Less evidence to produce wherever your providers already cover it.
Prepared to the standard your assessor and HITRUST expect.
Four questions. This is the first conversation we have with every HITRUST client, condensed.
A starting point. The customer that asked for HITRUST has the final word on the tier.
Based on HITRUST CSF v11. We confirm the current version when we scope your assessment.
A foundational set of cybersecurity requirements (44 under CSF v11).
Usually fitsLower-risk vendors, or a first step.
A broader, fixed set of leading-practice requirements.
Usually fitsModerate-risk technology vendors.
Tailored by risk factors and scored for maturity, with an interim assessment.
Usually fitsHigh data volumes, or when customers specify it.
Confirm what your customers require and settle the tier.
Requirement-level gaps and expected scores.
Policies, procedures, controls and inheritance.
Evidence organized in MyCSF and tested in a pre-assessment.
Evidence kept current through the certification period.
Why e1, i1 or r2 fits, and what the alternative would cost.
Requirement-level findings with expected scores.
What your providers cover, and what stays with you.
Evidence indexed to requirements and ready for fieldwork.
HITRUST harmonizes dozens of authoritative sources, so much of your existing evidence works twice.
| Control area | HITRUST CSF | HIPAA Security Rule | SOC 2 | ISO/IEC 27001 | NIST CSF 2.0 |
|---|---|---|---|---|---|
| Risk analysis & management | Directly addressed | Directly addressed | Directly addressed | Directly addressed | Directly addressed |
| Access control & authentication | Directly addressed | Directly addressed | Directly addressed | Directly addressed | Directly addressed |
| Encryption of health data | Directly addressed | Partially addressed | Partially addressed | Partially addressed | Partially addressed |
| Third-party assurance | Directly addressed | Partially addressed | Directly addressed | Directly addressed | Directly addressed |
| Maturity scoring | Directly addressed | Not addressed– | Not addressed– | Partially addressed | Partially addressed |
| AI system security | Partially addressed | Not addressed– | Not addressed– | Not addressed– | Partially addressed |
Directly addressed Partially addressed or different evidence expectations , Not a primary objective. AI coverage applies when the AI Security Assessment is included. HIPAA compliance is ultimately a legal determination.
Scope centers on the production platform that holds PHI. Strong cloud inheritance can cut the effort considerably.
High data volumes push r2 risk factors upward, and clearinghouse connections widen the scope.
Re-identification risk and data-use agreements decide which systems fall in scope.
Add the AI Security Assessment, and pair it with ISO/IEC 42001 when buyers want broader AI governance.
Understated volumes change r2 requirements late in the day.
Intent with no documented “how” drags scores down.
Requirements tested by hand that your providers already cover.
AI features handling health data with no inventory or review.
Requirement, tier and scope agreed.
OutputRecommendation memo
Requirement-level gap assessment.
OutputGap report
Documentation, controls and inheritance.
OutputRemediated controls
External Assessor fieldwork and submission.
OutputValidated assessment
HITRUST quality assurance and decision.
OutputHITRUST certification
An Authorized External Assessor validates your e1, i1 or r2 assessment and submits it to HITRUST, which runs quality assurance and issues the certification. We take you from scoping to that decision and manage the validated assessment along the way.
It is strong evidence of your safeguards. HIPAA compliance also covers privacy and breach notification, and it is ultimately a legal determination.
If a customer requires it, yes. Much of your SOC 2 evidence is reusable, and we plan both together so the work is done once.
Yes, when your customers accept an e1. If they specify an r2, starting lower rarely shortens the path.
Under current rules, e1 and i1 run for one year. An r2 runs for two years with an interim assessment.
Send us the clause from the contract or questionnaire. A senior practitioner will tell you exactly what it requires and how fast you can get there.