Additional References: π‘[Track changes to system files and registry keys](https://learn.microsoft.com/azure/defender-for-cloud/file-integrity-monitoring-overview) π‘[Connect Microsoft Defender for Cloud alerts to Microsoft Sentinel](https://learn.microsoft.com/azure/sentinel/connect-defender-for-cloud) π‘[Deploying and Managing Microsoft Defender for Cloud as Code](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/deploying-and-managing-microsoft-defender-for-cloud-as-code/ba-p/3649653) π‘[Collect data in custom log formats to Microsoft Sentinel](https://learn.microsoft.com/azure/sentinel/connect-custom-logs?tabs=DCG) π‘[Azure Monitor Agent overview - Azure Monitor](https://learn.microsoft.com/azure/azure-monitor/agents/agents-overview) π‘[Use entity behavior analytics to detect advanced threats](https://learn.microsoft.com/azure/sentinel/enable-entity-behavior-analytics) |\r\n| | 2.4 Remote Access | Microsft Entra ID Microsft Entra ID Conditional Access (CA) Microsoft Intune Microsoft Defender for Endpoint (MDE) | π [Entra ID](https://portal.azure.us/#view/Microsoft_AAD_Devices/DevicesMenuBlade/~/Devices/menuId~/null) π [Microsoft Intune](https://endpoint.microsoft.us/#view/Microsoft_Intune_Enrollment/ReportingMenu/~/deviceCompliance) π [M365 Defender Portal](https://security.microsoft.us/machines?category=endpoints) | π‘[Require compliant, hybrid joined devices, or MFA - Microsoft Entra](https://learn.microsoft.com/azure/active-directory/conditional-access/howto-conditional-access-policy-compliant-device) π‘[Conditional Access APIs and PowerShell - Microsoft Entra](https://learn.microsoft.com/azure/active-directory/conditional-access/howto-conditional-access-apis) π‘[Device compliance policies in Microsoft Intune](https://learn.microsoft.com/mem/intune/protect/device-compliance-get-started) π‘[Configure compliance policies with actions for noncompliance in Microsoft Intune](https://learn.microsoft.com/mem/intune/protect/actions-for-noncompliance) π‘[Configure Microsoft Defender for Endpoint in Intune](https://learn.microsoft.com/mem/intune/protect/advanced-threat-protection-configure) π‘[Configure Conditional Access in Microsoft Defender for Endpoint](https://learn.microsoft.com/microsoft-365/security/defender-endpoint/configure-conditional-access?view=o365-worldwide) π‘[Enhance security with the principle of least privilege](https://learn.microsoft.com/azure/active-directory/develop/secure-least-privileged-access) π‘[Best practices for Azure AD roles](https://learn.microsoft.com/azure/active-directory/roles/best-practices) π‘[Least privileged roles by task in Azure Active Directory](https://learn.microsoft.com/azure/active-directory/roles/delegate-by-task) |\r\n| | 2.5 Partially & Fully Automated Asset, Vulnerability and Patch | Microsoft Intune Microsoft Endpoint Configuration Manager (MECM) Mircosoft Defender for Endpoint (MDE) Threat & Vulnerability Management (TVM) Azure Arc-enabled Servers Azure Automation | π [Entra ID](https://portal.azure.us/#view/Microsoft_AAD_Devices/DevicesMenuBlade/~/Devices/menuId~/null) π [Microsoft Intune](https://endpoint.microsoft.us/#view/Microsoft_Intune_Enrollment/ReportingMenu/~/deviceCompliance) π [M365 Defender Portal](https://security.microsoft.us/machines?category=endpoints) π [Azure Arc](https://portal.azure.us/#view/Microsoft_Azure_HybridCompute/AzureArcCenterBlade/~/overview) | π‘ [What is Windows Update for Business?](https://learn.microsoft.com/windows/deployment/update/waas-manage-updates-wufb) π‘ [Microsoft Configuration Manager MECEM](https://learn.microsoft.com/mem/configmgr/core/understand/introduction) π‘ [Update rings for Windows 10 and later policy in Intune](https://learn.microsoft.com/mem/intune/protect/windows-10-update-rings?source=recommendations) π‘ [Manage Windows 10 and Windows 11 software updates in Intune](https://learn.microsoft.com/mem/intune/protect/windows-update-for-business-configure) π‘ [Deploy software updates with Configuration Manager](https://learn.microsoft.com/mem/configmgr/sum/deploy-use/deploy-software-updates) π‘ [Use Intune to remediate vulnerabilities identified by Microsoft Defender for Endpoint](https://learn.microsoft.com/mem/intune/protect/atp-manage-vulnerabilities) π‘ [Remediate vulnerabilities (Defender for Endpoint)](https://learn.microsoft.com/microsoft-365/security/defender-vulnerability-management/tvm-remediation?view=o365-worldwide) π‘ [Choose how to deliver updates for the Microsoft 365 Apps](https://learn.microsoft.com/deployoffice/fieldnotes/choose-how-to-deliver-updates) π‘ [Windows Release Health](https://learn.microsoft.com/windows/release-health/) π‘ [Manage updates and patches for your VMs](https://learn.microsoft.com/azure/automation/update-management/manage-updates-for-vm) π‘ [Automate your patching using Azure Arc and Azure Automation](https://techcommunity.microsoft.com/t5/manufacturing/automate-your-patching-using-azure-arc-and-azure-automation/ba-p/3214141) |\r\n| | 2.6 Unified Endpoint Management (UEM) & Mobile Device Management (MDM) | Microsoft Intune Azure Arc-enabled Servers Azure Autiomation | π [Entra ID](https://portal.azure.us/#view/Microsoft_AAD_Devices/DevicesMenuBlade/~/Devices/menuId~/null) π [Microsoft Intune](https://endpoint.microsoft.us/#view/Microsoft_Intune_Enrollment/ReportingMenu/~/deviceCompliance) π [M365 Defender Portal](https://security.microsoft.us/machines?category=endpoints) π [Azure Arc](https://portal.azure.us/#view/Microsoft_Azure_HybridCompute/AzureArcCenterBlade/~/overview) | π‘[What is Microsoft Intune](https://learn.microsoft.com/mem/intune/fundamentals/what-is-intune) π‘[Manage your devices and control device features in Microsoft Intune](https://learn.microsoft.com/mem/intune/fundamentals/manage-devices) π‘[Zero Trust with Microsoft Intune](https://learn.microsoft.com/mem/intune/fundamentals/zero-trust-with-microsoft-intune) π‘[Supported operating systems and browsers in Intune](https://learn.microsoft.com/mem/intune/fundamentals/supported-devices-browsers) π‘[Enrollment guide: Microsoft Intune enrollment](https://learn.microsoft.com/mem/intune/fundamentals/deployment-guide-enrollment) π‘[Manage iOS/iPadOS software update policies in Intune](https://learn.microsoft.com/mem/intune/protect/software-updates-ios) π‘[Manage macOS software update policies in Intune](https://learn.microsoft.com/mem/intune/protect/software-updates-macos) π‘[Microsoft Intune How-To Guides](https://learn.microsoft.com/mem/intune/#how-to-guides) π‘[What is Azure Arc-enabled servers?](https://learn.microsoft.com/azure/azure-arc/servers/overview) π‘[Automate your patching using Azure Arc and Azure Automation](https://techcommunity.microsoft.com/t5/manufacturing/automate-your-patching-using-azure-arc-and-azure-automation/ba-p/3214141) |\r\n| | 2.7 Endpoint & Extended Detection & Response (EDR & XDR) | Microsoft 365 Defender Microsoft Defender for Endpoint (MDE) Microsoft Defednder for Identity (MDI) Microsoft Defender for Office 365 (MDO) Microsoft Defender for Cloud Apps (MDA) Microsoft Defender for Cloud (MDfC) Microsoft Sentinel | π [Entra ID](https://portal.azure.us/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview) π [Sentinel](https://portal.azure.us/#blade/HubsExtension/BrowseResource/resourceType/microsoft.securityinsightsarg%2Fsentinel) π [Microsoft Defender for Cloud: Recommendations](https://portal.azure.us/#blade/Microsoft_Azure_Security/SecurityMenuBlade/5) π [M365 Defender Portal](https://security.microsoft.us) | π‘[What is Microsoft Defender for Endpoint?](https://learn.microsoft.com/microsoft-365/security/defender-endpoint/microsoft-defender-endpoint?view=o365-worldwide) π‘[Zero Trust with Microsoft Defender for Endpoint](https://learn.microsoft.com/microsoft-365/security/defender-endpoint/zero-trust-with-microsoft-defender-endpoint?view=o365-worldwide) π‘[What is Microsoft 365 Defender?](https://learn.microsoft.com/microsoft-365/security/defender/microsoft-365-defender?view=o365-worldwide) π‘[Zero Trust with Microsoft 365 Defender](https://learn.microsoft.com/microsoft-365/security/defender/zero-trust-with-microsoft-365-defender?view=o365-worldwide) π‘[Overview of endpoint detection and response (EDR) with Microsoft 365 Defender](https://learn.microsoft.com/microsoft-365/security/defender-endpoint/overview-endpoint-detection-response?view=o365-worldwide) π‘[Implement Microsoft Sentinel and Microsoft 365 Defender for Zero Trust](https://learn.microsoft.com/security/operations/siem-xdr-overview) π‘[Manage endpoint detection and response (EDR) policy for endpoint security in Intune](https://learn.microsoft.com/mem/intune/protect/endpoint-security-edr-policy) π‘[Set up your XDR tools](https://learn.microsoft.com/security/operations/setup-xdr-tools) π‘[Architect your Microsoft Sentinel workspace](https://learn.microsoft.com/security/operations/siem-workspace) π‘[Ingest data sources and configure incident detection in Sentinel](https://learn.microsoft.com/security/operations/ingest-data-sources) π‘[Respond to an incident using Microsoft Sentinel and Microsoft 365 Defender](https://learn.microsoft.com/security/operations/respond-incident) |\r\n| Application & Workload 3.x | | | | |\r\n| | 3.1 Application Inventory | Entra ID Microsoft Defender for Cloud Apps (MDA) Microsoft Defender for Endpoint (MDE) Microsoft Intune | π [Entra ID Applications - Useage & Insights](https://portal.azure.us/?feature.msaljs=true#view/Microsoft_AAD_IAM/EnterpriseApplicationsInsightsMenuBlade/~/ApplicationActivity) π [Application Security Groups](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Network%2FapplicationSecurityGroups) π [Microsoft Defender for Cloud Apps - Discovery](https://security.microsoft.us/cloudapps/discovery) π [Virtual Network Gateways](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Network%2FvirtualNetworkGateways) π [Microsoft Defender for Cloud: Recommendations](https://portal.azure.us/#blade/Microsoft_Azure_Security/SecurityMenuBlade/5) | π‘ [Cloud Discovery Setup](https://learn.microsoft.com/defender-cloud-apps/set-up-cloud-discovery) π‘ [Deploy Intune Softare inventory & Security Policies](https://learn.microsoft.com/answers/questions/67892/can-we-use-intune-to-inventory-software-on-devices) π‘ [Configure Blocking Unwanted or Unapproved Applications](https://learn.microsoft.com/microsoft-365/security/defender-endpoint/detect-block-potentially-unwanted-apps-microsoft-defender-antivirus?view=o365-worldwide) π‘ [Generating Software Bill of Materials (SBOM)](https://devblogs.microsoft.com/engineering-at-microsoft/generating-software-bills-of-materials-sboms-with-spdx-at-microsoft/) π‘ [Microsoft Open Source Software Bill of Materials SBOM](https://devblogs.microsoft.com/engineering-at-microsoft/microsoft-open-sources-software-bill-of-materials-sbom-generation-tool/) π‘ [Github Software Bill of Materials - SBOM-Tool](https://github.com/microsoft/sbom-tool) π‘ [Active Directory Federation Services Health](https://learn.microsoft.com/azure/active-directory/hybrid/connect/how-to-connect-health-adfs) π‘ [Azure Active Directory Application Audit](https://github.com/jsa2/AADAppAudit#azure-ad-application-analytics-solution) π‘ [Azure Active Directory Application Proxy](https://learn.microsoft.com/azure/active-directory/app-proxy/what-is-application-proxy) π‘ [Using Microsoft Defender for Cloud Asset Inventory](https://learn.microsoft.com/azure/defender-for-cloud/asset-inventory) π‘ [Working with Discovered Apps](https://learn.microsoft.com/defender-cloud-apps/discovered-apps) π‘ [Software Inventory](https://learn.microsoft.com/microsoft-365/security/defender-vulnerability-management/tvm-software-inventory?view=o365-worldwide) |\r\n| | 3.2 Secure Software Development & Integration | Azure Policy Microsoft Defender for Cloud (MDfC) Microsoft Defender for Endpoint (MDE) | π [Azure DevOps](https://portal.azure.us/#view/AzureTfsExtension/OrganizationsTemplateBlade) π [Azure Dev Test Center](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.DevTestLab%2Flabs) π [Azure DevTest Lab](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.DevTestLab%2Flabs) π [Intune App Security](https://endpoint.microsoft.us) π [Microsoft Defender for Cloud: Recommendations](https://portal.azure.us/#blade/Microsoft_Azure_Security/SecurityMenuBlade/5) π [M365 Defender Portal](https://security.microsoft.us/) | |\r\n| | 3.3 Software Risk Management | Microsoft Defender for Cloud Apps (MDA) Mircosoft Defender for Endpoint (MDE) Threat & Vulnerability Management (TVM) Microsoft Intune | π [Azure Enterprise Apps Portal](https://portal.azure.us/#view/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/~/AppAppsPreview) π [Intune Application Security](https://endpoint.microsoft.us/#view/Microsoft_Intune_DeviceSettings/AppsMenu/~/overview) π [Microsoft Defender for Cloud: Recommendations](https://portal.azure.us/#blade/Microsoft_Azure_Security/SecurityMenuBlade/5) π [M365 Defender Portal](https://security.microsoft.us/) | π‘ [Manage and Secure Apps In Intune](https://learn.microsoft.com/mem/intune/fundamentals/manage-apps) π‘ [App Protection Policies in Intune](https://learn.microsoft.com/mem/intune/apps/app-protection-policy) π‘ [Microsoft Container Registry](https://mcr.microsoft.com/) π‘ [GitHub Actaion For Vulnerability Scanning](https://github.com/marketplace/actions/anchore-container-scan) π‘ [Code Scanning with CodeQL](https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql) π‘ [Keeping your supply chain secure with Dependabot](https://docs.github.com/en/code-security/dependabot) π‘ [Secure Supply Chain Consumption Framework](https://www.microsoft.com/securityengineering/opensource/osssscframeworkguide) π‘ [Generating Software Bill of Materials (SBOM)](https://devblogs.microsoft.com/engineering-at-microsoft/generating-software-bills-of-materials-sboms-with-spdx-at-microsoft/) π‘ [Microsoft Open Source Software Bill of Materials SBOM](https://devblogs.microsoft.com/engineering-at-microsoft/microsoft-open-sources-software-bill-of-materials-sbom-generation-tool/) π‘ [Github Software Bill of Materials - SBOM-Tool](https://github.com/microsoft/sbom-tool) |\r\n| | 3.4 Resource Authorization & Integration | Entra ID Conditional Access (CA) Entra ID Application Proxy Azure Policy Entra ID Privilleged Identity Management (PIM) Microsoft 365 Defender Microsoft Intune Microsoft Defender for Cloud (MDfC) | π [Azure Identity Governance](https://portal.azure.us/#blade/Microsoft_AAD_ERM/DashboardBlade) π [Entra ID](https://portal.azure.us/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview) π [Azure Application Proxy](https://portal.azure.us/#view/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/~/AppProxy) π [Managed Service Identity](https://portal.azure.us/#blade/Microsoft_AAD_IAM/ManagedAppMenuBlade/Overview/objectId/6f3afa5d-4b81-4f10-8806-fb75689672da/appId/c75517e9-05c9-49e9-9990-94f68b04ffc4) π [Intune Application Security](https://endpoint.microsoft.us/#view/Microsoft_Intune_DeviceSettings/AppsMenu/~/overview) π [Microsoft Defender for Cloud: Recommendations](https://portal.azure.us/#blade/Microsoft_Azure_Security/SecurityMenuBlade/5) π [M365 Defender Portal](https://security.microsoft.us/) | π‘ [Deploy Microsoft Defender for Cloud - Enterprise Cloud Application Protection](https://learn.microsoft.com/azure/defender-for-cloud/defender-for-cloud-introduction) π‘ [Configure Microsoft Cloud Identity for Enterprise Architects](https://www.microsoft.com/download/details.aspx?id=54431) π‘ [Deploying Application & Authorization Azure App Services](https://learn.microsoft.com/azure/app-service/overview-authentication-authorization) π‘ [How to create and deploy a custome Authorization Manager](https://learn.microsoft.com/dotnet/framework/wcf/extending/how-to-create-a-custom-authorization-manager-for-a-service) π‘ [Configure with Entra Identity Platform](https://learn.microsoft.com/azure/active-directory/develop/v2-oauth2-auth-code-flow) π‘ [How-to Manage Apps Remove User Access with Entra](https://learn.microsoft.com/azure/active-directory/manage-apps/methods-for-removing-user-access) π‘ [Setup Protecting Apps w. Entra Conditional Access](https://learn.microsoft.com/azure/active-directory/conditional-access/concept-conditional-access-cloud-apps) π‘ [Role Based Access Control Configuration with Intune](https://learn.microsoft.com/mem/intune/fundamentals/role-based-access-control) |\r\n| | 3.5 Continuous Monitoring and Ongoing Authorizations | Entra ID - Conditional Access (CA) Microsoft Defender for Cloud Apps (MDA) Microsoft Senitnel Playbooks Entra ID - Privileged Identity Management (PIM) | π [Microsoft Defender for Cloud: Recommendations](https://portal.azure.us/#blade/Microsoft_Azure_Security/SecurityMenuBlade/5) π [Application Insights](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/microsoft.insights%2Fcomponents) π [Entra ID](https://portal.azure.us/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview) π [Application Security Groups Portal](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Network%2FapplicationSecurityGroups) π [Microsoft Sentinel](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/microsoft.securityinsightsarg%2Fsentinel) | π‘ [How-to-Build a Successful App Security Program](https://www.microsoft.com/security/blog/2021/03/29/how-to-build-a-successful-application-security-program/) π‘ [Setting up Hybrid Continuous Monitoring with Sentinel](https://learn.microsoft.com/azure/architecture/hybrid/hybrid-security-monitoring) π‘ [Deploy Adaptive Appliation Conrols Microsoft Defender for Cloud](https://learn.microsoft.com/azure/defender-for-cloud/adaptive-application-controls) π‘ [Configure Azure Security Management & Monitoring](https://learn.microsoft.com/azure/security/fundamentals/management-monitoring-overview) π‘ [Leverage Security Baselines for M365 Apps Enterprise](https://learn.microsoft.com/deployoffice/security/security-baseline) π‘ [Utilize Application Control for Windows](https://learn.microsoft.com/windows/security/application-security/application-control/windows-defender-application-control/wdac) |\r\n| Data 4.x | | | | |\r\n| | 4.1 Data Catalog Risk Alignment | Purview Data Catalog Purview Data Map Microsoft Sentinel | π [Microsoft Purview Portal](https://compliance.microsoft.us) π [Microsoft Sentinel](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/microsoft.securityinsightsarg%2Fsentinel) π [M365 Defender Portal](https://security.microsoft.us/) π [Azure Data Classification Service](https://portal.azure.us/#view/Microsoft_AAD_IAM/ManagedAppMenuBlade/~/Overview/objectId/30ea52ed-e5a7-4e51-a4ea-6c3b96a8be36/appId/7c99d979-3b9c-4342-97dd-3239678fb300) | π‘ [Create a Azrure Data Catalog](https://learn.microsoft.com/azure/data-catalog/data-catalog-get-started) π‘ [Use the Service Catalog](https://learn.microsoft.com/system-center/scsm/service-catalog?view=sc-sm-2022) π‘ [Azure Data Catalog FAQ](https://learn.microsoft.com/azure/data-catalog/data-catalog-frequently-asked-questions) π‘ [Establishing Sensitivity Labels](https://learn.microsoft.com/microsoft-365/compliance/sensitivity-labels?view=o365-worldwide) π‘ [Create and Publish Sensitivity Labels](https://learn.microsoft.com/microsoft-365/compliance/create-sensitivity-labels?view=o365-worldwide)Β π‘ [Get Started with Trainable Classifiers](https://learn.microsoft.com/microsoft-365/compliance/classifier-get-started-with?view=o365-worldwide)Β π‘ [Set up Azure Rights Management](https://learn.microsoft.com/azure/information-protection/what-is-azure-rms) π‘ [Deploy Azure Information Protection](https://learn.microsoft.com/azure/information-protection/aip-classification-and-protection) π‘ [Sentinel Data Connectors](https://learn.microsoft.com/azure/sentinel/connect-data-sources) π‘ [Discover Data & Apply Sensitivity Labels Automatically](https://learn.microsoft.com/microsoft-365/compliance/apply-sensitivity-label-automatically?view=o365-worldwide) |\r\n| | 4.2 DoD Enterprise Data Governance | Purview Data Governance Purview Data Estate Insights Microsoft Defender for Cloud (MDfC) Microsoft Sentinel | π [Microsoft Purview Portal](https://compliance.microsoft.us) π [Microsoft Sentinel](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/microsoft.securityinsightsarg%2Fsentinel) π [M365 Defender Portal](https://security.microsoft.us/machines?category=endpoints) π [Microsoft Defender for Cloud: Recommendations](https://portal.azure.us/#blade/Microsoft_Azure_Security/SecurityMenuBlade/5) | π‘ [Implement Microsoft Purview - IRM & Compliance - DoD Deployments](https://learn.microsoft.com/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/plan-for-microsoft-purview-dod-deployments) π‘ [Implement a Data Governance Maturity Model Framework](https://learn.microsoft.com/azure/cloud-adoption-framework/scenarios/cloud-scale-analytics/govern) π‘ [Deploy Azure Data Governance](https://learn.microsoft.com/azure/cloud-adoption-framework/scenarios/cloud-scale-analytics/govern) π‘ [Leverage Microsoft Defender for For Cloud Goverance Rules](https://learn.microsoft.com/azure/defender-for-cloud/governance-rules) π‘ [Implement Purview Data Governance](https://learn.microsoft.com/purview/?view=o365-worldwide) π‘ [Purview Data Lineage Machine Learning](https://learn.microsoft.com/samples/microsoft/purview-machine-learning-lineage-solution-accelerator/purview-machine-learning-lineage-solution-accelerator/)Β π‘ [Get Started with Trainable Classifiers](https://learn.microsoft.com/microsoft-365/compliance/classifier-get-started-with?view=o365-worldwide)Β π‘ [Azure Collaboration Governance](https://learn.microsoft.com/microsoft-365/solutions/collaboration-governance-overview?view=o365-worldwide) π‘ [Deploy Azure Information Protection](https://learn.microsoft.com/azure/information-protection/aip-classification-and-protection) π‘ [Configure Sentinel Data Connectors](https://learn.microsoft.com/azure/sentinel/connect-data-sources) π‘ [Monitor Your SQL Deployments](https://learn.microsoft.com/azure/azure-sql/database/sql-insights-overview?view=azuresql) π‘ [Apply Sensitivity Labels Automatically](https://learn.microsoft.com/microsoft-365/compliance/apply-sensitivity-label-automatically?view=o365-worldwide) |\r\n| | 4.3 Data Labeling and Tagging | Purview Information Protection | π [Microsoft Purview Portal](https://compliance.microsoft.us) π [Microsoft Sentinel](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/microsoft.securityinsightsarg%2Fsentinel) π [M365 Defender Portal](https://security.microsoft.us/) π [Microsoft Defender for Cloud: Recommendations](https://portal.azure.us/#blade/Microsoft_Azure_Security/SecurityMenuBlade/5) | π‘ [Create Sensitivity Labels](https://learn.microsoft.com/microsoft-365/compliance/sensitivity-labels?view=o365-worldwide) π‘ [Create and Publish Sensitivity Labels](https://learn.microsoft.com/microsoft-365/compliance/create-sensitivity-labels?view=o365-worldwide)Β π‘ [Deploy with Trainable Classifiers](https://learn.microsoft.com/microsoft-365/compliance/classifier-get-started-with?view=o365-worldwide)Β π‘ [Utilize Rights Management](https://learn.microsoft.com/azure/information-protection/what-is-azure-rms) π‘ [Deploy Azure Information Protection](https://learn.microsoft.com/azure/information-protection/aip-classification-and-protection) π‘ [Apply Sensitivity Labels Automatically](https://learn.microsoft.com/microsoft-365/compliance/apply-sensitivity-label-automatically?view=o365-worldwide) π‘ [Use the Service Catalog](https://learn.microsoft.com/system-center/scsm/service-catalog?view=sc-sm-2022) |\r\n| | 4.4 Data Monitoring and Sensing | Purview Data Loss Protection (DLP) Microsoft Defender for Cloud Apps (MDA) Microsoft Defender for Endpoint (MDE) Microsoft Sentinel | π [Microsoft Purview Portal](https://compliance.microsoft.us) π [Microsoft Sentinel](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/microsoft.securityinsightsarg%2Fsentinel) π [M365 Defender Portal](https://security.microsoft.us/) π [Azure Monitor Control Service](https://portal.azure.us/#blade/Microsoft_AAD_IAM/ManagedAppMenuBlade/Overview/objectId/512ba5b8-8ced-42b9-8a94-c93befaf66a1/appId/e933bd07-d2ee-4f1d-933c-3752b819567b) | π‘ [Leverage Data Monitoring & Self Healing](https://learn.microsoft.com/compliance/assurance/assurance-monitoring-and-self-healing) π‘ [Deploy Microsoft 365 Monitorning](https://learn.microsoft.com/microsoft-365/enterprise/microsoft-365-monitoring?view=o365-worldwide) π‘ [Senitnel Data Collection Best Practices](https://learn.microsoft.com/azure/sentinel/best-practices-data)Β π‘ [Deploy Microsoft Purview](https://learn.microsoft.com/purview/purview)Β π‘ [Utilze Azure Rights Management](https://learn.microsoft.com/azure/information-protection/what-is-azure-rms) π‘ [Configure Azure Information Protection](https://learn.microsoft.com/azure/information-protection/aip-classification-and-protection) π‘ [Configure Sentinel Data Connectors](https://learn.microsoft.com/azure/sentinel/connect-data-sources) π‘ [Monitor Your SQL Deployments](https://learn.microsoft.com/azure/azure-sql/database/sql-insights-overview?view=azuresql) |\r\n| | 4.5 Data Encryption & Rights Management | Purview Data Loss Protection (DLP) Microsoft Defender for Cloud Apps (MDA) Microsoft Defender for Endpoint (MDE) | π [Azure Encryption](https://portal.azure.us/#blade/Microsoft_AAD_IAM/ManagedAppMenuBlade/Overview/objectId/21426118-88fd-4b5e-b106-3bd5f098f31a/appId/dbc36ae1-c097-4df9-8d94-343c3d091a76) π [Azure Rights Management Service](https://portal.azure.us/#blade/Microsoft_AAD_IAM/ManagedAppMenuBlade/Overview/objectId/5f0c1df8-5bab-4fb3-b1a5-19bdba46c704/appId/00000012-0000-0000-c000-000000000000) π [M365 Data At Rest Encryption](https://portal.azure.us/#blade/Microsoft_AAD_IAM/ManagedAppMenuBlade/Overview/objectId/882ab41e-90f7-4f4e-8b24-3503495a83e6/appId/c066d759-24ae-40e7-a56f-027002b5d3e4) π [Microsoft Purview Portal](https://compliance.microsoft.us) π [M365 Defender Portal](https://security.microsoft.us/) | π‘ [Utilize Azure Encrption](https://learn.microsoft.com/azure/security/fundamentals/encryption-overview) π‘ [Deploy Azure Rights Management](https://learn.microsoft.com/azure/information-protection/what-is-azure-rms) π‘ [Deploy Purview Information Protection](https://learn.microsoft.com/purview/information-protection) π‘ [Configure Dynamic Key & Encrption Delivery](https://learn.microsoft.com/azure/media-services/latest/drm-content-protection-concept)Β π‘ [Deploy Azure Information Protection](https://learn.microsoft.com/azure/information-protection/aip-classification-and-protection) |\r\n| | 4.6 Data Loss Prevention (DLP) | Purview Data Loss Protection (DLP) Purview Information Protection | π [Microsoft Purview Portal](https://compliance.microsoft.us) π [Endpoint DLP](https://portal.azure.us/#blade/Microsoft_AAD_IAM/ManagedAppMenuBlade/Overview/objectId/780e77f3-df11-4525-b201-973a1b691cab/appId/c98e5057-edde-4666-b301-186a01b4dc58) π [Microsoft Sentinel](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/microsoft.securityinsightsarg%2Fsentinel) π [Entra ID - Diagnostic Settings](https://portal.azure.us/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/DiagnosticSettings) π [Conditional Access Policies](https://portal.azure.us/#view/Microsoft_AAD_ConditionalAccess/ConditionalAccessBlade/~/Policies) π [M365 Defender Portal](https://security.microsoft.us/) | π‘ [Implement Data Loss & Prevention (DLP)](https://learn.microsoft.com/purview/dlp-learn-about-dlp) π‘ [Informaiton Protection & Data Loss and Prevention- GITHUB LAB](https://microsoft.github.io/ComplianceCxE/dag/mip-dlp/) π‘ [Deploy Adaptive Protection- Data Loss & Protections](https://learn.microsoft.com/purview/dlp-adaptive-protection-learn) π‘ [Apply Rules for DLP Exchange Online](https://learn.microsoft.com/exchange/security-and-compliance/data-loss-prevention/dlp-rule-application) π‘ [Utilize Trainable Classifiers](https://learn.microsoft.com/microsoft-365/compliance/classifier-get-started-with?view=o365-worldwide)Β π‘ [Deploy Azure Information Protection](https://learn.microsoft.com/azure/information-protection/aip-classification-and-protection) |\r\n| | 4.7 Data Access Control | Microsoft Defender for Cloud Apps (MDA) Entra ID Conditional Access (CA) Purview Insider Risk Management Purview Information Protection Purview Data Loss Prevention (DLP) Microsoft Intune | π [Microsoft Purview Portal](https://compliance.microsoft.us) π [Entra ID Privileged Identity Management](https://portal.azure.us/#blade/Microsoft_Azure_PIMCommon/CommonMenuBlade) π [Entra ID Conditional Access](https://portal.azure.us/#blade/Microsoft_AAD_ConditionalAccess/ConditionalAccessBlade) π [Azure Internal Access Scope Portal](https://portal.azure.us/#blade/Microsoft_AAD_IAM/ManagedAppMenuBlade/Overview/objectId/a0779651-4c07-4392-a11f-a1694cb497b1/appId/c29427db-9ecc-4750-ad93-d256863f2e37) π [Virtual Network Terminal Access Points](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/microsoft.network%2Fvirtualnetworktaps) π [Microsoft Sentinel](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/microsoft.securityinsightsarg%2Fsentinel) π [Entra ID - Diagnostic Settings](https://portal.azure.us/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/DiagnosticSettings) π [Conditional Access Policies](https://portal.azure.us/#view/Microsoft_AAD_ConditionalAccess/ConditionalAccessBlade/~/Policies) π [M365 Defender Portal](https://security.microsoft.us/) π [Azure Data Explorer](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Kusto%2Fclusters) | π‘ [Configure Conditional Access in Azure Active Directory](https://learn.microsoft.com/azure/active-directory/conditional-access/overview) π‘ [Use Conditional Access Microsoft Intune](https://learn.microsoft.com/mem/intune/protect/conditional-access) π‘ [Use Conditional Access APIs](https://learn.microsoft.com/azure/active-directory/conditional-access/howto-conditional-access-apis) π‘ [Deploy Conditional Access Policies](https://learn.microsoft.com/azure/active-directory/conditional-access/plan-conditional-access#deploy-conditional-access-policies)Β π‘ [Use Conditional Access With Data Explorer](https://learn.microsoft.com/azure/data-explorer/security-conditional-access) π‘ [Deploy Common Conditional Access Policies](https://learn.microsoft.com/azure/active-directory/conditional-access/concept-conditional-access-policy-common?tabs=secure-foundation) π‘ [Build Conditional Access](https://learn.microsoft.com/azure/active-directory/conditional-access/concept-conditional-access-policies) |\r\n| Network & Environment 5.x | | | | |\r\n| | 5.1 Data Flow Mapping | Azure Monitor Net Insights Network Watcher Microsoft Defender for Endpoint (MDE) | π [Network Security Perimeters](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Network%2FnetworkSecurityPerimeters) π [Network Interfaces](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Network%2Fnetworkinterfaces) π [Azure Network Watcher](https://portal.azure.us/#view/Microsoft_Azure_Network/NetworkWatcherMenuBlade/~/overview) π [Azure Firewall](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Network%2FazureFirewalls) π [Web Application Firewall](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Network%2FFrontDoorWebApplicationFirewallPolicies) π [DDoS Protection Plans](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Network%2FddosProtectionPlans) π [Firewall Manager](https://portal.azure.us/#view/Microsoft_Azure_HybridNetworking/FirewallManagerMenuBlade/~/firewallManagerOverview) π [M365 Defender Portal](https://security.microsoft.us/) | π‘ [Use Data Flow Mapping Power Platform](https://learn.microsoft.com/power-query/dataflows/create-use) π‘ [User Azure Network Traffic Analytics](https://learn.microsoft.com/azure/network-watcher/traffic-analytics) π‘ [Azure Blue Print ](https://learn.microsoft.com/azure/governance/blueprints/overview) π‘ [Leverage Azure Data Visualization with Data Explorer](https://learn.microsoft.com/azure/data-explorer/viz-overview) π‘ [Use Power Automate for Event Tagging](https://learn.microsoft.com/microsoft-365/security/defender-endpoint/api-microsoft-flow?view=o365-worldwide) π‘ [Secure & Govern Workloads with Network-level Segmentation](https://learn.microsoft.com/azure/architecture/reference-architectures/hybrid-networking/network-level-segmentation) π‘ [Deploy Software Defined Netoworking](https://learn.microsoft.com/azure-stack/hci/concepts/plan-software-defined-networking-infrastructure) π‘ [Manage Software Defined Netoworking](https://learn.microsoft.com/windows-server/networking/sdn/manage/manage-sdn) π‘ [Key Components of Software Defined Networking Data Sheet](https://learn.microsoft.com/windows-server/networking/sdn/technologies/Software-Defined-Networking-Technologies) |\r\n| | 5.2 Software Defined Networking (SDN) | Secure Access Service Edge (SASE) Microsoft Network Secuirty Groups (NSG) Entra ID App Proxy | π [Manage Virtual Network](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Network%2FvirtualNetworks) π [Network Security Groups](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Network%2FNetworkSecurityGroups) π [Network Managers](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Network%2FnetworkManagers) π [Network Watcher](https://portal.azure.us/#view/Microsoft_Azure_Network/NetworkWatcherMenuBlade/~/overview) π [Network Security Perimeters](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Network%2FnetworkSecurityPerimeters) π [Entra App Proxy](https://portal.azure.us/#view/Microsoft_AAD_IAM/AppProxyOverviewBlade) | π‘ [Use Secure Access Service Edge SASE - Software Defined Networking Zero Trust](https://www.microsoft.com/security/business/security-101/what-is-sase) π‘ [Software Defined Network Monitoring using Sentinel](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/software-defined-monitoring-using-automated-notebooks-and-azure/ba-p/2587775) π‘ [Plan Software Defined Netoworking](https://learn.microsoft.com/azure-stack/hci/concepts/plan-software-defined-networking-infrastructure) π‘ [Implementing Software Defined Networking](https://learn.microsoft.com/windows-server/networking/sdn/) π‘ [Manage Software Detined Netoworking](https://learn.microsoft.com/windows-server/networking/sdn/manage/manage-sdn) π‘ [Deploy Software Defined Networking](https://learn.microsoft.com/windows-server/networking/sdn/deploy/deploy-a-software-defined-network-infrastructure-using-scripts) π‘ [Secure the Network Controller](https://learn.microsoft.com/azure-stack/hci/manage/nc-security) π‘ [SDN for Win Server 2019 and 2022](https://learn.microsoft.com/windows-server/networking/sdn/sdn-whats-new) π‘ [Key Components of Software Defined Networking Data Sheet](https://learn.microsoft.com/windows-server/networking/sdn/technologies/Software-Defined-Networking-Technologies) π‘ [IPV6 Config Interface](https://learn.microsoft.com/javascript/api/%40azure/arm-databoxedge-profile-2020-09-01-hybrid/ipv6config?view=azure-node-latest&wt.mc_id=searchAPI_azureportal_inproduct_rmskilling&sessionId=a3b01375fbf840fe9b8065377eabbd7d) π‘ [Leverage IPV6 for Azure Virtual Networks](https://learn.microsoft.com/azure/virtual-network/ip-services/ipv6-overview?wt.mc_id=searchAPI_azureportal_inproduct_rmskilling&sessionId=a3b01375fbf840fe9b8065377eabbd7d) π‘ [Segementation Security Strategies](https://learn.microsoft.com/azure/well-architected/security/design-segmentation) π‘ [Implement Network Segmentation Paterns On Azure](https://learn.microsoft.com/azure/well-architected/security/design-network-segmentation) π‘ [Utilize Microsoft Packet Monitor](https://learn.microsoft.com/windows-server/networking/technologies/pktmon/pktmon) |\r\n| | 5.3 Macro Segmentation | Azure Subscription Azure VNet(s) Azure VNet Manager Network Security Groups (NSG) Azure Firewall | π [Impletment Network Segmentation](https://learn.microsoft.com/azure/well-architected/security/design-network-segmentation) π [Azure Features for Segmentation](https://learn.microsoft.com/azure/well-architected/security/design-network-segmentation#azure-features-for-segmentation) π [Network Service](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.HybridNetwork%2Fpublishers%2Fnetworkservicedesigngroups) π [Network Watcher](https://portal.azure.us/#view/Microsoft_Azure_Network/NetworkWatcherMenuBlade/~/overview) | π‘ [Impletment Network Segmentation](https://learn.microsoft.com/azure/well-architected/security/design-network-segmentation) π‘ [Azure Features for Segmentation](https://learn.microsoft.com/azure/well-architected/security/design-network-segmentation#azure-features-for-segmentation) π‘ [Segementation Security Strategies](https://learn.microsoft.com/azure/well-architected/security/design-segmentation) π‘ [Network Service Designs](https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/Microsoft.HybridNetwork%2Fpublishers%2Fnetworkservicedesigngroups) π‘ [Network Watcher](https://portal.azure.com/#view/Microsoft_Azure_Network/NetworkWatcherMenuBlade/~/overview) |\r\n| | 5.4 Micro Segmentation | Azure Security Groups (ASG) Entra ID App Proxy Microsoft Tunnel | π [Virtual Networks Termal Access Points](https://portal.azure.us/#view/HubsExtension/BrowseResourceBlade/resourceType/microsoft.network%2Fvirtualnetworktaps) π [Conditional Access](https://portal.azure.us/#view/Microsoft_AAD_ConditionalAccess/ConditionalAccessBlade/~/Overview) π [Cloud Access Routers](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Orbital%2FcloudAccessRouters) π [Entra ID Conditional Access](https://portal.azure.us/#view/Microsoft_AAD_ConditionalAccess/ConditionalAccessBlade/~/Overview) π [Azure Monitor Networks](https://portal.azure.us/#view/Microsoft_Azure_Monitoring/AzureMonitoringBrowseBlade/~/networkInsights) π [Azure Connection Monitor](https://portal.azure.us/#view/Microsoft_Azure_FlowLog/ConnectionMonitorV2ViewModel) π [Azure Network Watcher](https://portal.azure.us/#view/Microsoft_Azure_Network/NetworkWatcherMenuBlade/~/overview/menuId~/%7B%22target%22%3A%7B%7D%7D) | π‘ [Enabling JIT Access Controls](https://learn.microsoft.com/azure/defender-for-cloud/just-in-time-access-usage?wt.mc_id=searchAPI_azureportal_inproduct_rmskilling&sessionId=a3b01375fbf840fe9b8065377eabbd7d) π‘ [Conditional Access Block Access by Location](https://learn.microsoft.com/azure/active-directory/conditional-access/howto-conditional-access-policy-location?wt.mc_id=searchAPI_azureportal_inproduct_rmskilling&sessionId=a3b01375fbf840fe9b8065377eabbd7d) π‘ [Secure Networks with Zero Trust](https://learn.microsoft.com/security/zero-trust/deploy/networks) π‘ [Implement Network Segmentation Paterns On Azure](https://learn.microsoft.com/azure/well-architected/security/design-network-segmentation?wtmc_id=searchAPI_azureportal_inproduct_rmskilling&sessionId=a3b01375fbf840fe9b8065377eabbd7d) π‘ [Microsoft Packet Monitor](https://learn.microsoft.com/windows-server/networking/technologies/pktmon/pktmon) |\r\n| Automation & Orchestration 6.x | | | | |\r\n| | 6.1 Policy Decision Point (PDP) & Policy Orchestration | Entra ID Conditional Access (CA) Azure Policy Azure Automation Azure ML Azure Firewall Microsoft Sentinel | π [Azure Automation](https://portal.azure.us/#view/Microsoft_AAD_IAM/ManagedAppMenuBlade/~/Overview/objectId/d2175af3-6958-4008-83ac-ac2b81eafac7/appId/fc75330b-179d-49af-87dd-3b1acf6827fa) π [Azure Machine Learning](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.MachineLearningServices%2Fworkspaces) π [Azure Policy](https://portal.azure.us/#blade/Microsoft_Azure_Policy/PolicyMenuBlade) π [Azure Virtual Desktop](https://portal.azure.us/#view/Microsoft_Azure_WVD/WvdManagerMenuBlade/~/overview) π [Entra ID](https://portal.azure.us/#view/Microsoft_AAD_Devices/DevicesMenuBlade/~/Devices/menuId~/null) | π‘ [Visibility,Automation and Orchestration with Zero Trust](https://learn.microsoft.com/) π‘ [Azure Orchestration for Azure Security Policy](https://learn.microsoft.com/security/benchmark/azure/baselines/azure-policy-security-baseline) π‘ [Configuration Analyzer for Security Policies](https://learn.microsoft.com/microsoft-365/security/office-365-security/configuration-analyzer-for-security-policies?view=o365-worldwide) π‘ [Azure Automation Overview](https://learn.microsoft.com/azure/automation/overview) π‘ [Azure Security Baseline for Automation](https://learn.microsoft.com/security/benchmark/azure/baselines/automation-security-baseline) π‘ [Azure Policy](https://learn.microsoft.com/azure/governance/policy/overview) π‘ [What is Azure Firewall?](https://learn.microsoft.com/azure/firewall/overview) π‘ [Apply Zero Trust principles to a hub virtual network in Azure](https://learn.microsoft.com/security/zero-trust/azure-infrastructure-networking) π‘ [Management of Role Permissions and Automation](https://learn.microsoft.com/azure/automation/automation-role-based-access-control) π‘ [Using Azure Machine Learning to assign roles](https://learn.microsoft.com/azure/machine-learning/how-to-assign-roles?view=azureml-api-2&tabs=labeler) π‘ [Azure AD Seccurity Groups ML](https://learn.microsoft.com/azure/machine-learning/how-to-assign-roles?view=azureml-api-2&tabs=labeler#use-azure-ad-security-groups-to-manage-workspace-access) |\r\n| | 6.2 Critical Process Automation | Microsoft Power Automate Azure Logic Apps Microsoft Sentinel Playbooks Microsoft 365 Defender Automated Investigation & Response | π [Azure Automation](https://portal.azure.us/#view/Microsoft_AAD_IAM/ManagedAppMenuBlade/~/Overview/objectId/d2175af3-6958-4008-83ac-ac2b81eafac7/appId/fc75330b-179d-49af-87dd-3b1acf6827fa) π [Microsoft Sentinel Automation Blade](https://portal.azure.us/?feature.msaljs=true#view/Microsoft_Azure_Security_Insights/MainMenuBlade/~/Automationl) π [Azure Logic Apps Blade](https://portal.azure.us/?feature.msaljs=true#view/HubsExtension/BrowseResource/resourceType/Microsoft.Logic%2Fworkflows) π [M365 Defender Portal](https://security.microsoft.us/) | π‘ [Azure Automation Overview](https://learn.microsoft.com/azure/automation/overview) π‘ [Azure Security Baseline for Automation](https://learn.microsoft.com/security/benchmark/azure/baselines/automation-security-baseline) π‘ [Visibility, Automation, and Orchestration with Zero Trust](https://learn.microsoft.com/) π‘ [Automation in Microsoft Sentinel](https://learn.microsoft.com/azure/sentinel/automation) π‘ [Automate Threat Response with Playbooks](https://learn.microsoft.com/azure/sentinel/automate-responses-with-playbooks) π‘ [Automated Investigation & Response M365 Defender](https://learn.microsoft.com/microsoft-365/security/defender/m365d-autoir?view=o365-worldwide) π‘ [Power Automate U.S Government](https://learn.microsoft.com/power-automate/us-govt) |\r\n| | 6.3 Machine Learning | Microsoft Sentinel Fusion ML Microsoft Sentinel Bring Your Own Machine Learning (BYOML) Microsoft Defender for Cloud (MDfC) Azure ML | π [Azure Machine Learning](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.MachineLearningServices%2Fworkspaces) π [Power Automate](https://make.gov.powerautomate.us/) π [Power Platform Admin Center](https://admin.appsplatform.us/) π [Sentinel](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/microsoft.securityinsightsarg%2Fsentinel) π [Defender for Cloud](https://portal.azure.us/#view/Microsoft_Azure_Security/SecurityMenuBlade/~/0) | π‘ [Advanced multistage attack detection in Microsoft Sentinel](https://learn.microsoft.com/azure/sentinel/fusion) π‘ [Bring your own Machine Learning (ML) into Microsoft Sentinel](https://learn.microsoft.com/azure/sentinel/bring-your-own-ml) π‘ [Azure Machine Learning](https://learn.microsoft.com/azure/machine-learning/?view=azureml-api-2) π‘ [Enterprise Security & Governance w. Machine Learning](https://learn.microsoft.com/azure/machine-learning/concept-enterprise-security?view=azureml-api-2) π‘ [Azure Government Isolaiton Guidelines using AI & ML](https://learn.microsoft.com/azure/azure-government/documentation-government-impact-level-5) π‘ [Quick Start Azure Machine Learning](https://learn.microsoft.com/azure/machine-learning/tutorial-azure-ml-in-a-day?view=azureml-api-2) π‘ [Azure security baseline for Azure Machine Learning](https://learn.microsoft.com/security/benchmark/azure/baselines/machine-learning-security-baseline) |\r\n| | 6.4 Artificial Intelligence | Microsoft Sentinel Fusion ML Microsoft Sentinel Tailored AI Azure ML | π [Azure AI Services](https://portal.azure.us/#blade/Microsoft_Azure_ProjectOxford/CognitiveServicesHub) π [Sentinel](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/microsoft.securityinsightsarg%2Fsentinel) π [Defender for Cloud](https://portal.azure.us/#view/Microsoft_Azure_Security/SecurityMenuBlade/~/0) | π‘ [AI Security Services](https://learn.microsoft.com/azure/ai-services/security-features) π‘ [Senintel Automation](https://learn.microsoft.com/azure/sentinel/automation) π‘ [AI ID & Access Risk Based Controls](https://azure.microsoft.com/products/category/identity/) π‘ [Implement Sentinel & M365 Defender for XDR - AI Driven Zero Trust ](https://learn.microsoft.com/security/operations/siem-xdr-overview) π‘ [Become a Sentinel Automation Ninja](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/become-a-microsoft-sentinel-automation-ninja/ba-p/3563377) |\r\n| | 6.5 Security Orchestration, Automation & Response (SOAR) | Microsoft 365 Defender Automated investigation and response Microsoft Sentinel Playbooks Microsoft Defender for Cloud (MDfC) Azure Logic Apps | π [Sentinel SIEM-SOAR](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/microsoft.securityinsightsarg%2Fsentinel) π [Logic Apps](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Logic%2Fworkflows) π [Microsoft Defender for Cloud](https://portal.azure.us/#blade/Microsoft_Azure_Security/SecurityMenuBlade) π [Entra ID](https://portal.azure.us/#view/Microsoft_AAD_Devices/DevicesMenuBlade/~/Devices/menuId~/null) | π‘ [Security Ochestration, Automation & Response (SOAR) In Sentinel](https://learn.microsoft.com/azure/sentinel/automation) π‘ [Sentinel SOAR](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/how-to-use-azure-sentinel-for-incident-response-orchestration/ba-p/2242397) π‘ [Microsoft Sentinel SOAR Content Catalog](https://learn.microsoft.com/azure/sentinel/sentinel-soar-content) π‘ [Automate Threat Response with Playbooks in Sentinel](https://learn.microsoft.com/azure/sentinel/automate-responses-with-playbooks) π‘ [Automated investigation and response in Microsoft 365 Defender](https://learn.microsoft.com/microsoft-365/security/defender/m365d-autoir?view=o365-worldwide) π‘ [Workflow Automation in Microsoft Defender for Cloud](https://learn.microsoft.com/azure/defender-for-cloud/workflow-automation) π‘ [SOAR Best Practices](https://www.microsoft.com/security/business/security-101/what-is-soar#SOARbestpractices) π‘ [Become a Sentinel Automation Ninja](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/become-a-microsoft-sentinel-automation-ninja/ba-p/3563377) |\r\n| | 6.6 API Standardization | Azure API Management Azure Monitor Log Analytics Azure Logic Apps Azure Policy | π [API Management Services](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.ApiManagement%2Fservice) π [API Connections](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Web%2Fconnections) π [API Playground](https://portal.azure.us/#blade/Microsoft_Azure_Resources/ArmPlayground) π [Azure Logic Apps](https://portal.azure.us/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Logic%2Fworkflows) | π‘ [Microsft API Management & Security](https://azure.microsoft.com/products/api-management/) π‘ [Mitigate OWASP Top 10 Security Threats Using Microsoft API Management](https://learn.microsoft.com/azure/api-management/mitigate-owasp-api-threats) π‘ [Security Baselines for API Management](https://learn.microsoft.com/security/benchmark/azure/baselines/api-management-security-baseline) π‘ [Secure and Compliant APIs for a Hybrid and Multi Cloud World](https://azure.microsoft.com/blog/secure-and-compliant-apis-for-a-hybrid-and-multi-cloud-world/) π‘ [Web API Design Best Practice](https://learn.microsoft.com/azure/architecture/best-practices/api-design) π‘ [Monitor & Protect Your APIs](https://learn.microsoft.com/azure/api-management/api-management-howto-use-azure-monitor) |\r\n| | 6.7 Security Operations Center (SOC) & Incident Response (IR) | Microsoft Sentinel Microsoft Defender for Cloud (MDfC) Microsoft 365 Defender | π [Sentinel SIEM-SOAR](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/microsoft.securityinsightsarg%2Fsentinel) π [Logic Apps](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Logic%2Fworkflows) π [Microsoft Defender for Cloud](https://portal.azure.us/#blade/Microsoft_Azure_Security/SecurityMenuBlade) π [Entra ID](https://portal.azure.us/#view/Microsoft_AAD_Devices/DevicesMenuBlade/~/Devices/menuId~/null) π [M365 Defender Portal](https://security.microsoft.us/) | π‘ [Security Operations In Azure](https://learn.microsoft.com/azure/well-architected/security/monitor-security-operations) π‘ [Microsoft SOC Best Practices Landing Page](https://www.microsoft.com/security/business/security-101/what-is-a-security-operations-center-soc?ef_id=_k_ce7dcd6e8f2d1919667ca9a72f733870_k_&OCID=AIDcmmdamuj0pc_SEM__k_ce7dcd6e8f2d1919667ca9a72f733870_k_&msclkid=ce7dcd6e8f2d1919667ca9a72f733870) π‘ [Playbook for Modernizing Security Operations Centers](https://www.microsoft.com/security/blog/2021/02/11/a-playbook-for-modernizing-security-operations/) π‘ [CISO Series Lessons Learned from Microsoft's SOC](https://www.microsoft.com/security/blog/2019/10/07/ciso-series-lessons-learned-from-the-microsoft-soc-part-3a-choosing-soc-tools/) π‘ [Integrating Microsoft 365 Defender into your security operations](https://learn.microsoft.com/microsoft-365/security/defender/integrate-microsoft-365-defender-secops?view=o365-worldwide) |\r\n| Visibility & Analytics 7.x | | | | |\r\n| | 7.1 Log All Traffic (Network, Data, Apps, Users) | Azure Monitor Log Analytics Microsoft Sentinel | π [Log Analytics Workspace](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.OperationalInsights%2Fworkspaces) π [Log Query Packs](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.OperationalInsights%2Fquerypacks) π [Sign-in Activity Logs](https://portal.azure.us/#blade/Microsoft_AAD_IAM/SignInEventsV3Blade) π [Activity Logs](https://portal.azure.us/#blade/Microsoft_Azure_Monitoring/AzureMonitoringBrowseBlade/activityLog) π [Audit Log](https://portal.azure.us/#blade/Microsoft_AAD_IAM/AuditEventsV2PillsBlade) π [Operation Log](https://portal.azure.us/#blade/Microsoft_Azure_Resources/OperationLogsBlade) π [Microsoft Azure Log Search Alerts](https://portal.azure.us/#blade/Microsoft_AAD_IAM/ManagedAppMenuBlade/Overview/objectId/c134d63b-957f-4cf7-8a34-d744aa8804df/appId/f6b60513-f290-450e-a2f3-9930de61c5e7) | π‘ [Azure Log Analytics](https://learn.microsoft.com/azure/azure-monitor/logs/log-analytics-overview) π‘ [Azure Monitor](https://learn.microsoft.com/azure/azure-monitor/overview) π‘ [Audit Logging and Monitoring](https://learn.microsoft.com/compliance/assurance/assurance-audit-logging) π‘ [Maturity Model for Log Management M2131](https://techcommunity.microsoft.com/t5/public-sector-blog/microsoft-sentinel-maturity-model-for-event-log-management-m-21/ba-p/3074336) π‘ [Device Log Capture - Intune](https://learn.microsoft.com/mem/intune/remote-actions/collect-diagnostics) π‘ [Application Logging](https://learn.microsoft.com/sql/relational-databases/performance/view-the-windows-application-log-windows-10?view=sql-server-ver16) π‘ [User Access Logging](https://learn.microsoft.com/windows-server/administration/user-access-logging/get-started-with-user-access-logging) π‘ [Azure Infrastructure Logs](https://learn.microsoft.com/azure/well-architected/scalability/monitor-infrastructure) π‘ [Network Logging](https://learn.microsoft.com/azure/azure-web-pubsub/howto-troubleshoot-network-trace) π‘ [Supported Logs for Network](https://learn.microsoft.com/azure/azure-monitor/reference/supported-logs/microsoft-network-networkmanagers-logs) |\r\n| | 7.2 Security Information and Event Management (SIEM) | Microsoft Sentinel Microsoft Defender for Cloud (MDfC) Microsoft 365 Defender | π [Sentinel](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/microsoft.securityinsightsarg%2Fsentinel) π [M365 Defender Portal](https://security.microsoft.us/) π [Microsoft Defender for Cloud](https://portal.azure.us/#view/Microsoft_Azure_Security/SecurityMenuBlade/~/0) | π‘[Microsoft Sentinel](https://learn.microsoft.com/azure/sentinel/overview) π‘[Implement Sentinel & M365](https://learn.microsoft.com/security/operations/siem-xdr-overview) π‘[Unified SIEM & XDR](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/what-s-new-unified-microsoft-siem-and-xdr-github-community/ba-p/3249533) π‘[Stream Alerts Defender for Cloud to SIEM](https://learn.microsoft.com/azure/defender-for-cloud/export-to-siem#stream-alerts-to-azure-sentinel) π‘[Azure Sentinel Github Repo](https://github.com/Azure/Azure-Sentinel) π‘[Sentinel & SOC Analysis Process](https://learn.microsoft.com/azure/sentinel/migration-security-operations-center-processes) π‘[Microsoft Sentinel Skill Up Training](https://learn.microsoft.com/azure/sentinel/skill-up-resources) |\r\n| | 7.3 Common Security and Risk Analytics | Microsoft Sentinel Microsoft Defender for Cloud (MDfC) | π [Sentinel](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/microsoft.securityinsightsarg%2Fsentinell) π [Defender For Cloud](https://portal.azure.us/#blade/Microsoft_Azure_Security/SecurityMenuBlade) π [Security Baselines](https://endpoint.microsoft.us/#home) | π‘[Microsoft Security Response Center Security Updates Guide](https://msrc.microsoft.com/update-guide) π‘[Explore Risks to Sensitive Data Microsoft Defender for Cloud](https://learn.microsoft.com/azure/defender-for-cloud/data-security-review-risks) π‘[Identify & Analyze Risks Across Your Environment](https://learn.microsoft.com/azure/defender-for-cloud/concept-attack-path) π‘[Cloud Security Posture Management](https://learn.microsoft.com/azure/defender-for-cloud/concept-cloud-security-posture-management) π‘[Microsoft Cloud Security Benchmark](https://learn.microsoft.com/azure/defender-for-cloud/concept-regulatory-compliance) |\r\n| | 7.4 User and Entity Behavior Analytics | Microsoft Sentinel UEBA Microsoft Defender for Cloud Apps (MDA) Microsoft Defender for Identity (MDI) Entra ID Conditional Access (CA) Purview Insider Risk Management | π [Entra ID](https://portal.azure.us/#view/Microsoft_AAD_Devices/DevicesMenuBlade/~/Devices/menuId~/null) π [Sentinel](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/microsoft.securityinsightsarg%2Fsentinell) π [Defender For Cloud](https://portal.azure.us/#blade/Microsoft_Azure_Security/SecurityMenuBlade) π [Microsoft Purview Portal](https://compliance.microsoft.us) π [M365 Defender Portal](https://security.microsoft.us/) | π‘ [ID Threats with User and Entity Behavior Analytics](https://learn.microsoft.com/azure/sentinel/identify-threats-with-entity-behavior-analytics) π‘ [Enable Entity Behavior Analytics to Detect Threats](https://learn.microsoft.com/azure/sentinel/enable-entity-behavior-analytics) π‘ [Microsoft Sentinel UEBA Reference](https://learn.microsoft.com/azure/sentinel/ueba-reference) π‘ [Investigate Incidents with UEBA](https://learn.microsoft.com/azure/sentinel/investigate-with-ueba) π‘ [Discover and Protect Sensitive Information in your Organization](https://learn.microsoft.com/defender-cloud-apps/tutorial-dlp) π‘ [Purview Insider Risk Management](https://learn.microsoft.com/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/plan-for-microsoft-purview-dod-deployments) |\r\n| | 7.5 Threat Intelligence Integration | Microsoft Sentinel Threat Intelligence (TI) Microsoft Graph Security Indicators Microsoft Defender Threat Intelligence (MDTI) | π [Sentinel](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/microsoft.securityinsightsarg%2Fsentinell) π [Defender For Cloud](https://portal.azure.us/#blade/Microsoft_Azure_Security/SecurityMenuBlade) π [Microsoft Threat Intelligence Portal](https://ti.defender.microsoft.com/) | π‘[Microsoft Threat Intelligence](https://learn.microsoft.com/defender/threat-intelligence/what-is-microsoft-defender-threat-intelligence-defender-ti) π‘[Microsoft Security Graph API](https://learn.microsoft.com/graph/api/resources/security-api-overview?view=graph-rest-beta) π‘[Create Threat Intelligence Indicators](https://learn.microsoft.com/graph/api/tiindicators-post?view=graph-rest-beta&tabs=http) π‘[Threat intelligence integration in Microsoft Sentinel](https://learn.microsoft.com/azure/sentinel/threat-intelligence-integration) π‘[Bring Your Own Threat Intelligence Feeds](https://learn.microsoft.com/defender-cloud-apps/additional-integrations) π‘[Accessing the Threat Intelligence Portal](https://learn.microsoft.com/defender/threat-intelligence/learn-how-to-access-microsoft-defender-threat-intelligence-and-make-customizations-in-your-portal) |\r\n| | 7.6 Automated Dynamic Policies | Entra ID Protection Microsoft Defender for Endpoint (MDE) Microsoft Defender for Cloud (MDfC) Microsoft Sentinel Fusion ML Microsoft Sentinel Bring Your Own Machine Learning (BYOML) Microsoft Sentinel Playbooks Microsoft Intune Azure Automation Purview Insider Risk Management | π [Sentinel](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/microsoft.securityinsightsarg%2Fsentinell) π [Defender For Cloud](https://portal.azure.us/#blade/Microsoft_Azure_Security/SecurityMenuBlade) π [Logic Apps](https://portal.azure.us/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Logic%2Fworkflows) π [Entra ID](https://portal.azure.us/#view/Microsoft_AAD_Devices/DevicesMenuBlade/~/Devices/menuId~/null) π [Azure Automation](https://portal.azure.us/#blade/Microsoft_AAD_IAM/ManagedAppMenuBlade/Overview/objectId/d2175af3-6958-4008-83ac-ac2b81eafac7/appId/fc75330b-179d-49af-87dd-3b1acf6827fa) π [Microsoft Purview Portal](https://compliance.microsoft.us) π [Microsoft Intune](https://endpoint.microsoft.us/#view/Microsoft_Intune_Enrollment/ReportingMenu/~/deviceCompliance) | π‘[Automate Threat Response with Microsoft Sentinel](https://learn.microsoft.com/azure/sentinel/automate-responses-with-playbooks) π‘[Adaptive Protection - Microsoft Purview](https://www.microsoft.com/security/blog/2023/02/06/introducing-adaptive-protection-in-microsoft-purview-people-centric-data-protection-for-a-multiplatform-world/#:~:text=With%20Adaptive%20Protection%2C%20DLP%20policies%20become%20dynamic%2C%20ensuring,efficient%20and%20empowered%20to%20do%20more%20with%20less.) π‘[Adaptive Policy Scopes M365](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/using-adaptive-policy-scopes-to-apply-m365-retention-to-shared/ba-p/3053641#:~:text=Back%20in%20October,in%20Microsoft%20365.) π‘[Adaptive Application Controls](https://learn.microsoft.com/azure/defender-for-cloud/adaptive-application-controls) π‘[AI-Driven Adaptive Device Controls Microsoft Defender for Endpoint](https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/ai-driven-adaptive-protection-in-microsoft-defender-for-endpoint/ba-p/2966491) π‘[AI-Driven Adaptive Protection Against Human Operated Ransomeware](https://www.microsoft.com/security/blog/2021/11/15/ai-driven-adaptive-protection-against-human-operated-ransomware/) π‘[Microsoft Defender for Cloud Automated Security Posture Management](https://learn.microsoft.com/azure/defender-for-cloud/concept-cloud-security-posture-management) π‘[Improve your network security posture with adaptive network hardening](https://learn.microsoft.com/azure/defender-for-cloud/adaptive-network-hardening) π‘[What is Microsoft Entra ID Protection?](https://learn.microsoft.com/azure/active-directory/identity-protection/overview-identity-protection) π‘[Azure Automation update management](https://learn.microsoft.com/azure/architecture/hybrid/azure-update-mgmt) π‘[Manage Windows 10 and Windows 11 software updates in Intune](https://learn.microsoft.com/mem/intune/protect/windows-update-for-business-configure) |"
+ },
+ "conditionalVisibility": {
+ "parameterName": "isess3Visible",
+ "comparison": "isEqualTo",
+ "value": "true"
+ },
+ "showPin": true,
+ "name": "ztalign"
+ }
+ ]
+ },
+ "conditionalVisibility": {
+ "parameterName": "pillar",
+ "comparison": "isEqualTo",
+ "value": "ess"
+ },
+ "name": "ZTGroup"
+ },
+ {
+ "type": 1,
+ "content": {
+ "json": "## DoD Zero Trust Capabilities (45) ##\r\n\r\n| ID # | Capability | Pillar | Capability Description | Capability Outcome | Impact to ZT | Associated Activities |\r\n|------|---------------------------------------------------------------------------|----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\r\n| 1.1 | User Inventory | 1 - User | Regular and Privileged users are identified and integrated into an inventory supporting regular modifications. Applications, software and services that have local users are all part of the inventory and highlighted. | System owners have control (visibility and administrative rights) of all authorized and authenticated users on the network | Users not on the authorized user list will be denied access by policy | * Inventory User |\r\n| 1.2 | Conditional User Access | 1 - User | Through maturity levels Conditional Access works to create a dynamic level of access for users in the environment. This starts with traditional role based access controls across a federate ICAM, expands to be application focused roles and ultimately utilizes enterprise attributes to provide dynamic access rules. | Eventually, organizations control user, device, and non-user entity DAAS access through dynamically changing user risk profiles and fine grained access control to include the use of user risk assessments | Users not known to the system and users who present an unacceptable degree of risk will be denied access with greater accuracy | * Implement App Based Permissions per Enterprise * Rule Based Dynamic Access Pt1 * Rule Based Dynamic Access Pt2 * Enterprise Gov't roles and Permissions Pt1 * Enterprise Gov't roles and Permissions Pt2 |\r\n| 1.3 | Multi-Factor Authentication (MFA) | 1 - User | This capability initially focuses on developing an organization focused MFA provider and Identity Provider to enable the centralization of users. Retirement of local and/or built-in accounts and groups is a critical piece to this capability. At the later maturity levels alternative and flexible MFA tokens can be used to provide access for standard and external users. | DoD organizations require users and non-user entities to authenticate using at least two of the following three attributes: knowledge (user ID/password), possession (CAC/token), or something you are (inherence, e.g., iris/fingerprints), in order to access DAAS | Users not presenting multiple forms of authentication will be denied access to DAAS system and resources | * Organizational MFA/IDP * Alternative Flexible MFA Pt1 * Alternative Flexible MFA Pt2 |\r\n| 1.4 | Privileged Access Management (PAM) | 1 - User | The capability focuses on removal of permanent administrator/elevated privileges by first creating a Privileged Account Management (PAM) system and migrating privileged users to it. The capability is then expanded upon by using automation with privilege escalation approvals and feeding analytics into the system for anomaly detection. | DoD organizations control, monitor, secure, and audit privileged identities (e.g., through password vaulting, JIT/JEA with PAWS) across their IT environments | Critical assets and applications secured, controlled, monitored and managed through limits on admin access | * Implement System and Migrate Privileged Users Pt1 * Implement System and Migrate Privileged Users Pt2 * Real time Approvals & JIT/JEA Analytics Pt1 * Real time Approvals & JIT/JEA Analytics Pt2 |\r\n| 1.5 | Identity Federation & User Credentialing | 1 - User | The initial scope of this capability focuses on standardizing the Identity Lifecycle Management (ILM) processes and integrating with the standard organizational IDP/IDM solution. Once completed the capability shifts to establishing an Enterprise ILM process/solution either through a single solution or identity federation. | DoD organizations manually issue, manage, and revoke credentials bound to DoD person, device, and NPE identities. Identity information is developed and shared across entitles and trust domains providing βsingle sign-onβ convenience and efficiencies to identified (authenticated and authorized) users and devices. | Visibility and accuracy of user authentication information is increased, to include DoD users and users managed by other agencies. Users lacking sufficient credentials are denied access according to established policies. | * Organizational Identity Life-Cycle Management * Enterprise Identity Life-Cycle Management Pt1 * Enterprise Identity Life-Cycle Management Pt2 * Enterprise Identity Life-Cycle Management Pt3 |\r\n| 1.6 | Behavioral, Contextual ID, and Biometrics | 1 - User | Utilizing the Enterprise IDP, user and entity behavioral analytics (UEBA) are enabled with basic user attributes. Once completed this is expanded into Organizational specific attributes using Organizational IDPs as available. Finally UEBA are integrated with the PAM and JIT/JEA systems to better detect anomalous and malicious activities. | DoD organizations utilize behavioral, contextual, and biometric telemetry to enhance risk-based authentication and access controls | Behavioral, contextual, and biometric telemetry enhances MFA with | * Implement User & Entity Behavior Activity (UEBA) and User Activity Monitoring (UAM) Tooling * User Activity Monitoring Pt1 * User Activity Monitoring Pt2 |\r\n| 1.7 | Least Privileged Access | 1 - User | DoD organizations govern access to DAAS using the absolute minimum access required to perform routine, legitimate tasks or activities. DoD Application Owners identify the necessary roles and attributes for standard and privileged user access. Privileged access for all DoD organization DAAS is audited and removed when unneeded. | DoD organizations govern access to DAAS using the absolute minimum access required to perform routine, legitimate tasks or activities | Users on the network only have access to the DAAS for which they are authorized and authenticated over a specific timeframe | * Deny User by Default Policy |\r\n| 1.8 | Continuous Authentication | 1 - User | The DoD organizations and overall enterprise will methodically move towards continuous attribute based authentication. Initially the capability focuses on standardizing legacy single authentication to a organizationally approved IDP with users and groups. The second stages adds in based rule based (time) authentication and ultimately matures to Continuous Authentication based on the application/software activities and privileges requested. | DoD organizations continuously authenticate and authorize users' access to DAAS within and across sessions using MFA | Users not continuously presenting multiple forms of authentication will be denied access to DAAS system and resources | * Single Authentication * Periodic Authentication * Continuous Authentication Pt1 * Continuous Authentication Pt2 |\r\n| 1.9 | Integrated ICAM Platform | 1 - User | DoD organizations and overall enterprise employ enterprise-level identity management and public key infrastructure (PKI) systems to track user, administrator and NPE identities across the network and ensure access is limited to only those who have the need and the right to know. Organizations can verify they need and have the right to access via credential management systems, identity governance and administration tools, and an access management tool. PKI systems can be federated but must either trust a central root certificate authority (CA) and/or cross-sign standardized organizational CAβs. | DoD organizations employ enterprise-level identity management systems to track user and NPE identities across the network and ensure access is limited to only those who have the need and the right to know; organizations can verify they need and have the right to access via credential management systems, identity governance and administration tools, and an access management tool | Identities of users and NPE are centrally managed to ensure authorized and authenticated access to DAAS resources across platforms | * Enterprise PKI/IDP Pt1 * Enterprise PKI/IDP Pt2 * Enterprise PKI/IDP Pt3 |\r\n| 2.1 | Device Inventory | 2 - Device | DoD organizations establish and maintain an approved inventory list of all devices authorized to access the network and enroll all devices on the network prior to network connection. Device attributes will include technical details such as the PKI (802.1x) machine certificate, device object, patch/vulnerability status and others to enable successor activities. | DoD organizations establish and maintain a trusted inventory list of all devices authorized to access the network and enroll all devices on the network prior to network connection | By default policy, devices will be denied network access; the only devices permitted access to the network shall be known, authorized, and listed in the device inventory | * Device Health Tool Gap Analysis * NPE/PKI, Device under Management * Enterprise IDP Pt1 * Enterprise IDP Pt2 |\r\n| 2.2 | Device Detection and Compliance | 2 - Device | DoD organizations employ asset management systems for user devices to maintain and report on IT and Cybersecurity compliance. Managed devices (enterprise and mobile) attempting to connect to a DoD network or access a DAAS resource is detected and has its compliance status confirmed (via C2C) | DoD organizations employ asset management systems for user devices to maintain and report on IT compliance. Any device (including mobile, IOT, managed, and unmanaged) attempting to connect to a DoD network or access a DAAS resource is detected and has its compliance status confirmed (via C2C) | Any device attempting to connect to the network will be detected; only those devices that are compliant (e.g., anti-virus is up to date, approved configuration) will receive access to requested DAAS | * Implement C2C/Compliance Based Network Authorization Pt1 * Implement C2C/Compliance Based Network Authorization Pt2 |\r\n| 2.3 | Device Authorization w/ Real Time Inspection | 2 - Device | DoD Organizations conduct foundational and extended device tooling (NextGen AV, AppControl, File Integrity Monitoring (FIM), etc.) integration to better understand the risk posture. Organizational PKI systems are integrated to expand the existing Enterprise PKI to devices as well. Lastly Entity Activity Monitoring is also integrated to identify anomalous activities. | DoD organizations establish processes (e.g., Enterprise PKI) and utilize tools to identify any device (including unmanaged devices, infrastructure devices, and endpoint devices) attempting to access the network, and make a determination if the device should be authorized to access the network. Maturation of this capability monitoring and detection of this activity on endpoints and IT infrastructure in real time | Components can use policies to deny devices by default and explicitly allow access to DAAS resources only by devices that meet mandated configuration standards. Security threats identified are remediated faster through continuous activity inspection enables faster remediation of security threats | * Entity Activity Monitoring Pt1 * Entity Activity Monitoring Pt2 * Implement Application Control & File Integrity Monitoring (FIM) Tools * Integrate NextGen AV Tools with C2C * Fully Integrate Device Security stack with C2C as appropriate * Enterprise PKI Pt1 * Enterprise PKI Pt2 |\r\n| 2.4 | Remote Access | 2 - Device | DoD organizations audit existing device access processes and tooling to set a least privilege baseline. In phase 2 this access is expanded to cover basic BYOD and IOT support using the Enterprise IDP for approved applications. The final phases expand coverage to include all BYOD and IOT devices for services using the approved set of device attributes. | DoD organizations establish policies to allow authorized users and devices access to the network or a device from a geographical distance through a network connection | Enables properly authorized and authenticated users and NPEs to access DAAS from remote locations | * Deny Device by Default Policy * Managed and Limited BYOD & IOT Support * Managed and Full BYOD & IOT Support Pt1 * Managed and Full BYOD & IOT Support Pt2 |\r\n| 2.5 | Partially & Fully Automated Asset, Vulnerability and Patch Management | 2 - Device | DoD organizations establish processes to automatically test and deploy vendor patches for connected devices; hybrid patch management (both human and automated) is employed | DoD organizations establish processes to automatically test and deploy vendor patches for connected devices; hybrid patch management (both human and automated) is employed | Risk is minimized by automatically deploying vendor patches to all network devices | * Implement Asset, Vulnerability and Patch Management Tools |\r\n| 2.6 | Unified Endpoint Management (UEM) & Mobile Device Management (MDM) | 2 - Device | DoD organizations establish a centralized UEM solution that provides the choices of agent and/or agentless management of computer and mobile devices to a single console regardless of device location. DoD-issued devices can be remotely managed and security policies are enforced. | DoD organizations establish a centralized UEM tool that provides the choices of agent and/or agentless management of computer and mobile devices to a single console. DoD-issued mobile devices are remotely managed and security policies are enforced. | DAAS resources are protected through agent and agentless management, IT is able to manage, secure, and deploy resources and applications on any device from a single console to provide redress of cybersecurity threats. Security vulnerabilities are mitigated and policy enforcement measures are received through IT remote management of DoD-issued mobile devices | * Implement UEDM or equivalent Tools * Enterprise Device Management Pt1 * Enterprise Device Management Pt2 |\r\n| 2.7 | Endpoint & Extended Detection & Response (EDR & XDR) | 2 - Device | DoD organizations use endpoint detection and response (EDR) tooling to monitor, detect, and remediate malicious activity on endpoints. Expanding the capability to include XDR tooling allows organizations to account for activity beyond the endpoints such as cloud and network as well. | DoD organizations use EDR tools to monitor, detect, and remediate malicious activity on endpoints as a baseline. Upgrading to XDR tools allows organizations to account for activity beyond the endpoints. | Threats originating from network- connected endpoints are initially reduced through active investigation and response. Maturation focuses on forensics and faster threat detection and remediation are enabled by correlating data across multiple security layers (e.g., email, cloud, endpoint) | * Implement Endpoint Detection & Response (EDR) Tools and Integrate with C2C * Implement Extended Detection & Response (XDR) Tools and Integrate with C2C Pt1 * Implement Extended Detection & Response (XDR) Tools and Integrate with C2C Pt2 |\r\n| 3.1 | Application Inventory | 3 - Applications and Workloads | System owners ensure that all applications and application components are identified and inventoried; only applications and application components that have been authorized by the appropriate authorizing official/CISO/CIO shall be utilized within the system owner's purview | System owners ensure that all applications and application components are identified and inventoried; only applications and application components that have been authorized by the appropriate authorizing official/CISO/CIO shall be utilized within the system owner's purview | Unauthorized applications and application components are not used on or within the system | * Application/Code Identification |\r\n| 3.2 | Secure Software Development & Integration | 3 - Applications and Workloads | Foundational software and application security processes and infrastructure are established following Zero Trust principles and best practices. Controls such as code review, runtime protection, secure API gateways, container and serverless security are integrated and automated. | Organization-defined security controls and practices are integrated, to include Zero Trust security controls and virtualization, into the software development lifecycle and DevOps toolchain. Custom software development teams use DevSecOps to integrate static and dynamic application security testing into software delivery workflows in accordance with the organization's requirements (policies, technologies, and processes). | Zero Trust security concepts, processes, and capabilities are accepted and integrated across the DevOps toolchain, to include static and dynamic application security testing necessary for the discovery of weaknesses and vulnerabilities during application development | * Build DevSecOps Software Factory Pt1 * Build DevSecOps Software Factory Pt2 * Automate Application Security & Code Remediation Pt1 * Automate Application Security & Code Remediation Pt2 |\r\n| 3.3 | Software Risk Management | 3 - Applications and Workloads | DoD organizations establish software/application risk management program. Foundational controls include Bill of Materials risk management, Supplier Risk Management, approved repositories and update channels, and vulnerability management program. Additional controls include Continual validation within the CI/CD pipelines and vulnerability maturation with external sources. | DoD establishes policies and procedures to secure supply chain cybersecurity for code components within DoD and DIB systems by evaluating and identifying supplier sourcing risk for approved sources, creating repositories and update channels for use by development teams, creating Bill of Materials for applications to identify source, supportability and risk posture, and establishing industry standard (DIB) and approved vulnerability databases for use in DevSecOps | Code used in DAAS and associated components of the supply chain is secure, vulnerabilities are reduced, and DoD is aware of potential risks | * Approved Binaries/Code * Vulnerability Management Program Pt1 * Vulnerability Management Program Pt2 * Continual Validation |\r\n| 3.4 | Resource Authorization & Integration | 3 - Applications and Workloads | DoD establishes a standardized resource authorization gateway for authorizations via the CI/CD pipelines in a risk approach that reviews the User, Device and Data security posture. Authorizations utilize a programmatic (e.g., Software Defined) approach in a live/production environment. Attributes are enriched utilizing other pillar activities and the API and Authorization gateway. Approved enterprise APIs are micro- segmented using authorizations. | DoD establishes a standard approach managing the authorizations of resources in a risk approach that reviews the User, Device and Data security posture. | Resource authorization enables the ability for limited access to those resources and in a programmatic way in later stages. This improvise the ability to remove access when it is not needed. | * Resource Authorization Pt1 * Resource Authorization Pt2 * SDC Resource Authorization Pt1 * SDC Resource Authorization Pt2 * Enrich Attributes for Resource Authorization Pt1 * Enrich Attributes for Resource Authorization Pt2 * REST API Micro-Segments |\r\n| 3.5 | Continuous Monitoring and Ongoing Authorizations | 3 - Applications and Workloads | DoD organizations employ automated tools and processes to continuously monitor applications and assess their authorization to operate | DoD organizations employ automated tools and processes to continuously monitor applications and assess their authorization to operate | Near real time visibility into the effectiveness of deployed security controls | * Continuous Authorization to Operate (cATO) Pt1 * Continuous Authorization to Operate (cATO) Pt2 |\r\n| 4.1 | Data Catalog Risk Alignment | 4 - Data | Data owners ensure that data is identified and inventoried and any changes to the data landscape are automatically detected and included within the catalog. The data landscape must then be reviewed to identify potential risks related to data loss, attack, or any other unauthorized alteration and/or access | Data owners ensure that data is identified and inventoried and any changes to the data landscape are automatically detected and included within the catalog. The data landscape must then be reviewed to identify potential risks related to data loss, attack, or any other unauthorized alteration and/or access | Data assets are known and can therefore be collected, tagged, and protected according to risk levels in alignment with a prioritization framework, and encrypted for protection | * Data Analysis |\r\n| 4.2 | DoD Enterprise Data Governance | 4 - Data | DoD establishes enterprise data labeling/tagging and DAAS access control/sharing policies (e.g., SDS policy) that are enforceable. Developed enterprise standards ensure an appropriate level of interoperability between DoD Organizations. | DoD establishes enterprise data labeling/tagging and DAAS access control/sharing policies (e.g., SDS policy) that are enforceable at the field level | Decision rights and accountability framework ensure appropriate behavior in the valuation, creation, consumption, and control of data and analytics | * Define Data Tagging Standards * Interoperability Standards * Develop Software Defined Storage (SDS) Policy |\r\n| 4.3 | Data Labeling and Tagging | 4 - Data | Data owners label and tag data in compliance with DoD enterprise governance on labeling/tagging policy. As phases advance automation is used to meet scaling demands and provide better accuracy. | Data owners label and tag data in compliance with DoD enterprise governance on labeling/tagging policy | Establishing machine enforceable data access controls, risk assessment, and situational awareness require consistently and correctly labeled and tagged data | * Implement Data Tagging & Classification Tools * Manual Data Tagging Pt1 * Manual Data Tagging Pt2 * Automated Data Tagging & Support Pt1 * Automated Data Tagging & Support Pt2 |\r\n| 4.4 | Data Monitoring and Sensing | 4 - Data | Data owners will capture active metadata that includes information about the access, sharing, transformation, and use of their data assets. Data Loss Prevention (DLP) and Data Rights Management (DRM) enforcement point analysis is conducted to determine where tooling will be deployed. Data outside of DLP and DRM scope such as File Shares and Databases is actively monitored for anomalous and malicious activity using alternative tooling. | Data owners will capture active metadata that includes information about the access, sharing, transformation, and use of their data assets | Data in all states are detectable and observable | * DLP Enforcement Point Logging and Analysis * DRM Enforcement Point Logging and Analysis * File Activity Monitoring Pt1 * File Activity Monitoring Pt2 * Database Activity Monitoring * Comprehensive Data Activity Monitoring |\r\n| 4.5 | Data Encryption & Rights Management | 4 - Data | DoD organizations establish and implement a strategy for encrypting data at rest and in transit using Data Rights Management (DRM) tooling. The DRM solution utilizes data tags to determine protection and lastly integrates with ML and AI to automate protection | DoD organizations establish and implement a strategy for encrypting data at rest and in transit | Encrypting data in all states reduces the risk of unauthorized data access and improves data security | * Implement DRM and Protection Tools Pt1 * Implement DRM and Protection Tools Pt2 * DRM Enforcement via Data Tags and Analytics Pt1 * DRM Enforcement via Data Tags and Analytics Pt2 * DRM Enforcement via Data Tags and Analytics Pt3 |\r\n| 4.6 | Data Loss Prevention (DLP) | 4 - Data | DoD organizations utilize the identified enforcement points to deploy approved DLP tools and integrate tagged data attributes with DLP. Initially the DLP solution is put into a \"monitor-only\" mode to limit business impact and later using analytics is put into a \"prevent\" mode. Extended data tag attributes are used to feed the DLP solution and lastly integrate with ML and AI. | DoD organizations have identified enforcement points, deployed approved DLP tools at those enforcement points, and integrate tagged data attributes with DLP | Data breaches and data exfiltration transmissions are detected and mitigated | * Implement Enforcement Points * DLP Enforcement via Data Tags and Analytics Pt1 * DLP Enforcement via Data Tags and Analytics Pt2 * DLP Enforcement via Data Tags and Analytics Pt3 |\r\n| 4.7 | Data Access Control | 4 - Data | DoD organizations ensure appropriate access to and use of data based on the data and user/NPE/device properties. Software Defined Storage (SDS) is utilized to scale manage permissions to DAAS. Lastly the SDS solution(s) is integrated with DRM tooling improving protections. | DoD organizations ensure appropriate access to and use of data based on the data and user/NPE/device properties | Unauthorized entities, or any entity on an unauthorized device cannot access data; Zero Trust cybersecurity will be sufficiently strong to separate community of interest data access for data in the same classification | * Integrate DAAS Access w/ SDS Policy Pt1 * Integrate DAAS Access w/ SDS Policy Pt2 * Integrate DAAS Access w/ SDS Policy Pt3 * Integrate Solution(s) and Policy with Enterprise IDP Pt1 * Integrate Solution(s) and Policy with Enterprise IDP Pt2 * Implement SDS Tool and/or integrate with DRM Tool Pt1 * Implement SDS Tool and/or integrate with DRM Tool Pt2 |\r\n| 5.1 | Data Flow Mapping | 5 - Network and Environment | DoD organizations reconcile data flows by gathering, mapping, and visualizing network traffic data flows and patterns to ensure authorized access and protection for network and DAAS resources specifically tagging programmatic (e.g., API) access when possible. | DoD organizations reconcile data flows by gathering, mapping, and visualizing network traffic data flows and patterns to ensure authorized access and protection for network and DAAS resources | Sets the foundation for network segmentation and tighter access control by understanding data traffic on the network | * Define Granular Control Access Rules & Policies Pt1 * Define Granular Control Access Rules & Policies Pt2 |\r\n| 5.2 | Software Defined Networking (SDN) | 5 - Network and Environment | DoD organizations define API decision points and implement SDN programmable infrastructure to separate the control and data planes and centrally manage and control the elements in the data plane. Integrations are conducted with decision points and segmentation gateway to accomplish the plane separation. Analytics are then integrated to real time decision making for access to resources. | DoD organizations define API decision points and implement SDN programmable infrastructure to separate the control and data planes and centrally manage and control the elements in the data plane | Enables the control of packets to a centralized server, provides additional visibility into the network, and enables integration requirements | * Define SDN APIs* Implement SDN Programable Infrastructure * Segment Flows into Control, Management, and Data Planes * Network Asset Discovery & Optimization * Real-Time Access Decisions |\r\n| 5.3 | Macro Segmentation | 5 - Network and Environment | DoD organizations establish network boundaries and provide security against networked assets located within an environment by validating the device, user, or NPE on each attempt of accessing a remote resource prior to connection. | DoD organizations establish network perimeters and provide security against devices located within an environment by validating the device, user, or NPE on each attempt of accessing a remote resource prior to connection | Network segmentation is defined by a large perimeter to enable resource segmentation by function and user type | * Datacenter Macro segmentation * B/C/P/S Macro segmentation |\r\n| 5.4 | Micro Segmentation | 5 - Network and Environment | DoD organizations define and document network segmentation based on identity and / or application access in their virtualized and/or cloud environments. Automation is used to apply policy changes through programmatic (e.g., API) approaches. Lastly where possible organizations will utilize host-level process micro segmentation. | DoD organizations define and document network segmentation based on identity and / or application access in their virtualized cloud environments | Network segmentation enabled by narrower and specific segmentation in a virtualized environment via identity and / or application access, allowing for improved protection of data in transit as it crosses system boundaries (e.g., in a coalition environment, system high boundaries) and supported dynamic, real-time access decisions and policy changes | * Implement Micro segmentation * Application & Device Micro segmentation * Process Micro segmentation * Protect Data In Transit |\r\n| 6.1 | Policy Decision Point (PDP) & Policy Orchestration | 6 - Automation and Orchestration | DoD organizations initially collect and document all rule based policies to orchestrate across the security stack for effective automation; DAAS access procedures and policies will be defined, implemented, and updated. Organizations mature this capability by establishing PDPs and PEPs (including the Next Generation Firewall) to make DAAS resource determinations and enable, monitor, and terminate connections between a user/device and DAAS resources according to predefined policy. | DoD organizations initially collect and document all rule based policies to orchestrate across the security stack for effective automation; DAAS access procedures and policies will be defined, implemented, and updated. Organizations mature this capability by establishing PDPs and PEPs (including the Next Generation Firewall) to make DAAS resource determinations and enable, monitor, and terminate connections between a user/device and DAAS resources according to predefined policy | PDPs and PEPs ensure proper implementation of DAAS access policies to users or endpoints that are properly connected (or denied access) to requested resources | * Policy Inventory & Development * Organization Access Profile * Enterprise Security Profile Pt1 * Enterprise Security Profile Pt2 |\r\n| 6.2 | Critical Process Automation | 6 - Automation and Orchestration | DoD organizations employ automation methods, such as RPA, to address repetitive, predictable tasks for critical functions such as data enrichment, security controls, and incident response workflows according to system security engineering principles. | DoD organizations employ automation methods, such as RPA, to address repetitive, predictable tasks for critical functions such as data enrichment, security controls, and incident response workflows according to system security engineering principles | Response time and capability is increased with orchestrated workflows and risk management processes | * Task Automation Analysis * Enterprise Integration & Workflow Provisioning Pt1 * Enterprise Integration & Workflow Provisioning Pt2 |\r\n| 6.3 | Machine Learning | 6 - Automation and Orchestration | DoD organizations employ ML to execute (and enhance execution of) critical functions such as incident response, anomaly detection, user baselining, and data tagging. | DoD organizations employ ML to execute (and enhance execution of) critical functions such as incident response, anomaly detection, user baselining, and data tagging | Response time and capability is increased with orchestrated workflows and risk management processes | * Implement Data Tagging & Classification ML Tools |\r\n| 6.4 | Artificial Intelligence | 6 - Automation and Orchestration | DoD organizations employ AI to execute (and enhance execution of) critical functions - particularly risk and access determinations and environmental analysis. | DoD organizations employ AI to execute (and enhance execution of) critical functions - particularly risk and access determinations and environmental analysis | Response time and capability is increased with orchestrated workflows and risk management processes | * Implement AI automation tools * AI Driven by Analytics decides A&O modifications |\r\n| 6.5 | Security Orchestration, Automation & Response (SOAR) | 6 - Automation and Orchestration | DoD organizations achieve initial operational capability of security technologies to orchestrate and automate policies (e.g., PEPs and PDPs) and rulesets to improve security operations, threat and vulnerability management, and security incident response by ingesting alert data, triggering playbooks for automated response and remediation. | DoD organizations achieve IOC of security technologies to orchestrate and automate policies (e.g., PEPs and PDPs) and rulesets to improve security operations, threat and vulnerability management, and security incident response by ingesting alert data, triggering playbooks for automated response and remediation | Pre-defined playbooks from collection to incident response and triage enables initial process automation that accelerates a security team's decision and response speed | * Response Automation Analysis * Implement SOAR Tools * Implement Playbooks |\r\n| 6.6 | API Standardization | 6 - Automation and Orchestration | DoD establishes and enforces enterprise-wide programmatic interface (e.g., API ) standards; all non-compliant APIs are identified and replaced. | DoD establishes and enforces enterprise-wide API standards; all non-compliant APIs are identified and replaced | Standardizing APIs across the department improves application interfaces, enabling orchestration, and enhancing interoperability | * Tool Compliance Analysis * Standardized API Calls & Schemas Pt1 * Standardized API Calls & Schemas Pt2 |\r\n| 6.7 | Security Operations Center (SOC) & Incident Response (IR) | 6 - Automation and Orchestration | In the event a computer network defense service provider (CNDSP) does not exist, DoD organizations define and stand up security operations centers (SOC) to deploy, operate, and maintain security monitoring, protections and response for DAAS; SOCs provide security management visibility for status (upward visibility) and tactical implementation (downward visibility). Workflows within the SOC are automated using automation tooling and enrichment occurs between service providers and technologies. | In the event a CNDSP does not exist, DoD organizations define and stand up SOCs to deploy, operate, and maintain security monitoring, protections and response for DAAS; SOCs provide security management visibility for status (upward visibility) and tactical implementation (downward visibility) | Standardized, coordinated, and accelerated incident response and investigative efforts | * Workflow Enrichment Pt1 * Workflow Enrichment Pt2 * Workflow Enrichment Pt3 * Automated Workflow |\r\n| 7.1 | Log All Traffic (Network, Data, Apps, Users) | 7 - Visibility and Analytics | DoD organizations collect and process all logs including network, data, application, device, and user logs and make those logs available to the appropriate Computer Network Defense Service Provider (CNDSP) or security operations center (SOC). Logs and events follow a standardized format and rules/analytics are developed as needed. | DoD organizations collect and process all logs including network, data, application, device, and user logs and make those logs available to the appropriate Computer Network Defense Service Provider (CNDSP) or SOC | Foundational to the development of automated hunt and incident response playbooks | * Scale Considerations * Log Parsing * Log Analysis |\r\n| 7.2 | Security Information and Event Management (SIEM) | 7 - Visibility and Analytics | Computer Network Defense Service Provider (CNDSP) or security operations centers (SOC) monitor, detect, and analyze data logged into a security information and event management (SIEM) tool. User and device baselines are created using security controls and integrated with the SIEM. Alerting within the SIEM is matured over the phases to support more advanced data points (e.g., Cyber Threat Intel, Baselines, etc.) | CNDSPs/SOCs monitor, detect, and analyze data logged into a security information and event management (SIEM) tool | Processing and exploiting data in the SIEM enables effective security analysis of anomalous user behavior, alerting, and automation of relevant incident response to common threat events | * Threat Alerting Pt1 * Threat Alerting Pt2 * Threat Alerting Pt3 * Asset ID & Alert Correlation * User/Device Baselines |\r\n| 7.3 | Common Security and Risk Analytics | 7 - Visibility and Analytics | Computer Network Defense Service Provider (CNDSP) or security operations centers (SOC) employ data tools across their enterprises for multiple data types to unify data collection and examine events, activities, and behaviors. | CNDSPs/SOCs employ big data tools across their enterprises for multiple data types to unify data collection and examine events, activities, and behaviors | Analysis integrated across multiple data types to examine event, activities, and behaviors | * Implement Analytics Tools * Establish User Baseline Behavior |\r\n| 7.4 | User and Entity Behavior Analytics | 7 - Visibility and Analytics | DoD organizations initially employ analytics to profile and baseline activity of users and entities and to correlate user activities and behaviors and detect anomalies. Computer Network Defense Service Provider (CNDSP) or security operations centers (SOC) mature this capability through the employment of advanced analytics to profile and baseline activity of users and entities and to correlate user activities and behaviors, and detect anomalies. | DoD organizations initially employ analytics to profile and baseline activity of users and entities and to correlate user activities and behaviors, and detect anomalies. CNDSPs/SOCs mature this capability through the employment of advanced analytics to profile and baseline activity of users and entities and to correlate user activities and behaviors, and detect anomalies | Advanced analytics support detection of anomalous users, devices, and NPE actions and advanced threats | * Baseline & Profiling Pt1 * Baseline & Profiling Pt2 * UEBA Baseline Support Pt1 * UEBA Baseline Support Pt2 |\r\n| 7.5 | Threat Intelligence Integration | 7 - Visibility and Analytics | Computer Network Defense Service Provider (CNDSP) or security operations centers (SOC) integrate threat intelligence information and streams about identities, motivations, characteristics, and tactics, techniques and procedures (TTPs) with data collected in the SIEM. | CNDSPs/SOCs integrate threat intelligence information and streams about identities, motivations, characteristics, and tactics, techniques and procedures (TTPs) with data collected in the SIEM | Integrating threat intelligence into other SIEM data enhances monitoring efforts and incident response | * Cyber Threat Intelligence Program Pt1 * Cyber Threat Intelligence Program Pt2 |\r\n| 7.6 | Automated Dynamic Policies | 7 - Visibility and Analytics | DoD Organization ML & AI solutions dynamically and automatically update security profiles and device configuration through continuous security posture monitoring, risk and confidence scoring, and automated patch management. | CNDSPs/SOCs dynamically and automatically update security profiles and device configuration through continuous security posture monitoring, risk and confidence scoring, and automated patch management | Users and NPEs are denied access based on automated, real-time security profiles based on external conditions and evolving risk and confidence scores | * AI-enabled Network Access * AI-enabled Dynamic Access Control |",
+ "style": "info"
+ },
+ "conditionalVisibility": {
+ "parameterName": "DoDZT",
+ "comparison": "isEqualTo",
+ "value": "Capabilities"
+ },
+ "name": "ZTCapabilities"
+ },
+ {
+ "type": 1,
+ "content": {
+ "json": "## DoD Zero Trust Activities (152) ##\r\n\r\n| ID# | Activity Name | Associated Capability | Phase | Duration (months) | Descriptions | Outcomes | Controls | Predecessor(s) | Successor(s) |\r\n|-------|---------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|-----------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|\r\n| 1.1.1 | Inventory User | 1.1 User Inventory | Target Level ZT | 25.9 | DoD Organizations establish and update a user inventory manually if needed, preparing for automated approach in later stages. Accounts both centrally managed by an IdP/ICAM and locally on systems will be identified and inventoried. Privileged accounts will be identified for future audit and both standard and privileged user accounts local to applications and systems will be identified for future migration and/or decommission. | Identified Managed Regular Users; Identified Managed Privileged Users; Identified applications using their own user account management for non-administrative and administrative accounts | | | |\r\n| 1.2.1 | Implement App Based Permissions per Enterprise | 1.2 Conditional User Access | Target Level ZT | 17.7 | The DoD enterprise working with the Organizations establishes a basic set of user attributes for authentication and authorization. These are integrated with the βEnterprise Identity Life-Cycle Management Pt1β activity process for a complete enterprise standard. The enterprise Identity, Credential and Access Management (ICAM) solution is enabled for self-service functionality for adding/updating attributes within the solution. Remaining Privileged Access Management (PAM) activities are fully migrated to PAM solution. | Enterprise roles/attributes needed for user authorization to application functions and/or data have been registered with enterprise ICAM; DoD Enterprise ICAM has self-service attribute/role registration service that enables application owners to add attributes or use existing enterprise attributes; Privileged activities are fully migrated to PAM | | | |\r\n| 1.2.2 | Rule Based Dynamic Access Pt1 | 1.2 Conditional User Access | Target Level ZT | 22.1 | DoD Organizations utilize the rules from the βPeriodic Authenticationβ activity to build basic rules enabling and disabling privileges dynamically. High-risk user accounts utilize the PAM solution to move to dynamic privileged access using Just-In-Time access and Just-Enough Administration methods. | Access to applicationβs/serviceβs functions and/or data are limited to users with appropriate enterprise attributes; All possible applications use JIT/JEA permissions for administrative users | | Single Authentication | Rule Based Dynamic Access Pt2; AI- enabled Network Access |\r\n| 1.2.3 | Rule Based Dynamic Access Pt2 | 1.2 Conditional User Access | Advanced ZT | 15.5 | DoD Organizations expand the development of rules for dynamic access decision making accounting for risk. Solutions used for dynamic access are integrated with cross pillar Machine Learning and Artificial Intelligence functionality enabling automated rule management. | Components and services are fully utilizing rules to enable dynamic access to applications and services; Technology utilized for Rule Based Dynamic Access supports integration with AI/ML tooling | | Rule Based Dynamic Access Pt1; File Activity Monitoring Pt2 | |\r\n| 1.2.4 | Enterprise Gov't roles and Permissions Pt1 | 1.2 Conditional User Access | Advanced ZT | 11.6 | DoD Organizations federate remaining user and group attributes as appropriate to the Enterprise Identity, Credential and Access Management (ICAM) solution. The updated attribute set is used to create universal roles for Organizations to use. Core functions of the Identity Provider (IdP) and Identity, Credential and Access Management (ICAM) solutions are migrated to cloud services and/or environments enabling improved resilience and performance. | Component attribute and role data repository federated with enterprise ICAM; Cloud-based enterprise IdP can be used by cloud and on-premises applications; A standardized set of roles and permissions are created and aligned to attributes | | | Enterprise Gov't roles and Permissions Pt2 |\r\n| 1.2.5 | Enterprise Gov't roles and Permissions Pt2 | 1.2 Conditional User Access | Advanced ZT | 11.2 | DoD Organizations move all possible functions of the Identity Provider (IdP) and Identity, Credential and Access Management (ICAM) solutions to cloud environments. Enclave/DDIL environments local capabilities to support disconnected functions but ultimately are managed by the centralized Identity, Credential and Access Management (ICAM) solutions. Updated roles are now mandated for usage and exceptions are reviewed following a risk-based approach. | Majority of components utilize cloud IdP functionality Where possible on-prem IdP is decommissioned; Permissions and roles are mandated for usage when evaluating attributes | | Enterprise Gov't roles and Permissions Pt1 | |\r\n| 1.3.1 | Organizational MFA/IDP | 1.3 Multi-Factor Authentication (MFA) | Target Level ZT | 10.6 | DoD Organizations procure and implement a centralized Identity Provider (IdP) solution and Multi-Factor (MFA) solution. The IdP and MFA solution may be combined in a single application or separated as needed assuming automated integration is supported by both solutions. Both IdP and MFA support integration with the Enterprise PKI capability as well enabling key pairs to be signed by the trusted root certificate authorities. Mission/Task-Critical applications and services are utilizing the IdP and MFA solution for management of users and groups. | Component is using IdP with MFA for critical applications/services; Components have implemented an Identity Provider (IdP) that enables DoD PKI multifactor authentication; Organizational Standardized PKI for critical services | | | Alternative Flexible MFA Pt1 |\r\n| 1.3.2 | Alternative Flexible MFA Pt1 | 1.3 Multi-Factor Authentication (MFA) | Advanced ZT | 17.4 | DoD Organizationβs Identity Provider (IdP) supports alternative methods of multi-factor authentication complying with Cyber Security requirements (e.g., FIPS 140-2, FIPS 197, etc.). Alternative tokens can be used for application-based authentication. Multi-Factor options support Biometric capability and can be managed using a self-service approach. Where possible multi-factor provider(s) is moved to cloud services instead of being hosted on-premise. | IdP provides user self-service alternative token; IdP provides alt token MFA for approved applications per policy | | Organizational MFA/IDP | Alternative Flexible MFA Pt2 |\r\n| 1.3.3 | Alternative Flexible MFA Pt2 | 1.3 Multi-Factor Authentication (MFA) | Advanced ZT | 14.6 | Alternative tokens utilize user activity patterns from cross pillar activities such as \"User Activity Monitoring (UAM) and User & Entity Behavior Analytics (UEBA)\" to assist with access decision making (e.g., not grant access when pattern deviation occurs). This functionality is further extended onto Biometric enabled alternative tokens as well. | User Activity Patterns Implemented | | Alternative Flexible MFA Pt1 | |\r\n| 1.4.1 | Implement System and Migrate Privileged Users Pt1 | 1.4 Privileged Access Management (PAM) | Target Level ZT | 12.4 | DoD Organizations procure and implement a Privileged Access Management (PAM) solution support all critical privileged use cases. Application/Service integration points are identified to determine status of support for the PAM solution. Applications/Services that easily integrate with PAM solution are transitioned over to using solution versus static and direct privileged permissions. | Privilege Access Management (PAM) tooling is implemented; applications and devices that support and do not support PAM tools identified; Applications that support PAM, now use PAM for controlling emergency/built-in accounts | MA-5 (1) individuals without appropriate access | | Implement System and Mitigate Privileged Users Pt2 |\r\n| 1.4.2 | Implement System and Migrate Privileged Users Pt2 | 1.4 Privileged Access Management (PAM) | Target Level ZT | 14.4 | DoD Organizations utilize the inventory of supported and unsupported Applications/Services for integration with privileged access management (PAM) solution to extend integrations. PAM is integrated with the more challenging Applications/Services to maximize PAM solution coverage. Exceptions are managed in a risk-based methodical approach with the goal of migration off and/or decommissioning Applications/Services that do not support PAM solution. | Privileged activities are migrated to PAM and access is fully managed | | Implement System and Mitigate Privileged Users Pt1 | Real time Approvals & JIT/JEA Analytics Pt1 |\r\n| 1.4.3 | Real time Approvals & JIT/JEA Analytics Pt1 | 1.4 Privileged Access Management (PAM) | Advanced ZT | 12.5 | Identification of necessary attributes (Users, Groups, etc.) are automated and integrated into the Privileged Access Management (PAM) solution. Privilege access requests are migrated to the PAM solution for automated approvals and denials. | Identified accounts, applications, devices, and data of concern (of greatest risk to DoD mission); Using PAM tools, applied JIT/JEA access to high-risk accounts; Privileged access requests are automated as appropriate | IA-12 (4) in-person validation and verification; AC-3 (14) individual access; CM-8 (4) accountability information; | Implement System and Mitigate Privileged Users Pt2 | Real time Approvals & JIT/JEA Analytics Pt2 |\r\n| 1.4.4 | Real time Approvals & JIT/JEA Analytics Pt2 | 1.4 Privileged Access Management (PAM) | Advanced ZT | 8.9 | DoD Organizations integrate User & Entity Behavior Analytics (UEBA) and User Activity Monitoring (UAM) solutions with the Privileged Access Management (PAM) solution providing user pattern analytics for decision making. | UEBA or similar analytic system integrated with PAM tools for JIT/JEA account approvals | IA-4 (5) dynamic management; AC-2 (6) dynamic account management | Real time Approvals & JIT/JEA Analytics Pt1 | |\r\n| 1.5.1 | Organizational Identity Life-Cycle Management | 1.5 Identity Federation & User Credentialing | Target Level ZT | 14.8 | DoD Organizations establish a process for life cycle management of users both privileged and standard. Utilizing the Organizational Identity Provider (IdP) the process is implemented and followed by the maximum number of users. Any users who fall outside of the standard process are approved through risk-based exceptions to be evaluated regularly for decommission. | Standardized Identity Lifecycle Process | MA-5 (1) individuals without appropriate access | | Enterprise Identity Life-cycle Management Pt1 |\r\n| 1.5.2 | Enterprise Identity Life- Cycle Management Pt1 | 1.5 Identity Federation & User Credentialing | Target Level ZT | 11.7 | The DoD Enterprise works with Organizations to review and align the existing Identity Lifecycle Processes, policy, and standards. A finalized agreed upon policy and supporting process are developed and followed by the DoD Organizations. Utilizing the centralized or federated Identity Provider (IdP) and Identity & Access Management (IdAM) solutions, DoD Organizations implement the Enterprise Lifecycle Management process for the maximum number of identities, groups, and permissions. Exceptions to the policy are managed in a risk based methodical approach. | Automated Identity Lifecycle Processes; Integrated with Enterprise ICAM process and tools | | Organization Identity Life-cycle Management | Enterprise Identity Life-cycle Management Pt2 |\r\n| 1.5.3 | Enterprise Identity Life- Cycle Management Pt2 | 1.5 Identity Federation & User Credentialing | Advanced ZT | 12.8 | DoD Organizations further integrate the critical automation functions of the Identity Provider (IdP) and Identity, Credential and Access Management (ICAM) solutions following the Enterprise Lifecycle Management process to enable Enterprise automation and analytics. Identity Lifecycle Management primary processes are integrated into the cloud-based Enterprise ICAM solution. | Integration w/ Critical IDM/IDP functions; Primary ILM functions are cloud based | | Enterprise Identity Life-cycle Management Pt1 | Enterprise Identity Life-cycle Management Pt3 |\r\n| | | | | | | | | | |\r\n| 1.5.4 | Enterprise Identity Life- Cycle Management Pt3 | 1.5 Identity Federation & User Credentialing | Advanced ZT | 9.2 | DoD Organizations integrate remaining Identity Lifecycle Management processes with the Enterprise Identity, Credential and Access Management solution. Enclave/DDIL environments while still authorized to operate integrate with the Enterprise ICAM using local connectors to the cloud environment. | All ILM functions moved to cloud as appropriate; Integration with all IDM/IDP functions | | Enterprise Identity Life-cycle Management Pt2 | |\r\n| 1.6.1 | Implement User & Entity Behavior Activity (UEBA) and User Activity Monitoring (UAM) Tooling | 1.6 Behavioral, Contextual ID, and Biometrics | Target Level ZT | 15.9 | DoD Organizations procure and implement User & Entity Behavior Analytics (UEBA) and User Activity Monitoring (UAM) solutions. Initial integration point with Enterprise IdP is completed enabling future usage in decision making. | UEBA and UAM functionality is implemented for Enterprise IDP | | | Establish User Baseline Behavior; Baseline & Profiling Pt1 |\r\n| 1.6.2 | User Activity Monitoring Pt1 | 1.6 Behavioral, Contextual ID, and Biometrics | Advanced ZT | 13.5 | DoD Organizations integrate User & Entity Behavior Analytics (UEBA) and User Activity Monitoring (UAM) solutions with Organizational Identity Providers (IdP) for extended visibility as needed. Analytics and data generated by UEBA and UAM for critical applications/services are integrated with the Just-in-Time and Just-Enough-Access solution improving decision making further. | UEBA is integrated with Org IDPs as appropriate; UEBA is integrated with JIT/JEA for critical services | | User/Device Baselines | User Activity Monitoring Pt2 |\r\n| 1.6.3 | User Activity Monitoring Pt2 | 1.6 Behavioral, Contextual ID, and Biometrics | Advanced ZT | 11.2 | DoD Organizations continue the analytics usage from User & Entity Behavior Analytics (UEBA) and User Activity Monitoring (UAM) solutions by using generated data for all monitored applications and services when decision making occurs in the Just-in-Time and Just- Enough-Access solution. | UEBA/Entity Monitoring is integrated with JIT/JEA for all services | | User Activity Monitoring Pt1 | Real-Time Access Decisions; AI- enabled Dynamic Access Control; Enrich Attributes for Resource Authorization Pt1; AI-enabled Network Access |\r\n| 1.7.1 | Deny User by Default Policy | 1.7 Least Privileged Access | Target Level ZT | 22.7 | DoD Organizations audit internal user and group usage for permissions and revoke permissions when possible. This activity includes the revocation and/or decommission of excess permissions and access for application/service-based identities and groups. Where possible static privileged users are decommissioned or reduced permissions preparing for future rule/dynamic based access. | Applications updated to deny by default to functions/data requiring specific roles/attributes for access; Reduced default permissions levels are implemented; Applications/services have reviewed/audited all privileged users and removed those users who do not need that level of access; Applications' identify functions and data requiring specific roles/attributes for access | AC-17 (10) authenticate remote commands; SC-7 (15) networked privileged access | | |\r\n| 1.8.1 | Single Authentication | 1.8 Continuous Authentication | Target Level ZT | 19.2 | DoD Organizations employ basic authentication processes to authenticate users and NPEs at least once per session (e.g., logon). Importantly users being authenticated are managed by the parallel activity βOrganizational MFA/IDPβ with the Organizational Identity Provider (IdP) versus using application/service-based identities and groups. | Authentication implemented across applications per session | | | Periodic Authentication; Rule Based Dynamic Access Pt1 |\r\n| 1.8.2 | Periodic Authentication | 1.8 Continuous Authentication | Target Level ZT | 25.4 | DoD Organizations enable period authentication requirements for applications and services. Traditionally these are based on duration and/or duration timeout but other period based analytics can be used to mandate re-authentication of user sessions. | Authentication implemented multiple times per session based on security attributes | | Single Authentication | Continuous Authentication Pt1; AI- enabled Network Access |\r\n| 1.8.3 | Continuous Authentication Pt 1 | 1.8 Continuous Authentication | Advanced ZT | 16.8 | DoD Organizationsβ applications/service utilize multiple session authentications based on security attributes and access requested. Privilege changes and associational transaction requests required additional levels of authentication such as Multi-Factor Authentication (MFA) pushes to users. | Transaction authentication implemented per session based on security attributes | | Periodic Authentication | Continuous Authentication Pt2 |\r\n| 1.8.4 | Continuous Authentication Pt 2 | 1.8 Continuous Authentication | Advanced ZT | 16.8 | DoD Organizations continue usage of transaction-based authentication to include integration such as user patterns. | Transaction authentication implemented per session based on security attributes | | Continuous Authentication Pt1 | Real-Time Access Decisions; AI- enabled Dynamic Access Control |\r\n| 1.9.1 | Enterprise PKI/IDP Pt1 | 1.9 Integrated ICAM Platform | Target Level ZT | 12.4 | The DoD Enterprise works with Organizations to implement Enterprise Public Key Infrastructure (PKI) and Identity Provider (IdP) solutions in a centralized and/or federated fashion. The Enterprise PKI solution utilizes a single or set of Enterprise level Root Certificate Authorities (CA) which can then be trusted by Organizations to build Intermediate CAβs off. The Identity Provider solution may either be a single solution or federated set of Organizational IdPs with standard level of access across Organizations and standardized set of attributes. Organizationsβ IdPs and PKI Certificated Authorities are integrated with the Enterprise IdP and PKI solutions. | Components are using IdP with MFA for all applications/services; Organizational MFA/PKI integrated with Enterprise MFA/PKI; Organizational Standardized PKI for all services | | | Enterprise PKI/IDP Pt2 |\r\n| 1.9.2 | Enterprise PKI/IDP Pt2 | 1.9 Integrated ICAM Platform | Advanced ZT | 27.2 | DoD Organizations enable Biometric support in the Identity Provider (IdP) for mission/task-critical applications and services as appropriate. Biometric functionality is moved from Organizational solutions to the Enterprise. Organizational Multi-Factor (MFA) and Public Key Infrastructure (PKI) is decommissioned and migrated to the Enterprise as appropriate. | Critical Organizational Services Integrated w/ Biometrics; Decommission organizational MFA/PKI as appropriate in leu of enterprise MFA/PKI; Enterprise Biometric Functions Implemented | | Enterprise PKI/IDP Pt1 | Enterprise PKI/IDP Pt3 |\r\n| 1.9.3 | Enterprise PKI/IDP Pt3 | 1.9 Integrated ICAM Platform | Advanced ZT | 30.0 | DoD Organizations integrate the remaining applications/services with Biometrics functionalities. Alternative Multi-Factor (MFA) tokens can be used. | All Organizational Services Integrate w/ Biometrics | | Enterprise PKI/IDP Pt2 | |\r\n| 2.1.1 | Device Health Tool Gap Analysis | 2.1 Device Inventory | Target Level ZT | 9.8 | DoD Organizations develop a manual inventory of devices within the environment. Device attributes tracked in the inventory enable functionality outlined in the ZTA target level. | Manual inventory of devices is created per organization w/ owners | | | |\r\n| 2.1.2 | NPE/PKI, Device under Management | 2.1 Device Inventory | Target Level ZT | 22.8 | DoD Organizations utilize the DoD Enterprise PKI solution/service to deploy x509 certificates to all supported and managed devices. Additional other Non-Person Entities (NPEs) that support x509 certificates are assigned in the PKI and/or IdP systems. | Non-person entities are managed via Org PKI and Org IDP | | Enterprise Device Management Pt1 | Implement C2C/Compliance Based Network Authorization Pt1; Enterprise PKI Pt1; Deny Device by Default Policy |\r\n| 2.1.3 | Enterprise IDP Pt1 | 2.1 Device Inventory | Target Level ZT | 12.8 | The DoD Enterprise Identity Provider (IdP) either using a centralized technology or federated organizational technologies integrates Non- Person Entities (NPEs) such as devices and service accounts. Integration is tracked in the Enterprise Device Management solution when applicable as to whether it is integrated or not. NPEs not able to be integrated with the IdP are either marked for retirement or excepted using a risk based methodical approach. | NPEs including devices are integrated with Enterprise IDP | IA-3 (4) device attestation | | Enterprise IDP Pt2 |\r\n| 2.1.4 | Enterprise IDP Pt2 | 2.1 Device Inventory | Advanced ZT | 8.8 | The DoD Enterprise Identity Provider (IdP) either using a centralized technology or federated organizational technologies adds additional dynamic attributes for NPEs such as location, usage patterns, etc. | Conditional device attributes are part of the IdP profile | | Enterprise IDP Pt1 | |\r\n| 2.2.1 | Implement C2C/Compliance Based Network Authorization Pt1 | 2.2 Device Detection and Compliance | Target Level ZT | 9.4 | The DoD Enterprise working with the Organizations develops a policy, standard and requirements for Comply to Connect. Once agreement is reached solution procurement is started, a vendor(s) is selected, and implementation begins with base level functionality in ZT Target environments (low risk). Base level checks are implemented in the new Comply to Connection solution enabling the ability to meet ZTA target functionalities. | C2C is enforced at the enterprise level for low risk and testing environments; Basic devices checks are implemented using C2C | AC-20 (5) network accessible storage devices β prohibited use | NPE/PKI Device Under Management; Integrate NextGen AV Tools with C2C; Managed and Limited BYOD & IOT Support; Implement Asset, Vulnerability and Patch Management Tools | Implement C2C/Compliance Based Network Authorization Pt2 |\r\n| 2.2.2 | Implement C2C/Compliance Based Network Authorization Pt2 | 2.2 Device Detection and Compliance | Advanced ZT | 18.2 | DoD Organizations expand the deployment and usage of Comply to Connect to all supported environments required to meet ZT advanced functionalities. Comply to Connect teams integrate their solution(s) with the Enterprise IdP and Authorization Gateways to better manage access and authorizations to resources. | C2C is enforced in all supported environments; Advanced devices checks are completed and integrated with dynamic access (Enterprise IDP / ZTNA) | | Implement C2C/Compliance Based Network Authorization Pt1; Fully Integrate Device Security Stack w/ C2C as appropriate | Real-Time Access Decisions |\r\n| 2.3.1 | Entity Activity Monitoring Pt1 | 2.3 Device Authorization w/ Real Time Inspection | Advanced ZT | 16.4 | Using the developed User and Device baselines, DoD Organizations utilize the implemented User and Entity Behavioral Activity (UEBA) solution to integrate baselines. UEBA device attributes and baselines are available to be used for device authorization detections. | UEBA attributes are integrated for device baselining; UEBA attributes are available for usage with device access | | User/Device Baselines; Implement User & Entity Behavior Activity (UEBA); User Activity Monitoring Tooling | Entity Activity Monitoring Pt2 |\r\n| 2.3.2 | Entity Activity Monitoring Pt2 | 2.3 Device Authorization w/ Real Time Inspection | Advanced ZT | 16.7 | DoD Organizations utilize the User and Entity Behavioral Activity (UEBA) solution with network access solutions to mandate UEBA attributes (e.g., device health, logon patterns, etc.) for accessing environments and resources. | UEBA attributes are mandated for device access | | Entity Activity Monitoring Pt1 | Real-Time Access Decisions; AI- enabled Dynamic Access Control; Enrich Attributes for Resource Authorization Pt1; AI-enabled Network Access |\r\n| 2.3.3 | Implement Application Control & File Integrity Monitoring (FIM) Tools | 2.3 Device Authorization w/ Real Time Inspection | Target Level ZT | 16.2 | DoD Organizations procure and implement File Integrity Monitoring (FIM) and Application Control solutions. FIM continues development and expansion of monitoring in the Data Pillar. Application Control is deployed to low-risk environments in a monitor only mode establishing baseline allowances. Application control teams being integration with the Enterprise and Organization PKI environments utilize certificates for application allowances. NextGen AV covers all possible services and applications. | AppControl and FIM tooling is implemented on all critical services/applications; EDR tooling covers maximum amount of services/applications; AppControl and FIM data is sent to C2C as needed | | | |\r\n| 2.3.4 | Integrate NextGen AV Tools with C2C | 2.3 Device Authorization w/ Real Time Inspection | Target Level ZT | 18.5 | DoD Organizations procure and implement Next Generation Anti-Virus & Anti-Malware solutions as needed. These solutions are integrated with the initial deployment of Comply to Connect for baseline status checks of signatures, updates, etc. | Critical NextGen AV data is being sent to C2C for checkslll; NextGen AV tooling is implemented on all critical services/applicationslll | | | Implement C2C/Compliance Based Network Authorization Pt1 |\r\n| 2.3.5 | Fully Integrate Device Security stack with C2C as appropriate | 2.3 Device Authorization w/ Real Time Inspection | Advanced ZT | 13.3 | DoD Organizations continue the deployment of Application Control to all environments and in prevention mode. File Integrity Monitoring (FIM) and Application Controls analytics are integrated into Comply to Connect for expanded access decision making data points. Comply to Connect analytics are evaluated for further device/endpoint security stack data points such as UEDM and are integrated as necessary. | AppControl and FIM deployment is expanded to all necessary services/applications; Remaining data from Device Security tooling is implemented with C2C | | | Implement C2C/Compliance Based Network Authorization Pt2; Managed and Full BYOD & IOT Support Pt2 |\r\n| 2.3.6 | Enterprise PKI Pt1 | 2.3 Device Authorization w/ Real Time Inspection | Advanced ZT | 22.7 | The DoD Enterprise Public Key Infrastructure (PKI) is expanded to include the addition of NPE and device certificates. NPEs and device that do not support PKI certificates are marked for retirement and decommission starts. | Devices that are unable to have certificates are phased out and/or moved to minimal access environments; All devices and NPEs have certs installed for authentication in the Enterprise PKI | | Implement UEDM or equivalent Tools; NPE/PKI Device Under Management | Enterprise PKI Pt2 |\r\n| 2.3.7 | Enterprise PKI Pt2 | 2.3 Device Authorization w/ Real Time Inspection | Advanced ZT | 10.5 | DoD Organizations utilize certificates for device authentication and machine to machine communications. Unsupported devices complete retirement and exceptions are approved using a risk based methodical approach. | Devices are required to authenticate to communicate with other services and devices | | Enterprise PKI Pt1 | |\r\n| 2.4.1 | Deny Device by Default Policy | 2.4 Remote Access | Target Level ZT | 9.6 | DoD Organizations block all unmanaged remote and local device access to resources. Compliant managed devices are provided risk based methodical access following ZTA target level concepts. | Components can block device access by default to resources (apps/data) and explicitly allow compliant devices per policy; Remote Access is enabled following a \"deny device by default policy\" approach | | NPE/PKI Device Under Management | |\r\n| 2.4.2 | Managed and Limited BYOD & IOT Support | 2.4 Remote Access | Target Level ZT | 39.7 | DoD Organizations utilize Unified Endpoint and Device Management (UEDM) and similar solutions to ensure that managed Bring Your Own Device (BYOD) and Internet of Things (IoT) devices are fully integrated with Enterprise IdP enable user and device-based authorization are supported. Device access for all applications requires dynamic access policies. | All applications require dynamic permissions access for devices; BYOD and IOT device permissions are baselined and integrated with Enterprise IDP | | | Implement C2C/Compliance Based Network Authorization Pt1; Managed and Full BYOD & IOT Support Pt1 |\r\n| 2.4.3 | Managed and Full BYOD & IOT Support Pt1 | 2.4 Remote Access | Advanced ZT | 24.7 | DoD Organizations utilize Unified Endpoint and Device Management (UEDM) and similar solutions to enable access for managed and approved devices to Mission and Operational Critical services/applications using dynamic access policies. BYOD and Internet of Things (IoT) devices are required to meet standard baseline checks before authorization. | Only BYOD and IOT devices that meet mandated configuration standards allowed to access resources; Critical Services require dynamic access for devices | | Managed and Limited BYOD & IOT Support | Managed and Full BYOD & IOT Support Pt2 |\r\n| 2.4.4 | Managed and Full BYOD & IOT Support Pt2 | 2.4 Remote Access | Advanced ZT | 24.6 | DoD Organizations utilize Unified Endpoint and Device Management (UEDM) and similar solutions to enable access for unmanaged devices meeting device checks and standard baselines. All possible services/applications are integrated to allow access to managed devices. Unmanaged devices are integrated with services/applications based on risk driven methodical authorization approach. | All possible services require dynamic access for deviceslll | | Fully Integrate Device Security Stack w/ C2C as appropriate; Managed and Full BYOD & IOT Support Pt1 | |\r\n| 2.5.1 | Implement Asset, Vulnerability and Patch Management Tools | 2.5 Partially & Fully Automated Asset, Vulnerability and Patch Management | Target Level ZT | 18.4 | DoD Organizations implement solution(s) for managing assets/devices configurations, vulnerabilities, and patches. Using minimum compliance standards (e.g., STIGs, etc.) teams can confirm or deny managed device compliance. As part of the procurement and implementation process for solutions, APIs or other programmatic interfaces will be in scope for future levels of automation and integration. | Components can confirm if devices meet minimum compliance standards or not; Components have asset management, vulnerability, and patching systems with APIs that will enable integration across the systems | | | Implement C2C/Compliance Based Network Authorization Pt1 |\r\n| 2.6.1 | Implement UEDM or equivalent Tools | 2.6 Unified Endpoint Management (UEM) & Mobile Device Management (MDM) | Target Level ZT | 18.1 | DoD Organizations will work closely with the βImplement Asset, Vulnerability, and Patch Management toolsβ activity to procure and implement and Unified Endpoint and Device Management (UEDM) solution ensuring that requirements are integrated with the procurement process. Once a solution is procured the UEDM team(s) ensure that critical ZT target functionalities such as minimum compliance, asset management, and API support are in place. | Components can confirm if devices meet minimum compliance standards or not; Components have asset management system(s) for user devices (phones, desktops, laptops) that maintains IT compliance, which is reported up to DoD enterprise; Components asset management systems can programmatically, i.e., API, provide device compliance status and if it meets minimum standards | AC-7 (2) purge or wipe mobile device | | Enterprise PKI Pt1 |\r\n| 2.6.2 | Enterprise Device Management Pt1 | 2.6 Unified Endpoint Management (UEM) & Mobile Device Management (MDM) | Target Level ZT | 17.6 | DoD Organizations migrate the manual device inventory to an automated approach using the Unified Endpoint and Device Management solution. Approved devices are able to be managed regardless of location. Devices part of critical services are mandated to be managed by the Unified Endpoint and Device Management solution supporting automation. | Manual inventory is integrated with an automated management solution for critical services; Enable ZT Device Management (from any location with or without remote access) | | | NPE/PKI Device Under Management; Enterprise Device Management Pt2 |\r\n| 2.6.3 | Enterprise Device Management Pt2 | 2.6 Unified Endpoint Management (UEM) & Mobile Device Management (MDM) | Target Level ZT | 12.6 | DoD Organizations migrate the remaining devices to Enterprise Device Management solution. EDM solution is integrated with risk and compliance solutions as appropriate. | Manual inventory is integrated with an automated management solution for all services | | Enterprise Device Management Pt1 | |\r\n| 2.7.1 | Implement Endpoint Detection & Response (EDR) Tools and Integrate with C2C | 2.7 Endpoint & Extended Detection & Response (EDR & XDR) | Target Level ZT | 16.5 | DoD Organizations procure and implement Endpoint Detection and Response (EDR) solution(s) within environments. EDR is protecting, monitoring, and responding to malicious and anomalous activities enabling ZT Target functionality and is sending data to the Comply to Connection solution for expanded device and user checks. | Endpoint Detection & Response Tooling is implemented ; Critical EDR data is being sent to C2C for checks; NextGen AV tooling covers maximum amount of services/applications | | | Implement Extended Detection & Response (XDR) & Integrate w/ C2C Pt 1 |\r\n| 2.7.2 | Implement Extended Detection & Response (XDR) Tools and Integrate with C2C Pt1 | 2.7 Endpoint & Extended Detection & Response (EDR & XDR) | Target Level ZT | 19.2 | DoD Organizations procure and implement Extended Detection & Response (XDR) solution(s). Integration points with cross pillar capabilities are identified and prioritized based on risk. The riskiest of these integration points are actioned and integration is started. EDR continues coverage of endpoints to include the maximum number of services and applications as part of the XDR implementation. Basic analytics are sent from the XDR solution stack to the SIEM. | Integration Points have been identified per Capability; Riskiest integration points have been integrated w/ XDR; Basic alerting is in place with SIEM and/or other mechanisms | | Implement Endpoint Detection & Response (EDR) Tools & Integrate w/ C2C; Threat Alerting Pt1 | Implement Extended Detection & Response (XDR) & Integrate w/ C2C Pt 2 |\r\n| 2.7.3 | Implement Extended Detection & Response (XDR) Tools and Integrate with C2C Pt2 | 2.7 Endpoint & Extended Detection & Response (EDR & XDR) | Advanced ZT | 19.9 | XDR solution stack completes identification of integration points expanding coverage to the fullest amount possible. Exceptions are tracked and managed using a risk based methodical approach for continued operation. Extended analytics enabling ZT Advanced functionalities are integrated into the SIEM and other appropriate solutions. | Remaining integration points have been integrate as appropriate; Extended alerting and response is enabled with other Analytics tools at least using SIEM | | Implement Extended Detection & Response (XDR) & Integrate w/ C2C Pt 1 | Threat Alerting Pt3 |\r\n| 3.1.1 | Application/Code Identification | 3.1 Application Inventory | Target Level ZT | 16.7 | DoD Organizations create an inventory of approved applications and code (e.g., source code, libraries, etc.). Each organization will track the supportability (i.e., active, legacy, etc.) and hosted location (i.e., cloud, on-premise, hybrid, etc.) at least in the inventory. | Component has identified applications and classified as either legacy, virtualized on-premises, and cloud hosted | | | |\r\n| 3.1.2 | Resource Authorization Pt1 | 3.4 Resource Authorization & Integration | Target Level ZT | 18.5 | The DoD Enterprise standardizes on resource authorization approaches (e.g., Software Defined Perimeter) with the organizations. At a minimum the resource authorization gateways will be integrated with identities and devices. Organizations deploy approved resource authorization gateways and enable for external facing applications/services. Additional applications for migration and applications unable to be migrated are identified for exception or decommission. | Resource Authorization Gateway is in place for external facing applications; Resource Authorization policy integrated with identity and device; Enterprise-wide Guidance on conversion standards are communicated to stakeholders | | NPE/PKI, Device under Management Datacenter Macro segmentation | Resource Authorization Pt2 |\r\n| 3.1.3 | Resource Authorization Pt2 | 3.4 Resource Authorization & Integration | Target Level ZT | 20.6 | Resource authorization gateways are used for all possible applications/services. Application unable to utilize gateways are either decommissioned or excepted using a risk based methodical approach. Authorizations are further integrated with the CI/CD pipeline for automated decision making. | Resource Authorization gateway is utilized for all applications; Resource Authorization is integrated with DevSecOps and CI/CD for automated functions | | Resource Authorization Pt1 | |\r\n| 3.2.1 | Build DevSecOps Software Factory Pt1 | 3.2 Secure Software Development & Integration | Target Level ZT | 19.3 | The DoD enterprise creates the foundational standards for modern DevSecOps processes and CI/CD pipelines. The concepts are applied in a standardized technology stack across DoD organizations able to meet future Application Security requirements. An enterprise-wide Vulnerability Management program is integrated with the CI/CD pipelines following the Vulnerability Management Program activities. | Developed Data/Service Standards for DevSecOps; CI/CD Pipeline is fully functional and tested successfully; Vulnerability Management program is officially in place and operating | SC-3 (3) minimize nonsecurity functionality | | Build DevSecOps Software Factory Pt2 |\r\n| 3.2.2 | Build DevSecOps Software Factory Pt2 | 3.2 Secure Software Development & Integration | Target Level ZT | 10.8 | DoD Organizations will use their approved CI/CD pipelines to develop most new applications. Any exceptions will follow a standardized approval process to be allowed to develop in a legacy fashion. DevSecOps processes are also used to develop all new applications and update existing applications. Continual validation functions are integrated into the CI/CD pipelines and DevSecOps processes and integrated with existing applications. | Development of applications is migrated to CI/CD pipeline; Continual validation process/technology is implemented and in use; Development of applications is migrated to DevSecOps process and technology | AC-6 (4) separate processing domains; CM 7 (6) confined environments with limited privileges | Build DevSecOps Software Factory Pt1 | Continuous Authorization to Operate (cATO) Pt1 |\r\n| 3.2.3 | Automate Application Security & Code Remediation Pt1 | 3.2 Secure Software Development & Integration | Target Level ZT | 18.0 | A standardized approach to application security including code remediation is implemented across the DoD enterprise. Part one (1) of this activity includes the integration of a Secure API gateway with applications utilizing API or similar calls. Code reviews are conducted in a methodical approach and standardized protections for containers and their infrastructure are in place. Additionally, any serverless functions where the 3rd party manages the infrastructure such as Platform as a Service utilize adequate serverless security monitoring and response functions. Code Reviews, Container and Serverless security functions are integrated into the CI/CD and/or DevSecOps process appropriate. | Secure API Gateway is operational and majority of API calls are passing through gateway; Application Security functions (e.g., code review, container and serverless security) are implemented as part of CI/CD and DevSecOps | SI-7 (12) integrity verification; SI-7 (15) code authentication; SC-7 (21) isolation of system components; | Implement Asset, Vulnerability and Patch Management Tools | Automate Application Security & Code Remediation Pt2; REST API Micro-Segments |\r\n| 3.2.4 | Automate Application Security & Code Remediation Pt2 | 3.2 Secure Software Development & Integration | Advanced ZT | 16.2 | DoD Organizations modernize approaches to delivering internally developed and managed services following best practice approaches such as Microservices. These approaches will enable more resilient and secure architectures by allowing for quicker changes to code in each microservice as security issues are discovered. Further advancement security remediation activities continue across the DoD Enterprise with the inclusion of runtime security functions for containers as appropriate, automated vulnerable library updates and automated CI/CD approvals during the release process. | Secure API Gateway is operational and majority of API calls are passing through gateway; Services are provided following a Service Oriented Architecture (SOA); Security Remediation activities (e.g., runtime security, library updates, release approvals) are fully automated | CM-7 (7) code execution in protected environments; CM-14 Signed Components; SI-7 (17) runtime application self-protection | Automate Application Security & Code Remediation Pt1 | |\r\n| 3.3.1 | Approved Binaries/Code | 3.3 Software Risk Management | Target Level ZT | 23.4 | The DoD enterprise uses best practice approaches to manage approved binaries and code in a methodical approach. These approaches will include supplier sourcing risk management, approved repository usage, bill of materials supply chain risk management, and industry standard vulnerability management. | Supplier sourcing risk evaluated and identified for approved sources; Repository and update channel established for use by development teams; Bill of Materials is created for applications identify source, supportability and risk posture; Industry standard (DIB) and approved vulnerability databases are pulled in to be used in DevSecOps | SI-19 (7) validated algorithms and software | Vulnerability Management Program Pt1 | |\r\n| 3.3.2 | Vulnerability Management Program Pt1 | 3.3 Software Risk Management | Target Level ZT | 7.8 | The DoD Enterprise works with Organizations to establish and manage a Vulnerability Management program. The program includes a policy and standards agreed upon by all Organizations. The developed program includes at a minimum the track and management of public vulnerabilities based on DoD applications/services. Organizations establish a vulnerability management team with key stakeholders where vulnerabilities are discussed and managed following the Enterprise policy and standards. | Vulnerability Management Team is in place w/ appropriate stakeholder membership; Vulnerability Management policy and process is in place and agreed to w/ stakeholders; Public source of vulnerabilities are being utilized for tracking | SA-11 (2) threat modeling and vulnerability analyses | | Approved Binaries/Code; Vulnerability Management Program Pt2 |\r\n| 3.3.3 | Vulnerability Management Program Pt2 | 3.3 Software Risk Management | Target Level ZT | 12.1 | Processes are established at the DoD Enterprise level for managing the disclosure of vulnerabilities in DoD maintained/operated services both publicly and privately accessible. DoD Organizations expand the vulnerability management program to track and manage closed vulnerability repositories such as DIB, CERT, and others. | Controlled (e.g., DIB, CERT) sources of vulnerabilities are being utilized for tracking; Vulnerability management program has a process for accepting external/public disclosures for managed services | | Vulnerability Management Program Pt1 | Automate Application Security & Code Remediation Pt1 |\r\n| 3.3.4 | Continual Validation | 3.3 Software Risk Management | Target Level ZT | 11.1 | DoD Organizations will implement a continual validation approach for application development where parallel deployment is conducted and integrated with an approved environment level (e.g., UAT, Prod). Applications unable to integrate continual validation into their CI/CD process are identified and exceptions are provided as needed using a methodical approach. | Updated Applications are deployed in a live and/or production environment; Applications that were marked for retirement and transition are decommissioned; Continual validation tools are implemented and applied to code in the CI/CD pipeline; Code requiring continuous validation is identified and validation criteria are established | | | |\r\n| 3.4.1 | SDC Resource Authorization Pt1 | 3.4 Resource Authorization & Integration | Target Level ZT | 31.1 | The DoD Enterprise provides a standardized approach for code based compute management (i.e., Software Defined Compute) following industry best practices. Using risk-based approaches baselines are created using the approved set of code libraires and packages. DoD Organizations work with the approved code/binaries activities to ensure that applications are identified which can and cannot support the approach. Applications which can support a modern software- based configuration and management approaches are identified and transitioning begins. Applications which cannot follow software-based configuration and management approaches are identified and allowed through exception using a methodical approach. | Applications unable to be updated to use approved binaries/code are marked for retirement and transition plans are created; Identified applications without approved binaries and code are updated to use approved binaries/code; Enterprise-wide Guidance on conversion standards are communicated to stakeholders | | | SDC Resource Authorization Pt2 |\r\n| 3.4.2 | SDC Resource Authorization Pt2 | 3.4 Resource Authorization & Integration | Target Level ZT | 21.8 | Applications which support software-based configuration and management have been transitioned to a production/live environment and are in normal operations. Where possible applications which cannot support software-based configuration and management are decommissioned. | Updated Applications are deployed in a live and/or production environment; Applications that were marked for retirement and transition are decommissioned | | SDC Resource Authorization Pt1 | |\r\n| 3.4.3 | Enrich Attributes for Resource Authorization Pt1 | 3.4 Resource Authorization & Integration | Advanced ZT | 17.6 | Initial attributes from sources such as User and Entity Activity Monitoring, Micro-segmentation services, DLP and DRM are integrated into the Resource Authorization technology stack and policy. Any additional attributes for later integration are identified and planned. Attributes are used to create basic risk posture of users, NPEs and devices allowing for authorization decisions. | Most API calls are passing through the Secure API Gateway; Resource Authorization receives data from Analytics Engine; Authorization policies incorporate identified attributes in making authorization decisions; Attributes to be used for initial enrichment are identified; Identified attributes are assigned to resources and/or entities | SC-3 (2) access and flow control functions | User Activity Monitoring Pt2; Entity Activity Monitoring Pt2; Application & Device Micro segmentation; Manual Data Tagging Pt2; DLP Enforcement via Data Tags and Analytics Pt2; DRM Enforcement via Data Tags and Analytics Pt2 | Enrich Attributes for Resource Authorization Pt2 |\r\n| 3.4.4 | Enrich Attributes for Resource Authorization Pt2 | 3.4 Resource Authorization & Integration | Advanced ZT | 17.8 | Extended identified attributes are integrated with the resource authorization technology and policy. Confidence scoring is introduced across the attributes to create a more advanced method of authorization decision making in an automated fashion. | Authorization policies incorporate confidence levels in making authorization decisions; Confidence levels for attributes are defined | | Enrich Attributes for Resource Authorization Pt1 | |\r\n| 3.4.5 | REST API Micro-Segments | 3.4 Resource Authorization & Integration | Advanced ZT | 18.1 | Using the DoD Enterprise approved API gateway(s), application calls are micro-segmented only allowing authenticated and authorized access to specific destinations (e.g., microservices). When possible, API Micro-Segmentation consoles are integrated and aware of other Micro Segmentation consoles such as Software Defined Perimeter Controllers and/or Software Defined Networking Consoles. | Approved Enterprise APIs are Micro-Segmented appropriately | SC-39 (2) separate execution domain per thread | Automate Application Security & Code Remediation Pt1 | |\r\n| 3.5.1 | Continuous Authorization to Operate (cATO) Pt1 | 3.5 Continuous Monitoring and Ongoing Authorizations | Advanced ZT | 15.1 | DoD Organizations utilize automation solutions within the environment to standardize the monitoring of controls and offer the capability to identify deviations. Where appropriate monitoring and testing is integrated with DevSecOps processes. | Controls derivation is standardized and ready for automation; Controls testing is integrated with DevSecOps processes and technology | | Policy Inventory & Development; Build DevSecOps Software Factory Pt2 | Continuous Authorization to Operate (ATO) Pt2 |\r\n| 3.5.2 | Continuous Authorization to Operate (cATO) Pt2 | 3.5 Continuous Monitoring and Ongoing Authorizations | Advanced ZT | 21.8 | DoD Organizations fully automate control derivation, testing and monitoring processes. Deviations are automatically tested and resolved using existing cross pillar automation infrastructure. Dashboarding is used to monitor the status of authorizations and analytics are integrated with the responsible authorizing officials. | Controls testing is fully automated; Integration with standard IR and SOC operations is automated; Control derivation and applicability is fully automated; Dashboards are used to track continuing authorization status | | Continuous Authorization to Operate (ATO) Pt1; Threat Alerting Pt3; Automated Workflow | |\r\n| 4.1.1 | Data Analysis | 4.1 Data Catalog Risk Alignment | Target Level ZT | 17.4 | DoD Organizations update the service and application catalog(s) with data classifications. Data tags are also added to each service and application. | The service catalog is updated with data types for each application and service based on data classification levels | | | |\r\n| 4.2.1 | Define Data Tagging Standards | 4.2 DoD Enterprise Data Governance | Target Level ZT | 15.8 | The DoD Enterprise works with organizations to establish data tagging and classification standards based on industry best practices. Classifications are agreed upon and implemented in processes. Tags are identified as manual and automated for future activities. | Enterprise data classification and tagging standards are developed; Organizations align to enterprise standards and begin implementation | | | Implement Data Tagging & Classification Tools; Manual Data Tagging Pt1 |\r\n| 4.2.2 | Interoperability Standards | 4.2 DoD Enterprise Data Governance | Target Level ZT | 14.4 | The DoD Enterprise collaborating with the organizations develops interoperability standards integrating mandatory Data Rights Management (DRM) and Protection solutions with necessary technologies to enable ZT target functionality. | Formal standards are in place by the Enterprise for the appropriate data standards | | | Implement DRM and Protection Tools Pt1 |\r\n| 4.2.3 | Develop Software Defined Storage (SDS) Policy | 4.2 DoD Enterprise Data Governance | Target Level ZT | 9.9 | The DoD enterprise working with organizations establishes a software define storage (SDS) policy and standards based on industry best practices. DoD organizations evaluate current data storage strategy and technology for implementation of SDS. Where appropriate storage technology is identified for SDS implementation. | Determine need for SDS tool implementation; Policy for SDS is created at the enterprise and org levels | | | Integrate DAAS Access w/ SDS Policy Pt1; Integrate Solution & Policy w/ Enterprise IDP Pt1 |\r\n| 4.3.1 | Implement Data Tagging & Classification Tools | 4.3 Data Labeling and Tagging | Target Level ZT | 15.9 | DoD Organizations utilize the enterprise standard and requirements to implement data tagging and classification solution(s). Organizations ensure that future ML and AI integrations are supported by solutions through DoD enterprise requirements. | A requirement of Data classification and tagging tools must include integration and/or support of Machine Learning (ML); Data classification and tagging tools are implemented at org and enterprise levels | | Define Data Tagging Standards | Implement Enforcement Points |\r\n| 4.3.2 | Manual Data Tagging Pt1 | 4.3 Data Labeling and Tagging | Target Level ZT | 17.6 | Using the DoD Enterprise data tagging and classification policy and standards, manual tagging starts using basic data level attributes to meet ZT target functionality. | Manual data tagging begins at the enterprise level with basic attributes | SI-18 (2) data tags | Define Data Tagging Standards | Manual Data Tagging Pt2; DRM Enforcement via Data Tags and Analytics Pt1; DLP Enforcement via Data Tags and Analytics Pt1 |\r\n| 4.3.3 | Manual Data Tagging Pt2 | 4.3 Data Labeling and Tagging | Advanced ZT | 16.1 | DoD organizational specific data level attributes are integrated into the manual data tagging process. DoD enterprise and organizations collaborate to decide which attributes are required to meet ZTA advanced functionality. Data level attributes for ZTA advanced functionality are standardized across the enterprise and incorporated. | Manual data tagging is expanded to the program/org levels with specific attributes | AC-4 (6) metadata | Manual Data Tagging Pt1 | Enrich Attributes for Resource Authorization Pt1 |\r\n| 4.3.4 | Automated Data Tagging & Support Pt1 | 4.3 Data Labeling and Tagging | Advanced ZT | 14.1 | DoD Organizations use data loss prevention, rights management, and/or protection solutions to conduct scanning of data repositories. Standardized tags are applied to supported data repositories and data types. Unsupported data repositories and types are identified. | Basic automation begins by scanning data repositories and applying tags | | Implement Data Tagging & Classification ML Tools | Automated Data Tagging & Support Pt2 |\r\n| 4.3.5 | Automated Data Tagging & Support Pt2 | 4.3 Data Labeling and Tagging | Advanced ZT | 38.8 | Remaining supported data repositories have basic and extended data tags which are applied using machine learning and artificial intelligence. Extended data tags are applied to existing repositories. Unsupported data repositories and data types are evaluated for decommissioning using a risk based methodical approach. Approved exceptions utilize manual data tagging approaches with data owners and/or custodians to manage tagging. | Full automation of data tagging is completed; Results of data tagging are fed into ML algorithms to develop AI driven data tagging | | Automated Data Tagging & Support Pt1 | |\r\n| 4.4.1 | DLP Enforcement Point Logging and Analysis | 4.4 Data Monitoring and Sensing | Target Level ZT | 10.8 | DoD Organizations identify data loss prevention (DLP) enforcement points such as specific services and user endpoints. Using the established DoD Enterprise cybersecurity incident response standard, DoD organizations ensure the appropriate detail of data is captured. Additionally, protection, detection, and response use cases are developed to better outline solution coverage. | Enforcement points are identified; Standardized Logging schema is enforced at the enterprise and org levels | AC-3 (8) revocation of access authorizations | | Comprehensive Data Activity Monitoring |\r\n| 4.4.2 | DRM Enforcement Point Logging and Analysis | 4.4 Data Monitoring and Sensing | Target Level ZT | 12.6 | DoD Organizations identify data rights management (DRM) enforcement points such as specific services and user endpoints. Using the established DoD Enterprise cybersecurity incident response standard, DoD organizations ensure the appropriate detail of data is captured. Additionally, protection, detection, and response use cases are developed to better outline solution coverage. | Enforcement points are identified; Standardized Logging schema is enforced at the enterprise and org levels | | | Comprehensive Data Activity Monitoring |\r\n| 4.4.3 | File Activity Monitoring Pt1 | 4.4 Data Monitoring and Sensing | Target Level ZT | 16.8 | DoD Organizations utilize File Monitoring tools to monitor the most critical data classification levels in applications, services, and repositories. Analytics from monitoring is fed into the SIEM with basic data attributes to accomplish ZT Target functionality. | Data and files of critical classification are actively being monitored; Basic Integration is in place with monitoring system such as the SIEM | MP-8 (3) controlled unclassified information | | File Activity Monitoring Pt2 |\r\n| 4.4.4 | File Activity Monitoring Pt2 | 4.4 Data Monitoring and Sensing | Target Level ZT | 18.9 | DoD Organizations utilize File Monitoring tools to monitor all regulatory protected data (e.g., CUI, PII, PHI, etc.) in applications, services, and repositories. Extended integration is used to send data to appropriate inter/intra-pillar solutions such as Data Loss Prevention, Data Rights Management/Protection and User & Entity Behavior Analytics. | Data and files of all regulated classifications are actively being monitored; Extended integrations are in place as appropriate to further manage risk | MP-8 (4) classified information | File Activity Monitoring Pt1 | Rule Based Dynamic Access Pt2; Database Activity Monitoring |\r\n| 4.4.5 | Database Activity Monitoring | 4.4 Data Monitoring and Sensing | Advanced ZT | 18.2 | DoD Organizations procure, implement, and utilize Database Monitor solutions to monitor all databases containing regulated data types (CUI, PII, PHI, etc.). Logs and analytics from the database monitoring solution are fed to the SIEM for monitoring and response. Analytics are fed into cross pillar activities such as \"Enterprise Security Profile\" and \"Real Time Access\" to better direct decision making. | Appropriate Database are being actively monitored; Monitoring technology is integrated with solutions such as SIEM, PDP and Dynamic Access Control mechanisms | | File Activity Monitoring Pt2 | Comprehensive Data Activity Monitoring |\r\n| 4.4.6 | Comprehensive Data Activity Monitoring | 4.4 Data Monitoring and Sensing | Advanced ZT | 27.2 | DoD Organizations expand monitoring of data repositories including databases as appropriate based on a methodical risk approach. Additional data attributes to meet the ZT Advanced functionalities are integrated into the analytics for additional integrations. | Data Activity monitoring mechanisms are integrated to provide a unified view of monitoring across data repositories; Appropriate integrations exist with solutions such as SIEM and PDP | | DLP Enforcement Point Logging and Analysis; DRM Enforcement Point Logging and Analysis; Database Activity Monitoring | AI-enabled Dynamic Access Control; FF Baseline & Profiling Pt. 2; AI- enabled Network Access |\r\n| 4.5.1 | Implement DRM and Protection Tools Pt1 | 4.5 Data Encryption & Rights Management | Target Level ZT | 11.7 | DoD Organizations procure and implement DRM and Protection solution(s) as needed following the DoD Enterprise standard and requirements. Newly implement DRM and protection solution(s) are implemented with high risk data repositories using ZTA target level protections. | DRM and protection tools are enabled for high risk data repositories with basic protections | AU-9 (2) store on separate physical systems or components | Interoperability Standards | Implement DRM and Protection Tools Pt2 |\r\n| 4.5.2 | Implement DRM and Protection Tools Pt2 | 4.5 Data Encryption & Rights Management | Target Level ZT | 22.0 | DRM and protection coverage is expanded to cover all in scope data repositories. Encryption keys are automatically managed to meet best practices (e.g., FIPS). Extended data protection attributes are implemented based on the environment classification. | DRM and protection tools are enabled for possible repositories | AC-3 (9) controlled release; MP-6 (8) remote purging or wiping of information; SI-19 (4) removal, masking, encryption, hashing, or replacement of direct identifiers | Implement DRM and Protection Tools Pt1 | |\r\n| 4.5.3 | DRM Enforcement via Data Tags and Analytics Pt1 | 4.5 Data Encryption & Rights Management | Target Level ZT | 16.2 | Data rights management (DRM) and protection solutions are integrated with basic data tags defined by the DoD Enterprise standard. Initial data repositories are monitored and have protect and response actions enabled. Data at rest is encrypted in repositories. | Data Tags are integrated with DRM and monitored repositories are expanded; Based on data tags, data is encrypted at rest | | Manual Data Tagging Pt1 | DRM Enforcement via Data Tags and Analytics Pt2 |\r\n| 4.5.4 | DRM Enforcement via Data Tags and Analytics Pt2 | 4.5 Data Encryption & Rights Management | Advanced ZT | 19.0 | Extended data repositories are protected with DRM and Protection solutions. DoD Organizations implement extended data tags applicable to organizations versus mandated enterprise. Data is encrypted in extended repositories using additional tags. | All applicable data repositories are protected using DRM; Data is encrypted using extended data tags from the org levels | SC-16 (3) cryptographic binding | DRM Enforcement via Data Tags and Analytics Pt1 | Enrich Attributes for Resource Authorization Pt1; DRM Enforcement via Data Tags and Analytics Pt3 |\r\n| 4.5.5 | DRM Enforcement via Data Tags and Analytics Pt3 | 4.5 Data Encryption & Rights Management | Advanced ZT | 23.3 | DRM and Protection solutions integrate with AI and ML tooling for encryption, rights management and protection functions. | Analytics from ML/AI are integrated with DRM to better automate protections; Encryption protection is integrated with AI/ML and updated encryption methods are used as needed | AC-4 (19) validation of metadata | DRM Enforcement via Data Tags and Analytics Pt2 | |\r\n| 4.6.1 | Implement Enforcement Points | 4.6 Data Loss Prevention (DLP) | Target Level ZT | 21.2 | Data loss prevention (DLP) solution is deployed to the in-scope enforcement points. DLP solution is set to βmonitor-onlyβ and/or βlearningβ mode limiting impact. DLP solution results are analyzed, and policy is fine tuned to manage risk to an acceptable level. | Identified enforcement points have DLP tool deployed and set to monitor mode with standardized logging | | Implement Data Tagging & Classification Tools | Process Micro segmentation |\r\n| 4.6.2 | DLP Enforcement via Data Tags and Analytics Pt1 | 4.6 Data Loss Prevention (DLP) | Target Level ZT | 21.3 | Data loss prevention (DLP) solution is updated from monitor only mode to prevention mode. Basic data tags are utilized for DLP solution and logging schema is integrated. | Enforcement Points to set to prevent mode integrating the logging schema and manual tags | | Manual Data Tagging Pt1 | DLP Enforcement via Data Tags and Analytics Pt2 |\r\n| 4.6.3 | DLP Enforcement via Data Tags and Analytics Pt2 | 4.6 Data Loss Prevention (DLP) | Advanced ZT | 19.0 | Data loss prevention (DLP) solution is updated to include extended data tags based on parallel Automation activities. | Enforcement points have extended data tag attributes applied for additional prevention | | DLP Enforcement via Data Tags and Analytics Pt1 | Enrich Attributes for Resource Authorization Pt1; DLP Enforcement via Data Tags and Analytics Pt3 |\r\n| 4.6.4 | DLP Enforcement via Data Tags and Analytics Pt3 | 4.6 Data Loss Prevention (DLP) | Advanced ZT | 41.6 | Data loss prevention (DLP) solution is integrated with automated data tagging techniques to include any missing enforcement points and tags. | Automated tagging attributes are integrated with DLP and resulting metrics are used for ML | | DLP Enforcement via Data Tags and Analytics Pt2 | |\r\n| 4.7.1 | Integrate DAAS Access w/ SDS Policy Pt1 | 4.7 Data Access Control | Target Level ZT | 15.3 | Utilizing the DoD enterprise SDS policy, organizational DAAS policy is developed with intended integration in mind. SDS implementation guide is developed by DoD organizations due to environment specific nature. | Attribute base fine-grained DAAS policy is developed w/ enterprise and org level support; SDS Integration plan is developed to support DAAS policy | | Develop Software Defined Storage (SDS) Policy | Integrate DAAS Access w/ SDS Policy Pt2 |\r\n| 4.7.2 | Integrate DAAS Access w/ SDS Policy Pt2 | 4.7 Data Access Control | Advanced ZT | 12.6 | DoD Organizations implement the DAAS policy in an automated fashion. | Attribute based fine-grained DAAS Policy implemented in an automated fashion | | Integrate DAAS Access w/ SDS Policy Pt1; Implement SDS Tool and/or Integrate w/ DRM Tool Pt1 | Integrate DAAS Access w/ SDS Policy Pt3 |\r\n| 4.7.3 | Integrate DAAS Access w/ SDS Policy Pt3 | 4.7 Data Access Control | Advanced ZT | 9.2 | Newly implemented SDS technology and/or functionalities are integrated with the DAAS policy in a risk-based fashion. A phased approach should be taken to during implementation to measure results and adjust accordingly. | SDS is integrated with DAAS policy functionality; all data in all applications are protected with attribute based fine- grained DAAS policy | | Integrate DAAS Access w/ SDS Policy Pt2 | |\r\n| 4.7.4 | Integrate Solution(s) and Policy with Enterprise IDP Pt1 | 4.7 Data Access Control | Target Level ZT | 13.9 | DoD Organizations develop an integration plan using the SDS policy and technology/functionality with the enterprise Identity Provider (IdP) solution. | Integration plan between SDS and authoritative Identity Provider is developed to support existing DAAS access | | Develop Software Defined Storage (SDS) Policy; Enterprise IDP Pt1 | Integrate Solution & Policy w/ Enterprise IDP Pt2 |\r\n| 4.7.5 | Integrate Solution(s) and Policy with Enterprise IDP Pt2 | 4.7 Data Access Control | Advanced ZT | 9.2 | Newly implemented SDS technology and/or functionalities are integrated with the Enterprise Identity Provider (IdP) following the integration plan. Identity attributes required to meet ZT Target functionalities are required for integration. | Complete integration with Enterprise IDP and SDS toolingto support all attribute based fine-grained DAAS access | | Integrate Solution & Policy w/ Enterprise IDP Pt1 | |\r\n| 4.7.6 | Implement SDS Tool and/or integrate with DRM Tool Pt1 | 4.7 Data Access Control | Advanced ZT | 17.4 | Depending on the need for a Software Defined Storage tool, a new solution is implemented or an existing solution is identified meeting the functionality requirements to be integrated with DLP, DRM/Protection, and ML solutions. | If tooling is needed ensure there is supported integrations with DLP, DRM and ML tooling | | Develop Software Defined Storage (SDS) Policy; Integrate Solution & Policy w/ Enterprise IDP Pt1 | Integrate DAAS Access w/ SDS Policy Pt2; Implement SDS Tool and/or Integrate w/ DRM Tool Pt2 |\r\n| 4.7.7 | Implement SDS Tool and/or integrate with DRM Tool Pt2 | 4.7 Data Access Control | Advanced ZT | 15.3 | DoD Organizations configure the SDS functionality and/or solution to be integrated with the underlying DLP and DRM/Protection infrastructure as appropriate. Lower-level integrations enable more effective protection and response. | Integrate SDS infrastructure with existing DLP and DRM infrastructure | | Implement SDS Tool and/or Integrate w/ DRM Tool Pt1 | |\r\n| 5.1.1 | Define Granular Control Access Rules & Policies Pt1 | 5.1 Data Flow Mapping | Target Level ZT | 10.3 | The DoD Enterprise working with the Organizations creates granular network access rules and policies. Associated Concept of Operations (ConOps) are developed in alignment with access policies as well ensure future supportability. Once agreed upon, DoD Organizations will implement these access policies into existing network technologies (e.g., Next Generation Firewalls, Intrusion Prevention Systems, etc.) to improve initial risk levels. | Provide Technical Standards; Develop Concept of Operations; Identify Communities of Interest | | | Define SDN APIs; Define Granular Control Access Rules & Policies Pt2 |\r\n| 5.1.2 | Define Granular Control Access Rules & Policies Pt2 | 5.1 Data Flow Mapping | Target Level ZT | 8.0 | DoD Organizations utilize data tagging and classification standards to develop data filters for API access to the SDN Infrastructure. API Decision Points are formalized within the SDN architecture and implemented with non-mission/task critical applications and services. | Define Data Tagging Filters for API Infrastructure | | Define Granular Control Access Rules & Policies Pt1 | |\r\n| 5.2.1 | Define SDN APIs | 5.2 Software Defined Networking (SDN) | Target Level ZT | 8.3 | The DoD Enterprise works with the Organizations to define the necessary APIs and other programmatic interfaces to enable Software Defined Networking (SDN) functionalities. These APIs will enable Authentication Decision Point, Application Delivery Control Proxy and Segmentation Gateways automation. | SDN APIs are standardized and implemented; APIs are functional for AuthN Decision Point, App Delivery Control Proxy and Segmentation Gateways | | Define Granular Control Access Rules & Policies Pt1 | Implement SDN Programable Infrastructure |\r\n| 5.2.2 | Implement SDN Programable Infrastructure | 5.2 Software Defined Networking (SDN) | Target Level ZT | 32.0 | Following the API standards, requirements and SDN API functionalities, DoD Organizations will implement Software Defined Networking (SDN) infrastructure to enable automation tasks. Segmentation Gateways and Authentication Decision Points are integrated into the SDN infrastructure along with output logging into a standardized repository (e.g., SIEM, Log Analytics) for monitoring and alerting. | Implemented Application Delivery Control Proxy; Established SIEM Logging Activities; Implemented User Activity Monitoring (UAM); Integrated with Authentication Decision Point; Implemented Segmentation Gateways | | Define SDN APIs; Standardized API Calls & Schemas Pt1 | |\r\n| 5.2.3 | Segment Flows into Control, Management, and Data Planes | 5.2 Software Defined Networking (SDN) | Target Level ZT | 13.0 | Network infrastructure and flows are segmented either physically or logically into control, management, and data planes. Basic segmentation using IPv6/VLAN approaches is implemented to better organize traffic across data planes. Analytics and NetFlow from the updated infrastructure is automatically fed into Operations Centers and analytics tools. | IPv6 Segmentation; Enable Automated NetOps Information Reporting; Ensure Configuration Control Across Enterprise; Integrated with SOAR | AC-4 (21) physical or logical separation of information flows | | B/C/P/S Macro segmentation; Application & Device Micro segmentation |\r\n| 5.2.4 | Network Asset Discovery & Optimization | 5.2 Software Defined Networking (SDN) | Advanced ZT | 30.2 | DoD Organizations automate network asset discovery through the SDN infrastructure limiting access to devices based on risk based methodical approaches. Optimization is conducted based on the SDN analytics to improve overall performance along with provide necessary approved access to resources. | Technical Refreshment/Technology Evolution; Provide Optimization/Performance Controls | | | |\r\n| 5.2.5 | Real-Time Access Decisions | 5.2 Software Defined Networking (SDN) | Advanced ZT | 15.6 | SDN Infrastructure utilizes cross Pillar data sources such as User Activity Monitoring, Entity Activity Monitoring, Enterprise Security Profiles and more for real-time access decisions. Machine learning is used to assist decision making based on advanced network analytics (full packet capture, etc.). Policies are consistently implemented across the Enterprise using unified access standards. | Analyze SIEM Logs with Analytics Engine to Provide Real- Time Policy Access Decisions; Support Sending Captured Packets, Data/Network Flows, and other Specific Logs for Analytics; Segment End-to-End Transport Network Flows; Audit Security Policies for Consistency across Enterprise; Protect Data-in-Transit During Coalition Information Sharing | | Continuous Authentication Pt2; User Activity Monitoring Pt2; Implement C2C/Compliance Based Network Authorization Pt2; Entity Activity Monitoring Pt2; AI-enabled Network Access; Enterprise Security Profile Pt2 | |\r\n| 5.3.1 | Datacenter Macro segmentation | 5.3 Macro Segmentation | Target Level ZT | 17.6 | DoD Organizations implement data center focused macro- segmentation using traditional tiered (web, app, db) and/or service- based architectures. Proxy and/or enforcement checks are integrated with the SDN solution(s) based on device attributes and behavior. | Log Actions to SIEM; Establish Proxy/Enforcement Checks of Device Attributes, Behavior, and other Data; Analyze Activities with Analytics Engine | | | Implement Micro segmentation |\r\n| 5.3.2 | B/C/P/S Macro segmentation | 5.3 Macro Segmentation | Target Level ZT | 18.1 | DoD Organizations implement base, camp, post, and station macro- segmentation using logical network zones limiting lateral movement. Proxy and/or enforcement checks are integrated with the SDN solution(s) based on device attributes and behavior. | Establish Proxy/Enforcement Checks of Device Attributes, Behavior, and other Data; Log Actions to SIEM; Analyze Activities with Analytics Engine; Leverage SOAR to Provide RT Policy Access Decisions | | Segment Flows into Control, Management, and Data Planes | |\r\n| 5.4.1 | Implement Micro segmentation | 5.4 Micro Segmentation | Target Level ZT | 17.3 | DoD Organizations implement Micro-Segmentation infrastructure into SDN environment enabling basic segmentation of service components (e.g., web, app, db), ports and protocols. Basic automation is accepted for policy changes including API decision making. Virtual hosting environments implement micro-segmentation at the host/container level. | Accept Automated Policy Changes; Implement API Decision Points; Implement NGF/Micro FW/Endpoint Agent in Virtual Hosting Environment | SC-7 (22) separate subnets for connecting to different security domains | Datacenter Macro segmentation | Application & Device Micro segmentation |\r\n| 5.4.2 | Application & Device Micro segmentation | 5.4 Micro Segmentation | Target Level ZT | 17.9 | DoD Organizations utilize Software Defined Networking (SDN) solution(s) to establish infrastructure meeting the ZT Target functionalities β logical network zones, role, attribute and conditional based access control for user and devices, privileged access management services for network resources, and policy-based control on API access. | Assign Role, Attribute, & Condition Based Access Control to User & Devices; Provide Privileged Access Management Services; Limit Access on Per Identity Basis for User & Device; Create Logical Network Zones; Support Policy Control via REST API | | Segment Flows into Control, Management, and Data Planes; Implement Micro segmentation | Enrich Attributes for Resource Authorization Pt1 |\r\n| 5.4.3 | Process Micro segmentation | 5.4 Micro Segmentation | Advanced ZT | 20.3 | DoD Organizations utilize existing micro-segmentation and SDN automation infrastructure enabling process micro-segmentation. Host- level processes are segmented based on security policies and access is granted using real-time access decision making. | Segment Host-Level Processes for Security Policies; Support Real-Time Access Decisions and Policy Changes; Support Offload of Logs for Analytics and Automation; Support Dynamic Deployment of Segmentation Policy | AC-4 (7) one-way flow mechanisms; AC-4 (17) domain authentication; SC-7 (20) dynamic isolation and segregation | Implement Enforcement Points | |\r\n| 5.4.4 | Protect Data In Transit | 5.4 Micro Segmentation | Target Level ZT | 9.1 | Based on the data flow mappings and monitoring, policies are enabled by DoD Organizations to mandate protection of data in transit. Common use cases such as Coalition Information Sharing, Sharing Across System Boundaries and Protection across Architectural Components are included in protection policies. | Protect Data In Transit During Coalition Information Sharing; Protect Data in Transit Across System High Boundaries; Integrate Data In Transit Protection Across Architecture Components | | | |\r\n| 6.1.1 | Policy Inventory & Development | 6.1 Policy Decision Point (PDP) & Policy Orchestration | Target Level ZT | 9.8 | The DoD Enterprise works with the Organizations to catalog and inventory existing Cyber Security policies and standards. Policies are updated and created in cross pillar activities as needed to meet critical ZT Target functionality. | Policies have been collected in reference to applicable compliance and risk (e.g. RMF, NIST); Policies have been reviewed for missing Pillars and Capabilities per the ZTRA; Missing areas of policies are updated to meet the capabilities per ZTRA | | | Continuous Authorization to Operate (cATO) Pt1 |\r\n| 6.1.2 | Organization Access Profile | 6.1 Policy Decision Point (PDP) & Policy Orchestration | Target Level ZT | 19.4 | DoD Organizations develop basic access profiles for mission/task and non-mission/task DAAS access using the data from the User, Data, Network, and device pillars. The DoD Enterprise works with the Organizations to develop an Enterprise Security Profile using the existing Organizational security profiles to create a common access approach to DAAS. A phased approach can be used in organizations to limit risk to mission/task critical DAAS access once the security profile(s) are created. | Organization scoped profile(s) are created to determine access to DAAS using capabilities from User, Data, Network, and Device pillars; Initial enterprise profile access standard is developed for access to DAAS ; When possible the organization profile(s) utilizes enterprise available services in the User, Data, Network and Device pillars; Organization Mission/Task critical profile(s) are created | | | Enterprise Security Profile Pt1 |\r\n| 6.1.3 | Enterprise Security Profile Pt1 | 6.1 Policy Decision Point (PDP) & Policy Orchestration | Target Level ZT | 16.0 | The Enterprise Security profile covers the User, Data, Network and Device pillars initially. Existing Organizational Security Profiles are integrated for non-mission/task DAAS access following an iterative approach to tuning access. | Enterprise Profile(s) are created to access DAAS using capabilities from User, Data, Network and Device Pillars; Non-mission/task critical organization profile(s) are integrated with the enterprise profile(s) using a standardized approach | | Organization Access Profile | Enterprise Security Profile Pt2 |\r\n| 6.1.4 | Enterprise Security Profile Pt2 | 6.1 Policy Decision Point (PDP) & Policy Orchestration | Advanced ZT | 12.5 | The minimum number of Enterprise Security Profile(s) exist granting access to the widest range of DAAS across Pillars within the DoD Organizations. Mission/task organization profiles are integrated with the Enterprise Security Profile(s) and exceptions are managed in a risk based methodical approach. | Enterprise Profile(s) have been reduced and simplified to support widest array of access to DAAS; Where appropriate Mission/Task Critical profile(s) have been integrated and supported Organization profiles are considered the exception | | Enterprise Security Profile Pt1 | Real-Time Access Decisions AI-enabled Dynamic Access Control |\r\n| 6.2.1 | Task Automation Analysis | 6.2 Critical Process Automation | Target Level ZT | 6.3 | DoD Organizations identify and enumerate all task activities that can be executed both manually and in an automated fashion. Task activities are organized into automated and manual categories. Manual activities are analyzed for possible retirement. | Automatable tasks are identified; Tasks are enumerated | | | |\r\n| 6.2.2 | Enterprise Integration & Workflow Provisioning Pt1 | 6.2 Critical Process Automation | Target Level ZT | 23.4 | The DoD enterprise establishes baseline integrations within the Security Orchestration, Automation and Response solution (SOAR) required to enable target level ZTA functionality. DoD organizations identify integration points and prioritize key ones per the DoD enterprise baseline. Critical integrations occur meeting key services enabling recovery and protection capabilities. | Implement full enterprise integration; Identify key integrations; Identify recovery and protection requirements | | | Enterprise Integration & Workflow Provisioning Pt2 |\r\n| 6.2.3 | Enterprise Integration & Workflow Provisioning Pt2 | 6.2 Critical Process Automation | Advanced ZT | 12.7 | DoD Organizations integrate remaining services to meet baseline requirements and advanced ZTA functionality requirements as appropriate per environment. Service provisioning is integrated and automated into workflows where required meeting ZTA target functionalities. | Services identified; Service provisioning is implemented | CM-3 (3) automated change implementation | Enterprise Integration & Workflow Provisioning Pt1 | Automated Workflow |\r\n| 6.3.1 | Implement Data Tagging & Classification ML Tools | 6.3 Machine Learning | Target Level ZT | 16.0 | DoD Organizations utilize existing Data Tagging and Classification standards and requirements to procure Machine Learning solution(s) as needed. Machine Learning solution(s) is implemented in organizations and existing tagged and classified data repositories are used to establish baselines. Machine learning solution(s) applies data tags in a supervised approach to continually improve analysis. | Implemented data tagging and classification tools are integrated with ML tools | | Define Data Tagging Standards | Automated Data Tagging & Support Pt1 |\r\n| 6.4.1 | Implement AI automation tools | 6.4 Artificial Intelligence | Advanced ZT | 25.7 | DoD Organizations identify areas of improvement based on existing machine learning techniques for Artificial Intelligence. AI solutions are identified, procured, and implemented using the identified areas as requirements. | Develop AI Tool Requirements; Procure and Implement AI Tools | | | Automated Workflow |\r\n| 6.4.2 | AI Driven by Analytics decides A&O modifications | 6.4 Artificial Intelligence | Advanced ZT | 42.0 | DoD Organizations utilizing existing machine learning functions implement and use AI technology such as neural networks to drive automation and orchestration decisions. Decision making is moved to AI as much as possible freeing up human staff for other efforts. Utilizing historical patterns, AI will make anticipatory changes in the environment to better reduce risk. | AI is able to make changes to automated workflow activities | | | |\r\n| 6.5.1 | Response Automation Analysis | 6.5 Security Orchestration, Automation & Response (SOAR) | Target Level ZT | 9.0 | DoD Organizations identify and enumerate all response activities that executed both manually and in an automated fashion. Response activities are organized into automated and manual categories. Manual activities are analyzed for possible retirement. | Automatable response activities are identified; Response activities are enumerated | AC-21 (1) automated decision support; SI- 4 (3) automated tool and mechanism integration; SI-18 (1) automation support | | |\r\n| 6.5.2 | Implement SOAR Tools | 6.5 Security Orchestration, Automation & Response (SOAR) | Target Level ZT | 14.9 | DoD enterprise working with Organizations develops a standard set of requirements for security orchestration, automation, and response (SOAR) tooling to enable target level ZTA functions. DoD Organizations use approved requirements to procure and implement SOAR solution. Basic infrastructure integrations for future SOAR functionality is completed. | Develop requirements for SOAR tool; Procure SOAR tools | | Standardized API Calls & Schemas Pt1; Workflow Enrichment Pt1 | |\r\n| 6.5.3 | Implement Playbooks | 6.5 Security Orchestration, Automation & Response (SOAR) | Advanced ZT | 14.0 | DoD organizations review all existing playbooks to identify for future automation. Existing manual and automated processes missing playbooks have playbooks developed. Playbooks are prioritized for automation to be integrated with the Automated Workflows activities covering Critical Processes. Manual processes without playbooks are authorized using a risk based methodical approach. | When possible automated playbooks based on automated workflows capability; Manual Playbooks are developed and implemented | CA-7 (6) automation support for monitoring; CM-3 (1) automated documentation, notification, and prohibition of changes; CM-3 (5) automated security response | | |\r\n| 6.6.1 | Tool Compliance Analysis | 6.6 API Standardization | Target Level ZT | 7.3 | Automation and Orchestration tooling and solutions are analyzed for compliance and capabilities based on the DoD Enterprise programmatic interface standard and requirements. Any additional tooling or solutions are identified to support the programmatic interface standards and requirements. | API status is determined compliance or non-compliance to API standards; Tools to be used are Identified | | | |\r\n| 6.6.2 | Standardized API Calls & Schemas Pt1 | 6.6 API Standardization | Target Level ZT | 13.6 | The DoD enterprise works with organizations to establish a programmatic interface (e.g., API) standard and requirements as needed to enable target ZTA functionalities. DoD Organizations update programmatic interfaces to the new standard and mandate newly acquired/developed tools to meet the new standard. Tools unable to meet the standard are allowed by exception using a risk based methodical approach. | Initial calls and schemas are implemented; Non-compliant tools are replaced | | | Implement SDN Programable Infrastructure; Implement SOAR Tools; Standardized API Calls & Schemas Pt2 |\r\n| 6.6.3 | Standardized API Calls & Schemas Pt2 | 6.6 API Standardization | Target Level ZT | 14.2 | DoD Organizations complete the migration to the new programmatic interface standard. Tools marked for decommission in the previous activity are retired and functions are migrated to modernized tools. Approved schemas are adopted based on the DoD Enterprise standard/requirements. | All calls and schemas are implemented | | Standardized API Calls & Schemas Pt1 | |\r\n| 6.7.1 | Workflow Enrichment Pt1 | 6.7 Security Operations Center (SOC) & Incident Response (IR) | Target Level ZT | 7.3 | DoD Enterprise works with organizations to establish a cybersecurity incident response standard using industry best practices such as NIST. DoD Organizations utilize the enterprise standard to determine incident response workflows. External sources of enrichment are identified for future integration. | Threat events are identified; Workflows for threat events are developed | | | Implement SOAR Tools; Workflow Enrichment Pt2 |\r\n| 6.7.2 | Workflow Enrichment Pt2 | 6.7 Security Operations Center (SOC) & Incident Response (IR) | Target Level ZT | 9.1 | DoD organizations identify and establish extended workflows for additional incident response types. Initial enrichment data sources are used for existing workflows. Additional enrichment sources are identified for future integrations. | Workflows for Advanced threat events are developed; Advanced Threat events are identified | SI-4 (7) automated response to suspicious events | Workflow Enrichment Pt1 | Workflow Enrichment Pt3 |\r\n| 6.7.3 | Workflow Enrichment Pt3 | 6.7 Security Operations Center (SOC) & Incident Response (IR) | Advanced ZT | 12.4 | DoD organizations use final enrichment data sources on basic and extended threat response workflows. | Enrichment data has been identified; Enrichment data is integrated into workflows | | Workflow Enrichment Pt2 | Automated Workflow |\r\n| 6.7.4 | Automated Workflow | 6.7 Security Operations Center (SOC) & Incident Response (IR) | Advanced ZT | 14.4 | DoD organizations focus on automating Security Orchestration, Automation and Response (SOAR) functions and playbooks. Manual processes within security operations are identified and fully automated as possible. Remaining manual processes are decommissioned when possible or marked for exception using a risk based approach. | Workflow processes are fully automated; Manual Processes have been identified; Remaining Processes are marked as exceptions and documented | MA-2 (2) automated maintenance activities; PE-8 (1) automated records maintenance and review; RA-5 (6) automated trend analysis; SC-7 (17) automated enforcement of protocol formats; SI-5 (1) automated alerts and advisories; SI-7 (2) automated notifications of integrity violations; SI-7 (5) automated response to integrity violations | Workflow Enrichment Pt3; Implement AI automation tools; Enterprise Integration & Workflow Provisioning Pt2 | Continuous Authorization to Operate (cATO) Pt2 |\r\n| 7.1.1 | Scale Considerations | 7.1 Log All Traffic (Network, Data, Apps, Users) | Target Level ZT | 11.6 | DoD Organizations conduct analysis to determine current and future needs of scaling. Scaling is analyzed following common industry best practice methods and ZT Pillars. The team works with existing Business Continuity Planning (BCP) and Disaster Recovery Planning (DPR) groups to determine distributed environment needs in emergencies and as organizations grow. | Sufficient infrastructure in place; Distributed environment established; Sufficient bandwidth for network traffic | | | |\r\n| 7.1.2 | Log Parsing | 7.1 Log All Traffic (Network, Data, Apps, Users) | Target Level ZT | 6.3 | DoD Organizations identify and prioritize log and flow sources (e.g., Firewalls, Endpoint Detection & Response, Active Directory, Switches, Routers, etc.) and develop a plan for collection of high priority logs first then low priority. An open industry-standard log format is agreed upon at the DoD Enterprise level with the Organizations and implemented in future procurement requirements. Existing solutions and technologies are migrated to the format on a continual basis. | Standardized log formats; Rules developed for each log format | | | Implement Analytics Tools; Asset ID & Alert Correlation |\r\n| 7.1.3 | Log Analysis | 7.1 Log All Traffic (Network, Data, Apps, Users) | Target Level ZT | 10.3 | Common user and device activities are identified and prioritized based on risk. Activities deemed the most simplistic and risky have analytics created using different data sources such as logs. Trends and patterns are developed based on the analytics collected to look at activities over longer periods of time. | Develop analytics per activity; Identify activities to analyze | RA-5 (10) correlate scanning information; SI-4 (13) analyze traffic and event patterns; SI-4 (18) analyze traffic and covert exfiltration | | Establish User Baseline Behavior; User/Device Baselines; Baseline & Profiling Pt1 |\r\n| 7.2.1 | Threat Alerting Pt1 | 7.2 Security Information and Event Management (SIEM) | Target Level ZT | 7.5 | DoD Organizations utilize existing Security Information and Event Management (SIEM) solution to develop basic rules and alerts for common threat events (malware, phishing, etc.) Alerts and/or rule firings are fed into the parallel βAsset ID & Alert Correlationβ activity to being automation of responses. | Rules developed for threat correlation | | | Threat Alerting Pt2; Implement Extended Detection & Response (XDR) Tools and Integrate with C2C Pt1 |\r\n| 7.2.2 | Threat Alerting Pt2 | 7.2 Security Information and Event Management (SIEM) | Target Level ZT | 16.5 | DoD Organizations expand threat alerting in the Security Information and Event Management (SIEM) solution to include Cyber Threat Intelligence (CTI) data feeds. Deviation and anomaly rules are developed in the SIEM to detect advanced threats. | Develop analytics to detect deviations | | Threat Alerting Pt1; Cyber Threat Intelligence Program Pt1 | Threat Alerting Pt3 |\r\n| 7.2.3 | Threat Alerting Pt3 | 7.2 Security Information and Event Management (SIEM) | Advanced ZT | 12.9 | Threat Alerting is expanded to include advanced data sources such as Extended Detection & Response (XDR), User & Entity Behavior Analytics (UEBA), and User Activity Monitoring (UAM). These advanced data sources are used to develop improved anomalous and pattern activity detections. | Identify Triggering Anomalous Events; Implement Triggering Policy | AU-6 (6) correlation with physical monitoring; PE-6 (4) monitoring physical access to systems | Threat Alerting Pt2; Implement Extended Detection & Response (XDR) Tools and Integrate with C2C Pt2 | Continuous Authorization to Operate (cATO) Pt2 |\r\n| 7.2.4 | Asset ID & Alert Correlation | 7.2 Security Information and Event Management (SIEM) | Target Level ZT | 10.2 | DoD Organizations develop basic correlation rules using asset and alert data. Response to common threat events (e.g., malware, phishing, etc.) are automated within the Security Information and Event Management (SIEM) solution. | Rules developed for asset ID based responses | | Log Parsing | |\r\n| 7.2.5 | User/Device Baselines | 7.2 Security Information and Event Management (SIEM) | Target Level ZT | 13.0 | DoD Organizations develop user and device baseline approaches based on DoD Enterprise standards for the appropriate pillar. Attributes utilized in baselining are pulled from the enterprise wide standards developed in cross pillar activities. | Identify user and device baselines | | Implement User & Entity Behavior Activity (UEBA) and User Activity Monitoring (UAM) Tooling; Log Analysis | User Activity Monitoring Pt1; Entity Activity Monitoring Pt1 |\r\n| 7.3.1 | Implement Analytics Tools | 7.3 Common Security and Risk Analytics | Target Level ZT | 12.1 | DoD Organizations procure and implement basic Cyber-focused analytics tools. Analytics development is prioritized based on risk and complexity looking for easy impactful analytics first. Continued analytics development focuses on Pillar requirements to better meet reporting needs. | Develop requirements for analytic environment; Procure and implement analytic tools | | Log Parsing | |\r\n| 7.3.2 | Establish User Baseline Behavior | 7.3 Common Security and Risk Analytics | Target Level ZT | 13.8 | Utilizing the analytics developed for users and devices in a parallel activity, baselines are established in a technical solution. These baselines are applied to an identified set of users based on risk initially and then expanded to the larger DoD Organization user base. The technical solution used is integrated with machine learning functionality to begin automation. | Identify users for baseline; Establish ML-based baselines | | Implement User & Entity Behavior Activity (UEBA) and User Activity Monitoring (UAM) Tooling; Log Analysis | |\r\n| 7.4.1 | Baseline & Profiling Pt1 | 7.4 User and Entity Behavior Analytics | Target Level ZT | 12.3 | Utilizing the analytics developed for users and devices in a parallel activity, common profiles are created for typical user and device types. Analytics taken from baselining are updated to look at larger containers, profiles. | Develop analytics to detect changing threat conditions; Identify user and device threat profiles | | Implement User & Entity Behavior Activity (UEBA) and User Activity Monitoring (UAM) Tooling; Log Analysis | Baseline & Profiling Pt2; UEBA Baseline Support Pt 1 |\r\n| 7.4.2 | Baseline & Profiling Pt2 | 7.4 User and Entity Behavior Analytics | Advanced ZT | 22.7 | DoD Organizations expand baselines and profiles to include unmanaged and non-standard device types including Internet of Things (IoT) and Operational Technology (OT) through data output monitoring. These devices are again profiled based on standardized attributes and use cases. Analytics are updated to consider the new baselines and profiles accordingly enabling further detections and response. Specific risky users and devices are automatically prioritized for increased monitoring based on risk. Detection and response are integrated with cross pillar functionalities. | Add threat profiles for IoT and OT devices; Develop and extend analytics; Extend threat profiles to individual users and devices | | Baseline & Profiling Pt1 | |\r\n| 7.4.3 | UEBA Baseline Support Pt 1 | 7.4 User and Entity Behavior Analytics | Advanced ZT | 6.3 | User & Entity Behavior Analytics (UEBA) within DoD Organizations expands monitoring to advanced analytics such as Machine Learning (ML). These results are in turn reviewed and fed back into the ML algorithms to improve detection and response. | Implement ML-based Analytics to detect anomalies | RA-3 (4) predictive cyber analytics; SI-4 (25) optimize network traffic analysis | Baseline & Profiling Pt1 | AI-enabled Network Access; UEBA Baseline Support Pt2 |\r\n| 7.4.4 | UEBA Baseline Support Pt 2 | 7.4 User and Entity Behavior Analytics | Advanced ZT | 6.3 | User & Entity Behavior Analytics (UEBA) within DoD Organizations completes it expansion by using traditional and machine learning (ML) based results to be fed into Artificial Intelligence (AI) algorithms. Initially AI based detections are supervised but ultimately using advanced techniques such as neural networks, UEBA operators are not part of the learning process | Implement ML-based Analytics to detect anomalies | | UEBA Baseline Support Pt1 | |\r\n| 7.5.1 | Cyber Threat Intelligence Program Pt1 | 7.5 Threat Intelligence Integration | Target Level ZT | 9.9 | The DoD Enterprise works with the Organizations to develop and Cyber Threat Intelligence (CTI) program policy, standard and process. Organizations utilize this documentation to develop organizational CTI teams with key mission/task stakeholders. CTI Teams integrate common feeds of data with the Security Information and Event Management (SIEM) for improved alerting and response. Integrations with Device and Network enforcement points (e.g., Firewalls, Endpoint Security Suites, etc.) are created to conduct basic monitoring of CTI driven data. | Cyber Threat Intelligence team is in place with critical stakeholders; Public and Baseline CTI feeds are being utilized by SIEM for alerting; Basic integration points exist with Device and Network enforcement points (e.g., NGAV, NGFW, NG-IPS) | AU-6 (5) integrated analysis of audit records; SI-4 (17) integrated situational awareness | | Cyber Threat Intelligence Program Pt2; Threat Alerting Pt 2 |\r\n| 7.5.2 | Cyber Threat Intelligence Program Pt2 | 7.5 Threat Intelligence Integration | Target Level ZT | 19.5 | DoD Organizations expand their Cyber Threat Intelligence (CTI) teams to include new stakeholders as appropriate. Authenticated, private and controlled CTI data feeds are integrated into Security Information and Event Management (SIEM) and enforcement points from the Device, User, Network and Data pillars. | Cyber Threat Intelligence team is in place with extended stakeholders as appropriate; Controlled and Private feed are being utilized by SIEM and other appropriate Analytics tools for alerting and monitoring; Integration is in place for extended enforcement points within the Device, User, Network and Data pillars (UEBA, UAM) | AU-5 (2) real-time alerts; SI-6 (3) report verification results | Cyber Threat Intelligence Program Pt1 | |\r\n| 7.6.1 | AI-enabled Network Access | 7.6 Automated Dynamic Policies | Advanced ZT | 27.8 | DoD Organizations utilize the SDN Infrastructure and Enterprise Security Profiles to enable Artificial Intelligence (AI)/Machine Learning (ML) driven network access. Analytics from previous activities is used to teach the AI/ML algorithms improving decision making. | Network Access is AI driven based on environment analytics | SI-8 (3) continuous learning capability | UEBA Baseline Support Pt1; Periodic Authentication; Rule Based Dynamic Access Pt1 The following activities are to be completed in parallel: Comprehensive Data Activity Monitoring User Activity Monitoring Pt2 Entity Activity Monitoring Pt2 | Real-Time Access Decisions; AI- enabled Dynamic Access Control |\r\n| 7.6.2 | AI-enabled Dynamic Access Control | 7.6 Automated Dynamic Policies | Advanced ZT | 24.4 | DoD Organizations utilize previous rule based dynamic access to teach Artificial Intelligence (AI)/Machine Learning (ML) algorithms to make access decision to various resources. The βAI-enabled Network Accessβ activity algorithms are updated to enable broader decision making to all DAAS. | JIT/JEA are integrated with AI; Access is AI driven based on environment analytics | | Continuous Authentication Pt2; AI- enabled Network Access |\t|",
+ "style": "info"
+ },
+ "conditionalVisibility": {
+ "parameterName": "DoDZT",
+ "comparison": "isEqualTo",
+ "value": "Activities"
+ },
+ "name": "ZTActivities"
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "items": [
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "# [Recommended Data Connectors](https://docs.microsoft.com/azure/sentinel/connect-data-sources)\r\n---\r\n\r\nAfter onboarding Microsoft Sentinel into your workspace, connect data sources to start ingesting your data into Microsoft Sentinel. Microsoft Sentinel comes with many connectors for Microsoft products, available out of the box and providing real-time integration. For example, service-to-service connectors include Microsoft 365 Defender connectors and Microsoft 365 sources, such as Office 365, Azure Active Directory (Azure AD), Microsoft Defender for Identity, and Microsoft Defender for Cloud Apps. Check out these references if you're new to Microsoft Sentinel."
+ },
+ "customWidth": "40",
+ "name": "NS Guide"
+ },
+ {
+ "type": 1,
+ "content": {
+ "json": ""
+ },
+ "customWidth": "10",
+ "name": "text - 2"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "b1cd1f8a-e807-4deb-93f4-7812e5ed014a",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Data Connectors >>",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorsBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights"
+ }
+ }
+ ]
+ },
+ "customWidth": "20",
+ "name": "EL0"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "nav",
+ "links": [
+ {
+ "id": "b9a6293e-1c7b-4ec2-ad2a-d72b5ee01722",
+ "cellValue": "https://docs.microsoft.com/azure/sentinel/best-practices",
+ "linkTarget": "Url",
+ "linkLabel": "Best Practices",
+ "style": "link"
+ },
+ {
+ "id": "1bad541e-219a-4277-9510-876b0e8cad51",
+ "cellValue": "https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/azure-sentinel-all-in-one-accelerator/ba-p/1807933",
+ "linkTarget": "Url",
+ "linkLabel": "Microsoft Sentinel All-In-One Accelerator",
+ "style": "link"
+ },
+ {
+ "id": "7e8ff8aa-f632-4a4d-90cf-a71da0dc6b31",
+ "cellValue": "https://docs.microsoft.com/learn/browse/?wt.mc_id=resilience_skilling_webpage_gdc&terms=sentinel",
+ "linkTarget": "Url",
+ "linkLabel": "Microsoft Sentinel Training",
+ "style": "link"
+ }
+ ]
+ },
+ "customWidth": "40",
+ "name": "links - 29"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "group - 7"
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "## Event Logging (EL0) Connectors",
+ "style": "info"
+ },
+ "name": "text - 13"
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Azure Activity Connector](https://docs.microsoft.com/azure/azure-monitor/essentials/activity-log)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "909d0019-23cb-43ad-8285-9f1dca1cd1be",
+ "version": "KqlParameterItem/1.0",
+ "name": "AzureActivity",
+ "label": "Status",
+ "type": 1,
+ "query": "AzureActivity\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "Azure Activity Connector"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "58cc25ab-a9af-4516-99e1-fa22e0637a76",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "AzureActivity"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "33",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Azure Active Directory (AAD) Connector](https://docs.microsoft.com/azure/sentinel/connect-azure-active-directory)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "23ba579d-c894-43be-9fe1-d1b04bc34d7a",
+ "version": "KqlParameterItem/1.0",
+ "name": "SignInLogs",
+ "label": "Status",
+ "type": 1,
+ "query": "SigninLogs\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "Azure Active Directory"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "7c97e893-29f3-4d4c-a379-f220bb82518c",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "AzureActiveDirectory"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Azure Active Directory (AAD) Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Office 365 Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#microsoft-office-365)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "68bd12c8-e473-45d1-8bbc-2dd9f326ea69",
+ "version": "KqlParameterItem/1.0",
+ "name": "OfficeActivity",
+ "label": "Status",
+ "type": 1,
+ "query": "OfficeActivity\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "Azure Activity Connector - Copy - Copy"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "6a86eb8d-5487-4aad-ae7b-b526e68a249f",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "Office365"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Office 365 Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Microsoft Defender for Cloud Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#microsoft-defender-for-cloud)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "1673e4cf-354f-4a42-bed2-2374be47779e",
+ "version": "KqlParameterItem/1.0",
+ "name": "MDfC",
+ "label": "Status",
+ "type": 1,
+ "query": "SecurityAlert\r\n| where ProviderName == \"Azure Security Center\"\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "Azure Activity Connector - Copy - Copy - Copy"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "56600b70-0e55-433a-be86-b7c561bced8b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "AzureSecurityCenter"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Microsoft Defender for Cloud Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Network Security Groups (NSG) Connector](https://docs.microsoft.com/azure/virtual-network/virtual-network-nsg-manage-log)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "b17ce357-e8d5-4c7c-a4f0-765598462a1c",
+ "version": "KqlParameterItem/1.0",
+ "name": "NSG",
+ "label": "Status",
+ "type": 1,
+ "query": "AzureDiagnostics\r\n| where Category == \"NetworkSecurityGroupEvent\"\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "Azure Activity Connector - Copy - Copy - Copy - Copy"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "935bb630-1fce-4021-b7b4-c010b9e05973",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "AzureNSG"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Network Security Groups (NSG) Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Windows Security Events (AMA) Connector](https://docs.microsoft.com/azure/sentinel/connect-azure-windows-microsoft-services?tabs=SA%2CAMA#windows-agent-based-connections)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "d9af27d9-8c90-4c85-a57f-f329257d9956",
+ "version": "KqlParameterItem/1.0",
+ "name": "AMA",
+ "label": "Status",
+ "type": 1,
+ "query": "SecurityEvent\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "Azure Activity Connector - Copy - Copy - Copy - Copy - Copy"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d002eb41-c632-429b-8504-846b69314620",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "WindowsSecurityEvents"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Windows Security Events (AMA) Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Security Events via Legacy Agent Connector](https://docs.microsoft.com/azure/sentinel/connect-azure-windows-microsoft-services?tabs=SA%2CLAA#windows-agent-based-connections)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "b2737fbc-c0e2-4584-9fba-ee7d057d7db0",
+ "version": "KqlParameterItem/1.0",
+ "name": "SecurityEvent",
+ "label": "Status",
+ "type": 1,
+ "query": "SecurityEvent\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "Azure Activity Connector - Copy - Copy - Copy - Copy - Copy - Copy"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "9a8b0649-e79b-4a30-be25-4a5486f302ee",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "SecurityEvents"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Security Events via Legacy Agent Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [DNS Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#windows-dns-server-preview)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "8b7ac3ca-b46c-43e0-ae8c-e2b5189596bc",
+ "version": "KqlParameterItem/1.0",
+ "name": "DNS",
+ "label": "Status",
+ "type": 1,
+ "query": "DnsEvents\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces",
+ "value": null
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "Azure Activity Connector - Copy - Copy - Copy - Copy - Copy - Copy"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "2d8731f5-c225-4a39-9914-6391b2c89ecb",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "DNS"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "DNS Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Azure Storage Accounts Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#azure-storage-account)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "4f291c03-8d98-47b6-ba82-1282322bb7a5",
+ "version": "KqlParameterItem/1.0",
+ "name": "StorageLogs",
+ "label": "Status",
+ "type": 1,
+ "query": "StorageBlobLogs\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "Azure Activity Connector - Copy - Copy - Copy - Copy - Copy - Copy - Copy"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "6d9cd26b-3fcd-4556-b2eb-3dcb711c4de4",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "AzureStorageAccount"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Azure Storage Logs Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Common Event Format (CEF) Connector](https://docs.microsoft.com/azure/sentinel/connect-common-event-format)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "4fcf795c-75b8-4010-bd24-1d66511ff6e8",
+ "version": "KqlParameterItem/1.0",
+ "name": "CommonSecurityLog",
+ "label": "Status",
+ "type": 1,
+ "query": "CommonSecurityLog\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "Azure Activity Connector - Copy - Copy - Copy - Copy - Copy - Copy - Copy - Copy"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "452e02e1-b0c4-4b9b-8a54-bc9295db22b9",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "CEF"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Common Event Format (CEF) Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Syslog Connector](https://docs.microsoft.com/azure/sentinel/connect-syslog)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "fa63a08f-dd08-4e11-bcb6-c075a6d6c15c",
+ "version": "KqlParameterItem/1.0",
+ "name": "Syslog",
+ "label": "Status",
+ "type": 1,
+ "query": "Syslog\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "Azure Activity Connector - Copy - Copy - Copy - Copy - Copy - Copy - Copy - Copy - Copy"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "021644a3-bd51-4b09-8117-017a89c71d58",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "Syslog"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Syslog Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Amazon Web Services (AWS) Connector](https://docs.microsoft.com/azure/sentinel/connect-aws?tabs=s3)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "18ed59f0-c497-44b1-94b7-8700051cf189",
+ "version": "KqlParameterItem/1.0",
+ "name": "AWS",
+ "label": "Status",
+ "type": 1,
+ "query": "AWSCloudTrail\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "Azure Activity Connector - Copy - Copy - Copy - Copy - Copy - Copy - Copy - Copy - Copy - Copy - Copy"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "393c465e-4398-428b-8da2-87ac07d8a987",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "AWS"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Amazon Web Services (AWS) Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Amazon Web Services (AWS) S3 Connector](https://docs.microsoft.com/azure/sentinel/connect-aws?tabs=s3)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "AWSS3",
+ "label": "Status",
+ "type": 1,
+ "query": "AWSVPCFlow\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "Azure Activity Connector - Copy - Copy - Copy - Copy - Copy - Copy - Copy - Copy - Copy - Copy"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "AwsS3"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Amazon Web Services (AWS) S3 Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Google Cloud Platform IAM Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#google-workspace-g-suite-preview)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "GCP",
+ "label": "Status",
+ "type": 1,
+ "query": "GCP_IAM_CL\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces",
+ "value": null
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 3"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "1f2ba663-dd7a-49b6-87ba-0b8adf6d2d34"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Amazon Web Services (AWS) S3 Connector - Copy",
+ "styleSettings": {
+ "showBorder": true
+ }
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "group - 5",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "## Basic Event Logging (EL1) Connectors",
+ "style": "info"
+ },
+ "name": "text - 13"
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Microsoft 365 Defender Connector](https://docs.microsoft.com/azure/sentinel/connect-microsoft-365-defender?tabs=MDE)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "M365Defender",
+ "label": "Status",
+ "type": 1,
+ "query": "AlertEvidence\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 3"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "MicrosoftThreatProtection"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Microsoft 365 Defender Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Microsoft Defender for Endpoint Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#microsoft-defender-for-endpoint)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "MDE",
+ "label": "Status",
+ "type": 1,
+ "query": "SecurityAlert\r\n| where ProviderName == \"MDATP\"\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 3"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "MicrosoftDefenderAdvancedThreatProtection"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Microsoft 365 Defender Connector - Copy",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Azure Firewall Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#azure-firewall)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "AzureFirewall",
+ "label": "Status",
+ "type": 1,
+ "query": "AzureDiagnostics\r\n| where ResourceType == \"AZUREFIREWALLS\"\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 1"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "AzureFirewall"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Azure Firewall Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Windows Firewall Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#windows-firewall)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "WindowsFirewall",
+ "label": "Status",
+ "type": 1,
+ "query": "WindowsFirewall\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 3"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "WindowsFirewall"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Windows Firewall Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Azure Web Application Firewall Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#azure-web-application-firewall-waf)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "AzureWAF",
+ "label": "Status",
+ "type": 1,
+ "query": "AzureDiagnostics | where ResourceType in (\"APPLICATIONGATEWAYS\", \"FRONTDOORS\", \"CDNWEBAPPLICATIONFIREWALLPOLICIES\", \"PROFILES\")\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 3"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "WAF"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Azure Web Application Firewall Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Azure SQL Databases Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#azure-sql-databases)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "8b7ac3ca-b46c-43e0-ae8c-e2b5189596bc",
+ "version": "KqlParameterItem/1.0",
+ "name": "SQL",
+ "label": "Status",
+ "type": 1,
+ "query": "AzureDiagnostics | where Category contains \"SQL\"\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 3"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "2d8731f5-c225-4a39-9914-6391b2c89ecb",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "AzureSql"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "SQL Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Azure Key Vault Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#azure-key-vault)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "AzureKeyVault",
+ "label": "Status",
+ "type": 1,
+ "query": "AzureDiagnostics | where ResourceProvider == \"MICROSOFT.KEYVAULT\"\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 3"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "AzureKeyVault"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Azure Key Vault Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Azure DDoS Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#azure-ddos-protection)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "DDoS",
+ "label": "Status",
+ "type": 1,
+ "query": "AzureDiagnostics | where ResourceType == \"PUBLICIPADDRESSES\"\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "Azure Activity Connector - Copy - Copy - Copy - Copy - Copy - Copy - Copy - Copy - Copy - Copy"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "DDOS"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Azure DDoS Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [VMware ESXi Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#vmware-esxi-preview)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "VMwareESXi",
+ "label": "Status",
+ "type": 1,
+ "query": "VMwareESXi\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces",
+ "value": null
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 3"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "VMwareESXi"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "VMware ESXi Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Microsoft Defender for Cloud: Continuous Export](https://docs.microsoft.com/azure/defender-for-cloud/continuous-export?tabs=azure-portal)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "SecurityRecommendation",
+ "label": "Status",
+ "type": 1,
+ "query": "SecurityRecommendation\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 3"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Feature",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "SecurityMenuBlade",
+ "extensionName": "Microsoft_Azure_Security"
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Continuous Export Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "group - 6",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "## Intermediate Event Logging (EL2) Connectors",
+ "style": "info"
+ },
+ "name": "text - 13"
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Azure Information Protection Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#azure-information-protection-preview)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "InformationProtectionLogs_CL",
+ "type": 1,
+ "query": "InformationProtectionLogs_CLββ\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces",
+ "label": "Status",
+ "value": null
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 1"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "AzureInformationProtection"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Azure Information Protection Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Dynamics 365 Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#dynamics-365)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "Dynamics365Activity",
+ "label": "Status",
+ "type": 1,
+ "query": "Dynamics365Activity\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 1"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "Dynamics365"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Dynamics 365 Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Azure Kubernetes Service (AKS) Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#azure-kubernetes-service-aks)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "AKS",
+ "label": "Status",
+ "type": 1,
+ "query": "AzureDiagnostics\r\n| where Category == \"kube-audit\"\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 1"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "AzureKubernetes"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Azure Kubernetes Service (AKS) Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Qualys Vulnerability Management Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#qualys-vulnerability-management-vm-preview)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "Qualys",
+ "label": "Status",
+ "type": 1,
+ "query": "QualysHostDetection_CL\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces",
+ "value": null
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 1"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "QualysVulnerabilityManagement"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Qualys Vulnerability Management Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "group - 6"
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "## Advanced Event Logging (EL3) Connectors",
+ "style": "info"
+ },
+ "name": "text - 13"
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Entity Behavior (UEBA)](https://docs.microsoft.com/azure/sentinel/enable-entity-behavior-analytics)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "BehaviorAnalytics",
+ "label": "Status",
+ "type": 1,
+ "query": "BehaviorAnalyticsββ\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 1"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Feature",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "EntitySearchBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights"
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Entity Behavior (UEBA) Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Azure Active Directory Identity Protection Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#azure-active-directory-identity-protection)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "AADIP",
+ "label": "Status",
+ "type": 1,
+ "query": "SecurityAlert | where ProductName == \"Azure Active Directory Identity Protection\"ββ\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 1"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "AzureActiveDirectoryIdentityProtection"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Azure Active Directory Identity Protection Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Threat Intelligence TAXII Connector](https://docs.microsoft.com/azure/sentinel/connect-threat-intelligence-taxii)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "TAXII",
+ "label": "Status",
+ "type": 1,
+ "query": "ThreatIntelligenceIndicator | where SourceSystem !in (\"SecurityGraph\", \"Microsoft sentinel\", \"Microsoft Sentinel\") ββ\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 1"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "ThreatIntelligenceTaxii"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Threat Intelligence TAXII Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Threat Intelligence Platform Connector](https://docs.microsoft.com/azure/sentinel/connect-threat-intelligence-tip)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "ThreatIntelligence",
+ "label": "Status",
+ "type": 1,
+ "query": "ThreatIntelligenceIndicator | where SourceSystem in (\"SecurityGraph\", \"Microsoft sentinel\", \"Microsoft Sentinel\") ββ\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 1"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "ThreatIntelligence"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Threat Intelligence Platform Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Microsoft Defender for IoT Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#microsoft-defender-for-iot)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "MD4IOT",
+ "label": "Status",
+ "type": 1,
+ "query": "SecurityAlert | where ProductName == \"Azure Security Center for IoT\"ββ\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 1"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "IoT"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Microsoft Defender for IoT Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ },
+ {
+ "type": 12,
+ "content": {
+ "version": "NotebookGroup/1.0",
+ "groupType": "editable",
+ "loadType": "always",
+ "items": [
+ {
+ "type": 1,
+ "content": {
+ "json": "### [Microsoft Purview: Insider Risk Management Connector](https://docs.microsoft.com/azure/sentinel/data-connectors-reference#microsoft-purview-insider-risk-management-irm-preview)"
+ },
+ "customWidth": "33",
+ "name": "text - 2"
+ },
+ {
+ "type": 9,
+ "content": {
+ "version": "KqlParameterItem/1.0",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "parameters": [
+ {
+ "id": "548cdd92-87c3-4e69-be08-52ecca0f76a8",
+ "version": "KqlParameterItem/1.0",
+ "name": "IRM",
+ "label": "Status",
+ "type": 1,
+ "query": "SecurityAlert\r\n| where ProductName == \"Microsoft 365 Insider Risk Management\"ββ\r\n| limit 1\r\n| summarize count()\r\n| extend Results = iff(count_ ==0, \"β Not Connected\", \"β Connected\")\r\n| project Results",
+ "crossComponentResources": [
+ "{Workspace}"
+ ],
+ "timeContext": {
+ "durationMs": 0
+ },
+ "timeContextFromParameter": "TimeRange",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ }
+ ],
+ "style": "pills",
+ "queryType": 0,
+ "resourceType": "microsoft.operationalinsights/workspaces"
+ },
+ "customWidth": "33",
+ "name": "parameters - 1"
+ },
+ {
+ "type": 11,
+ "content": {
+ "version": "LinkItem/1.0",
+ "style": "list",
+ "links": [
+ {
+ "id": "d9b9144c-69bc-4eb2-a747-a9e0d206780b",
+ "linkTarget": "OpenBlade",
+ "linkLabel": "Enable Connector",
+ "style": "secondary",
+ "bladeOpenContext": {
+ "bladeName": "DataConnectorBlade",
+ "extensionName": "Microsoft_Azure_Security_Insights",
+ "bladeParameters": [
+ {
+ "name": "dataConnectorId",
+ "source": "static",
+ "value": "OfficeIRM"
+ }
+ ]
+ }
+ }
+ ]
+ },
+ "customWidth": "33",
+ "name": "EL0"
+ }
+ ],
+ "exportParameters": true
+ },
+ "name": "Microsoft Purview: Insider Risk Management Connector",
+ "styleSettings": {
+ "showBorder": true
+ }
+ }
+ ]
+ },
+ "name": "group - 6"
+ }
+ ],
+ "exportParameters": true
+ },
+ "conditionalVisibility": {
+ "parameterName": "ifess2Visible",
+ "comparison": "isEqualTo",
+ "value": "true"
+ },
+ "name": "Recommended Data Connectors - Copy"
+ }
+ ],
+ "fromTemplateId": "sentinel-DoDZeroTrust",
+ "$schema": "https://github.com/Microsoft/Application-Insights-Workbooks/blob/master/schema/workbook.json"
+}