HHS separates the discovery and assessment of a security incident from the notification duties that may follow. A reliable record preserves facts first and avoids turning an early alert into a final legal conclusion.
Incident evidence map
| Evidence | Record | Boundary |
|---|---|---|
| Discovery | Reporter, time, and system | Do not alter the original alert |
| Scope | Users, records, and systems involved | Preserve uncertainty as uncertainty |
| Safeguards | Containment and access changes | Follow the incident plan |
| Assessment | Authorized risk analysis and decision | Legal or compliance owner decides |
| Notification | Required notices and dates | Apply current HHS and state rules |
Keep the queue factual
Use neutral fields such as observed event, affected system, evidence requested, owner, and next action. Keep copies of logs, messages, access changes, and decisions in the approved incident record.
Administrative support can open the record, collect approved evidence, and coordinate reminders. It should not decide whether a breach occurred or whether notification is required.
FAQ
Is every security incident a breach?
No. The applicable rules require an assessment of the facts and circumstances. Escalate the question to the agency's privacy or compliance owner.
Can logs be cleaned up after review?
Preserve source evidence under the incident-response and retention policies. Work from copies when analysis requires annotation.
What should a handoff contain?
State what was observed, what evidence is attached, what remains unknown, who owns the decision, and when the next review occurs.
Related research
See the HIPAA audit controls review and remote ePHI review.

