There is no such thing as a HIPAA certificate.

  • We tell you plainly what your customer is asking for: HIPAA aligned safeguards you can show, a HITRUST e1 or i1, or both.
  • We find where patient data lives in Microsoft 365 and Azure, update the risk analysis and set the safeguards with your IT team or MSP.
  • You get evidence a health system’s vendor review or a HITRUST external assessor can follow.

Book a 30 minute call

How HIPAA and HITRUST work flowsLine drawing. A vendor review asks for a HIPAA certificate, which does not exist. The work finds where patient data lives in the Microsoft 365 tenant and on devices, in Exchange, Teams and SharePoint, and what is met outside the tenant: business associate agreements, training and facilities. A risk analysis sets the safeguards. That produces evidence for vendor reviews, and, for HITRUST e1 or i1, controls that run for 90 days before an external assessor tests them.Vendor review“Send your HIPAA certificate”Where patient data livesMicrosoft 365 tenant and devicesExchange, TeamsSharePointOutside the tenantBAAs, training, facilitiesHIPAA alignedEvidence forvendor reviewsHITRUST e1 or i1Controls run90 days firstExternal assessorThey need evidenceRisk analysis first

200+ Microsoft 365 and Azure tenants. 100+ engagements. HITRUST e1 and i1 work for healthcare clients. 20+ years in regulated technology.

Why we say HIPAA aligned

HHS “does not endorse or otherwise recognize private organizations’ ‘certifications’ regarding the Security Rule.”

So nobody can sell you a HIPAA certificate. What a health system can check is evidence that your safeguards are in place, or a HITRUST result from an independent external assessor.

What you are being asked for, and what to send

Three requests that usually start this work.

“Please send your HIPAA certificate.”

Typical ask from a health system’s vendor review

There is no such certificate. The reviewer wants to know that patient data is protected where you keep it.

What to sendA summary of your current risk analysis, the safeguards in place and who owns them, or a HITRUST result.

“HITRUST e1 or i1 is required.”

Typical ask from a customer’s procurement team

The level sets the scope: 44 requirements for e1 on CSF v11.9, 182 for i1. Both are valid for one year.

What to askWhich level, and by when. Then check that date against the 90 day rule below.

“When did we last update the risk analysis?”

Typical question from your own compliance lead

The Security Rule requires an accurate and thorough risk analysis, and OCR has made it the focus of an enforcement initiative. One written years ago, before the move to Microsoft 365, will not describe what you run today.

What to doUpdate it when systems change, and keep each dated version.

HITRUST e1, i1 or r2, and the 90 day rule

Each level adds scope. None of them can be tested the week your controls go live.

e1

Essential safeguards

Requirements
43
Valid for
One year
Fits when
It is a first assessment, or the program is still being written down

i1

Leading security practices

Requirements
182
Valid for
One year, with no interim assessment
Fits when
A customer names it, or a documented program is already in place

r2

Risk based, tailored to you

Requirements
Set by your own risk factors, so the count varies
Valid for
Two years, with an interim assessment at the one year mark
Fits when
A customer names it, or your risks call for the broadest scope

The 90 day rule

HITRUST asks that controls run for at least 90 days before the assessor tests them, and testing has to finish within a 90 day window. So the timeline starts when your controls are in place, not when the assessment is booked.

90 days
A control has to be in place and operating before the external assessor can test it as implemented.
60 days
Policies and procedures have to be in place before the assessor can consider them.
90 day window
All of the assessor’s testing happens in one window that ends when you sign the management representation letter.

Not sure what your customer is asking for? Take the HIPAA and HITRUST check

Last checked

Where the HIPAA Security Rule stands, November 2026

The overhaul is still a proposal. Enforcement of the current rule is not waiting for it.

Proposed

Proposed Security Rule changes published

The proposal would require encryption of patient data with limited exceptions, multifactor authentication, and an inventory of technology assets with a map of how patient data moves. Comments closed on March 7, 2025, and no final rule has been issued.

Long term

Final action moved to July 2027

The 2026 Unified Agenda, published in July 2026, lists the rule as a long term action with final action projected for July 2027. Agenda dates often slip, so we check each new agenda.

Enforced

Risk analysis is what OCR checks first

OCR announced its 14th enforcement action under its Risk Analysis Initiative, a settlement with a group health plan after a ransomware attack. The current rule already requires an accurate and thorough risk analysis.

How the work runs, and what sets the time

From where patient data lives to a result you can show. A step gives a length only when a rule sets one.

  1. A 30 minute call

    Length 30 minutes

    Bring the customer’s request and your last risk analysis. You leave knowing what they are really asking for, and whether HITRUST is part of it.

  2. Find where patient data lives

    What sets the time How many places hold patient data, inside and outside the tenant

    We trace patient data through Exchange, SharePoint, OneDrive, Teams and devices, and list the vendors that handle it. That map is the scope for everything after it.

  3. Risk analysis

    What sets the time The size of the map, and how quickly owners can answer questions

    For each place patient data lives: the threats, the safeguards in place, the risk that is left and who owns it. Dated, so you can show when it was done.

  4. Safeguards and evidence

    What sets the time What the risk analysis finds, and whether new licenses are needed

    We set MFA, encryption, device rules, sharing limits and logging in Entra ID, Intune, Defender and Purview with your IT team or MSP, in stages so nobody is locked out. Policies and training are written for how your people work. Business associate agreements, facilities and training are documented with the people who own them.

  5. HITRUST, if you need it

    Length At least 90 days of operation before testing, then a 90 day testing window. HITRUST sets both.

    An external assessor organization tests the controls and submits the assessment to HITRUST. We prepare the evidence and support you through it. We are not your assessor.

What we need from your side

Admin access agreed with your IT team, a person who can approve changes, your security official, the customer’s request, your last risk analysis and your list of vendors that handle patient data. Training, facilities and vendor agreements need the people who own them. Your point of contact is a senior security and compliance lead who also directs the engineering in Microsoft 365 and Azure.

What you get is evidence someone else can check

Three formats from a HIPAA and HITRUST engagement. Each one is a sample format with illustrative content, not a client’s document.

Risk analysis register

Where patient data lives, what threatens it, what protects it and who owns the risk that is left.

Risk analysis register, 45 CFR 164.308(a)(1)

Sample format, illustrative content

Sample risk analysis register
Where it lives Threat Safeguard Owner Risk left
SharePoint: intake forms Shared by links anyone can open Planned: sharing limited to named people, and a sensitivity label on the library Practice manager High
Exchange Online Phishing that leads to a taken over mailbox MFA through Conditional Access, Defender for Office 365 IT lead Medium
Billing team laptops A lost or stolen laptop BitLocker enforced through Intune, with remote wipe IT lead Low
Teams chat with a billing vendor Patient data shared with a vendor Outside the tenant: a business associate agreement on file. In it: guest access reviewed each quarter Compliance lead Medium

HITRUST 90 day tracker

When each control went live, and the first day the assessor can test it.

HITRUST e1, 90 day tracker

Sample format, illustrative content

Sample HITRUST 90 day tracker
Control In place since Testable from Status
MFA for remote access and email Jan 12 Apr 12 Ready
Security policy approved Feb 2 Apr 3, as policies need 60 days Ready
Laptop encryption Mar 3 Jun 1 Running
Vendors checked against their contracts Not yet 90 days after it starts Not started

Vendors that handle patient data

The Security Rule expects business associate agreements with vendors that handle patient data. This list shows which ones you have.

Vendor and agreement list

Sample format, illustrative content

Sample vendor and agreement list
Vendor Patient data Agreement
Microsoft 365 and Azure Yes On file Microsoft’s Data Protection Addendum
Billing service Yes On file
Phone system with voicemail to email Yes Missing
Marketing email tool No Not needed

Work we have delivered

Real engagements, described without naming the clients.

  • Healthcare, HITRUST

    HITRUST e1 and i1 work for healthcare clients.

  • Incident response

    A full Microsoft 365 incident response after an adversary in the middle (AiTM) session token theft.

  • Independent assessment

    A defense contractor we prepared passed its CMMC Level 2 C3PAO assessment with every requirement met.

About Ethereum Tech

Who this is for, and who it is not for

A good fit

  • Healthcare providers, clinics and practices on Microsoft 365.
  • Health technology companies and other vendors asked for HIPAA proof or a HITRUST result.
  • Teams whose risk analysis was written before their current systems.
  • IT teams and MSPs that want a specialist beside them.

Not a fit

  • You want a HIPAA certificate. None exists.
  • You need the HITRUST assessment itself. An external assessor organization runs it, independent of us.
  • You want a report with no changes made.
  • You need help desk support.
  • You need a legal opinion, for example on whether you are a business associate or what an agreement should say. That belongs with your counsel.

Questions before you book

Can you give us a HIPAA certificate?

No one can, in any official sense. HHS does not recognize private HIPAA certifications. What we give you is HIPAA aligned safeguards you can show, and HITRUST readiness when a customer wants outside assurance.

Which HITRUST level?

The one your customer names. If they have not named one, e1 is 44 requirements on CSF v11.9 and suits a first assessment, and i1 is 182 and suits a documented program. Both last one year. r2 is risk based, lasts two years and needs an interim assessment at the one year mark.

How soon can we have an e1?

Not before the 90 day rule allows. Each control has to run for at least 90 days before the assessor tests it, and testing happens within a 90 day window. So the date depends on how many of the e1 requirements already run today, which the first review shows.

Do we need a business associate agreement with Microsoft?

If patient data is in Microsoft 365 or Azure, the Security Rule expects one. Microsoft includes its HIPAA business associate agreement by default in its Data Protection Addendum for in scope services. Microsoft also says that using its services does not on its own make you compliant. How you set them up is what we work on.

Can controls Microsoft runs count toward HITRUST?

Some can. Microsoft supports HITRUST’s shared responsibility program, and when a service provider’s HITRUST certification covers a requirement, you may be able to rely on it without waiting out the 90 days. Your own settings, users and data stay your responsibility.

Does the proposed rule change our plan?

Not yet. It was proposed on January 6, 2025, and final action is projected for July 2027. We build to the current Security Rule and treat the proposals, such as required encryption and MFA, as good practice.

Are you the HITRUST assessor?

No. An external assessor organization performs the assessment. We prepare you and support you through it.

Do you replace our IT provider or MSP?

No. We work with your IT team or MSP. We make or guide the changes in Entra ID, Intune, Defender and Purview, and they keep running the environment day to day.

How is the work priced?

As a fixed scope project, or as a fractional security and compliance officer on retainer. We agree the scope in writing before work starts.

What happens after you book

  1. Pick a 30 minute time that suits you.
  2. We talk through the request, your date and where patient data lives.
  3. You leave knowing what to send and whether HITRUST is part of it.

Bring the customer’s request and your last risk analysis to a 30 minute call.

You leave knowing what to send, which HITRUST level fits and what comes next.

Book a 30 minute call

(786) 577-9743 sales@ethereumtech.ai