Skip to content

Control 1.2: SharePoint Oversharing Detection (DSPM for AI) — Verification & Testing

Test cases and evidence collection for validating SharePoint oversharing detection and remediation.

Test Cases

Test 1: DSPM Activation and Unified Experience Verification

  • Objective: Confirm DSPM is enabled and the unified experience is accessible from both Purview and MAC
  • Steps:
  • Navigate to Microsoft Purview > Data Security Posture Management > Overview
  • Verify the service status shows "Active"
  • Confirm the last scan date is within the past 7 days
  • Confirm the default assessment is present for the top 100 SharePoint sites by usage, and use a custom assessment if evidence is needed for sites outside that weekly default scope
  • Verify AI observability section is accessible
  • Navigate to Microsoft 365 Admin Center > Copilot > Security and confirm DSPM security controls are accessible from this path
  • Expected Result: DSPM is active, the weekly default assessment is present for the documented top-100-sites scope, and both access paths (Purview and MAC) are functional
  • Evidence: Screenshots of DSPM overview from Purview portal and MAC Security tab with timestamps

Test 2: Oversharing Detection Accuracy

  • Objective: Verify that DSPM correctly identifies overshared sites
  • Steps:
  • Create a test SharePoint site with "Everyone except external users" access
  • Upload a document with a Confidential sensitivity label to the test site
  • Wait for the next weekly default assessment cycle or run a custom assessment and allow the documented result-processing window
  • Check that the test site appears in the oversharing report
  • Clean up the test site after verification
  • Expected Result: The test site with sensitive labeled content and broad access appears as a Critical or High finding
  • Evidence: DSPM finding showing the test site with correct risk classification

Test 3: Remediation Effectiveness

  • Objective: Confirm that remediated sites no longer appear as overshared
  • Steps:
  • Select a site that was previously flagged and remediated
  • Verify the sharing capability has been restricted via Get-SPOSite -Identity <url>
  • Wait for the next DSPM scan to process the change
  • Confirm the site no longer appears in the oversharing findings or shows as remediated
  • Expected Result: Remediated sites are marked as resolved in subsequent scans
  • Evidence: Before and after DSPM reports showing finding resolution

Test 4: Oversharing Policy Alert Functionality

  • Objective: Verify that oversharing policies generate alerts when triggered
  • Steps:
  • Create or identify an active oversharing detection policy
  • Simulate the policy condition (e.g., share a sensitive document broadly)
  • Wait for the alert generation cycle (up to 24 hours)
  • Verify the alert appears in Purview > Alerts and email notification is received
  • Reverse the simulated oversharing action
  • Expected Result: Alert is generated and delivered to configured recipients within the expected timeframe
  • Evidence: Alert record from Purview and email notification screenshot

Test 5a: AI Observability Functional Verification

  • Objective: Verify AI observability is populated and the governance team is reviewing unsanctioned or high-risk AI-app findings
  • Steps:
  • Navigate to Microsoft Purview > Data Security Posture Management > AI Observability
  • Confirm the inventory of AI apps and agents is populated with recent activity data
  • Verify the governance team has reviewed recent high-risk or unsanctioned AI-app findings in the past 30 days
  • If the tenant also uses the separate Microsoft 365 admin center Agents > Shadow AI page, confirm that review workflow is documented separately from DSPM
  • Expected Result: AI observability is active and the governance team has a process to review findings from DSPM and, if applicable, the separate Shadow AI preview surface
  • Evidence: Screenshot of AI observability findings dashboard; review record or alert configuration screenshot

Test 6: Copilot Access Validation Post-Remediation

  • Objective: Confirm Copilot respects remediated permissions and does not surface overshared content
  • Steps:
  • Identify a user who previously had unintended access to sensitive content via oversharing
  • After remediation, have the user query Copilot for content from the restricted site
  • Verify Copilot does not return results from the restricted site
  • Document the Copilot response
  • Expected Result: Copilot only returns content the user has legitimate access to post-remediation
  • Evidence: Copilot interaction log showing no results from restricted content

Evidence Collection

Evidence Item Format Storage Location Retention
DSPM activation screenshot PNG/PDF Compliance evidence repository 7 years
Oversharing assessment export CSV Compliance evidence repository 7 years
Remediation log CSV Compliance evidence repository 7 years
Alert notification records PDF Compliance evidence repository 7 years
Copilot access validation results PDF Compliance evidence repository 7 years

Compliance Mapping

Regulation Requirement How This Control Supports It
FINRA Rule 3110 Supervisory systems and WSPs Oversharing detection supports supervision of access and communications risks
SEC Regulation S-P Safeguards for customer records and information Detecting and remediating oversharing helps meet technical safeguard obligations
GLBA §501(b) Information security program / access controls for NPI Reduces risk of unauthorized access to non-public personal information
SOX Section 404 Internal controls over financial reporting Where applicable, helps address access control risks over financial reporting data