Skip to content
HIPAA ComplianceConsulting

Regulatory Advisory Service

HIPAA Security Rule Consulting

Standard-by-standard guidance on the Security Rule: what each implementation specification requires, how to meet it in your environment, and how to document the decision.

Reviewed Request a HIPAA Consultation

The HIPAA Security Rule is short compared with many regulations, but it is dense. It sets out standards across administrative, physical and technical safeguards, attaches required and addressable implementation specifications to many of them, and leaves much of the “how” to each organization. That flexibility is where most compliance mistakes happen.

Security Rule consulting is the regulatory side of our security work. Where HIPAA security consulting covers program building and governance broadly, this service focuses on interpreting the rule itself, mapping each requirement to your systems, and producing the documentation that shows your choices were reasoned.

Key points

  • Applies to ePHI only; covers 45 CFR §§164.302–164.318.
  • Flexibility under §164.306(b) must be backed by documented reasoning.
  • Every addressable specification needs a recorded decision.
  • We track the proposed 2025 Security Rule changes but assess against the current rule.

Service overview

We work through the Security Rule with your team standard by standard. For each implementation specification we establish what the rule requires, what you currently do, whether that is reasonable and appropriate for your size and risk profile, and how it is documented. The result is a clear map from regulation to controls, with gaps and decisions recorded.

Who needs Security Rule consulting

  • Organizations whose IT team or managed service provider is technically capable but unfamiliar with the Security Rule’s structure.
  • Healthcare IT vendors and SaaS platforms mapping product controls to HIPAA for customers.
  • Practices with policies copied from templates that do not reflect their actual systems.
  • Organizations that skipped addressable specifications without documenting why.
  • Compliance leaders preparing for possible changes from the proposed Security Rule update.

Regulatory considerations

The Security Rule is organized into general rules (§164.306), administrative safeguards (§164.308), physical safeguards (§164.310), technical safeguards (§164.312), organizational requirements including business associate contracts (§164.314), and policies, procedures and documentation (§164.316).

Examples of required and addressable implementation specifications (current rule)
Safeguard areaRequired (examples)Addressable (examples)
Administrative — §164.308Risk analysis; risk management; sanction policy; information system activity review; security incident response and reporting; data backup, disaster recovery and emergency mode operation plansWorkforce clearance; termination procedures; security reminders; log-in monitoring; password management; contingency plan testing
Physical — §164.310Disposal of ePHI and media; media re-useFacility security plan; access control and validation; maintenance records; media accountability
Technical — §164.312Unique user identification; emergency access procedure; audit controls (standard); person or entity authentication (standard)Automatic logoff; encryption and decryption; mechanism to authenticate ePHI; transmission encryption

Common Security Rule challenges

  • Treating “addressable” as “optional” and leaving no documentation of the decision.
  • Audit controls enabled in the EHR but not in email, file storage or cloud consoles that also hold ePHI.
  • Contingency plans that cover backup but not emergency mode operations or restoration priorities.
  • Termination procedures that disable network accounts but miss SaaS applications and shared credentials.
  • Encryption decisions based on vendor marketing rather than verified configuration.
  • Security policies that are not reviewed periodically or updated as required by §164.316(b)(2)(iii).

Our approach

We use NIST SP 800-66 Rev. 2, which maps each Security Rule standard to key activities and to related NIST guidance, as our working reference. For each specification we look for evidence of implementation rather than relying on policy language.

Documenting addressable decisions

For each addressable specification we produce a short decision record: the risk it addresses, whether implementation is reasonable and appropriate, what you implemented (or the equivalent alternative), and who approved it. Those records are retained under §164.316 and are among the first things reviewers ask for.

Scaling the rule to your organization

Section 164.306(b) lets you weigh your size, complexity, capabilities, technical infrastructure, the cost of security measures and the probability and criticality of potential risks. That does not mean small organizations can skip standards; it means the way a standard is met can differ. Audit controls for a four-person practice using a cloud EHR may rely heavily on the vendor’s logging plus a documented monthly review, while a hospital may need centralized log collection and alerting. We help you choose and document the approach that fits.

Periodic evaluation

The evaluation standard (§164.308(a)(8)) requires periodic technical and nontechnical evaluation in response to environmental or operational changes affecting ePHI security. We set up a simple trigger list — new systems, new vendors, new locations, incidents — so the control map is revisited when it matters, not only on an annual date.

Linking to risk analysis

Decisions about safeguards should trace back to your security risk analysis. Where that analysis is missing or outdated, we recommend updating it first, because §164.306(b) expects safeguard choices to reflect the probability and criticality of potential risks.

Typical deliverables

  • Security Rule control map: every standard and implementation specification, current implementation, owner and evidence location.
  • Decision records for each addressable implementation specification.
  • Security policies and procedures aligned to the control map — see HIPAA policies and procedures.
  • Prioritized list of gaps, labelled as HIPAA requirements or recommended practices.
  • Briefing note on the proposed Security Rule changes and their potential impact on your environment, clearly marked as proposed.

Engagement process

  1. 1

    Kickoff

    We confirm scope, the systems that hold ePHI and who owns each safeguard area.

  2. 2

    Standard-by-standard review

    Working sessions with IT and compliance cover administrative, physical and technical safeguards in turn.

  3. 3

    Evidence check

    We review configuration exports, logs and records that demonstrate each control.

  4. 4

    Decisions and documentation

    We draft decision records and policy updates for your review and approval.

  5. 5

    Close-out

    You receive the control map and gap list, with a review schedule to keep them current.

Cost factors

The main factors are the number and type of systems holding ePHI, whether you operate on-premises, in the cloud or both, the number of locations, the state of existing policies and evidence, and whether you need a full control map or a focused review of specific safeguard areas. Organizations with a recent, well-documented risk analysis typically need less discovery time. The Security Rule requirements resource outlines the full scope.

Frequently asked questions

Does the Security Rule require encryption?

Under the current rule, encryption of ePHI at rest and in transmission are addressable implementation specifications. You must assess whether encryption is reasonable and appropriate and either implement it, implement an equivalent alternative, or document why neither is reasonable. In practice, encryption is widely implemented, and properly encrypted data may fall outside the definition of unsecured PHI for breach notification purposes.

Does the Security Rule apply to business associates?

Yes. Business associates are directly subject to the Security Rule for the ePHI they create, receive, maintain or transmit on behalf of covered entities.

Is the 2025 proposed rule in effect?

It was published as a proposal on January 6, 2025. Proposed rules are not enforceable until finalized and effective. Check the Federal Register and HHS for its current status.

How is this different from your security consulting service?

Security Rule consulting focuses on interpreting and mapping the regulation and documenting compliance decisions. Security consulting is broader program work — governance, vendor and cloud security, incident readiness — that builds on that foundation.

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.