Independent HIPAA security risk analysis

Your annual SRA shouldn't be a checkbox exercise.

We perform independent HIPAA security risk assessments for healthcare practices — validated against technical evidence from the systems actually protecting your ePHI, not just what the policy says or the questionnaire asked.

Independent assessor
No security products sold
Aligned to NIST SP 800-66 Rev. 2 and the OCR Audit Protocol

Representation versus reality

The checklist says yes. The environment may disagree.

A questionnaire asks what people believe is happening. Evidence shows what is actually happening. Most SRAs stop at the first question — “Do you have this control?” — and record the answer. We ask the second one: can you demonstrate that the control is appropriately implemented and operating?

01 / IAM

MFA is required — except where it isn't.

Your policy requires multi-factor authentication, and your checklist says it's enabled. We check privileged accounts, Conditional Access exclusions, stale accounts, and emergency access accounts. An active administrator account outside the MFA policy is the kind of gap a questionnaire never finds — and an attacker looks for first.

02 / HR

The termination checklist was signed. The account is still active.

HR did the paperwork. We verify whether accounts were actually disabled — user accounts, shared mailboxes, service accounts, and vendor logins included. Offboarding that exists on paper but not in the directory is a finding, not a formality.

03 / ENC

“Yes, our laptops are encrypted.”

It's the answer every practice gives. We verify whether encryption is actually enforced and reporting healthy on each device — and whether the backups holding the same ePHI are encrypted too.

04 / BCP

Backups run every night. Nobody has ever restored one.

A backup you've never tested is a hope, not a control. We look for evidence that recovery actually works — because that's the question that matters the day you need it.

None of these show up in a self-attestation. All of them show up in an evidence-backed assessment. That's the difference between a checkbox report and a risk analysis you can defend.

The engagement

What actually happens during the assessment

No generic template. The work follows your ePHI, your systems, and the safeguards operating in your environment.

Scope

We identify where your ePHI lives: systems, workflows, locations, and vendors. The assessment covers your actual environment.

Collect evidence

We review policies, configuration exports, and system evidence relevant to the safeguards protecting ePHI.

Validate

We determine whether each safeguard operates as represented — checking accounts, settings, and activity rather than taking the policy's word for it.

Analyze risk

We evaluate threats, vulnerabilities, and existing controls to determine likelihood and impact for each finding.

Remediate

You get prioritized findings with actionable remediation steps, sequenced so your IT team or MSP knows what to fix first.

The record

Deliverables leadership, IT, and an auditor can each use

A risk analysis should support decisions at every level — without losing the trail back to the evidence.

Executive Risk Brief

What leadership needs to know: where you stand, what matters most, and what happens next. No jargon.

HIPAA Security Risk Analysis

The formal risk analysis document, structured around the Security Rule's requirement: 45 CFR §164.308(a)(1)(ii)(A).

Technical Security Assessment

Control-by-control validation results: what was tested, what the evidence showed, and where reality diverged from representation.

Risk & Remediation Register

Every finding, risk-rated and prioritized, with clear remediation actions.

Evidence Index

An inventory of every artifact reviewed, mapped to the safeguard it supports — making the analysis traceable and defensible.

Remediation Roadmap

A sequenced plan your IT team or MSP can execute, instead of a compliance binder nobody opens again.

We don't sell the security products we're evaluating.

We assess security controls. We don't make our money selling the products we're assessing — so there's no upsell hiding behind a finding and no reason to soften one.

An independent assessment means the results are the results: documented, evidence-backed, and free of any sales agenda. That's what makes the findings credible to anyone who reads them later — your board, your cyber-insurance carrier, or an auditor.

Recognized references

Not a proprietary black box.

Our methodology is grounded in recognized sources and applied to your environment. The goal isn't a thicker binder. It's an accurate, thorough risk analysis where every conclusion traces back to evidence.

  • 01
    HIPAA Security RuleRisk analysis requirement — 45 CFR §164.308(a)(1)(ii)(A)
  • 02
    NIST SP 800-66 Rev. 2Implementation guidance for the Security Rule
  • 03
    OCR Audit ProtocolThe control areas examined by OCR
  • 04
    HHS/ONC methodologySecurity risk assessment methodology

Built for practices like yours

Physician groups, dental practices, behavioral-health organizations, outpatient clinics, home-health agencies, and specialty practices — roughly 10 to 250 people — that want more than a checkbox SRA. If your MSP currently performs your assessment in-house, an independent assessment validates their work instead of asking them to grade their own homework.

Questions, answered plainly.

Why “SRA” and “risk analysis” — are they the same thing?

Mostly, yes, in everyday use. “Risk analysis” is the term the HIPAA Security Rule itself uses. “SRA” is the shorthand most practices use day to day. The deliverable is the same: a formal, evidence-backed analysis of risk to your ePHI.

Is this the same as the free HHS SRA Tool?

No. The HHS SRA Tool is a self-guided questionnaire — useful as a starting point, but it records what you tell it. Our assessment independently validates your answers against technical evidence from your systems. If you've outgrown the tool, this is the next step.

We had an SRA done last year. Why do it again?

Because staff change, systems change, and vendors change. The Security Rule expects the analysis to be current. An existing-SRA review can also tell you whether last year's assessment meaningfully reflected your technical environment before you commission a full one again.

Is this a “HIPAA audit”?

Not in the regulatory sense — only OCR conducts HIPAA audits. What most people mean by a “HIPAA audit” is an independent third-party assessment of their HIPAA security posture. That's what this is: an independent assessment conducted with the rigor an auditor would expect to see.

Will this make us “HIPAA certified”?

There is no such thing as HIPAA certification — no government body issues one. An evidence-backed risk analysis gives you something real: documented proof that you performed a serious, thorough analysis and are addressing what it found.

Does this guarantee we'll pass an OCR audit?

No honest assessor can promise that. What it does is put you in a defensible position: an accurate, thorough risk analysis, grounded in evidence, with documented follow-through on findings.

Do you work with our MSP?

Yes. We coordinate evidence collection with your IT team or MSP, and the remediation roadmap is built for them to execute. The difference is that the assessment itself is independent — your MSP doesn't grade its own homework.

Start with the environment you have

Find out what your safeguards actually do.

Request an assessment, or start with a review of your current SRA. Either way, you'll talk with an assessor — not a sales rep.

Independent, evidence-backed review