Skip to content

Commit 9e8a5a6

Browse files
committed
transition draft
1 parent 3848572 commit 9e8a5a6

File tree

5 files changed

+150
-6
lines changed

5 files changed

+150
-6
lines changed

unified-secops-platform/TOC.yml

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,8 @@
2020
href: /azure/sentinel/microsoft-365-defender-sentinel-integration?toc=/unified-secops-platform/toc.json&bc=/unified-secops-platform/breadcrumb/toc.json&tabs=defender-portal
2121
- name: Experience in the Defender portal
2222
href: /azure/sentinel/microsoft-sentinel-defender-portal?toc=/unified-secops-platform/toc.json&bc=/unified-secops-platform/breadcrumb/toc.json
23+
- name: Transition to unified SecOps from the Azure portal
24+
href: transition.md
2325
- name: Microsoft Copilot
2426
href: /defender-xdr/security-copilot-in-microsoft-365-defender?toc=/unified-secops-platform/toc.json&bc=/unified-secops-platform/breadcrumb/toc.json
2527
- name: Microsoft Security Exposure Management
@@ -40,9 +42,11 @@
4042
- name: Deploy
4143
items:
4244
- name: Overview
43-
href: overview-deploy.md
45+
href: deploy/overview-deploy.md
4446
- name: Connect Microsoft Sentinel to Microsoft Defender
45-
href: microsoft-sentinel-onboard.md
47+
href: deploy/microsoft-sentinel-onboard.md
48+
- name: Transition to unified SecOps by persona
49+
href: deploy/transition.md
4650
- name: Reduce security risk
4751
items:
4852
- name: Improve security posture and reduce risk"
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
title: include file
3+
description: include file
4+
ms.topic: include
5+
ms.date: 04/22/2025
6+
---
7+
8+
The minimal required permission for an analyst to view Microsoft Sentinel data is to delegate permissions for the Azure RBAC Sentinel Reader role. These permissions are also applied to the unified portal. Without these permissions, the Microsoft Sentinel navigation menu is not available on the unified portal, despite the analyst having access to the Microsoft Defender portal.
9+
10+
A best practice is to have all Microsoft Sentinel related resources in the same Azure resource group, then delegate Microsoft Sentinel role permissions (like the Sentinel Reader role) at the resource group level that contains the Microsoft Sentinel workspace. By doing this, the role assignment applies to all the resources that support Microsoft Sentinel.

unified-secops-platform/overview-deploy.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,9 +72,11 @@ For more information, see [Onboard Microsoft Sentinel](/azure/sentinel/quickstar
7272

7373
Provision your users based on the access plan you'd [prepared earlier](overview-plan.md#plan-roles-and-permissions). To comply with Zero Trust principles, we recommend that you use role-based access control (RBAC) to provide user access only to the resources that are allowed and relevant for each user, instead of providing access to the entire environment.
7474

75+
[!INCLUDE [mininum-access-requirements](/includes/mininum-access-requirements.md)]
76+
7577
For more information, see:
7678

77-
- [Activate Microsoft Defender XDR Unified role-based access control (RBAC)](/defender-xdr/activate-defender-rbac)
79+
- [Onboarding prerequisites](deploy/microsoft-sentinel-onboard.md#prerequisites)
7880
- [Assign Microsoft Entra ID roles to users](/entra/identity/role-based-access-control/manage-roles-portal)
7981
- [Grant a user access to Azure roles](/azure/role-based-access-control/quickstart-assign-role-user-portal)
8082

unified-secops-platform/overview-plan.md

Lines changed: 17 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -178,12 +178,19 @@ The following table describes portals for other workloads that can impact your s
178178

179179
## Plan roles and permissions
180180

181-
Use Microsoft Entra role based access control (RBAC) to create and assign roles within your security operations team to grant appropriate access to services included in Microsoft's unified SecOps platform.
181+
Microsoft's unified security operations (SecOps) platform unifies the following role-based access control (RBAC) models:
182182

183-
The Microsoft Defender XDR Unified role-based access control (RBAC) model provides a single permissions management experience that provides one central location for administrators to control user permissions across several security solutions. For more information, see [Microsoft Defender XDR Unified role-based access control (RBAC)](/defender-xdr/manage-rbac).
183+
- [Microsoft Entra ID RBAC](/entra/identity/role-based-access-control/custom-overview), used for delegating access to Defender access, like device groups
184+
- [Azure RBAC](/azure/role-based-access-control/), used by Microsoft Sentinel to delegate permissions
185+
- [Defender unified RBAC](/defender-xdr/manage-rbac), used to delegate permissions across Defender solutions
184186

185-
For the following services, use the different roles available, or create custom roles, to give you fine-grained control over what users can see and do. For more information, see:
187+
While permissions granted through Azure RBAC for Microsoft Sentinel are federated during runtime with Defender's unified RBAC, Azure RBAC and Defender RBAC are still managed separately.
188+
189+
Defender's unified RBAC isn't required to onboard your workspace to the Defender portal, and Microsoft Sentinel permissions continue to work as expected in the Defender portal even without unified RBAC. However, using unified RBAC does simplify the delegation of permissions across Defender solutions. For more information, see [Activate Microsoft Defender XDR Unified role-based access control (RBAC)](/defender-xdr/activate-defender-rbac).
186190

191+
[!INCLUDE [mininum-access-requirements](includes/mininum-access-requirements.md)]
192+
193+
For the following services, use the different roles available, or create custom roles, to give you fine-grained control over what users can see and do. For more information, see:
187194

188195
| Security service | Link to role requirements |
189196
| ------------------------ | ------------------------------------------- |
@@ -201,6 +208,13 @@ For the following services, use the different roles available, or create custom
201208
| Microsoft Defender for Cloud | [User roles and permissions](/azure/defender-for-cloud/permissions) |
202209
| Microsoft Purview Insider Risk Management | [Enable permissions for insider risk management](/purview/insider-risk-management-configure?tabs=purview-portal#step-1-required-enable-permissions-for-insider-risk-management) |
203210

211+
For more information, see:
212+
213+
- [Plan roles and permissions for Microsoft Sentinel](/azure/sentinel/roles)
214+
- [Azure built-in roles](/azure/role-based-access-control/built-in-roles)
215+
- [Microsoft Sentinel roles](/azure/role-based-access-control/built-in-roles#security)
216+
- [Onboarding prerequisites](deploy/microsoft-sentinel-onboard.md#prerequisites)
217+
204218
## Plan Zero Trust activities
205219

206220
Microsoft's unified SecOps platform is part of [Microsoft's Zero Trust security model](zero-trust.md), which includes the following principles:
Lines changed: 114 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,114 @@
1+
---
2+
title: Transitioning to Microsoft's unified SecOps platform
3+
description: Learn about the different security roles involved in transitioning to Microsoft's unified SecOps platform from Microsoft Sentinel in the Azure portal.
4+
ms.service: unified-secops-platform
5+
ms.author: bagol
6+
author: batamig
7+
ms.date: 11/22/2024
8+
ms.collection:
9+
- M365-security-compliance
10+
- tier1
11+
- usx-security
12+
ms.topic: conceptual
13+
# customer intent: As a security professional, I want to understand the benefits and process of transitioning to Microsoft's unified SecOps platform so I can effectively plan my organization's migration from the standalone Microsoft Sentinel portal before its decommissioning.
14+
---
15+
16+
# Transition to Microsoft's unified SecOps platform
17+
18+
Microsoft's unified security operations (SecOps) platform provides a single platform for end-to-end security operations (SecOps). This platform combines services like [Microsoft Defender XDR](/defender-xdr/microsoft-365-defender), [Microsoft Sentinel](/azure/sentinel/overview), [Microsoft Security Exposure Management](/security-exposure-management/microsoft-security-exposure-management), and [Microsoft Security Copilot](/copilot/security/microsoft-security-copilot) within the Microsoft Defender portal. The unified SecOps platform provides multi-tenant and multi-workspace capabilities, a single incident queue, alert correlation, and automatic attack disruption to ensure streamlined workflows and enhances security operations efficiency.
19+
20+
Starting in May 2026, customers using the Microsoft Sentinel experience in the Azure portal will be redirected to the unified SecOps platform in the Microsoft Defender portal. Microsoft Sentinel in the Azure portal will be decommissioned on July 1, 2026. To prepare for this change, we recommend that customers that are still using the Microsoft Sentinel experience in the Azure portal proactively transition to Microsoft's unified SecOps platform in the Microsoft Defender portal.
21+
22+
For more information, see the relevant documentation for each feature and [Capability differences between portals](/azure/sentinel/microsoft-sentinel-defender-portal##capability-differences-between-portals).
23+
24+
## Benefits of transitioning to the unified SecOps platform
25+
26+
Transitioning to the unified SecOps platform offers the following benefits, and more:
27+
28+
- **Streamlined Operations**: Manage all security incidents, alerts, and investigations from a single, unified interface.
29+
- **Enhanced Threat Detection**: Leverage advanced AI and machine learning for faster and more accurate threat detection and response. Benefit from an improved signal-to-noise ratio and enhanced alert correlation, ensuring that critical threats are identified and addressed promptly.
30+
- **New Features**: Access robust tools like Case Management for organizing and managing security incidents.
31+
- **Embedded Copilot Experience**: For customers using Copilot, enjoy a seamless experience for incident summaries and reports, guided investigation, auto-generated Microsoft Teams messages, code analysis, and more.
32+
- **Unified hunting, incidents, and investigation**: For customers using Defender XDR, benefit from a comprehensive view for more efficient threat detection and response.
33+
- **Enhanced visibility and reduced risk exposure**: Analyze attack paths to see how a cyber attacker could exploit vulnerabilities to move laterally across exposed assets in your environment. Use guided recommendations to reduce exposure and prioritize actions based on each exposure's potential impact.
34+
- **Tailored post-incident recommendations**: Prevent similar or repeat cyberattacks with tailored post incident recommendations tied to Microsoft Security Exposure Management initiatives.
35+
36+
For more information, see [Microsoft Sentinel in the Microsoft Defender portal](/azure/sentinel/microsoft-sentinel-defender-portal).
37+
38+
## Transition to unified SecOps as a security architect
39+
40+
The following content is relevant for security architects on a SecOps team that's transitioning from Microsoft Sentinel in the Azure portal to unified SecOps in the Defender portal:
41+
42+
- **Access**:
43+
44+
[!INCLUDE [mininum-access-requirements](../includes/mininum-access-requirements.md)]
45+
46+
- [Plan roles and permissions](../overview-plan.md#plan-roles-and-permissions), including role-based access control (RBAC)
47+
- [Configure roles and permissions](overview-deploy.md#configure-roles-and-permissions)
48+
49+
- **Multiple workspaces and tenants**:
50+
51+
- [Multiple Microsoft Sentinel workspaces in the Defender portal](/azure/sentinel/prepare-multiple-workspaces)
52+
- [Extend Microsoft Sentinel across workspaces and tenants](/azure/sentinel/extend-sentinel-across-workspaces-tenants)
53+
- [Microsoft Defender multitenant management](../mto-overview.md)
54+
55+
- **Log tiering and retention**:
56+
57+
Microsoft Sentinel classifies security data as primary security data and secondary security data. For primary security data, which you want to monitor closely, we recommend the analytic tier. For secondary security data, we recommend auxiliary. Both types of data are accessible for queries in the **Advanced hunting** page in the Defender portal.
58+
59+
- [When to use auxiliary logs in Microsoft Sentinel](/azure/sentinel/basic-logs-use-cases)
60+
- [Log retention plans in Microsoft Sentinel](/azure/sentinel/log-plans)
61+
- [Set up a table with the Auxiliary plan for low-cost data ingestion and retention in your Log Analytics workspace](/azure/azure-monitor/logs/create-custom-table-auxiliary)
62+
- [Microsoft Sentinel in the Defender portal: threat management](/azure/sentinel/microsoft-sentinel-defender-portal#threat-management)
63+
64+
## Transition to unified SecOps as a security engineer
65+
66+
The following content is relevant for security engineers on a SecOps team that's transitioning from Microsoft Sentinel in the Azure portal to unified SecOps in the Defender portal:
67+
68+
- **Data collection**:
69+
70+
- [Microsoft Sentinel data connectors](/azure/sentinel/connect-data-sources?tabs=defender-portal)
71+
- Experience in the Defender portal:
72+
- [Visibility of connectors used by the unified security operations platform](/azure/sentinel/microsoft-sentinel-defender-portal)
73+
- [Defender for Cloud](/azure/sentinel/microsoft-sentinel-defender-portal) <!--add bookmarks for data connector specifics, also add content there re mdc and dlp items. that's on ed>
74+
- [DLP data](/azure/sentinel/microsoft-sentinel-defender-portal) <!--add bookmarks for data connector specifics, also add content there re mdc and dlp items. that's on ed>
75+
76+
- **Automation**: [Automation in the Microsoft Defender portal](/azure/sentinel/automation/automation#automation-in-the-microsoft-defender-portal)
77+
78+
- **Ecosystem**: Distribute content across workspaces using one of the following methods:
79+
80+
- [Deploy content as code from your repository](/azure/sentinel/ci-cd)
81+
- [Microsoft Defender multitenant management](../mto-overview.md)
82+
83+
- **SOC optimization**: [Optimize your security operations](/azure/sentinel/soc-optimization/soc-optimization-access?toc=%2Funified-secops-platform%2Ftoc.json&bc=%2Funified-secops-platform%2Fbreadcrumb%2Ftoc.json&tabs=defender-portal)
84+
85+
- **APIs**
86+
87+
- [Microsoft Sentinel in the Defender portal: Capability differences between portals](/azure/sentinel/microsoft-sentinel-defender-portal) <!--add bookmark for API related information-->
88+
- [Microsoft Sentinel REST API reference](/rest/api/securityinsights/)
89+
90+
## Transition to unified SecOps as a security analyst or manager
91+
92+
The following content is relevant for security analysts or security managers on a SecOps team that's transitioning from Microsoft Sentinel in the Azure portal to unified SecOps in the Defender portal:
93+
94+
- **Incident and alert management**
95+
96+
- **Attack disruption**
97+
98+
- **Advanced hunting**
99+
100+
- **Entities and user and entity behavior analytics (UEBA)**
101+
102+
- **Case management**
103+
104+
- **Security Copilot integraton**
105+
106+
- **Threat intelligence**
107+
108+
- **Visualization and reporting with workbooks**
109+
110+
## Related content
111+
112+
- **Webinar**: [Transition to the Unified SOC Platform: Deep Dive and Interactive Q&A for SOC Professionals](https://www.youtube.com/watch?v=WIM6fbJDkK4)
113+
- **Blog**: [Technical FAQs for the unified SOC platform](https://techcommunity.microsoft.com/blog/microsoftsentinelblog/unified-security-operations-platform---technical-faq/4189136)
114+
- **Community**: [Microsoft Community Hub](https://techcommunity.microsoft.com/blog/microsoftsentinelblog/frequently-asked-questions-about-the-unified-security-operations-platform/4212048)

0 commit comments

Comments
 (0)