# Incident Breach Notification

> Manage compliance obligations for incidents and data breaches — assessment, notification triggers, timelines, regulators, and affected individuals. Use when designing incident response playbooks with legal/compliance notification paths or handling a suspected breach.

- Skill: `itsual/incident-breach-notification` (Agent Skill)
- Install (CLI): `npx skillmds@latest add itsual/incident-breach-notification`
- Raw SKILL.md: https://api.skillmd.com/api/skills/itsual/incident-breach-notification/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: itsual (https://skillmd.com/u/itsual)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/itsual/incident-breach-notification

---


# Incident & Breach Notification

## Overview

Many regimes require timely notification of security incidents or personal data breaches to regulators and, in some cases, individuals. Compliance readiness is measured in hours, not weeks.

## When to Use

- Building incident response + notification playbooks
- Assessing whether an event is a notifiable breach
- Coordinating legal, privacy, security, and communications
- Post-incident regulatory engagement

## Core Practices

- Define incident intake and severity classification
- Assess notifiability against applicable laws quickly
- Preserve evidence and decision rationale
- Meet statutory timelines (know your clocks)
- Coordinate content of notices for accuracy and consistency
- Track follow-up commitments to regulators

## Principles

- Speed without facts creates mis-notification risk; delay creates penalty risk — practice the balance
- Cross-border operations may face multiple clocks
- Notification is not the end — remediation and lessons learned matter
- Pre-drafted templates accelerate good process

## Verification

- [ ] Playbooks include compliance notification decision trees
- [ ] Roles for legal/privacy/security are clear
- [ ] Tabletop exercises test timeline performance