For registered investment advisers (RIAs), protecting client information is both an operational responsibility and a regulatory obligation. Your firm may already have security policies, monitoring tools, and an IT provider in place. The challenge is ensuring those protections meet applicable requirements, reflect how your business actually operates, and are supported by documentation.
The Securities and Exchange Commission’s (SEC) 2024 amendments to Regulation S-P introduced additional requirements for incident response, customer notification, service provider oversight, and recordkeeping. With the compliance deadlines now passed, firms should be able to demonstrate how these requirements have been implemented and maintained.
This SEC compliance checklist focuses on the cybersecurity and customer-information safeguards that SEC-registered investment advisers, including wealth management firms, should review as part of their broader compliance programs.
Use it to identify potential gaps, clarify responsibilities between your compliance team and IT providers, and organize supporting documentation before an examination request arrives.
Key Insights
- Deadlines have passed. Larger covered entities were required to comply by December 3, 2025, and smaller entities by June 3, 2026. Firms should be able to show how the requirements are implemented.
- Vendors must report fast. Service provider policies should ensure the firm is notified within 72 hours of a breach affecting customer information. The firm remains responsible for oversight.
- Customers must be told promptly. Notice is generally due as soon as practicable, and no later than 30 days after the firm becomes aware of unauthorized access, subject to the rule's exceptions.
- Records are the proof. SEC-registered advisers generally keep compliance records for at least five years, with the first two years easily accessible.
- Close the loop on gaps. Document each finding, corrective action, owner, and verification so the work can be demonstrated during an examination.
SEC compliance checklist for wealth managers and RIAs
An effective compliance checklist should do more than identify regulatory requirements. It should connect each requirement to the people responsible for implementing it and the records that demonstrate the work has been completed.
| Action | Evidence to maintain | Suggested owner |
|---|---|---|
| Confirm regulatory applicability and assign compliance responsibilities | Registration records, compliance responsibility matrix | Chief compliance officer (CCO) |
| Review written information safeguards and technology risks | Current policies, risk assessments, information inventory | CCO and IT |
| Assess service provider security and oversight | Vendor inventory, due diligence, monitoring records | Compliance and IT |
| Maintain a written incident response program | Incident response plan, contacts, incident procedures | Compliance and IT |
| Establish customer notification procedures | Decision process, notification templates, incident records | CCO and legal counsel |
| Review security monitoring and testing | Monitoring reports, vulnerability assessments, remediation records | IT or security provider |
| Document findings and corrective actions | Risk register, remediation log, approvals | CCO and IT |
| Review records retention and secure disposal | Retention schedule, disposal policies, supporting records | Compliance and operations |
| Review safeguards following material technology or business changes | Change records, updated policies, training documentation | Compliance and IT |
The checklist combines regulatory obligations with recommended implementation practices. The evidence examples and suggested owners are practical recommendations, not universally prescribed SEC documents or job assignments.
Working through the table above, assign each action one of three statuses: Complete, Needs attention, or Not applicable. A determination of “Not applicable” should include an explanation, particularly when based on the firm’s registration status, services, or information-handling practices.
If this review surfaces gaps, Xantrion’s cybersecurity risk assessment can help you evaluate current controls and prioritize what to address first.
General SEC compliance requirements beyond cybersecurity
Cybersecurity is one component of a registered investment adviser’s broader compliance obligations. Under Rule 206(4)-7 of the Investment Advisers Act, SEC-registered advisers must adopt and implement written compliance policies and procedures reasonably designed to prevent violations of the Advisers Act, review their adequacy and effectiveness at least annually, and designate a chief compliance officer.
A comprehensive compliance program also addresses the firm’s code of ethics, fiduciary obligations, conflicts of interest, marketing practices, applicable custody requirements, and books and records.
Firms must also maintain applicable registration documents and disclosures. These may include Form ADV and associated brochure delivery obligations, Form CRS for firms serving retail investors, and other filings determined by their activities.
For a broader discussion, see our guide to financial regulatory compliance. The SEC also provides Form ADV instructions to help firms assess their filing obligations.
What is Regulation S-P, and does it apply to your firm?
Regulation S-P establishes privacy and customer-information protection requirements for certain financial institutions regulated by the SEC. Its provisions address how covered firms safeguard nonpublic personal information, communicate their information-sharing practices, and dispose of protected information.
The regulation is particularly relevant to RIAs because they routinely collect and maintain sensitive financial and identifying information.
Examples include account information, financial records, Social Security numbers, and other identifying details that could expose clients to financial harm or identity theft if accessed without authorization.
Regulation S-P applies to several categories of covered institutions, including:
- Investment advisers registered with the SEC
- Broker-dealers and funding portals
- Investment companies
- Transfer agents registered with the SEC or another appropriate regulatory agency
The term wealth manager describes a business activity rather than a regulatory registration category. Whether a wealth management firm is subject to specific Regulation S-P provisions depends on its registration and activities.
State-registered investment advisers are not automatically subject to every requirement applicable to SEC-registered advisers. However, state registration does not eliminate other privacy, information-security, or breach-notification obligations.
Firms should work with their compliance counsel to confirm which requirements apply to their operations.
The SEC’s Small Entity Compliance Guide provides an accessible introduction to the amended regulation.
Regulation S-P amendments: What changed?
In May 2024, the SEC adopted amendments intended to strengthen protections for customer information and establish clearer responsibilities when information is accessed or used without authorization.
The changes can be organized into five primary areas.
| Amendment area | Practical implication | Checklist focus |
|---|---|---|
| Incident response | Maintain a written program designed to detect, respond to, and recover from unauthorized access or use | Response procedures and responsibilities |
| Customer notification | Establish procedures for determining whether notice is required and providing timely notice | Investigation and notification records |
| Service provider oversight | Conduct due diligence and monitoring, including appropriate provider breach-notification arrangements | Vendor management |
| Safeguards and disposal | Protect the broader scope of customer information, including information handled on the firm's behalf | Information inventory and disposal |
| Recordkeeping | Maintain records documenting compliance with the amended requirements | Policies, decisions, and supporting evidence |
For example, an RIA may use a third-party portfolio management platform, cloud storage, a customer relationship management system, and an outsourced IT provider. The firm needs to understand which providers handle customer information, what safeguards are in place, and how potential incidents will be communicated.
The amendments also align Regulation S-P’s annual privacy-notice provisions with an existing statutory exception. A firm may qualify for an exception from delivering annual privacy notices if it shares nonpublic personal information with nonaffiliated third parties only under specified exceptions and has not changed the relevant information-disclosure policies and practices described in its most recent privacy notice.
Firms relying on this exception should periodically verify that they continue to meet its conditions.
The full regulatory language and SEC explanations are available in the 2024 Regulation S-P adopting release.
Regulation S-P compliance dates
The amendments took effect on August 2, 2024, but the SEC provided different compliance deadlines based on institution size.
| Institution category | Compliance deadline |
|---|---|
| Larger covered entities | December 3, 2025 |
| Smaller covered entities | June 3, 2026 |
For SEC-registered investment advisers, the larger-entity threshold is $1.5 billion or more in assets under management, measured according to the rule’s criteria for regulatory assets under management. The rule provides different size thresholds for broker-dealers, investment companies, and transfer agents.
Both compliance deadlines have passed.
Firms should now focus on whether their programs meet applicable requirements, whether written procedures are being followed, and whether they can produce supporting records. Where implementation gaps remain, the priority is to identify the deficiency, determine appropriate corrective action, and document the work performed.
The compliance dates establish when covered firms were required to meet the amendments. They should not be interpreted as the dates when all SEC enforcement began.
SEC Regulation S-P compliance: Requirements and action steps
Review written safeguards and identify customer-information risks
Regulation S-P requires covered institutions to maintain written policies and procedures addressing administrative, technical, and physical safeguards for customer records and information.
Start by identifying the systems where customer information is created, stored, accessed, transferred, and disposed of. Include cloud applications, collaboration platforms, advisor devices, document repositories, and relevant third-party services.
For example, a firm with remote advisors should examine whether access permissions, multifactor authentication, device management, and employee offboarding procedures provide appropriate protection without unnecessarily disrupting client service.
Risk assessments and information inventories are useful ways to organize this review, although the SEC does not prescribe one universal risk-assessment methodology for Regulation S-P compliance.
Recommended actions: Review existing safeguards against the firm’s current technology environment, identify material exposures, assign remediation responsibilities, and document how identified risks are addressed.
Evidence to maintain: Current approved policies, customer-information inventories, risk assessments, access-control reviews, and documented remediation decisions.
Maintain vendor due diligence and oversight
RIAs often depend on multiple service providers to deliver advisory services and maintain day-to-day operations. Outsourcing these functions does not remove the firm’s responsibility to oversee how customer information is protected.
The Regulation S-P amendments require written policies and procedures reasonably designed to provide service provider oversight, including due diligence and monitoring.
These policies must also be reasonably designed to ensure that relevant service providers take appropriate measures to protect customer information and notify the covered institution as soon as possible, but no later than 72 hours after becoming aware of a security breach resulting in unauthorized access to a customer information system maintained by the provider.
The 72-hour requirement concerns notification from the service provider to the covered institution. It is separate from the firm’s obligations to notify affected individuals.
Although the final rule does not universally mandate a particular written contract clause for service providers, firms should review agreements, reporting arrangements, and escalation procedures to determine whether their oversight program can operate effectively.
A practical review should establish which provider handles the information, who receives security notifications, what information the provider will supply, and how the firm initiates its incident response procedures.
Recommended actions: Maintain a current inventory of relevant vendors, evaluate safeguards, document ongoing oversight, and verify incident escalation contacts and procedures.
Evidence to maintain: Vendor assessments, monitoring reports, relevant agreements, escalation contacts, and records of corrective actions.
Maintain an incident response program
The amended rule requires covered institutions to develop, implement, and maintain a written incident response program reasonably designed to detect, respond to, and recover from unauthorized access to or use of customer information.
The program must include procedures for assessing the nature and scope of an incident and taking appropriate steps to contain and control it.
For an RIA, an incident could involve compromised advisor credentials, unauthorized access to a document repository, or a breach affecting a service provider that maintains customer information.
The response process should identify who investigates the incident, who coordinates with IT and outside providers, and who determines whether customer notification obligations apply.
It should also account for preserving relevant evidence, restoring affected systems, and documenting decisions.
The written program is a regulatory requirement. Periodic tabletop exercises and operational testing are recommended ways to identify weaknesses before an actual incident occurs.
Recommended actions: Establish clear response responsibilities, review escalation paths, coordinate with relevant service providers, and test the response process.
Evidence to maintain: The written incident response program, responsibility assignments, contact lists, exercise records, and incident documentation.
Establish customer notification procedures
One of the most consequential changes to Regulation S-P is the requirement to notify affected individuals following certain incidents involving sensitive customer information.
Under the amended rule, a covered institution generally must provide notice as soon as practicable, but 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, subject to the rule’s conditions and exceptions.
The requirement is tied to an incident involving sensitive customer information. A firm may avoid notification if a reasonable investigation determines that the sensitive information has not been, and is not reasonably likely to be, used in a manner resulting in substantial harm or inconvenience.
The firm should document the investigation and its determination rather than assume that notification is unnecessary because an incident appears limited.
Where notification is required, the notice must contain information about the incident, the affected information, and steps individuals can take to protect themselves.
The rule also provides for a limited delay when the U.S. Attorney General makes the specified national-security or public-safety determination and notifies the SEC in writing.
Firms may arrange for service providers to deliver notices on their behalf, but the covered institution retains ultimate responsibility for its notification obligations.
Recommended actions: Establish investigation and decision procedures, prepare notification templates, identify approval responsibilities, and define how notices will be delivered and documented.
Evidence to maintain: Investigation findings, notification determinations, approval records, notice templates, transmitted notices, and applicable legal documentation.
Maintain compliance records and secure disposal procedures
Relevant records include written safeguards, incident response policies, service provider oversight documentation, incident investigations, customer notification determinations, and supporting records.
For SEC-registered investment advisers, the applicable amended books-and-records requirements generally require preservation for at least five years, with the first two years in an easily accessible place, subject to the specific provisions governing the records.
Firms should confirm the retention period applicable to each category rather than applying another institution type’s requirements. For example, certain investment-company records are subject to different retention periods.
Secure disposal is another important component. The firm’s policies should address information maintained internally as well as information handled or maintained on its behalf, within the scope of the applicable safeguards and disposal requirements.
Disposal procedures may address paper records, storage devices, retired equipment, archived electronic information, and relevant third-party data-handling arrangements.
Recommended actions: Review record retention requirements, control access to compliance documentation, verify disposal procedures, and confirm that necessary records can be retrieved.
Evidence to maintain: Retention schedules, policy versions, incident records, oversight documentation, and relevant disposal records.
Documents to keep ready for an SEC cybersecurity examination
During its January 2026 Regulation S-P compliance outreach event, the SEC discussed documentation expectations and presented a sample examination exercise that included a document request discussion.
A practical document inventory might look like this:
| Document or record | Likely internal owner | Where maintained |
|---|---|---|
| Written information safeguards policies | CCO | Compliance repository |
| Incident response program | CCO and IT | Compliance and security repository |
| Service provider oversight procedures | Compliance and operations | Vendor management records |
| IT provider agreement and service scope | Operations | Contract repository |
| Technology risk assessments | IT and CCO | Security documentation |
| Security responsibility and escalation roster | IT and operations | Internal operations records |
| Monitoring and detection reports | IT or service provider | Security platform or provider reports |
| Vulnerability and remediation records | IT | Security or ticketing system |
| Incident investigation and notification records | CCO and legal | Restricted incident records |
| Policy reviews and corrective actions | CCO | Compliance tracking system |
Some records may be maintained directly by the firm, while others are generated by a managed IT or cybersecurity provider. Both arrangements require clarity about who owns the information and how the firm can retrieve it.
Before an examination request, verify that documentation is current, properly versioned, accessible to authorized personnel, and available for the relevant review period.
For additional information about how cybersecurity controls and documentation may be evaluated, read our guide to preparing for an SEC cybersecurity examination.
Keep the checklist current and close identified gaps
For each identified deficiency, establish a corrective action, assign an owner, set an appropriate target date, and determine how the completed work will be verified.
A simple gap log should capture:
- The finding and affected requirement or control
- The corrective action
- The responsible person
- The target completion date
- Evidence of completion
- Verification and final status
Consider a firm that discovers an outdated escalation contact in its service provider incident response procedures. The immediate task is to confirm the correct contact and update the documentation. The firm should then verify that the contact information works and that relevant personnel know which procedure to follow.
Compliance reviews should also respond to changes in the business. New advisors, acquisitions, cloud applications, vendors, or artificial intelligence tools may introduce additional information flows or alter existing security responsibilities.
The appropriate frequency and scope of reviews will depend on applicable legal requirements and the firm’s risks. Event-driven reviews and periodic technology assessments are useful practices, but should not be confused with regulatory review frequencies that apply to other parts of the firm’s compliance program.
Official SEC rules and Regulation S-P guidance
Current Regulation S-P rule text
Consult the operative regulation for the specific requirements governing privacy, customer-information safeguards, incident response, and disposal.
2024 Regulation S-P adopting release
Review the final amendments and the SEC’s explanation of their purpose, scope, and implementation requirements.
SEC Small Entity Compliance Guide
Use this staff-prepared guide for a more accessible overview of the amendments, applicability, notification requirements, and compliance deadlines.
January 2026 Regulation S-P compliance outreach
Review the SEC staff discussion and illustrative examination workshop, including a sample document request exercise. The workshop is educational and does not establish a universal examination checklist.
SEC examination priorities
Review the latest annual examination priorities, including the fiscal year 2027 priorities released in October 2026. These priorities identify areas of interest but do not replace or expand the underlying regulatory requirements.
Form ADV and Form CRS instructions
Consult the applicable filing instructions for registration, disclosure, and relationship-summary obligations.
Regulatory rules and forms establish binding requirements. Staff explanations, outreach presentations, and sample exercises help firms understand those requirements but should not be treated as substitutes for the rule itself.
For additional context, see Xantrion’s discussion of SEC exam priorities for 2026 and 2027.
How Xantrion helps RIAs address cybersecurity compliance gaps
Compliance officers establish and oversee the firm’s regulatory program, while internal IT teams and outside technology providers help implement security controls, monitor systems, respond to technical incidents, and produce supporting documentation.
Xantrion provides financial services IT support for RIAs, wealth management firms, and other regulated financial organizations. Our services include technology risk assessments, cybersecurity protection, ongoing monitoring, incident response support, and documentation to assist with compliance activities.
As a managed cybersecurity provider, we work with internal technology teams and firm leadership to assess existing controls, identify practical improvements, and help maintain protections as systems and business requirements change.
Our role is to provide technical expertise, implement appropriate safeguards, and support the firm’s documentation needs. Regulatory interpretation, legal determinations, and ultimate compliance accountability remain with the firm and its qualified advisers.
Review your firm’s cybersecurity readiness
If your firm needs to evaluate its current security controls, confirm responsibilities across service providers, or address documentation gaps, Xantrion can help assess your technology environment and prioritize improvements.
Contact Xantrion to discuss your cybersecurity and compliance-support requirements.
