Control 3.10: SEC Reg S-P -- Privacy of Consumer Financial Information
Control ID: 3.10 Pillar: Compliance & Audit Regulatory Reference: SEC Regulation S-P (17 CFR 248.30), GLBA Title V (Privacy), SEC Regulation S-ID (Identity Theft Red Flags) Last Verified: 2026-09-24 Regulatory Applicability: Firm/counsel determination — see Regulatory Applicability Questions Governance Levels: Baseline / Recommended / Regulated
Scope of verification: The Last Verified date covers Microsoft product configuration guidance in this control (Purview DLP for the Microsoft 365 Copilot and Copilot Chat location, audit/DSPM surfaces, web-search controls, and associated cmdlets). SEC Reg S-P amendment existence, effective date, 72-hour service-provider notification wording, 30-day customer-notification outside timeframe, and the December 3, 2025 / June 3, 2026 compliance dates were checked against official SEC sources as factual references only. Applicability, customer-notification triggers, service-provider contract treatment, GLBA mapping, and examination posture remain firm/counsel determinations.
Objective
Establish controls governing Microsoft 365 Copilot's access to consumer financial information, helping meet SEC Regulation S-P privacy requirements for safeguarding nonpublic personal information (NPI), maintaining privacy notice accuracy, supporting opt-out provisions, and implementing the safeguard requirements specified under the Safeguards Rule (Rule 248.30) -- including the amendments proposed in 2023 and adopted by the SEC in May 2024 (Release No. 34-100155), with staggered compliance dates in 2025 and 2026.
Why This Matters for FSI
SEC Regulation S-P implements the privacy provisions of the Gramm-Leach-Bliley Act (GLBA) Title V for SEC-registered broker-dealers, investment advisers, and investment companies. In broker-dealer workflows, NPI generally flows from the consumer or customer to the broker-dealer that receives, stores, and processes it; Copilot controls should focus on safeguarding that customer information inside Microsoft 365 rather than describing a broker-to-consumer data transfer. The regulation requires financial institutions to:
- Provide privacy notices to customers describing information-sharing practices
- Offer opt-out rights before sharing NPI with nonaffiliated third parties
- Implement safeguards to protect the security and confidentiality of customer records and information
Reg S-P 2024 amendments (staggered compliance dates): In May 2024, the SEC adopted amendments to Regulation S-P (Release No. 34-100155) that significantly strengthened the Safeguards Rule. The amendments introduced a mandatory incident response program requirement and a service provider notification requirement (requiring service providers to notify the covered institution within 72 hours of becoming aware of unauthorized access to customer information). Compliance dates were staggered by entity size:
- Large entities (those filing reports under Exchange Act Section 13 or 15(d) with $1 billion or more in assets or assets under management): compliance required by December 3, 2025
- Small entities (all other covered entities): compliance required by June 3, 2026
As of the 2026-09-24 verification date, the large-entity compliance date was December 3, 2025 and the small-entity compliance date was June 3, 2026. Institutions should verify their current compliance status against the amended Safeguards Rule requirements applicable to their entity size.
Microsoft 365 Copilot presents specific Reg S-P challenges because it accesses and processes NPI stored across Microsoft 365 -- customer account data in emails, financial information in SharePoint documents, client records in Teams conversations, and personal details in OneDrive files. Copilot's ability to surface, summarize, and generate content from NPI creates new vectors for potential unauthorized disclosure or inadequate safeguarding that must be addressed within the Reg S-P compliance framework.
Control Description
Regulatory applicability
Regulatory citations identify commonly referenced requirements. Applicability, record classification, and retention periods are a firm and counsel determination; this framework does not assert that any regulation applies or is satisfied. See the Regulatory Applicability Questions appendix.
This control addresses the intersection of Copilot functionality with Reg S-P requirements across all three pillars: privacy notices, opt-out provisions, and safeguards. The amended Reg S-P requirements (incident response program and 72-hour notification) are integrated throughout.
Reg S-P Amendment Details: Service Provider Notification and Incident Response Programs
The SEC's May 2024 adoption of the Reg S-P amendments proposed in 2023 introduced two specific requirements directly relevant to Microsoft 365 Copilot deployments:
SEC Rule 248.30(a)(3) — Service provider notification requirement: The amended rule requires covered institutions to adopt policies requiring their service providers to notify the covered institution within 72 hours of becoming aware of unauthorized access to customer information. For Copilot deployments, institutions should verify that contractual arrangements with Microsoft address this notification requirement.
SEC Rule 248.30(a)(4) — Mandatory incident response program: Covered institutions must have written policies and procedures for an incident response program that addresses unauthorized access to or use of customer information. The program must include procedures for: assessing the nature and scope of incidents; containing and remediating incidents; and notifying affected individuals. Copilot-related incidents -- including Copilot surfacing NPI to unauthorized users due to oversharing, or Copilot-generated content containing customer NPI sent to wrong recipients -- constitute incidents under this requirement.
NPI Categories Accessible to Copilot
| NPI Category | M365 Location | Copilot Access Path | Risk Level |
|---|---|---|---|
| Account information | Exchange (emails), SharePoint (documents) | Copilot can surface account numbers, balances, transaction history from grounding data | High |
| Financial status | SharePoint, OneDrive (financial documents) | Copilot can summarize income, assets, net worth from client files | High |
| Transaction records | Exchange (confirmations), SharePoint (reports) | Copilot can reference trade details, transaction amounts, counterparties | High |
| Social Security numbers | Exchange, SharePoint (applications, forms) | Copilot may surface SSNs from stored documents; constrain through permissions, sensitivity labels, and the Copilot DLP prompt/grounding actions — response text is not inspected | Critical |
| Contact information | Exchange (contacts), Teams (chat) | Copilot can access addresses, phone numbers, email addresses | Moderate |
| Employment information | SharePoint (KYC documents), Exchange | Copilot can reference employer, income, occupation from client files | Moderate |
| Investment preferences | Exchange, SharePoint, Teams | Copilot can surface risk tolerance, investment objectives, time horizons | Moderate |
| Health information | Exchange, SharePoint (insurance applications) | Copilot may access health data in insurance-related workflows | High |
Reg S-P Safeguards Rule Requirements and Copilot Controls
| Safeguards Rule Requirement | Copilot Control |
|---|---|
| Designate a qualified individual to oversee the safeguards program | Include Copilot in the designated individual's scope of responsibility |
| Conduct risk assessments of customer information | Assess Copilot as a system that accesses and processes customer information |
| Design and implement safeguards to control identified risks | Implement DLP, sensitivity labels, information barriers, and access controls for Copilot |
| Regularly test safeguard effectiveness | Include Copilot-specific test scenarios in safeguard testing program |
| Train personnel on safeguard policies | Include Copilot NPI access risks in security awareness training |
| Oversee service provider arrangements | Review Microsoft's data processing practices for Copilot NPI access |
| Establish an incident response program (Rule 248.30(a)(4)) | Incident response program must cover Copilot-related NPI incidents with written policies and procedures |
| Require service provider notification within 72 hours (Rule 248.30(a)(3)) | Institution's policies should require service providers (including Microsoft for Copilot) to notify the institution within 72 hours of unauthorized NPI access |
| Notify affected individuals within 30 days | Copilot-related NPI incidents trigger customer notification obligations within 30 days |
Privacy Notice Considerations
When Copilot accesses NPI, the firm's privacy notice must accurately describe:
- Categories of NPI collected and used: Privacy notices should reflect that AI tools access NPI for operational purposes
- Parties with whom NPI is shared: If Copilot processing involves Microsoft as a service provider, this should be reflected in service provider disclosures
- Security practices: The notice should reference AI-related safeguards as part of the firm's security program
- Consumer rights: Opt-out rights and procedures should be clearly stated
Copilot Surface Coverage
| Copilot Surface | NPI Exposure Risk | Safeguard Mechanism |
|---|---|---|
| Outlook Copilot | High -- emails contain client NPI (account info, SSNs, financial data) | DLP policies on Exchange; sensitivity labels on NPI-containing emails |
| Microsoft Copilot Chat | High -- Copilot Chat is web-grounded, but organizational content can also enter through pasted or uploaded content, / file references (ContextIQ), side-by-side awareness of open content in Teams and Outlook, and pay-as-you-go agents with organizational access; NPI risk therefore includes typed, pasted, and uploaded prompts, referenced or open content, agent grounding, and web search |
DLP for Microsoft 365 Copilot and Copilot Chat location; the Allow web search in Copilot policy in Cloud Policy service for Microsoft 365; the Copilot app's Web content toggle is a user setting; sensitivity labels |
| SharePoint/OneDrive Copilot | High -- financial documents, client files, KYC records | DLP policies; sensitivity labels; site-level permissions; information barriers |
| Teams Copilot | Moderate -- meeting transcripts may contain NPI discussed verbally | Teams DLP; meeting transcript controls; channel permissions |
| Word Copilot | Moderate -- Copilot may reference NPI when drafting client documents | DLP policies; sensitivity label inheritance; output review |
| Excel Copilot | High -- financial data, account information, portfolio data | DLP policies; sensitivity labels; file-level permissions |
| Copilot Pages | Moderate -- pages may contain NPI copied from other sources | OneDrive DLP; sharing controls; sensitivity labels |
| Copilot Notebooks | Moderate -- notebooks may contain NPI copied from other sources | OneDrive DLP; sharing controls; sensitivity labels on source content referenced or copied into the notebook (Notebooks don't have a Notebook-level label) |
Governance Levels
Baseline
- Note the amended Reg S-P timeline: proposed March 2023, final rule adopted May 2024 (Release No. 34-100155), compliance deadline December 3, 2025 for larger firms and June 3, 2026 for smaller firms; key changes include expanded scope (investment advisers AND broker-dealers), mandatory written policies, expanded "customer information" definition, mandatory breach notification (≤30 days), and requirement for service providers to notify the institution within 72 hours of unauthorized access
- Assess Copilot as a system that accesses NPI in the firm's Reg S-P risk assessment
- Verify DLP policies cover NPI data types (SSN, account numbers, financial data) across Copilot-accessible locations
- Review privacy notices for accuracy regarding AI tool usage and NPI access
- Include Copilot NPI access in the firm's information security program documentation
- Establish a written incident response program covering Copilot-related NPI incidents (SEC Rule 248.30(a)(4) requirement; must include the 72-hour vendor notification procedure per Rule 248.30(a)(3)); confirm Microsoft's Data Processing Agreement (DPA) addresses the service provider notification requirements under Rule 248.30(a)(3)
- Enable current Data Security Posture Management (Purview portal > Solutions > DSPM, or
https://purview.microsoft.com/datasecurityposturemanagement) to review AI observability for SITs in Copilot prompts and responses as the primary internal NPI detection mechanism - Train Copilot users on NPI handling obligations and Copilot-specific NPI risks
Recommended
- Implement sensitivity labels for NPI-containing content with DLP enforcement at the Copilot interaction layer
- Configure information barriers to prevent Copilot from surfacing NPI across organizational boundaries (e.g., advisory vs. brokerage)
- Deploy Copilot-specific DLP policies using the current
-LocationsJSON for WorkloadApplicationsplus-EnforcementPlanes @("CopilotExperiences")with FSI-relevant SITs: U.S. Social Security Number (SSN), ABA Routing Number, U.S. Bank Account Number, Credit Card Number, and U.S. Individual Taxpayer Identification Number (ITIN); include sensitivity-label content processing, SIT prompt processing, and SIT external web-search grounding restrictions; configure incident reports to route to the privacy/compliance team - Configure the current DSPM (Purview portal > Solutions > DSPM; DSPM for AI is the classic experience) — use AI observability and Discover > Activity explorer > AI activities to detect SITs in Copilot prompts and responses, and to identify oversharing of labeled content (e.g., Confidential — Customer Data) through Copilot interactions
- Conduct annual Reg S-P risk assessment with explicit Copilot NPI analysis
- Implement automated NPI detection and classification for content accessed by Copilot
- Configure the incident response program in Microsoft Purview: verify that service provider agreements require Microsoft to provide 72-hour notification per Rule 248.30(a)(3); establish escalation paths for Copilot NPI incidents
- Test incident response procedures with Copilot-related NPI breach scenarios
- Update privacy notices to explicitly address AI tool usage in NPI processing
- Monitor Copilot access patterns for anomalous NPI access
Regulated
- Implement real-time NPI access monitoring for Copilot interactions using Microsoft Sentinel
- Configure automated alerting for Copilot access to high-sensitivity NPI (SSNs, financial account numbers) by setting the severity level, alert toggle, and email recipients in the Incident reports section of each Copilot DLP rule
- Conduct quarterly NPI access reviews covering all Microsoft Copilot and Copilot Chat users, including users without a paid Microsoft 365 Copilot add-on
- Implement data minimization controls to limit NPI exposure through Copilot
- Implement the amended Reg S-P incident response workflow: (1) Detection via Data Security Posture Management / DLP alert; (2) Scope determination via UAL audit logs + DSPM AI observability to identify which customer NPI was exposed; (3) Verify service provider notification arrangements per Rule 248.30(a)(3); (4) Customer notification per amended Reg S-P requirements
- Prepare Reg S-P examination-ready documentation including Copilot NPI safeguard controls, incident response program documentation, and evidence of 72-hour notification readiness per Rule 248.30(a)(3)
- Conduct tabletop exercises for Copilot-related NPI breach scenarios including both 72-hour vendor notification and 30-day customer notification timelines
- Commission independent assessment of Copilot NPI safeguard effectiveness
- Implement continuous compliance monitoring for Reg S-P safeguard requirements across Copilot surfaces
Setup & Configuration
Step 1: Assess Copilot NPI Access Scope
- Inventory NPI data types stored across Microsoft 365 workloads:
- Exchange: Client emails, account statements, application forms
- SharePoint: Client files, KYC documents, financial records
- OneDrive: Individual files containing NPI
- Teams: Client conversations, meeting transcripts
- Map Copilot access to each NPI location based on user permissions
- Identify high-risk NPI access scenarios:
- Copilot Chat queries that could surface NPI from multiple sources
- Copilot summaries that aggregate NPI from multiple documents
- Copilot-drafted communications that reference NPI
- Document findings in the firm's Reg S-P risk assessment
Step 2: Configure DLP Policies for NPI Protection
- Navigate to Microsoft Purview portal
- Go to Data Loss Prevention > Policies
- Create or update DLP policies:
- Name:
FSI-RegSP-Copilot-Privacy-Protection - Description: Protects NPI from unauthorized disclosure through Copilot interactions
- Policy admins: Purview Compliance Admin, Purview Compliance Data Admin, or the Purview Data Security AI Admin role (Purview Data Security AI Admins role group)
- Location: Microsoft 365 Copilot and Copilot Chat (Custom policy template; other DLP locations are disabled for that policy)
- Coverage: Copilot Chat, Copilot in Word, Excel, PowerPoint, Outlook, and Teams meetings/chats; use separate workload DLP policies for Exchange, SharePoint, OneDrive, and Teams controls outside the Copilot interaction layer
- Sensitive information types:
- U.S. Social Security Number (SSN)
- U.S. Bank Account Number
- Credit Card Number
- U.S. Individual Taxpayer Identification Number (ITIN)
- U.S./U.K. Passport Number
- Custom SITs for firm-specific account numbers
- Policy actions:
Prevent Copilot from processing content > Processing promptsfor prompts containing regulated SITsPrevent Copilot from processing content > Performing Web Searchesto restrict external web search / web grounding when prompts contain NPI SITsPrevent Copilot from processing contentfor files and emails carrying selected sensitivity labels
- Web grounding control: In the Cloud Policy service for Microsoft 365, configure the Allow web search in Copilot policy for the approved user/group scope and align it with the DLP web-search restriction. The Web content toggle in the Copilot app is a user setting, not the admin control.
- User notifications: Enable policy tips explaining why content was blocked
- Alerting (configure on each rule): In the rule's Incident reports section, set Use this severity level in admin alerts and reports, turn Send an alert to admins when a rule match occurs to On, and add the Privacy Officer and compliance team under Send email alerts to these people. This is the alert-definition surface for this control — Microsoft Defender XDR and the Purview Data loss prevention > Alerts dashboard are where the resulting alerts are investigated, not where they are defined.
- User scope: Include all users who can reach Microsoft Copilot or Copilot Chat, including users without a paid Microsoft 365 Copilot add-on. Copilot Chat is available at no extra cost to users holding common Microsoft 365, Office 365, and Teams licenses, and organizational content can enter Copilot Chat through uploaded and pasted content,
/file references, and agents. Microsoft's default Copilot DLP policy ships scoped to all tenant users and groups. Document any deliberate narrowing of that scope.
- Name:
-
For Security & Compliance PowerShell creation, use the current Copilot location JSON and Copilot enforcement plane rather than workload-specific location switches:
$ErrorActionPreference = 'Stop' Connect-IPPSSession -ErrorAction Stop New-DlpCompliancePolicy ` -Name "FSI-RegSP-Copilot-Privacy-Protection" ` -Locations '[{"Workload":"Applications","Location":"470f2276-e011-4e9d-a6ec-20768be3a4b0","Inclusions":[{"Type":"Tenant","Identity":"All"}]}]' ` -EnforcementPlanes @("CopilotExperiences") ` -Mode Enable ` -ErrorAction StopCreate the rules with their alert configuration (
-GenerateAlert,-GenerateIncidentReport,-IncidentReportContent,-ReportSeverityLevel) alongside their restriction actions (-RestrictAccess,-RestrictWebGrounding); a rule with no alert recipients produces no notification. Then run the fail-closed validation in PowerShell Setup — Script 1b before reporting the control as implemented: it stops on nonterminating cmdlet errors, resolves exactly one case-sensitive policy-name match before validating anything (a$nullor non-existentIdentityvalue makesGet-DlpCompliancePolicyreturn every policy in the tenant), and verifiesMode=Enable, the Copilot location GUID scoped tenant-wide with no exclusions,EnforcementPlanes=CopilotExperiences, both expected rules and their parent policy, their conditions and volume thresholds, their restriction actions, and their alert, incident report, severity, and recipient configuration. Where a property is not exposed or cannot be read, it stops and tells you what to verify manually in the portal.Organizations should verify rule conditions and actions match their approved sensitivity labels, SITs, and override procedures before moving to Enforce mode.
Step 3: Implement Sensitivity Labels for NPI Content
- Create or verify sensitivity labels for NPI-containing content:
- Label:
Confidential - Client NPI - Protection: Encryption, prevent forwarding, watermark
- Auto-labeling: Configure auto-labeling rules for documents containing NPI patterns
- Copilot behavior: A Copilot DLP rule using the
Content contains > Sensitivity labelscondition with the Prevent Copilot from processing content action excludes labeled files and emails from being used to generate the response. Excluded items can still appear in the response citations. This is grounding-side exclusion; the generated response text itself is not inspected by DLP.
- Label:
- Deploy auto-labeling policies for SharePoint sites and OneDrive locations containing client records
Step 4: Update Privacy Notices
- Review the firm's current privacy notice under Reg S-P
- Assess whether AI tool usage is adequately disclosed:
- Does the notice describe the use of AI tools in processing customer information?
- Does the notice accurately describe information sharing with technology service providers (Microsoft)?
- Do opt-out procedures account for AI processing of NPI?
- Update privacy notices if needed:
- Add disclosure about AI-assisted processing of customer information
- Confirm Microsoft is disclosed as a service provider processing NPI
- Verify opt-out procedures are clear and actionable
- Distribute updated notices per Reg S-P requirements
Step 5: Configure Incident Response Program for Copilot NPI Events
The amended Reg S-P requires a written incident response program (SEC Rule 248.30(a)(4)). The rule also requires institutions to adopt policies requiring service providers to notify the institution within 72 hours of unauthorized access (SEC Rule 248.30(a)(3)). For Copilot deployments:
- Document Copilot-related NPI incident scenarios in the written incident response program:
- Scenario 1: Copilot surfaces client NPI to unauthorized user due to permission misconfiguration
- Scenario 2: Copilot-drafted communication includes client NPI that should not have been disclosed
- Scenario 3: User exports NPI from Copilot interaction and shares externally
- Define incident severity levels:
- Critical: SSN, account credentials, or bulk NPI exposure through Copilot
- High: Individual client financial data exposure through Copilot
- Medium: Client contact information exposure through Copilot
- Low: Near-miss or policy tip triggered without actual NPI disclosure
- Establish notification procedures:
- Internal escalation: Per the institution's incident response procedures
- Service provider notification: Verify that service provider agreements require Microsoft to notify the institution within 72 hours of becoming aware of unauthorized access (Rule 248.30(a)(3))
- Customer notification: Within 30 days of becoming aware (per amended Reg S-P)
- Configure alerting on the Copilot DLP rules themselves (each rule's Incident reports section: severity level, Send an alert to admins when a rule match occurs, and the Privacy Officer / compliance team as email recipients). Investigate the resulting alerts in Microsoft Purview Data loss prevention > Alerts, Activity explorer AI activities, and Microsoft Defender XDR — those surfaces triage alerts but do not define them.
Financial Sector Considerations
Reg S-P Amendments Adopted in 2024 (Proposed in 2023): What Changed for Copilot
The key changes relevant to Copilot deployments are the mandatory incident response program and the 72-hour vendor notification, both now in effect:
- Written incident response program (Rule 248.30(a)(4)): Required as written policies and procedures -- not an informal process. Copilot access to NPI must be addressed in these written policies, including Copilot-specific incident scenarios.
- Service provider notification requirement (Rule 248.30(a)(3)): The amended rule requires covered institutions to adopt policies requiring service providers to notify the institution within 72 hours of becoming aware of unauthorized access to customer information. For Copilot deployments, institutions should verify that their agreements with Microsoft include this notification requirement.
- Customer notification within 30 days: Applies to Copilot-related NPI incidents where customer information was accessed without authorization.
- Oversight of service providers: Strengthened under the amendments -- Microsoft's Copilot data processing practices must be assessed, and service provider agreements should address incident notification procedures.
NPI in Copilot Context Windows
Copilot's context window includes content from the user's Microsoft Graph -- emails, files, chats, and calendar. This means NPI from client communications, financial documents, and internal discussions is all accessible within a single Copilot interaction. The aggregation of NPI from multiple sources in a single Copilot response creates a higher-risk NPI exposure scenario than any individual workload alone.
Documented Copilot DLP limitations (read before relying on this control): In the Microsoft 365 Copilot and Copilot Chat location, sensitive information type (SIT) enforcement evaluates the text a user types into the prompt. The two documented SIT actions are Prevent Copilot from processing content > Processing prompts and > Performing Web Searches. Microsoft does not document a DLP action that inspects or blocks the text of a generated Copilot response; sensitive data in responses can be observed after the fact (DSPM / Activity explorer AI activities, Audit, eDiscovery) but is not blocked by this control. DLP also can't scan the contents of files uploaded directly into a prompt — only typed prompt text is checked. SIT-based prompt blocking is in preview and rolling out. The sensitivity label condition covers emails sent on or after January 1, 2025; calendar invites and Admin units are not supported. Policy updates can take up to four hours to take effect in the Copilot experience.
Opt-Out Considerations
Reg S-P requires that customers be given the opportunity to opt out of NPI sharing with nonaffiliated third parties. While Microsoft is typically a service provider (not a nonaffiliated third party) under GLBA, firms should assess whether:
- Copilot's processing of NPI constitutes "sharing" under the opt-out provisions
- Service provider exception requirements are met (contractual provisions, appropriate oversight)
- Any Copilot extensibility features (plugins, connectors) involve NPI sharing with additional parties
Intersection with State Privacy Laws
In addition to Reg S-P, state privacy laws may impose additional requirements on NPI processed by Copilot:
- California CCPA/CPRA: Right to know, delete, and opt out of sale/sharing of personal information
- New York DFS Cybersecurity Regulation (23 NYCRR 500): Cybersecurity program requirements including AI system governance
- Massachusetts 201 CMR 17.00: Data security requirements for personal information
- Firms operating in multiple states must maintain a jurisdiction-specific compliance matrix for NPI and AI
People Skills and Employee Privacy
People Skills
Microsoft People Skills uses Microsoft Graph activity data to infer and publish professional skills on user profiles. In the Microsoft 365 admin center, Feature access management controls the People Skills user experiences and skill-inferencing settings. People Skills user experiences, Skills AI Inferencing, Skills Profile Visibility, Show AI-Inferred skills, and Show Imported Skills are documented as On by default; users can opt out where supported. Administrators can manage these settings through Feature access management or PowerShell.
For SEC-regulated entities, AI-powered skill inferencing raises Reg S-P and GLBA employee privacy considerations:
- Employee NPI processing: The skill inferencing engine processes work activity data that may include interactions with customer financial information. Organizations should assess whether skill inference processing constitutes a new use of NPI that falls within the scope of privacy notice disclosures.
- Consent and transparency: Employees should be informed that their work activity is being analyzed to infer skills. Organizations should evaluate whether existing employee privacy notices and acceptable use policies cover this processing.
- Recommended posture: FSI organizations should evaluate whether to restrict People Skills through Feature access management after a privacy impact assessment; the feature is not disabled by default. See also Control 4.4 — Viva Suite Governance.
Verification Criteria
| # | Verification Step | Expected Outcome | Governance Level |
|---|---|---|---|
| 1 | Verify Copilot is included in Reg S-P risk assessment | Risk assessment documents Copilot NPI access scope and controls | Baseline |
| 2 | Test the Copilot DLP policy against NPI typed into a prompt, and validate the policy configuration fail-closed | Prompt containing an SSN is restricted or a policy tip is displayed; the validation script confirms Mode=Enable, the Copilot location GUID, EnforcementPlanes=CopilotExperiences, both expected rules with their restriction actions, and their alert configuration, with no exception raised |
Baseline |
| 3 | Verify privacy notice addresses AI tool usage | Privacy notice discloses use of AI tools in processing customer information | Baseline |
| 4 | Verify written incident response program exists and covers Copilot | Program includes Copilot-specific scenarios with written notification procedures (Rule 248.30(a)(4)) | Baseline |
| 5 | Verify service provider notification requirement is addressed | Service provider agreements require 72-hour notification to the institution per Rule 248.30(a)(3) | Baseline |
| 6 | Test sensitivity label auto-labeling for NPI content | Documents containing NPI patterns are automatically labeled | Recommended |
| 7 | Test incident response plan covers Copilot NPI scenarios | Plan includes Copilot-specific scenarios with notification procedures per amended Reg S-P | Recommended |
| 8 | Test information barrier enforcement in Copilot | Copilot does not surface NPI across barrier boundaries | Recommended |
| 9 | Run tabletop exercise for Copilot NPI breach | Exercise tests incident response procedures including service provider notification and customer notification timelines | Regulated |
| 10 | Verify real-time NPI access monitoring | Sentinel alerts trigger for anomalous Copilot NPI access patterns | Regulated |
| 11 | Review independent safeguard effectiveness assessment | Assessment validates Copilot NPI controls and identifies gaps | Regulated |
| 12 | Verify examination-ready documentation | Complete Reg S-P compliance package for Copilot, including incident response program documentation and compliance date evidence | Regulated |
Additional Resources
- SEC Regulation S-P (17 CFR Part 248)
- SEC Final Rule -- Regulation S-P Amendments (May 2024, Release No. 34-100155)
- GLBA Title V -- Privacy
- Interagency Guidelines for Safeguarding Customer Information
- Microsoft Purview DLP documentation
- Microsoft Learn: Data Security Posture Management
- Microsoft Learn: Prevent oversharing with data risk assessments
- Microsoft 365 Copilot data, privacy, and security
- Control 2.x -- DLP Policies (Pillar 2)
-
Related Controls: 2.1 DLP Policies for Copilot, 1.1 Copilot Readiness Assessment, 3.2 Data Retention Policies
FSI Copilot Governance Framework v1.8.0 - July 2026