Subcontractor Obligations in Business Associate Contracts: How obligations flow down the chain

Auditors ask about subcontractor obligations in business associate contracts early, because the answer tells them how the rest of the program is likely to look. The requirement is 45 CFR 164.314(a)(2)(iii).

What the rule says

45 CFR 164.314(a)(2)(iii) governs subcontractor obligations in business associate contracts. The operative text is not reproduced here: read it at the source linked below, because the conditions in it are the requirement and a summary of a conditional rule is not a safe substitute for the rule.

This is a required implementation specification. 45 CFR 164.306(d)(2) gives no documented-alternative route: you implement it, or you have a finding.

What this looks like in practice

In an assessment, 45 CFR 164.314(a)(2)(iii) is not one question. It resolves into several, and each one is really asking for different evidence. These are among the questions asked about it:

• Does the organization periodically reassess the security posture of existing third parties, with higher-risk parties reviewed more frequently?
• Do the organization's agreements require third parties to obtain equivalent protective commitments from any subcontractor that handles the organization's sensitive data on their behalf?

Ownership usually sits with the security official, though the evidence is often produced by someone else, which is where the trail breaks. A control that works but has no owner tends to stop working the month the person who quietly maintained it changes roles.

Who this applies to

Every business associate that permits a subcontractor to create, receive, maintain, or transmit ePHI on its behalf (45 CFR 164.308(b)(2)). 45 CFR 164.314(a)(2)(iii) applies the contract requirements of (a)(2)(i) and (a)(2)(ii) to that contract; a covered entity has no duty under this clause.

Building it, in order

These steps are one way to meet it, drawn from our question bank. Unless a step names a provision, the Security Rule does not require that particular measure: 45 CFR 164.306(b)(1) lets you use any security measures that allow you to reasonably and appropriately implement the standards and implementation specifications, chosen with the factors in 45 CFR 164.306(b)(2).

The sequence below is the order that produces evidence as a by-product rather than as a separate documentation exercise:

1. Define review cadences by risk tier (for example annual for high-risk, less frequent for lower-risk parties).
2. At each review, request updated independent audit reports, refreshed security questionnaire responses, or other evidence of current safeguards.
3. Track findings, require remediation of gaps, and record review dates in the vendor inventory.
4. Record how the measure chosen meets the cited provision. 45 CFR 164.306(b)(1) lets the organization use any security measures that allow it to reasonably and appropriately implement the standards and implementation specifications, and the Security Rule does not name this practice. The cited standard and any Required implementation specification must be met. An Addressable one must be implemented, or the organization documents why it is not reasonable and appropriate and implements an equivalent alternative measure if that is reasonable and appropriate (45 CFR 164.306(d)(3)). Choose the measure with the factors in 45 CFR 164.306(b)(2) and document it with the risk analysis.
5. Require each third-party agreement to obligate the third party to identify any subcontractor that will handle the organization's sensitive data.
6. Require the third party to bind each such subcontractor, by contract, to "agree to comply with the applicable requirements of this subpart", the Security Rule (45 CFR 164.314(a)(2)(i)(B), applied to the subcontract by 164.314(a)(2)(iii)).

Where else this maps

The questions behind 45 CFR 164.314(a)(2)(iii) also map to NIST SP 800-66 Rev. 2 5.1.9, 5.4.1, which is voluntary guidance rather than law; following it does not by itself establish compliance with any law. That matters for scoping: the same evidence can be written once and referenced from each, rather than rewritten per framework.

Evidence an assessor asks for

For this requirement the evidence types that satisfy it are agreement and report. The distinction matters more than it looks: a policy states what you intend to do, a procedure states how, and a record proves it happened on a date. Auditors ask for all three, and a practice that has written the first two often has nothing for the third.

Date every document and keep the superseded versions. 45 CFR 164.316(b)(2)(i) requires the documentation 164.316(b)(1) calls for (the Security Rule policies and procedures, and the written record of any action, activity or assessment the Security Rule requires to be documented) to be retained for six years from the date of its creation or the date when it last was in effect, whichever is later, so a policy you replaced two years ago is still part of the record.

Where this usually goes wrong

In our question bank this is weighted Critical: a gap here is raised as a critical finding (a partial answer as high). The usual cause of a gap is drift: the control was implemented once, the environment changed, and nothing re-checked it. A dated review on a fixed cadence is cheaper than the remediation.

What to do about it

• Produce the evidence, not the intention. For 45 CFR 164.314(a)(2)(iii) that means the executed agreement, with the signature date on it and a dated report with the period it covers and who reviewed it. If the only evidence is that someone knows how this works, you have a practice and not a record.
• Put a name on it. Your security official should be recorded as the owner. A control with no owner stops working the month the person who quietly maintained it changes roles, and nobody notices.
• Review it on a fixed date, not when you remember. In our question bank this is weighted Critical: a gap here is raised as a critical finding (a partial answer as high). Put the review on the calendar with an owner, and keep the dated output of each one.
• There is no documented-alternative route for the requirement itself. It is required (45 CFR 164.306(d)(2) for a specification, 164.306(c) for a standard), so a risk-based decision not to meet it is not available. How you meet it is yours to choose under 45 CFR 164.306(b); the measures in this post are examples, not the rule's text.

The practical test for 45 CFR 164.314(a)(2)(iii) is whether someone unfamiliar with your organization could read your documentation and tell what you do, who does it, and when it last happened. If they can, the documentation will hold up; whether the requirement is met is a judgment about what it shows, and your counsel owns that conclusion. If they need you in the room to explain it, it will not.

Related requirements

• Security Incident Reporting in Business Associate Contracts: Who tells whom, and how fast
• Policies and Procedures: Policies and procedures that reflect what you do
• Business Associate Contracts: The clauses the Security Rule makes mandatory

References

• 45 CFR 164.314(a)(2)(iii), in 45 CFR 164.314 on eCFR.
• The Required and Addressable designations are defined at 45 CFR 164.306(d).
• Crosswalk references in this post are the mappings in our question bank, and are not verified against the published text of those standards.
• This post describes what a requirement asks for and what evidence documents it. It is not legal advice, and your counsel owns the conclusion. State law may impose additional obligations; HIPAA preempts a State law only where it is contrary to HIPAA (45 CFR 160.202, 160.203).