Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Managed security service providers (MSSPs) often manage detections, workbooks, automation, and access across multiple customer tenants.
When transitioning existing Microsoft Sentinel deployments to Integrated Security Operations Center (ISOC) in Microsoft Defender, MSSPs must update their content deployment processes and validate access to ensure that security operations continue to function across customer environments.
This article describes the operational considerations and validation steps for transitioning MSSP-managed deployments.
Note
ISOC is in preview. Capabilities and availability might change during the preview period.
Prerequisites
Before transitioning MSSP-managed deployments:
- Ensure that each customer tenant is eligible for ISOC.
- Identify existing Microsoft Sentinel analytics rules, workbooks, automation, and other content managed by the MSSP.
- Identify the content distribution profiles, CI/CD pipelines, and deployment definitions used across customer tenants.
- Verify that the MSSP has the required delegated access and permissions in each customer tenant.
- Identify any content managed jointly by the MSSP and the customer.
- If you use Tenant Governance (GDAP), ensure that you've adopted Unified RBAC.
Update content deployment processes
Review and update the processes used to deploy and manage content across customer tenants.
Update content distribution profiles
Update content distribution profiles to deploy content that uses Microsoft Defender Advanced Hunting instead of Microsoft Sentinel workspace-based content.
Ensure that the updated profiles deploy:
- Custom detections instead of Microsoft Sentinel analytics rules.
- Workbooks that use Advanced Hunting data sources.
- Updated automation and Logic App playbooks.
For more information, see:
- Convert analytics rules to custom detections
- Update workbooks to use Advanced Hunting data
- Update Logic App playbook automation
Update CI/CD pipelines and deployment definitions
If you use CI/CD pipelines or infrastructure as code to deploy content across customer tenants, update the repositories, deployment pipelines, and automation processes.
Ensure that deployment definitions use the converted detections and Advanced Hunting-based content model consistently across customer tenants.
Validate that the updated deployment processes deploy the expected content before reducing ingestion into Microsoft Sentinel.
Validate delegated access and permissions
MSSPs must have the required delegated access and permissions in each customer tenant to manage and validate the transitioned content.
Before beginning migration activities:
Review the delegated access configured for each customer tenant.
Note
If you use Tenant Governance (GDAP) and assign permissions through ARM, migrate to Unified RBAC.
Verify that the MSSP has the required permissions for the Defender workloads and data used by the transitioned content.
Review user and group access to identify any permissions that must be updated.
Use SOC Optimization recommendations to identify potential access gaps.
Resolve identified access gaps and confirm that analysts can access the required data after the transition.
For more information about updating permissions, see Update permissions and roles with Unified RBAC.
Important
Unified RBAC is mandatory when you enable ISOC. MDE device groups aren't currently supported with Tenant Governance (GDAP).
Define shared content ownership
In some customer environments, both the MSSP and the customer manage detections, workbooks, or automation.
Before transitioning these environments, establish ownership and change-control processes to avoid conflicting updates.
Review the following considerations:
- Content ownership: Identify whether the MSSP or customer is responsible for managing each detection, workbook, and automation resource.
- Change control: Establish how changes to shared content are reviewed and applied.
- Deployment responsibilities: Determine who is responsible for updating and validating content deployments.
- Ongoing management: Confirm how the MSSP and customer coordinate changes after the transition.
Validate MSSP-managed deployments
Before reducing data ingestion into Microsoft Sentinel for a customer tenant, verify that the transitioned content and access configurations work as expected.
Complete the following validation steps for each customer tenant:
Validate content distribution profiles.
Confirm that content distribution profiles deploy the converted custom detections, Advanced Hunting-based workbooks, and updated automation.
Validate CI/CD pipelines and deployment definitions.
Confirm that repositories, pipelines, and deployment definitions have been updated to deploy content that uses the Advanced Hunting data model.
Validate delegated access and permissions.
Verify that the MSSP has the required delegated access and Defender workload permissions in the customer tenant.
Validate shared content ownership.
Confirm that ownership and change-control responsibilities are defined for content managed jointly by the MSSP and customer.
Validate user and group access.
Confirm that access reviews are complete, identified gaps are resolved, and analysts retain access to the data required for security operations.
Important
Complete the applicable content migration and validation steps before reducing ingestion into Microsoft Sentinel. Ensure that all resources dependent on a table have been updated to use the corresponding Advanced Hunting data and validated.
Next steps
After validating the MSSP-managed deployment, review the remaining dependencies before reducing ingestion into Microsoft Sentinel.
For more information, see: