Skip to content
HIPAA ComplianceConsulting

Security Advisory Services

HIPAA Security Consulting

Ongoing advisory to design and run a Security Rule program: governance, administrative, physical and technical safeguards, vendor and cloud security, and incident readiness.

Reviewed Request a HIPAA Consultation

An assessment tells you where you stand on one date. Security consulting is about what happens on every other date: who owns security decisions, how safeguards are chosen and maintained, how vendors and cloud services are vetted, and how the organization responds when something goes wrong.

Our HIPAA security consulting work helps covered entities and business associates build and operate a Security Rule program that holds up over time — one that your IT team can run, your leadership can understand, and your documentation can support.

Key points

  • Security consulting is continuous program work; an assessment is a point-in-time snapshot.
  • We advise across administrative, physical and technical safeguards, plus vendor and cloud security.
  • We separate HIPAA requirements from recommended practices such as MFA, EDR and penetration testing.
  • We work alongside your IT team and managed service providers rather than replacing them.

What HIPAA security consulting includes

Security consulting is a set of advisory workstreams you can engage together or individually. Most clients start with one urgent need and expand as the program matures.

Security Rule program design

Translating the Security Rule into a working program: roles, policies, procedures, a risk management cycle and an evaluation schedule. For the regulatory detail behind this, see our Security Rule consulting service.

Security governance

Designating and supporting the security official (§164.308(a)(2)), setting up a risk acceptance process, defining reporting to leadership, and making sure decisions are documented.

Safeguards advisory

Practical guidance on administrative (§164.308), physical (§164.310) and technical (§164.312) safeguards — what to implement, how to evidence it, and how to document decisions on addressable specifications.

Vendor and cloud security

Business associate due diligence, BAA coverage under §164.314 and §164.504(e), and shared-responsibility reviews for cloud and SaaS platforms. Related work is covered under HIPAA cloud compliance consulting.

Incident readiness

Security incident procedures (§164.308(a)(6)), contingency planning (§164.308(a)(7)), tabletop exercises and coordination with breach notification obligations.

Security consulting vs. a one-time assessment

The two work best together. An assessment such as a security risk analysis gives the consulting work a factual baseline; consulting turns findings into a program that improves between assessments.

One-time assessmentSecurity consulting
Time frameDefined start and end dateOngoing or recurring
Main outputReport of risks or gapsDecisions, designs, documents and guidance as you go
Question answeredWhere are we now?What should we do next, and how?
Typical triggerMissing or outdated risk analysis, customer requestGrowth, new systems, repeated findings, no in-house security lead
IndependenceEasier to keep findings independentAdvisor is closer to decisions; periodic independent review still recommended

Who benefits from security consulting

  • Practices and clinics where the “security official” is an office manager or outsourced IT provider without dedicated HIPAA time.
  • Healthcare SaaS and health IT vendors scaling quickly and fielding security questionnaires from covered entity customers.
  • Telehealth and digital health companies adding integrations, devices or new states.
  • Hospitals and health systems that need independent advice on specific programs such as vendor risk or incident response.
  • Business associates such as billing and transcription companies that need a right-sized program.

Regulatory considerations

The Security Rule is deliberately flexible. Under §164.306(b), organizations may use any security measures that allow them to reasonably and appropriately implement the standards, taking into account size, complexity, capabilities, technical infrastructure, cost and the probability and criticality of potential risks. That flexibility is useful, but it shifts the burden onto you to document why your choices are reasonable.

Addressable implementation specifications — such as encryption at rest (§164.312(a)(2)(iv)) or automatic logoff — are not optional. You must assess whether each is reasonable and appropriate, then implement it, implement an equivalent alternative, or document why neither is reasonable.

Under a 2021 amendment to the HITECH Act, HHS must consider whether an organization had recognized security practices in place for the previous 12 months when making certain enforcement decisions. Practices such as the NIST Cybersecurity Framework and the HHS 405(d) Health Industry Cybersecurity Practices (HICP) are commonly used for this purpose. This is a factor HHS considers, not a safe harbor.

Common security challenges

  • Policies that describe controls the organization does not actually run.
  • Shared or generic logins in clinical areas that defeat unique user identification (§164.312(a)(2)(i)).
  • Audit logs that are enabled but never reviewed, leaving information system activity review (§164.308(a)(1)(ii)(D)) unmet in practice.
  • Backups that have never been restored in a test, weakening the contingency plan.
  • Vendors handling ePHI without a BAA, or with a BAA but no security due diligence.
  • Assuming a cloud provider’s BAA makes the customer compliant — it does not; configuration and access remain your responsibility.

Our consulting approach

  • Baseline first: we start from your most recent risk analysis, or recommend one if it is missing or stale.
  • Prioritize by risk and obligation: legal requirements and high risks before nice-to-have improvements.
  • Fit the organization: controls sized for a five-provider practice look different from those for a multi-tenant SaaS platform.
  • Work through your people: we advise and document; your IT staff or managed service provider implements.
  • Keep evidence as you go, so the program is defensible if OCR or a customer asks.

Typical deliverables

  • Security program charter and roles, including the designated security official’s responsibilities.
  • Updated security policies and procedures mapped to Security Rule standards.
  • Decision records for addressable implementation specifications.
  • Vendor risk process, BAA tracker and cloud shared-responsibility matrix.
  • Incident response plan and tabletop exercise summary.
  • Periodic status reports for leadership.

Engagement process

  1. 1

    Discovery

    We review your current program, recent assessments, organization chart and the systems and vendors in scope.

  2. 2

    Program roadmap

    We agree on priorities and a sequence of workstreams, typically over the next two to four quarters.

  3. 3

    Workstream delivery

    We run each workstream with your owners — drafting documents, advising on control choices and reviewing evidence.

  4. 4

    Regular check-ins

    Scheduled working sessions keep decisions moving and record what has been done.

  5. 5

    Periodic re-baselining

    We revisit the risk analysis and roadmap after major changes or at an agreed interval.

Cost factors

Security consulting is usually scoped as a defined project or a recurring advisory arrangement. Cost depends on the number of workstreams, the size and complexity of your environment, how much documentation already exists, how many vendors and cloud services are in scope, and how much hands-on drafting you want from us versus review of your team’s work. We provide a written scope before any engagement begins; the HIPAA consulting cost page explains the drivers further.

Frequently asked questions

Do you implement security tools, or only advise?

Our role is advisory: we help you decide what to implement, document decisions and review evidence. Your IT team or managed service provider typically handles implementation. We can coordinate with them directly.

Is MFA required by HIPAA?

Not explicitly under the current Security Rule, although it is a widely recommended way to meet person or entity authentication and access control standards. The January 2025 NPRM proposed requiring it; that proposal is not final, so check its current status.

We use a HIPAA-eligible cloud provider. Are we covered?

A cloud provider signing a BAA covers its own obligations. You remain responsible for how you configure, access and monitor your environment. This is a shared-responsibility model, and both sides must do their part.

Can security consulting replace our risk analysis?

No. The risk analysis is a specific required activity. Consulting builds on it. If your analysis is missing or outdated, we will usually recommend completing one early in the engagement.

Does following NIST or HICP make us compliant?

Aligning with recognized frameworks is strong evidence of a reasonable program and is a factor HHS must consider in some enforcement decisions, but it is not proof of compliance on its own. You still need to meet each HIPAA standard and document your decisions.

Authoritative sources

This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.

Talk through your HIPAA obligations with a consultant

Tell us about your organization, how you handle patient information, and what’s prompting the review. We’ll suggest a practical scope — and tell you if you don’t need us.