HITRUST e1 vs i1: Choosing the Right Assessment as You Grow

HIPAA and HITRUSTPublished Last reviewed November 20267 min read

Short answer

HITRUST e1 is a foundational, one year validated assessment of 44 requirement statements on CSF v11.9, or 43 on v11.8, suited to younger or lower risk vendors. HITRUST i1 is a moderate assurance, threat adaptive assessment of 182 requirement statements, also valid for one year, with a lighter rapid recertification in year two. A growing health tech vendor should pick the one its largest customers and payers will accept in writing.

Check where you stand: take the HIPAA and HITRUST check. About two minutes, no email needed.

Update, November 2026

HITRUST released CSF v11.9.0 in late September 2026, and its e1 baseline is 44 requirement statements while the i1 stays at 182. New e1 and i1 assessments can be created on v11.8.0 only through December 31, 2026, and e1 and i1 assessments on v11.8.0 and earlier must be submitted by March 31, 2027.

For most growing health tech and healthcare services vendors, the right first HITRUST assessment is the one your largest customers will accept. The e1 is a foundational assessment of 44 requirement statements on CSF v11.9, or 43 on v11.8, valid for one year. The i1 is a moderate assurance, threat adaptive assessment of 182 requirement statements, also valid for one year. Ask your customers before you choose, because an e1 report that a health plan’s risk team will not accept means doing the work twice.

What is the difference between HITRUST e1 and i1?

Breadth and assurance. The e1 covers a short list of foundational security practices, while the i1 covers a much broader set chosen to address current threats. Both involve external assessor testing and centralized quality assurance by HITRUST, and both are valid for one year.

The numbers move with the CSF version, so check them against the version you will be assessed on. The e1 launched in January 2023 with 44 requirement statements. In CSF v11.7.0, released December 18, 2025, HITRUST set the e1 baseline at 43 and kept the i1 at 182. HITRUST released v11.8.0 in May 2026, and since May 7, 2026, new e1 and i1 assessments in MyCSF have to be created on v11.8.0.

AssessmentRequirement statementsAssuranceValid forUsually fits
e144 on CSF v11.9, 43 on v11.8Foundational1 yearYoung vendors, lower risk data flows, a first step toward the i1
i1182Moderate, threat adaptive1 year, with rapid recertification in year twoVendors that store PHI at volume or connect to customer systems
r2Tailored to risk factorsHighest2 yearsLarge vendors, or customers that require it by contract

The r2 sits above both as a tailored, risk based review of policy, procedure and implementation, valid for two years. The i1, in HITRUST’s words, is focused on implementation and threat adaptability, and its rapid recertification in year two tests a smaller core set of requirements instead of the full 182.

How do customers and payers use e1 and i1 reports?

Mostly as a stand in for their own vendor security review. A health system or health plan risk team takes your report and decides whether it can skip or shorten its own questionnaire and the follow up calls that usually come with it.

That is why the assessment type matters. HITRUST positions the e1 for lower risk programs and lightweight third party risk reviews, and the i1 for organizations that need threat relevant assurance. In practice, a hospital buying a scheduling tool that never touches clinical data may accept an e1. A payer sending you member files, or a provider group connecting your platform to its EHR, will often ask for an i1 or an r2, and some write the required level into the master services agreement or the business associate agreement. Read that contract language before you pick.

A HITRUST report is also not a HIPAA certification. It does not replace the Security Rule risk analysis you still owe under 45 CFR 164.308(a)(1)(ii)(A), and our HIPAA aligned security work treats the two as related but separate efforts.

Should a growing vendor choose the e1 or the i1?

Choose the e1 when your customers will accept it and your security program is still young. Choose the i1 when you handle meaningful volumes of PHI, sell to payers or larger health systems, or already know a customer will ask for it.

In our HITRUST e1 and i1 work for healthcare clients, four questions usually settle it:

  1. What did your top customers and your most important prospects ask for, in writing?
  2. How much PHI do you store or process, and do you connect to customer systems?
  3. Is your security program documented today, or will the assessment be the first time anyone writes policies down?
  4. Do you expect to need an i1 or an r2 within the next two years anyway?

HITRUST says validated e1 results can serve as a building block toward a later i1 or r2, so an e1 is not wasted. Still, the i1 tests roughly four times as many requirements, and preparing for them is the real work. If the first or last question points to an i1 within a year, we usually recommend going straight to it. Mapping that path against your sales pipeline is part of our GRC advisory and planning work.

How do Microsoft 365 and Azure controls map into a HITRUST assessment?

Through shared responsibility and inheritance. Azure has held HITRUST CSF certification since November 2016, and through the HITRUST Shared Responsibility and Inheritance Program you can prepopulate your MyCSF assessment with controls that are fully inherited from Azure or shared with it. A Microsoft HITRUST administrator then completes Microsoft’s part of the assessment in MyCSF.

Inheritance covers the platform, not your configuration. Microsoft is direct that you remain responsible for your own HITRUST CSF requirements, and that what you can rely on depends on which Azure offerings you use and how you implemented them. Microsoft’s HITRUST certification letter covers Azure, Dynamics 365, Power Platform and select Microsoft 365 services, so confirm a service is listed before you plan to inherit anything from it.

Your side of the shared responsibility matrix is where most evidence comes from, and a well run tenant produces a lot of it:

  • Access control: Conditional Access policies that require MFA, privileged role assignments in Microsoft Entra ID, and access review results.
  • Endpoint and mobile device security: Intune compliance policies, BitLocker status and Microsoft Defender for Endpoint onboarding.
  • Audit logging and monitoring: Microsoft Purview Audit retention settings and records of how alerts were reviewed and closed.
  • Data protection: sensitivity labels, Microsoft Purview Message Encryption, data loss prevention policies and retention policies.
  • Azure configuration: Azure Policy assignments and Microsoft Defender for Cloud recommendations for the subscriptions in scope.

Azure Policy includes a built in HITRUST and HIPAA regulatory compliance initiative, but it maps to HIPAA HITRUST 9.2 controls, an older CSF version, and Microsoft itself calls Azure Policy compliance a partial view of your overall status. Use it to find gaps, not as your evidence package. Our Microsoft 365 compliance work usually starts from exactly that gap list.

How should you prepare evidence for an e1 or i1?

Prepare evidence that proves each requirement is implemented across the full scope, dated inside the assessment window. A policy on its own rarely carries an implementation requirement.

  1. Fix the scope first: systems, Azure subscriptions, the Microsoft 365 tenant, facilities and the people in scope. Every system added late means more testing.
  2. Map each requirement statement to an owner and an evidence source before fieldwork starts.
  3. Export configuration evidence straight from the source: Conditional Access policies, Intune compliance reports, Purview audit settings and Azure Policy compliance state. Exports and screenshots that show dates and the tenant name hold up better than written descriptions.
  4. Collect samples for recurring controls: access reviews, offboarding tickets, vulnerability scan results, backup restore tests and training completion records.
  5. Start inheritance requests in MyCSF early so Microsoft’s portion is complete when your assessor needs it.
  6. Log every gap as a corrective action with an owner and a target date.

If you are weighing the e1 against the i1, our starting point check is a short way to see where your program stands today.

When you are ready, book a 30 minute call and we will look at what your customers are asking for and which assessment fits.

Frequently asked questions

Can an e1 be upgraded to an i1 later?

Not as a simple upgrade. HITRUST says validated e1 results can be applied as a building block toward a future i1 or r2, so the work carries forward. The i1 still tests 182 requirement statements, so expect to produce new evidence for everything the e1 did not cover.

Does a HITRUST report satisfy HIPAA?

Not on its own. The HITRUST CSF builds on HIPAA requirements, but there is no HHS approved certification for HIPAA. You still need your own Security Rule risk analysis, risk management plan and policies, and many customers review those separately from your HITRUST report.

Which HITRUST CSF version will a new e1 or i1 use?

The current one at the time you create the assessment. HITRUST announces creation and submission deadlines for each version in its advisories, and since May 7, 2026, new e1 and i1 assessments in MyCSF must be created on CSF v11.8.0. Requirement counts can shift slightly between versions.

What happens when an i1 reaches the end of its first year?

The i1 is valid for one year. In year two HITRUST offers a rapid recertification that focuses on approximately 60 core requirements rather than the full 182, which reduces the testing effort. Plan it early so your report does not lapse in the middle of a customer review.

Can we inherit HITRUST controls for Microsoft 365, not just Azure?

Possibly, for some services. Microsoft’s HITRUST certification letter covers Azure, Dynamics 365, Power Platform and select Microsoft 365 services. Inheritance is requested through MyCSF, and you remain responsible for how you configure access, devices and data protection in your own tenant.

Keep reading

Related guides

Have a question this raised?

Bring it to a 30 minute call and leave knowing where you stand and what comes next.

Book a 30 minute call

(786) 577-9743sales@ethereumtech.ai

Or take the two minute starting point check