HomeBlogCybersecurity

SEC Reg S-P for RIAs: The Deadline Passed, Now What?

Empty modern investment advisory boardroom at sunset with a closed laptop and a brass padlock resting on a stack of compliance documents, city skyline beyond the windows

The SEC Reg S-P compliance deadline for smaller RIAs was June 3, 2026, and it has passed. If your firm still doesn't have a written incident response program, a 30-day client notification process and documented vendor oversight, you're out of compliance right now, and the fix is a documentation problem before it's a technology problem.

Updated November 7, 2026: compliance dates, notice rules and service provider terms checked against the SEC's small entity compliance guide and the adopting release. This is general information, not legal advice.

Key points:

  • Smaller RIAs, those under $1.5 billion in assets under management, had until June 3, 2026.
  • Larger firms had until December 3, 2025. Both dates are behind us.
  • Three obligations drive everything else: a written incident response program, client notification within 30 days, and written oversight of service providers.
  • Late is recoverable. Undocumented is not. Write the plan and log the gaps before you start buying tools.

What the 2024 amendments actually added

A mandatory incident response program: written policies and procedures reasonably designed to detect, respond to, and recover from unauthorized access to or use of customer information. The SEC adopted the amendments on May 16, 2024. They took effect August 2, 2024, and compliance was tiered from their June 3, 2024 publication in the Federal Register: 18 months for larger entities (December 3, 2025) and 24 months for smaller ones (June 3, 2026).

The rule also sets a hard customer-notification deadline, requires written oversight of the providers that touch client data, and requires written records showing you comply. Reg S-P itself isn't new: the SEC first adopted it in 2000.

Smaller entity means under $1.5 billion in AUM

For a registered investment adviser, the adopting release defines a larger entity as one with $1.5 billion or more in assets under management, so a smaller entity is an adviser below that line. Either way, the rule applies to you today.

"Smaller" never meant "exempt." A two-person advisory running its practice through a handful of SaaS platforms carries the same core obligations as a national firm, scaled to its own size and risk.

What the incident response program must cover

Your written program has to address each of these:

  1. Assess the nature and scope of an incident.
  2. Contain and control it to prevent further unauthorized access or use.
  3. Notify affected clients, unless an investigation supports the exception below.
  4. Keep records of what happened and what you decided, because the amendments require written records documenting compliance.

This isn't a document you write once and file away. The program has to match how your firm actually operates: your systems, your custodian, your vendors. A generic template with someone else's tech stack in it won't hold up.

When do we have to tell clients?

As soon as practicable, and no later than 30 days after becoming aware that unauthorized access to or use of customer information has occurred or is reasonably likely to have occurred. The notice goes to the individuals whose sensitive customer information was, or is reasonably likely to have been, accessed or used without authorization, and it has to explain the incident, the data involved, and what clients can do to protect themselves.

There is one exception: no notice is required if, after a reasonable investigation, you determine that the sensitive information has not been, and is not reasonably likely to be, used in a way that would cause substantial harm or inconvenience. Document that investigation. A service provider can send notices on your behalf under a written agreement, but the responsibility stays with your firm.

Thirty days moves fast when you're also investigating and containing an attack. That's the whole argument for writing the response down before you need it.

Service providers must tell you within 72 hours

The amendments require written policies and procedures for service provider oversight, including due diligence and monitoring, reasonably designed to ensure each provider takes appropriate measures to:

  • Protect against unauthorized access to or use of customer information.
  • Notify you as soon as possible, and no later than 72 hours after becoming aware of a breach in security that resulted in unauthorized access to a customer information system it maintains.

When a provider notifies you, your own incident response program starts. The final rule dropped the proposal's requirement for a written contract, so the contract is not mandatory, but a contract term with the 72-hour notice is still the clearest evidence an examiner can see.

Every provider holding client data can start your notification clock: your custodian, your CRM, your portfolio management platform, your email host. That is the part that catches firms off guard.

Vendor agreements signed before 2024 generally weren't written with a 72-hour notice in mind, so contracts need a second look. The same discipline pays off at cyber insurance renewal, where carriers ask for most of the same things.

You missed June 3. Here's the order to fix it in

Document first, then remediate. A firm that can hand an examiner a real plan and a dated remediation log is in a very different position from one with nothing on paper, even when both are late.

Reg S-P obligates you to be able to produce a specific set of artifacts. Build them in this order:

  1. A data map: where client information lives and which providers touch it.
  2. The written incident response program, covering the elements above.
  3. Your client notification procedure, with the 30-day clock built in.
  4. A vendor inventory, plus the due diligence and monitoring policy behind it.
  5. Updated contracts carrying the 72-hour notification term.
  6. A dated gap log: what's missing, who owns it, when it closes.

Then remediate: tighten access controls and multi-factor authentication, and run a tabletop exercise so the plan isn't theoretical. Keep the records the rule requires as you go. Under the SEC's adviser recordkeeping rule, Rule 204-2, an RIA keeps them for five years, the first two in an easily accessible place.

A firm without in-house security staff usually leans on a virtual CISO to own the program and a managed security partner to run detection and response.

For the day-to-day IT behind these controls, see our IT services for wealth managers and RIAs.

If your firm needs the program built rather than described, see our Regulation S-P compliance help for RIAs, which covers the incident response program, service provider oversight and evidence organized for an SEC exam.

Frequently asked questions

Does Reg S-P apply to state-registered advisers?

The amendments apply to SEC-registered investment advisers, broker-dealers (including funding portals), investment companies and registered transfer agents. State-registered advisers fall under their state's rules, but those states often mirror federal expectations, and many custodians impose similar requirements by contract. Treating Reg S-P as a baseline is the safer posture.

We already have a WISP. Is that enough?

Usually not. A written information security program is a strong start, but Reg S-P specifically requires incident response procedures, the 30-day notification process, and documented vendor oversight. Most existing WISPs need to be extended to cover those elements explicitly rather than by implication.

Do our vendor contracts have to include the 72-hour notice?

Not by law. The SEC dropped the proposed written contract requirement, so what the rule requires is written oversight policies and procedures reasonably designed to ensure providers notify you within 72 hours. In practice, a contract clause is the simplest way to show an examiner that the expectation is real.

What are the penalties for missing the deadline?

Reg S-P is enforced through SEC examinations and enforcement actions. Deficiencies can lead to findings, remediation orders, fines, and reputational damage. An unprepared incident response also tends to cost more, and do more damage to client trust, than the compliance work would have.

How long does it take to get compliant?

A small firm with clean systems and a short vendor list can get the documentation in place in weeks rather than months. Firms with scattered data, aging infrastructure, or thin vendor contracts should budget longer. The date has passed, so this is overdue work rather than optional work.

Sources (checked on November 7, 2026)

NetSys has supported financial services firms across the New York metro and beyond since 1998. For a clear read on where your RIA stands against Reg S-P, book a complimentary risk assessment and we'll map the gaps.

Cyber Security

Discuss cyber security for your business.

Tell us about your current systems, the result you need and your timeline. We will discuss the work, responsibilities and pricing before you decide on an engagement.