Three assessment tiers, increasing assurance. e1 is the on-ramp, i1 is the workhorse most contracts actually mean, and r2 is the risk-based gold standard. Pick by what your partners require — not by which sounds most impressive.
i1 is the target for most vendors. When a healthcare partner or BAA says "HITRUST certified," they almost always mean i1 or higher (~182 controls, 1-year, moderate threat-adaptive assurance).
e1 is the on-ramp (~44 controls, 1-year) — foundational hygiene, a fast entry point or stepping stone before you mature to i1.
r2 is the gold standard (risk-based, 2-year, can scale to hundreds of controls) — for high-risk, heavily regulated environments, or when a major partner/regulator names it specifically. Don't over-buy it if i1 satisfies your buyers.
All three tiers side by side — the factors that decide your target.
| Factor | e1 (Essentials) | i1 (Implemented) | r2 (Risk-based) |
|---|---|---|---|
| Assurance level | Foundational hygiene | Moderate, threat-adaptive | Highest, risk-tailored |
| Control count | ~44 | ~182 | Hundreds (scales to risk/scope) |
| Validity | 1 year | 1 year | 2 years (with interim) |
| What it's for | Entry point / lower-risk systems | The broad baseline most partners accept | High-risk, regulated, highest-stakes partners |
| "HITRUST certified" usually means… | Not quite — too light for most asks | This one (i1+) | This, when explicitly required |
| Effort | Lightest | Manageable step up | Substantially heavier (evidence + time) |
| Progression | Same CSF framework — e1 controls are a subset of i1, and i1 feeds r2. Work carries forward as you climb: e1 → i1 → r2. | ||
No fence-sitting. Here's how to pick your tier.
Default to i1 unless a contract tells you otherwise. The single most common scenario is a healthcare partner whose vendor requirement says "HITRUST certified" with no tier specified — and in practice that means i1 or above. i1 gives you a moderate, threat-adaptive level of assurance that satisfies most procurement and BAA requirements, on a manageable one-year cycle. For the majority of vendors, i1 is the workhorse that unblocks deals.
Use e1 as an on-ramp, not a destination. If you're early, lower-risk, or want to demonstrate baseline hygiene fast, e1's ~44 foundational controls get you a HITRUST credential quickly and build toward i1. Just don't expect e1 to satisfy a partner who's really asking for i1 — confirm what the contract actually needs before you scope e1.
Only go r2 when something forces it. r2 is the risk-based, highest-assurance certification — genuinely the right call for high-risk data at scale or when a major payer, partner, or regulator names it. But it's the heaviest lift of the three, and over-certifying to r2 when your buyers would accept i1 burns budget and months you don't need to spend. The mistake we see: a team reads "r2 is the gold standard" and chases it before any deal requires it.
The smart play is almost always to certify at the tier your nearest deal needs and climb only when a real requirement appears — the shared CSF framework means the work carries forward. For the pairwise decisions, see e1 vs i1 (the on-ramp choice) and i1 vs r2 (the graduate-to-gold choice). And if HIPAA is the underlying driver, start with HIPAA vs HITRUST — the law vs the certification. Not sure which tier your contract requires? Text PJ for a straight read.
Match your situation to the tier.
Foundational hygiene, quick to earn, a stepping stone. Confirm a partner won't actually need i1 first.
The workhorse most partners mean. Moderate assurance, 1-year, unblocks the majority of healthcare deals.
The risk-based gold standard. Heaviest lift, 2-year validity. Pursue only when a real requirement forces it.
What teams Google before choosing a HITRUST tier.
They are three assessment tiers of the HITRUST CSF at increasing levels of assurance. e1 (Essentials, 1-year) is the lightest — roughly 44 controls focused on foundational cybersecurity hygiene, meant as an entry point or for lower-risk systems. i1 (Implemented, 1-year) is the moderate-assurance tier — around 182 controls covering a broad, threat-adaptive baseline; this is what most partners mean when a contract says "HITRUST certified." r2 (Risk-based, 2-year) is the most comprehensive — a risk-tailored assessment that can scale to hundreds of controls, designed for high-risk or heavily regulated environments and the highest assurance partners can ask for.
Decide by the assurance your partners and contracts actually require. If a healthcare partner or BAA simply says "HITRUST certified," they almost always mean i1 or higher, so i1 is the practical target for most vendors. Choose e1 if you only need to demonstrate basic security hygiene or want a fast on-ramp before maturing. Choose r2 if a major partner, payer, or regulator specifically requires the risk-based, highest-assurance certification, or your data and risk profile genuinely warrant it. Read the actual contract language before deciding — over-certifying to r2 when i1 satisfies your buyers is expensive.
For the majority of vendors, i1 is enough. It delivers a moderate, threat-adaptive level of assurance that most healthcare partners and procurement teams accept, and it's a one-year certification that's far less heavy than r2. You need r2 when a specific high-stakes partner requires the risk-based certification by name, when you handle especially sensitive data at scale, or when your risk profile demands the most rigorous, tailored control set. Don't jump to r2 on the assumption that "more is safer" — start at the tier your buyers ask for and escalate only when a real requirement forces it.
e1 and i1 are one-year certifications; r2 is a two-year certification with an interim assessment. Effort scales with the tier: e1 is the lightest (foundational controls), i1 is a meaningful but manageable step up (a broad implemented baseline), and r2 is substantially heavier (a risk-tailored assessment that can span hundreds of controls and requires more evidence, documentation, and time). The two-year validity of r2 offsets some of its cost over time, but the upfront and ongoing burden is the highest of the three.
Yes, and HITRUST is explicitly designed to support that progression. The tiers share the same CSF framework, so the work you do for a lower tier carries forward: e1's foundational controls are a subset of i1's broader baseline, and i1's implemented controls feed into r2's risk-based assessment. A common path is to start at e1 or i1 to win deals quickly, then graduate to r2 when a larger partner or regulator requires the higher assurance. Sequencing this way lets you earn revenue at the tier your current buyers need while building toward the next one.