Security compliance workflow for Tallyfy

Respond to data breaches before deadlines pass

GDPR gives you 72 hours from when you know about a breach. State laws vary. This Tallyfy template guides privacy officers and IT security through identification, containment, notification, and remediation - with structure to stay compliant when the clock is ticking.

7 steps

3 automations

Import into Tallyfy Preview steps

Financial Services Hospital/Health Care Security/Investigations security

Run this workflow in Tallyfy with people, AI, and conditions

Data Breach Response Plan Run #2,481 Running now

Status	Step	Assignee
Status: Completed	1. Identify the breach	TM Team member
Status: Active	2. Contain the breach	Claude AI agent
Status: Waiting	3. Determine scope and impact	TM Team member
Status: Conditional	4. Notify legal and regulatory authorities	Claude AI agent
+ 3 more steps below

Import this template into Tallyfy

Tallyfy is the accountability layer that lets this template mix people, AI agents, and conditions in one auditable flow

Process steps

Identify the breach

1 day from previous step

task

Something's leaked. Figure out what data, how much, and how it happened. The clock starts now. Write down the exact time you found out. For GDPR, you've got 72 hours from when you "know" - not when you're done investigating. That timeline matters a lot.

Contain the breach

1 day from previous step

task

Stop more data from leaking. Disable compromised accounts. Close exposed endpoints. Do it now. Contain first, investigate later. Every minute the breach keeps spreading means more customers affected and more regulators asking tough questions.

Determine scope and impact

1 day from previous step

task

What data was exposed? How many people? Which jurisdictions? This decides who you've got to notify and when. Be thorough but fast. You need answers to tell regulators and customers. Guessing wrong either way causes real problems.

Notify legal and regulatory authorities

1 day from previous step

task

72 hours for GDPR notification. State laws vary - some are faster. Your legal team needs to hear about this right away. Don't wait until you have all the answers. Regulators understand you're still investigating. What they won't forgive is silence.

Notify affected customers

1 day from previous step

task

Be straight, be clear, be helpful. Tell them what happened, what you're doing about it, and what they should do next. Offer credit monitoring if financial data was exposed. It's expensive, but it's cheaper than a lawsuit.

Implement remediation

1 day from previous step

task

Fix what broke. Patch the vulnerability. Change the credentials. Whatever let this happen - make sure it can't happen again. Don't just fix the symptom. Find the root cause. If it was a phishing email, why didn't your controls catch it?

Complete post-breach analysis

1 day from previous step

task

What did we learn? What needs to change? Document everything - regulators will want to see it. This isn't just bureaucracy. They'll ask what you've done so it doesn't happen again. Have a good answer ready.