Microsoft Purview – Data Security Posture Management (DSPM) for AI
Introduction to DSPM for AI In an age where Artificial Intelligence (AI) is rapidly transforming industries, ensuring the security and compliance of AI integrations is paramount. Microsoft Purview Data Security Posture Management (DSPM) for AI helps organizations monitor AI activity, enforce security policies, and prevent unauthorised data exposure. Microsoft Purview Data Security Posture Management (DSPM) for AI addresses three primary areas: Recommendations, Reports, and Data Assessments. DSPM for AI assists in identifying vulnerabilities associated with unprotected data and enables prompt action to enhance data security posture and mitigate risks effectively. Getting Started with DSPM for AI To manage and mitigate AI-related risks, Microsoft Purview provides easy-to-use graphical tools and comprehensive reports. These features allow you to quickly gain insights into AI use within your organization. The one-click policies offered by Microsoft Purview simplify the process of protecting your data and ensuring compliance with regulatory requirements. Prerequisites for Data Security Posture Management for AI To use DSPM for AI from the Microsoft Purview portal or the Microsoft Purview compliance portal, you must have the following prerequisites: You have the right permissions. Monitoring Copilot interactions requires: Users are assigned a license for Microsoft 365 Copilot. o Microsoft Purview auditing enabled. Check instructions for Turn auditing on or off. Required for monitoring interactions with third-party generative AI sites: Devices are onboarded to Microsoft Purview, required for: Gaining visibility into sensitive information that's shared with third-party generative AI sites. (e.g., credit card numbers pasted into ChatGPT). Applying endpoint DLP policies to warn or block users from sharing sensitive information with third-party generative AI sites. (e.g. a user identified as elevated risk in Adaptive Protection is blocked with the option to override when they paste credit card numbers into ChatGPT) The Microsoft Purview browser extension is deployed to users and required to discover site visits to third-party generative AI sites. Things to consider Recommendations may differ based on M365 licenses and features. Not all recommendations are relevant for every tenant and can be dismissed. Any default policies created while Data Security Posture Management for AI was in preview and named Microsoft Purview AI Hub won't be changed. For example, policy names will retain their Microsoft AI Hub -prefix. In this blog post we are going to focus on Recommendations. Recommendations Let's explore each of the recommendations in detail, which will encompass one-click policy creation, data assessments, step-by-step guidance, and regulations. The data in the reports section will be contingent upon the completion of each recommendation. Figure 1: Recommendations – DSPM for AI Control unethical behaviour in AI Type: One-click policy Solution: Communication Compliance Description: This policy identifies sensitive information within prompts and response activities in Microsoft 365 Copilot. Action: Create policy to setup a one-click policy. Conditions: Content matches any of these trainable classifiers: Regulatory Collusion, Stock manipulation, Unauthorized disclosure, Money laundering, Corporate Sabotage, Sexual, Violence, Hate, Self-harm By default, all users and groups are added. The customisation of the policy is also available during the one-click policy creation process. Figure 2: Recommendations – One-click policy Guided assistance to AI regulations Type: New AI regulations Solution: Compliance manager Description: This recommendation is based on the NIST AI RMF regulations, suggesting actions to help users protect data during interactions with AI systems. Action: Monitor AI interaction logs: Go to Audit logs, configure search with workload filter, select copilot and sensitive information type and review search results. Monitor AI interactions in other AI apps: Navigate to DSPM for AI and review interactions in other AI apps for sensitive content and turn on policies to discover data across AI interactions and other AI apps. Flag risky communication and content in AI interactions: Create Communication compliance policy to define the necessary conditions and fields and select Microsoft Copilot as location. Prevent sensitive data from being shared in AI apps: Create Data loss prevention (DLP) policy with sensitive information type as conditions for Teams and Channel messages location. Manage retention and deletion policies for AI interactions: Create a retention policy for Teams chat and Microsoft 365 Copilot interactions to preserve relevant AI activities for a longer duration while promptly deleting non-relevant user actions. Protect sensitive data referenced in Copilot responses Type: Assessment Solution: Data assessments Description: Use data assessments to identify potential oversharing risks, including unlabelled files. Action: Create Data Assessments, Navigate to DSPM for AI - Data Assessments and Create Assessments. Enter assessment name and description Select users and data sources to assets for oversharing data Conduct the assessment scan and review the results to gain insights into oversharing risks and recommended solutions to restrict access to sensitive data. Implement the necessary fixes to protect your data. Discover and govern interactions with ChatGPT Enterprise AI (preview) Type: ChatGPT Enterprise AI (Data discovery) Solution: Microsoft Purview Data Map Description: Register ChatGPT Enterprise workspace to discover and govern interactions with ChatGPT Enterprise AI. Action: If you’re organisation is using ChatGPT Enterprise, then enable the Connector In Microsoft Azure, use Key Vault to manage credentials for third-party connectors: Use Key Vault to create and manage the secret for the ChatGPT Enterprise AI Connector. In Microsoft Purview, configure the new connector using Data Map: How to manage data sources in the Microsoft Purview Data Map Create and start a new scan: Create a new scan, select credential, review, and run the scan. Protect sensitive data referenced in Microsoft 365 Copilot (preview) Type: Data Security Solution: Data loss prevention Description: Content with sensitivity labels will be restricted from Copilot interactions with a data loss prevention policy. Action: Create a custom DLP policy and select Microsoft 365 Copilot as the data source. Create a custom rule o Condition: content contains sensitivity labels. o Action: Prevent Copilot from processing content. Figure 3: Custom DLP policy condition and action Fortify your data security Type: Data security Solution: Data loss prevention Description: Data security risks can range from accidental oversharing of information outside of the organization to data theft with malicious intent. These policies will protect against the data security risks with AI apps. Action: A one-click policy is available to create a data loss prevention (DLP) policy for endpoints (devices), aimed at blocking the transmission of sensitive information to AI sites. It utilises Adaptive Protection to give a warn-with-override alert to users with elevated risk levels who attempt to paste or upload sensitive information to other AI assistants in browsers such as Edge, Chrome, and Firefox. This policy covers all users and groups in your org in test mode. Figure 4: Block with override for elevated risk users Information Protection Policy for Sensitivity Labels Type: Data security Solution: Sensitivity Labels Description: This policy will set up default sensitivity labels to preserve document access rights and protect Microsoft 365 Copilot output. Action: Create policies will navigate to Information protection portal to set up sensitivity labels and publishing policy. Protect your data from potential oversharing risks Type: Data Security Solution: Data Assessment Description: Data assessments provide insights on potential oversharing risks within your organisation for SharePoint Online and OneDrive for Business (roadmap) along with fixes to limit access to sensitive data. This report will include sharing links. Action: This is a default oversharing assessment policy. To see the latest oversharing scan results: Select View latest results and choose a data source. Complete fixes to secure your data. Figure 5: Data assessments – Oversharing assessment data with sharing links report Use Copilot to improve your data security posture (preview) Type: Data security posture management Solution: Data security posture management (DSPM) Description: Data Security Posture Management (preview) combines deep insights with Security Copilot capabilities to help you identify and address security risks in your org. Benefits: Data security recommendations Gain insights into your data security posture and get recommendations protecting sensitive data and closing security gaps. Data security trends Track your org's data security posture over time with reports summarizing sensitive label usage, DLP policy coverage, changes in risky user behaviour, and more. Security Copilot Security Copilot helps you investigate alerts, identify risk patterns, and pinpoint the top data security risks in your org.SharePoint Online: PowerShell script to check and disable the IRM option into the SPLists
In Office 365, the IRM solution has many impacts on the licensing model. In some cases, you can have to implement the IRM option for only a couple of site collections, with a limited number of persons. The issue is from license point of view, because the IRM activation is at the global level, but when it's done, any TeamSite Content Manager can enable the option into his list. But when it's done, the users who will access that SPList will have to be licensed with E3. So to limit that license gap impact, you can use the following script preparing a CSV file like: SiteCollectionURL; https://mytenant.sharepoint.com/sites/mysitecollwithIRMaccepted; The PowerShell will connect your tenant to get the Sites to check via the commands (getting the SPO TeamSites and SPO GroupSites): $sitesInfo1 = Get-SPOSite -Template "STS#0" -IncludePersonalSite:$false -Limit ALL | Sort-Object -Property url | Select * $sitesInfo2 = Get-SPOSite -Template "GROUP#0" -IncludePersonalSite:$false -Limit ALL | Sort-Object -Property url | Select * $sitesInfo = $sitesInfo2 + $sitesInfo1 | Sort url Into that list, the script will look into all SPList placed into all subsites and check if the IRM is enable or not: If no: it will be skipped with a line into the log If yes: it will be disable into the concerned list and a line will be added into the log At the end of that script the log will be zipped and sent via Email to the defined address. The disabled lists are placed into the body of that email too. The full script is below: [string]$GLOBAL:Logtofile = "" [string]$GLOBAL:LogtoEmail = "" [string]$username = "Adminaccount@tenant.onmicrosoft.com" [string]$PwdTXTPath = "C:\SECUREDPWD\ExportedPWD-$($username).txt" [string]$CSVExclusionFilePath = "C:\IRMCHECK\SiteCollectionsWithAuthorizedIRM.csv" [string]$EmailAddressFrom = "supportteam@Yourdomain.com" [string]$EmailAddressToSend = "supportteam@Yourdomain.com" [string]$EmailSubject = "SHAREPOINT ONLINE IRM CHECK - "+ $(Get-Date).ToString("yyyy-MM-dd-hh:mm") [string]$EmailSMTPServer = "smtp.Yourdomain.net" [string]$EmailSMTPPort = "25" $EmailencodingMail = [System.Text.Encoding]::UTF8 [string]$AllSiteWithListenableIRMLog = "AllSiteWithListenableIRM.log" [string]$FolderDestinationLogFile = "D:\IRMCHECK\LOGS\" [string]$DestinationLogFilePath = "" [string]$ZippedLogFilePath = "" [string]$MyRootFolderListURL = "" $OFS = "`r`n" [System.Diagnostics.Stopwatch] $sw; $sw = New-Object System.Diagnostics.StopWatch $sw.Start() function Load-DLLandAssemblies { [string]$defaultDLLPath = "" # Load assemblies to PowerShell session $defaultDLLPath = "C:\Program Files\SharePoint Online Management Shell\Microsoft.Online.SharePoint.PowerShell\Microsoft.SharePoint.Client.dll" [System.Reflection.Assembly]::LoadFile($defaultDLLPath) $defaultDLLPath = "C:\Program Files\SharePoint Online Management Shell\Microsoft.Online.SharePoint.PowerShell\Microsoft.SharePoint.Client.Runtime.dll" [System.Reflection.Assembly]::LoadFile($defaultDLLPath) $defaultDLLPath = "C:\Program Files\SharePoint Online Management Shell\Microsoft.Online.SharePoint.PowerShell\Microsoft.Online.SharePoint.Client.Tenant.dll" [System.Reflection.Assembly]::LoadFile($defaultDLLPath) } function Get-SPOWebs(){ param( $Url = $(throw "Please provide a Site Collection Url"), $Credential = $(throw "Please provide a Credentials") ) $context = New-Object Microsoft.SharePoint.Client.ClientContext($Url) $context.Credentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($Credential.UserName,$Credential.Password) $context.RequestTimeout = 1000000 # milliseconds $web = $context.Web $context.Load($web) $context.Load($web.Webs) $context.ExecuteQuery() foreach($web in $web.Webs) { Get-SPOWebs -Url $web.Url -Credential $Credential $web } } function Check-All-SPOWebLists(){ param( $Url = $(throw "Please provide a Site Collection Url"), $Credential = $(throw "Please provide a Credentials") ) $GLOBAL:Logtofile += " ------------------------------------------------------------------------------------ " + $OFS $GLOBAL:Logtofile += " Checks into the Subsite: "+ $Url + $OFS $context = New-Object Microsoft.SharePoint.Client.ClientContext($Url) $context.Credentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($Credential.UserName,$Credential.Password) $context.RequestTimeout = 1000000 # milliseconds $web = $context.Web $Mylists = $web.Lists; $Context.Load($Mylists) $Context.ExecuteQuery(); Write-host " -------------------- CHECK IN LISTS -------------------- " foreach($myList in $MyLists) { Write-host " ==== List Name:", $mylist.Title -ForegroundColor Magenta if($mylist.IrmEnabled) { Write-host " IRM Status (IrmEnabled):", $mylist.IrmEnabled -ForegroundColor Red Write-host " >>> NEED TO CONTROL OR DISABLE THE SETTING" -ForegroundColor Red # GET the Owner if possible ?? #Force the IRM Disable at the list level $mylist.IrmEnabled = $false $mylist.Update() $Context.ExecuteQuery() #Logging the change $GLOBAL:Logtofile += " IRM ACTIVE from the list: "+ $mylist.Title +" - in SPWeb: "+ $Url + $OFS $GLOBAL:LogtoEmail += " IRM ACTIVE from the list: "+ $mylist.Title +" - in SPWeb: "+ $Url + $OFS } else { Write-host " IRM Status (IrmEnabled):", $mylist.IrmEnabled -ForegroundColor Green $GLOBAL:Logtofile += " IRM Not active from the list: "+ $mylist.Title +" - in SPWeb: "+ $Url + $OFS } } $GLOBAL:Logtofile += " ------------------------------------------------------------------------------------ " + $OFS } cls Write-Host " ---------------------------------------------- " Load-DLLandAssemblies Write-Host " ---------------------------------------------- " $secureStringPwd = ConvertTo-SecureString -string (Get-Content $PwdTXTPath) $adminCreds = New-Object System.Management.Automation.PSCredential $username, $secureStringPwd Connect-SPOService -Url https://tenant-admin.sharepoint.com -credential $adminCreds -ErrorAction SilentlyContinue -ErrorVariable Err Write-host " -------------------------------------------------------------------------------------------- " -ForegroundColor green $SiteToExcludeList = Import-Csv -encoding UTF8 $CSVExclusionFilePath -delimiter ";" #$SiteToExcludeList | Format-Table Write-host " >>> CSV File content loaded:", $CSVExclusionFilePath, "- Total Lines:", $SiteToExcludeList.count -ForegroundColor Yellow Write-host " -------------------------------------------------------------------------------------------- " -ForegroundColor green $TempPathFilename = $(Get-Date).ToString("yyyyMMdd-hhmmss-fff")+"_"+ $AllSiteWithListenableIRMLog $DestinationLogFilePath = Join-Path -Path $FolderDestinationLogFile -ChildPath $TempPathFilename if (Test-Path $DestinationLogFilePath) { Remove-Item $DestinationLogFilePath -Force } #Retrieve all site collection infos (GroupSite and Classic TeamSite) $sitesInfo1 = Get-SPOSite -Template "STS#0" -IncludePersonalSite:$false -Limit ALL | Sort-Object -Property url | Select * $sitesInfo2 = Get-SPOSite -Template "GROUP#0" -IncludePersonalSite:$false -Limit ALL | Sort-Object -Property url | Select * $sitesInfo = $sitesInfo2 + $sitesInfo1 | Sort url #$sitesInfo = $sitesInfo1 | Sort url | Select-Object -First 2 #TO CHECK ONLY THE FIRST 2 CLASSIC TEAMSITE COLLECTION Write-Host "--------------------------------------------------------------------------------------------" Write-Host " =>>>>>>> Site collections number to check:", $sitesInfo.count -ForegroundColor Magenta Write-Host "--------------------------------------------------------------------------------------------" foreach($SiteToExclude in $SiteToExcludeList) { $sitesInfo = $sitesInfo | where {$_.url -ne $SiteToExclude.SiteCollectionURL} #remove all the excluded items from the site list } Write-Host "--------------------------------------------------------------------------------------------" Write-Host " =>>>>>>> Site collections number to check:", $sitesInfo.count -ForegroundColor Magenta Write-Host "--------------------------------------------------------------------------------------------" $GLOBAL:Logtofile += "--------------------------------------------------------------------------------------------" + $OFS $GLOBAL:Logtofile += " =>>>>>>> Site collections number to check: "+ $($sitesInfo.count) + $OFS $GLOBAL:Logtofile += "--------------------------------------------------------------------------------------------" + $OFS #Retrieve and print all sites foreach ($site in $sitesInfo) { #$SiteToExcludeList |Where-Object {$_.SiteCollectionURL -match $site.Url} Write-Host "===================================================================================================" Write-Host " => SPO Site collection:", $site.Url, "- Title:", $site.Title -ForegroundColor green Write-Host " => External Sharing:", $site.SharingCapability, "- Site Template Used:", $site.Template Write-Host "--------------------------------------------------------------------------------------------" $GLOBAL:Logtofile += "===================================================================================================" + $OFS $GLOBAL:Logtofile += " => SPO Site collection: "+ $($site.Url) +" - Title: "+ $($site.Title) + $OFS $GLOBAL:Logtofile += " => External Sharing: "+ $($site.SharingCapability) +" - Site Template Used: "+ $($site.Template) + $OFS $GLOBAL:Logtofile += "--------------------------------------------------------------------------------------------" + $OFS # ===> TO DO AND GET THE OFFICIAL SITE OWNER #Write-Host " => Owner:", $site.Owner Check-All-SPOWebLists -Url $site.Url -Credential $adminCreds -MyLogToFill $AllWebs = Get-SPOWebs -Url $site.Url -Credential $adminCreds foreach($MySPWeb in $AllWebs) { $GLOBAL:Logtofile += " ------------------------------------------------------------------------ " + $OFS $GLOBAL:Logtofile += " => Subsite: "+ $($MySPWeb.Url) +" - Title: "+ $($MySPWeb.Title) + $OFS Write-Host "--------------------------------------------------------------------------------------------" -ForegroundColor yellow Write-Host " ==>>", $MySPWeb.Title, "-", $MySPWeb.Url -ForegroundColor yellow Check-All-SPOWebLists -Url $MySPWeb.Url -Credential $adminCreds -MyLogToFill } Write-Host "--------------------------------------------------------------------------------------------" $GLOBAL:Logtofile += " ------------------------------------------------------------------------ " + $OFS } $sw.Stop() Write-host " ===================================================================================================" -ForegroundColor Green write-host " ===>>>>IRM Check and fix: ", $sw.Elapsed.ToString() -foreground Yellow Write-host " ===================================================================================================" -ForegroundColor Green $GLOBAL:Logtofile += " ===================================================================================================" + $OFS $GLOBAL:Logtofile += " ===>>>>IRM Check and fix: "+ $($sw.Elapsed.ToString()) + $OFS $GLOBAL:Logtofile += " ===================================================================================================" + $OFS if($GLOBAL:LogtoEmail -eq "") { $GLOBAL:LogtoEmail += " There is no place where IRM is enable" + $OFS + $OFS } $GLOBAL:LogtoEmail += " ===================================================================================================" + $OFS $GLOBAL:LogtoEmail += " FIND THE DETAILS INTO THE LOG FILE AVAILABLE INTO THE SERVER FOLDER: "+ $DestinationLogFilePath + $OFS $GLOBAL:LogtoEmail += " ===================================================================================================" + $OFS add-content -Encoding UTF8 -Path $DestinationLogFilePath -Value $GLOBAL:Logtofile -Force #Add the ZIP Action for the generated log file $ZippedLogFilePath = $DestinationLogFilePath +".zip" Compress-Archive -LiteralPath $DestinationLogFilePath -CompressionLevel Optimal -Update -Force -DestinationPath $ZippedLogFilePath Send-MailMessage -From $EmailAddressFrom -to $EmailAddressToSend -Subject $EmailSubject -Body $GLOBAL:LogtoEmail -SmtpServer $EmailSMTPServer -port $EmailSMTPPort -Attachments $ZippedLogFilePath -Encoding $EmailencodingMail You can use and adapt that script as you want to. Fabrice Romelard Sources used: https://thesharepointfarm.com/2013/07/using-powershell-to-manage-sharepoint-information-rights-management-settings/ https://social.technet.microsoft.com/Forums/lync/en-US/96139289-1458-48e6-908a-007ca5138d78/enable-and-configure-irm-for-sharepoint-online-using-powershell?forum=onlineservicessharepoint https://www.c-sharpcorner.com/blogs/how-to-configure-irm-in-sharepoint-onlineoffice-365-using-csom2 French version: http://blogs.developpeur.org/fabrice69/archive/2018/12/14/sharepoint-online-script-powershell-pour-d-sactiver-l-option-irm-des-sites-spo-non-autoris-s.aspxPurview Webinars
REGISTER FOR ALL WEBINARS HERE Upcoming Microsoft Purview Webinars JULY 15 (8:00 AM) Microsoft Purview | How to Improve Copilot Responses Using Microsoft Purview Data Lifecycle Management Join our non-technical webinar and hear the unique, real life case study of how a large global energy company successfully implemented Microsoft automated retention and deletion across the entire M365 landscape. You will learn how the company used Microsoft Purview Data Lifecyle Management to achieve a step up in information governance and retention management across a complex matrix organization. Paving the way for the safe introduction of Gen AI tools such as Microsoft Copilot. 2025 Past Recordings JUNE 10 Unlock the Power of Data Security Investigations with Microsoft Purview MAY 8 Data Security - Insider Threats: Are They Real? MAY 7 Data Security - What's New in DLP? MAY 6 What's New in MIP? APR 22 eDiscovery New User Experience and Retirement of Classic MAR 19 Unlocking the Power of Microsoft Purview for ChatGPT Enterprise MAR 18 Inheriting Sensitivity Labels from Shared Files to Teams Meetings MAR 12 Microsoft Purview AMA - Data Security, Compliance, and Governance JAN 8 Microsoft Purview AMA | Blog Post 📺 Subscribe to our Microsoft Security Community YouTube channel for ALL Microsoft Security webinar recordings, and more!
