KavanahKavanah

AI Agents

Auto-Planning

AI builds your sprint

Smart Triage

Auto-prioritize & assign

Agent Workflows

Automate any process

Risk Detection

Flag blockers early

Platform

Boards & Views

Kanban, timeline, list

Team Spaces

Shared project hubs

Team Chat

Communicate in context

Smart Alerts

AI-curated notifications

Learn

Courses

Two free courses

Blog

Tips and updates

Documentation

Guides and references

Support

Help Center

Get answers fast

Community

Connect with others

Trust & Compliance

SOC 2, ISO, HIPAA, GDPR

PricingApps
Log inGet started
GUIDE

Regulation S-P's New Deadlines, Run as a Project: 72 Hours, 30 Days, and the Vendors in Between

+
+

Oct 24, 2026

Will Schulz

Written by:

Will Schulz

Regulation S-P's New Deadlines, Run as a Project: 72 Hours, 30 Days, and the Vendors in Between
Listen
0:00 / ~2:36

In May 2024 the SEC adopted amendments to Regulation S-P that require broker-dealers, investment advisers, investment companies and transfer agents to keep written policies for an incident-response programme able to detect, respond to and recover from unauthorized access to customer information, and to notify affected individuals as soon as practicable and no later than 30 days after becoming aware of an incident. Larger entities had to comply by December 3, 2025; smaller entities have until June 3, 2026. If you are a smaller firm, that date has passed and the programme should be live.

1. The Three Clocks

Morrison Foerster's summary of the release sets out the three numbers that drive the plan. Service providers must notify the covered institution as soon as possible but no later than 72 hours after becoming aware of a breach. The institution must notify affected individuals as soon as reasonably practicable, and not later than 30 days after learning of unauthorized access or use. And the records of all this must be kept: three years for broker-dealers and transfer agents, five for registered investment advisers, six for investment companies.

2. Build the Programme as a Project

Write the work down as tasks with owners: inventory the service providers that receive, maintain or process customer information; get each one's breach-notice commitment in writing; draft the incident playbook and the customer-notice template; train the staff who will run it. Lowenstein's 2025 client alert lists much the same steps, including amending service-provider contracts to require breach notice within 72 hours and preparing customer-notice templates. A recurring task for the annual vendor review keeps the inventory from going stale.

3. Make the Incident Itself a Template

When an incident starts, nobody should be inventing the checklist. Keep an incident project template whose tasks are due relative to the day the firm became aware: containment, scoping, the sensitive-customer-information assessment, the notice decision, and the 30-day notice deadline. Discussion in the incident project is journaled under compliance mode, so the record of who decided what, and when, already exists when an examiner asks.

4. Your Project Tool Is a Service Provider Too

If customer information sits in your project tool, the vendor belongs on the inventory. Ask where data is processed, what encryption is used, and whether a SOC 2 report exists. Kavanah's security page answers those plainly: production data is processed in the United States, data is encrypted at rest with per-workspace keys for credentials, and its SOC 2 Type II observation period is underway with no report yet.

Our project management software for financial services page lists the rest of the vendor questions worth asking, and how Kavanah answers each one.

Part of the guide

Project management software for financial services

Sources

  1. 01SEC Adopts Rule Amendments to Regulation S-P to Enhance Protection of Customer Information — SEC press release 2024-58, May 16, 2024
  2. 02U.S. SEC Adopts Amendments to Reg S-P — Morrison Foerster, May 28, 2024
  3. 03Compliance Deadlines to Implement Significant Amendments to Regulation S-P Are Fast Approaching — Lowenstein Sandler, Aug 4, 2025
  4. 04Project Management Software for Financial Services: Records, Supervision and AI Agents You Can Defend — Kavanah

You might want to read

More Blog
+
+
Off-Channel Communications and Your Project Management Tool: What SEC Rule 17a-4 Means for Comments, Chat and AI
GUIDE

Off-Channel Communications and Your Project Management Tool: What SEC Rule 17a-4 Means for Comments, Chat and AI

The SEC's off-channel cases were about text messages. The same rule reaches the comment thread on your deal board. Here is what the rule says, what examiners keep finding, and what to switch on.

AI Agents at a Broker-Dealer: Mapping FINRA's 2026 Guidance to Controls You Can Switch On
GUIDE

AI Agents at a Broker-Dealer: Mapping FINRA's 2026 Guidance to Controls You Can Switch On

FINRA's 2026 oversight report names the risks of AI agents in plain language and asks firms to consider four controls. Here is each one, and what it looks like in a working system.

A FINRA Rule 2210 Approval Workflow You Can Actually Evidence
GUIDE

A FINRA Rule 2210 Approval Workflow You Can Actually Evidence

Rule 2210 wants a principal's approval before a retail communication is used, and a record with the approver's name and the date. Here is a workflow that captures both without anyone retyping them.

KavanahKavanah

© AW3 Technology, Inc. All rights reserved.