How it is structured
Regulation S-P is a set of privacy rules, adopted under the Gramm-Leach-Bliley Act (GLBA) and the Fair and Accurate Credit Transactions Act of 2003, that govern the treatment of nonpublic personal information about consumers by certain financial institutions (89 FR 47688). On 16 May 2024 the SEC announced amendments to modernise it “to address the expanded use of technology and corresponding risks that have emerged since the Commission originally adopted Regulation S-P in 2000” (SEC press release 2024-58). The Federal Register release gives the effective date as 2 August 2024.
The security obligations sit in 17 CFR 248.30, which the eCFR shows as last amended on 2 August 2024. Its structure, as the eCFR text reads:
- (a) Policies and procedures to safeguard customer information. Every covered institution “must develop, implement, and maintain written policies and procedures that address administrative, technical, and physical safeguards for the protection of customer information”, including a response program for unauthorised access or use, customer notification and service provider oversight.
- (b) Disposal. Covered institutions, other than notice-registered broker-dealers, must take reasonable measures to protect against unauthorised access to or use of information in connection with its disposal.
- (c) Recordkeeping for investment companies that are not registered under section 8 of the Investment Company Act, with other covered institutions covered by their own recordkeeping rules.
- (d) Definitions, including “covered institution”, “customer information”, “sensitive customer information” and “service provider”.
Customer notification
Under 17 CFR 248.30(a)(4)(iii) the notice goes out on this timetable: a covered institution “must provide the notice as soon as practicable, but not 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 text allows one delay: if the United States Attorney General determines that notice poses a substantial risk to national security or public safety and tells the Commission in writing, the institution may delay for the period the Attorney General specifies, up to 30 days after the date the notice was otherwise due. The notice itself must follow the content list in 248.30(a)(4)(iv), which includes a general description of the incident, the type of sensitive customer information involved, contact details and information about fraud alerts and credit reports.
When it applies: the compliance periods
The SEC press release says the amendments “will become effective 60 days after publication in the Federal Register. Larger entities will have 18 months after the date of publication in the Federal Register to comply with the amendments, and smaller entities will have 24 months after the date of publication in the Federal Register to comply.” The rule was published on 3 June 2024. By our calculation from that publication date, the larger-entity period ended on 3 December 2025 and the smaller-entity period ended on 3 June 2026. Both dates have passed, so every covered institution is now expected to be operating the amended requirements; confirm the dates for a specific client with counsel.
The Federal Register release says which firms are “larger entities”. Investment companies, together with others in the same group of related investment companies, qualify with net assets of $1 billion or more as of the end of the most recent fiscal year. Registered investment advisers qualify with $1.5 billion or more in assets under management. Broker-dealers and transfer agents qualify if they are not small entities under the Securities Exchange Act for purposes of the Regulatory Flexibility Act. Every other covered institution counts as a smaller entity.
Which of your clients it applies to
Section 248.30(d)(3) defines a covered institution as “any broker or dealer, any investment company, and any investment adviser or transfer agent registered with the Commission or another appropriate regulatory agency”. The SEC press release lists the groups as “broker-dealers (including funding portals), investment companies, registered investment advisers, and transfer agents”. Two scoping notes from the Federal Register release:
- Regulation S-P covers investment companies as defined in the Investment Company Act whether or not they are registered, so a business development company is in scope, while private funds relying on section 3(c)(1) or 3(c)(7) of that Act are not.
- Notice-registered broker-dealers keep their existing treatment: they are excluded from the disposal rule, and deemed to comply with the safeguards rule if they are subject to and comply with the financial privacy rules of the CFTC.
What the rule protects is “customer information”, meaning a record containing nonpublic personal information about a customer of a financial institution that is “in the possession of a covered institution or that is handled or maintained by the covered institution or on its behalf”. The words “on its behalf” are the reason an MSP that touches a client’s systems matters. A short triage for a new client: is it a broker-dealer, investment company, registered investment adviser or transfer agent, is it a larger or smaller entity, and which systems hold customer information?
How an MSP delivers it
This section mixes the rule’s text with practitioner guidance, and the guidance is labelled as such.
The MSP’s own position as a service provider. Section 248.30(d)(10) 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 a covered institution”. An MSP with administrator access to a client’s systems that hold customer information fits that wording. Three things follow from the rule:
- The covered institution’s response program must include written policies and procedures “reasonably designed to require oversight, including through due diligence and monitoring, of service providers” (17 CFR 248.30(a)(5)(i)).
- Those policies must be reasonably designed to ensure service providers take appropriate measures to protect against unauthorised access to or use of customer information, and to notify the covered institution “as soon as possible, but no later than 72 hours after becoming aware that a breach in security has occurred resulting in unauthorized access to a customer information system maintained by the service provider”. On receiving that notice the covered institution must start its incident response program.
- A covered institution may enter into a written agreement for the service provider to notify affected individuals on its behalf, but “the obligation to ensure that affected individuals are notified in accordance with paragraph (a)(4) of this section rests with the covered institution” (248.30(a)(5)(ii) and (iii)).
The rule binds the covered institution, not the MSP directly, so the MSP’s obligations reach it through the client’s oversight. The Federal Register release notes that the SEC dropped a proposed requirement for a written contract with each service provider and replaced it with the policies-and-procedures test above, so a contract is not mandated by the rule text. Practitioner view: a clause that records the 72-hour alert, the contact route and who may notify individuals gives the client something to show an examiner.
A delivery sequence we suggest (practitioner guidance, not rule text):
- Classify the client. Establish which covered-institution type it is and whether it is a larger or smaller entity, so you know which compliance period applied to it.
- Map customer information. List the systems, vendors and locations that hold customer information, since the rule’s scope includes information handled “on its behalf”.
- Build the incident response program with the client. Document how an incident is assessed, contained and recovered from, who decides whether sensitive customer information was involved and how notices are drafted and sent.
- Wire up your own alerting. Agree an internal rule that makes sure the client hears of a breach in a system you maintain within the 72-hour limit, and test it.
- Keep the records. Capture incident logs, investigation notes, notification decisions and copies of notices in a form the client can retain for the period its own recordkeeping rule sets.
- Review on a schedule. Re-run the vendor list, access rights and the incident exercise when systems or suppliers change, and report the results to the client’s compliance officer.
Split responsibilities in writing: the covered institution’s compliance function owns the policies, notification decisions and regulatory judgement, while the MSP operates the technical safeguards and supplies the evidence.
Requirements checklist
The table lists the amended requirements, paraphrased from 17 CFR 248.30 and the Federal Register release. The right-hand column is practitioner guidance on what an MSP typically prepares, not text from the rule.
| Amended requirement | What the rule says | Evidence an MSP typically prepares |
|---|---|---|
| Incident response program | Written policies and procedures must include a program reasonably designed to detect, respond to and recover from unauthorised access to or use of customer information (248.30(a)(3)) | Documented incident plan, roles, escalation contacts, detection and logging configuration, results of exercises |
| Assessment and containment | Procedures to assess the nature and scope of an incident, identify the systems and types of customer information involved, and contain and control it | Triage checklist, scoping worksheet, containment runbooks, incident tickets |
| Customer notification | Notify each affected individual whose sensitive customer information was, or is reasonably likely to have been, accessed or used without authorisation, unless a reasonable investigation shows it is not reasonably likely to be used in a way that causes substantial harm or inconvenience; the notice must meet the content list in 248.30(a)(4)(iv) | Notice templates mapped to the content list, decision record for each investigation, mailing and contact-route readiness |
| Service provider oversight | Written policies and procedures requiring oversight, including due diligence and monitoring, of service providers; service providers to notify the covered institution within 72 hours of becoming aware of a breach | Vendor register, due diligence files, monitoring records, the MSP’s own alert procedure and a record of its tests |
| Scope of information | “Customer information” and “sensitive customer information” definitions apply to the safeguards and disposal rules, including information handled on the institution’s behalf | Data map, list of systems holding customer information, access reviews |
| Disposal | Reasonable measures to protect against unauthorised access to or use of information when it is disposed of; disposal covers the sale, donation or transfer of any medium, including computer equipment | Asset disposal log, media sanitisation or destruction records |
| Recordkeeping | Written records documenting compliance, held under each covered institution’s own recordkeeping rule; for unregistered investment companies 248.30(c) sets six years, the first two in an easily accessible place | Retention schedule, archive of policies, incident records, notices and service provider documents |
| Annual privacy notice | The amendments “conform annual privacy notice delivery provisions to the terms of an exception provided by a statutory amendment to the” GLBA | Confirmation from the client’s compliance function of how it relies on the exception; usually outside MSP scope |
The recordkeeping periods differ by type. The Federal Register release lists three years for broker-dealers (17 CFR 240.17a-4(e)) and transfer agents (17 CFR 240.17ad-7(k)), five years for registered investment advisers (17 CFR 275.204-2(a)) and six years for registered investment companies (17 CFR 270.31a-1(b)), each with the first two in an easily accessible place where it says so. Check the current text of the rule that applies to the client.
Overlap with other frameworks
Regulation S-P is the SEC’s GLBA rule for its registrants, which means a firm that already runs a mature information security programme will have much of the evidence in place. The release repeatedly compares the final rule with the federal banking agencies’ incident response guidance, so banking-style incident response material is a reasonable starting point for a template, but each requirement still needs checking against 17 CFR 248.30 and the notification content list.
The same GLBA safeguarding idea sits behind the FTC Safeguards Rule, the Federal Trade Commission’s regulation at 16 CFR Part 314 for financial institutions under its jurisdiction. Which regulator’s rule applies depends on who supervises the client, so a client of the SEC follows Regulation S-P, and an MSP serving both kinds of client keeps the two programmes separate.
Other frameworks cover adjacent ground without replacing it. A SOC 2 or ISO/IEC 27001 programme can supply access control, logging and vendor management evidence, and the frameworks list shows which catalogue entries exist and how they map to each other. Neither one answers the specific questions the rule asks: the 30-day customer notification test, the 72-hour service provider alert, and the retention periods that apply to the client. Treat them as evidence sources, then map each Regulation S-P requirement to the artefact that proves it.
Common mistakes
- Assuming the MSP is outside the rule. The service provider definition covers entities permitted access to customer information through services provided directly to a covered institution. The client must oversee you, so expect due diligence questions and monitoring.
- Missing the 72-hour alert. The service provider’s period runs from becoming aware of a breach in security resulting in unauthorised access to a customer information system it maintains. Make sure staff know who to tell, and how, on day one.
- Treating the notice as the MSP’s job. Even where a written agreement hands notification to the service provider, the obligation rests with the covered institution. Agree who decides, who drafts and who signs off.
- Mixing up the 30 days. The text says “as soon as practicable, but not later than 30 days, after becoming aware” of unauthorised access or use. The clock starts at awareness, and the text provides for a delay only through a written determination by the United States Attorney General.
- Treating the compliance dates as still ahead. By our calculation the larger-entity date was 3 December 2025 and the smaller-entity date was 3 June 2026, so both have passed. A client that has no written incident response program, notification procedures and service provider oversight now needs them in place. The larger-entity test depends on assets, not headcount, so confirm the client’s category in writing.
- Under-keeping records. Retention periods differ by type, and the documentation of investigations and notification decisions is part of what must be kept. Do not default to a single period for every client.