164.314(a)(2)(i) Business Associate Contract Required Provisions
The contract between a covered entity and a business associate must provide that the business associate will comply with the applicable Security Rule requirements, ensure subcontractors comply, report security incidents
8
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Periodic BAA compliance reviews · Document repository
- Records of incidents reported by BAs · Document repository
governing documentDocuments that govern the control
- BAA template with required clauses traceable to 164.314(a)(2)(i) · Document repository
- Incident reporting requirements and SLAs · Document repository
- Subcontractor flow-down clause · Document repository
- Termination for cause clause · HR system / LMS
- BA breach notification timelines tied to 164.410 · Document repository
- Termination events and outcomes · HR system / LMS
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Incident reporting SLA missing or longer than reasonable
- Subcontractor flow-down not enforced
- Termination clauses never exercised
- BA breach reports late or incomplete
- BAA does not require Security Rule compliance explicitly
- Compliance reviews skipped
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet164.314(a)(1) Business Associate Contracts or Other Arrangements (Standard) · 164.314(a)(2)(ii) Other Arrangements (Government)