Compliance · SEC Regulation S-P
SEC Regulation S-P compliance for investment advisers and broker-dealers.
The SEC's 2024 amendments added a written incident response program, a 30-day deadline to notify affected individuals, and oversight of service providers, including notice to you within 72 hours of a breach. We build the program and the mechanics behind it, and get your evidence ready for an examination. Your securities counsel keeps the legal calls.
What the 2024 amendments require
What does Regulation S-P require now?
The SEC adopted the amendments on May 16, 2024 (Release No. 34-100155). They apply to broker-dealers (including funding portals), investment companies, SEC-registered investment advisers and registered transfer agents, which the rule calls covered institutions.
A written incident response program
Written policies and procedures for a program reasonably designed to detect, respond to and recover from unauthorized access to or use of customer information. It must include procedures to assess the nature and scope of an incident and to contain and control it.
Customer notice within 30 days
Notify individuals whose sensitive customer information was, or is reasonably likely to have been, accessed or used without authorization: as soon as practicable, and no later than 30 days after becoming aware of the incident. The notice must cover what happened, the data involved and how the individual can protect themselves.
A limited exception
No notice is required if, after a reasonable investigation, the firm determines the sensitive customer information has not been, and is not reasonably likely to be, used in a manner that would result in substantial harm or inconvenience. Making that call is a legal judgment.
Service-provider oversight and the 72-hour notice
Written policies and procedures to oversee service providers, including through due diligence and monitoring, so they protect customer information and notify you as soon as possible, and no later than 72 hours after becoming aware of a breach in security that results in unauthorized access to a customer information system they maintain.
A broader definition of customer information
The safeguards and disposal rules now cover nonpublic personal information about your own customers and the information you receive from another financial institution about its customers.
Written records of compliance
Covered institutions other than funding portals must make and maintain written records documenting compliance with the safeguards rule and the disposal rule.
The deadlines written into the rule
Who had to comply, and when
Both compliance dates have passed.
The SEC set a tiered schedule. Every covered institution is now past its date.
Larger entities: December 3, 2025
SEC-registered investment advisers with $1.5 billion or more in assets under management; investment companies that, with their group of related investment companies, have net assets of $1 billion or more; and broker-dealers and transfer agents that are not small entities under the SEC's small-entity definitions.
Smaller entities: June 3, 2026
Every covered institution that does not meet the larger-entity standard, which includes any SEC-registered adviser with less than $1.5 billion in assets under management.
What examiners will look at
The SEC Division of Examinations' fiscal year 2026 priorities say that after the compliance dates it will examine whether firms have developed, implemented and maintained policies and procedures under the amended rule.
Regulation S-P readiness checklist
What the 2024 amendments changed
- Incident response program: written policies and procedures to detect, respond to and recover from unauthorized access to or use of customer information.
- Customer notification: notify affected individuals as soon as practicable, and within 30 days of becoming aware.
- Service provider oversight: due diligence and monitoring, with providers telling you within 72 hours of a breach.
- Broader scope: "customer information" is now a defined term, and it reaches information about customers of other financial institutions that you receive.
- Transfer agents: the safeguards and disposal rules now cover them too.
- Records: written records documenting compliance (funding portals excepted).
- Annual privacy notice: the exception from the FAST Act is written into the rule, so the notice is not needed when its conditions are met.
What your incident response program should cover
- Who declares an incident, and how staff and vendors report one.
- How you assess the nature and scope: which systems, and which customer information.
- How you contain and control it, including preserving evidence.
- How you decide whether sensitive customer information was, or is reasonably likely to have been, accessed or used without authorization, and who signs that decision off with counsel.
- The notification path: drafting, approving and sending notices within the 30-day limit.
- Recovery, lessons learned, and the records an examiner will ask for.
What to check in each service provider contract
- Notice to you as soon as possible, and no later than 72 hours after the provider becomes aware of a breach affecting a system it maintains for you.
- The security measures the provider must keep, and your right to check them.
- Who sends customer notices, if you delegate that in writing. Responsibility for the notice stays with your firm either way.
- Secure disposal or return of customer information when the contract ends.
Service provider due diligence under Regulation S-P
The rule defines a service provider as any person or entity that receives, maintains, processes, or otherwise is permitted access to customer information through its provision of services directly to your firm. That usually means your custodian and portfolio-management platform, CRM, email and file hosting, managed IT provider, and anyone who backs up or archives client records.
Your written policies must require oversight of these providers, "including through due diligence and monitoring". In the adopting release the SEC explains what that does and does not mean:
- A written contract is not required, but the SEC says firms should generally consider whether one is appropriate to record what each side expects.
- A provider's assurance is not enough on its own where you know, or have reason to know, it is inaccurate.
- Independent certifications and attestations, such as a SOC 2 report, can form part of your due diligence, tailored to the relationship.
- Review the policies periodically over the life of the relationship, and update them with what your monitoring turns up.
- A provider's breach notice triggers your program: when it arrives, you must start your incident response program.
- If a provider notifies customers for you, you remain responsible. The SEC suggests confirming delivery, for example through the provider's attestation or by checking with a sample of affected customers, and keeping a copy of every notice.
Due diligence questions to ask each provider
- Which of our customer information do you receive, store or process, and where is it held?
- Who on your side can access it, and how is that access controlled and logged?
- Do you encrypt it at rest and in transit, and do you enforce multi-factor authentication?
- What independent evidence can you share: a SOC 2 Type II report, an ISO 27001 certificate, a recent penetration test summary?
- How and to whom will you report a breach, and can you commit to telling us within 72 hours of becoming aware of one?
- Who at your firm do we contact during an incident, and what records will you give us for our own investigation?
- Which subcontractors touch our customer information, and how do you oversee them?
- How do you return or securely dispose of our customer information when the relationship ends?
Keep the answers, the evidence and the date you reviewed them. That file is how you show an examiner the oversight actually happened.
Sources: SEC fact sheet, release 34-100155; adopting release 34-100155 (service providers, section II.A.4); FINRA cybersecurity advisory on the amendments. General information, not legal advice.
What we deliver
What we build for your Regulation S-P program.
The security work and the operating procedures, written down so you can show an examiner what you do and that you do it.
Gap assessment against the amended rule
We check your current controls and documents against each requirement: safeguards, incident response, customer notification, service providers, disposal and records. You get a ranked list of gaps with owners.
Written safeguards and incident response program
Policies and procedures covering administrative, technical and physical safeguards, and an incident response runbook that walks from detection through scoping, containment and recovery to the decision on customer notice.
Customer notification mechanics
A procedure with the 30-day clock built in, a notice template that covers the content the rule calls for, and a delivery and record step. Your counsel approves the wording and decides whether a notice is owed.
Service-provider oversight
An inventory of the vendors that touch customer information, a due-diligence and review cadence, and an intake procedure so a vendor's breach notice reaches the right person without delay. Counsel drafts the contract terms, including the 72-hour notice.
Technical safeguards, tested
Access control, multi-factor authentication, encryption, logging and monitoring around the systems that hold customer information, then a penetration test and an incident response tabletop to show the controls and the runbook work.
Examination evidence pack
The records that document compliance, indexed so you can produce them when examiners ask: the program, the risk assessment, incident assessments and notices, vendor reviews and training records.
Who does what
We do the security work. Your securities counsel makes the legal calls.
We are a security firm, not a law firm, and nothing on this page is legal advice. We work alongside your counsel and compliance team.
What we do
Build the safeguards and incident response program. Implement and test the technical controls. Run the gap assessment, the tabletop and an internal readiness review. Set up the 30-day notification procedure and the vendor notice intake. Assemble the evidence pack.
What stays with your securities counsel
What counts as sensitive customer information. Whether an incident triggers a notice or the exception applies. The legal wording of notices and privacy notices. Enforceable contract terms with service providers. Your examination posture and anything you say to the SEC.
How an engagement runs
From scoping call to an examination-ready program.
Scoped to your firm after a short call, with a fixed price agreed before we start.
Scoping call
Thirty minutes on what you are registered as, what already exists, which vendors touch customer information, and who your counsel is.
Gap assessment
We assess your firm against each requirement of the amended rule. Output: a ranked gap list and a remediation plan with a fixed quote.
Build
We write the program and runbook, implement the technical controls, and set up the notification and vendor procedures. Counsel reviews the legal content as we go.
Rehearse and package
A tabletop exercise against a realistic incident, fixes from what it shows, and an indexed evidence pack ready for an examination.
Regulation S-P FAQ
Does Regulation S-P apply to my firm?
What were the compliance dates?
When do we have to notify customers after an incident?
What is the 72-hour requirement for vendors?
Are you giving us legal advice?
We also prepare tax returns. Can you cover that too?
Where are you based?
What does it cost?
Sources
Where the rule details on this page come from.
Every requirement and date above is taken from the SEC releases and rule text below. This page is a summary to help you plan, not legal advice: rely on the rule text and your securities counsel.
- SEC press release 2024-58: SEC Adopts Rule Amendments to Regulation S-P to Enhance Protection of Customer Information (May 16, 2024)
- SEC fact sheet: Final Rules, Enhancements to Regulation S-P
- Adopting release: Regulation S-P, Release Nos. 34-100155; IA-6604; IC-35193
- Federal Register version: 89 FR 47688 (June 3, 2024)
- SEC staff: Enhancements to Regulation S-P, A Small Entity Compliance Guide
- Rule text: 17 CFR 248.30 (eCFR)
- SEC Division of Examinations: Fiscal Year 2026 Examination Priorities
Further reading
Read more
Regulation S-P: Mandating 72-Hour Vendor Breach Notification for RIAs and Broker-Dealers
The amended Regulation S-P now requires RIAs and broker-dealers to ensure their service providers contractually commit to notifying them of data breaches involving customer information within 72 hours. This post breaks down how to implement and enforce this critical contractual provision, ensuring your firm meets its regulatory obligations.
Building Your Regulation S-P Incident Response Program
Chief Compliance Officers: Understand the concrete requirements for building an incident response program under the updated Regulation S-P. This guide focuses on actionable steps and critical controls.
Building an Incident Response Plan You'll Actually Use
When Your Vendor Gets Breached: Protecting Your Data from Downstream Risk
A third-party security incident isn't just their problem-it's yours too. Learn how to minimize your exposure when a vendor's breach threatens your organization's data and reputation.
IRS Publication 4557 and the FTC Safeguards Rule: What Tax Preparers Must Do
What IRS Publication 4557 actually says, which parts are recommendations and which the FTC Safeguards Rule makes mandatory, with the IRS checklist and what to do after a data theft.
Related: Incident responsevCISO servicesCPA and tax firms (FTC Safeguards Rule)
Get your Regulation S-P program built and examination-ready.
A short scoping call, then a fixed-price proposal. Bring your securities counsel; we handle the security work.

