Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
Revoke all active sign-in sessions for users named in an identity access record exposure.
| Attribute | Value |
|---|---|
| Type | Playbook |
| Solution | SpyCloud Enterprise Protection CCF |
| Source | View on GitHub |
This playbook uses 2 Logic App connectors / built-in actions:
| Connector / Action | Type | Connections | Actions |
|---|---|---|---|
azuresentinel |
Managed | 1 | 2 |
http |
Built-in | 0 | 3 |
azuresentinel (Managed)| Action | Method | Endpoint | Other |
|---|---|---|---|
| Entities_-_Get_Accounts | post | /entities/account |
— |
| Add_comment_to_incident | post | /Incidents/Comment |
— |
http (Built-in)| Action | Method | Endpoint | Other |
|---|---|---|---|
| HTTP_-_Revoke_User_Sessions | POST | https://graph.microsoft.com/v1.0/users/@{concat(items('For_each')?['Name'],'@',items('For_each')?['UPNSuffix'])}/revokeSignInSessions |
— |
| GetAccessToken | POST | @concat(variables('loginUrl'), parameters('TenantID'), '/oauth2/v2.0/token') |
— |
| Log_ingestion | POST | @variables('log_ingestion_api') |
— |
📄 Source: SpyCloud_Session_Revocation/readme.md
This playbook revokes active Microsoft Entra sign-in sessions for users named in a SpyCloud identity access record exposure.
Identity access records cover session cookies, OAuth tokens and SSO credentials. That material grants account access without a password, so it survives a password reset and defeats single-factor controls. Revoking active sessions is the primary containment action, which is why this playbook does that and nothing else.
Capabilities
SpyCloud_ConditionalAccessLogsV2_CLThe deployment also creates the Microsoft Sentinel automation rule that invokes this playbook, so no separate wiring step is needed.
User.RevokeSessions.All, or User.ReadWrite.All), granted admin consentThis deployment creates an automation rule alongside the Logic App, and Sentinel refuses to create one unless it already has permission to run playbooks in the target resource group. Without it the deployment fails with Missing required permissions for Microsoft Sentinel on the playbook resource.
az role assignment create \
--role "Microsoft Sentinel Automation Contributor" \
--assignee 98785600-1bb7-4fb9-b9fa-19afe2c8a360 \
--scope /subscriptions/<subscription-id>/resourceGroups/<resource-group>
98785600-1bb7-4fb9-b9fa-19afe2c8a360 is the fixed application ID for Azure Security Insights.
Sentinel creates the data collection rule as Microsoft-Sentinel-SpyCloudwatchlist-DCR-<guid>, not under the name in the solution template, and pairs it with an auto-generated asi-<guid> endpoint. Read both from the live connector:
SUB=<subscription-id>; RG=<resource-group>; WS=<workspace-name>
az rest --method get --url "https://management.azure.com/subscriptions/$SUB/resourceGroups/$RG/providers/Microsoft.OperationalInsights/workspaces/$WS/providers/Microsoft.SecurityInsights/dataConnectors?api-version=2023-02-01-preview" --query "value[?properties.dcrConfig] | [0].properties.dcrConfig.{immutableId: dataCollectionRuleImmutableId, endpoint: dataCollectionEndpoint}"
Note that DCE_Immutable_ID takes the DCR's immutable ID despite its name.
All settings are supplied at deployment time.
azuredeploy.json)| Parameter | Type | Default | Description |
|---|---|---|---|
| PlaybookName | String | SpyCloud_Session_Revocation | Name of the Logic App resource |
| Revoke_User_Sessions | String | false | Set to true to revoke sessions. With false the playbook runs, comments on the incident and logs, but takes no action |
| ClientID | String | — | App Registration Client ID |
| TenantID | String | — | Azure Tenant ID |
| ClientSecret | SecureString | — | App Registration Client Secret |
| DCE_Endpoint | String | — | DCE Logs Ingestion Endpoint URL |
| DCE_Immutable_ID | String | — | DCR Immutable ID |
| Custom_Table_Name | String | SpyCloud_ConditionalAccessLogsV2_CL | Log table, shared with the Conditional Access playbook |
| Sentinel_Workspace_Resource_Id | String | Solution workspace | Workspace the automation rule is created in. Pre-filled when deploying from Content Hub |
| AccessRecordIncidentTitle | String | SpyCloud identity access record exposure | Incident title the automation rule matches on |
| Automation_Rule_Order | Int | 3 | Execution order of the automation rule |
Revoke_User_Sessions is a string with allowed values true / false, not a boolean. Microsoft Sentinel's Content Hub playbook editor renders no input control at all for ARM bool parameters, which would leave the toggle stuck at its default. The editor also ignores the declared allowed values and shows a plain textbox — type exactly true or false. Anything else fails the deployment when the value is converted back to a boolean, which is deliberate.
The deployment creates one connection, azuresentinel, which uses the playbook's system-assigned managed identity. There is no Authorize button and none is needed. Grant that managed identity the Microsoft Sentinel Responder role on the workspace, or the playbook cannot read incident entities or comment on incidents.
[Content truncated...]
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
↑ Back to Playbooks · Back to SpyCloud Enterprise Protection CCF