You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Azure security baseline for Microsoft Azure Peering Service
16
16
17
-
This security baseline applies guidance from the [Azure Security Benchmark version 2.0](../security/benchmarks/overview.md) to Microsoft Azure Peering Service. The Azure Security Benchmark provides recommendations on how you can secure your cloud solutions on Azure. The content is grouped by the **security controls** defined by the Azure Security Benchmark and the related guidance applicable to Microsoft Azure Peering Service.**Controls** not applicable to Microsoft Azure Peering Service, or for which the responsibility is Microsoft's, have been excluded.
17
+
This security baseline applies guidance from the [Azure Security Benchmark version 2.0](../security/benchmarks/overview.md) to Microsoft Azure Peering Service. The Azure Security Benchmark provides recommendations on how you can secure your cloud solutions on Azure. The content is grouped by the **security controls** defined by the Azure Security Benchmark and the related guidance applicable to Microsoft Azure Peering Service.
18
18
19
-
To see how Microsoft Azure Peering Service completely maps to the Azure Security Benchmark, see the [full Microsoft Azure Peering Service security baseline mapping file](https://github.com/MicrosoftDocs/SecurityBenchmarks/tree/master/Azure%20Offer%20Security%20Baselines).
19
+
> [!NOTE]
20
+
> **Controls** not applicable to Microsoft Azure Peering Service, or for which the responsibility is Microsoft's, have been excluded. To see how Microsoft Azure Peering Service completely maps to the Azure Security Benchmark, see the **[full Microsoft Azure Peering Service security baseline mapping file](https://github.com/MicrosoftDocs/SecurityBenchmarks/tree/master/Azure%20Offer%20Security%20Baselines)**.
20
21
21
22
## Network Security
22
23
@@ -89,9 +90,9 @@ Use single sign-on to manage and secure access to your organization’s data and
89
90
90
91
**Guidance**: Enable multifactor authentication with Azure Active Directory (Azure AD) and follow Identity and Access Management recommendations from Azure Security Center.
91
92
92
-
How to enable multifactor authentication in Azurehttps://docs.microsoft.com/azure/active-directory/authentication/howto-mfa-getstarted
93
+
-[How to enable multifactor authentication in Azure](../active-directory/authentication/howto-mfa-getstarted.md)
93
94
94
-
How to monitor identity and access within Azure Security Centerhttps://docs.microsoft.com/azure/security-center/security-center-identity-access
95
+
-[How to monitor identity and access within Azure Security Center](../security-center/security-center-identity-access.md)
95
96
96
97
**Responsibility**: Customer
97
98
@@ -101,9 +102,9 @@ How to monitor identity and access within Azure Security Center https://docs.mic
101
102
102
103
**Guidance**: Use Privileged Identity Management (PIM) with Azure Active Directory (Azure AD) for generation of logs and alerts when suspicious or unsafe activity occurs in the environment. In addition, use Azure AD risk detections to view alerts and reports on risky user behavior.
103
104
104
-
How to deploy Privileged Identity Management (PIM)https://docs.microsoft.com/azure/active-directory/privileged-identity-management/pim-deployment-plan
105
+
-[How to deploy Privileged Identity Management (PIM)](../active-directory/privileged-identity-management/pim-deployment-plan.md)
105
106
106
-
Understand Azure AD risk detectionshttps://docs.microsoft.com/azure/active-directory/identity-protection/overview-identity-protection
107
+
-[Understand Azure AD risk detections](../active-directory/identity-protection/overview-identity-protection.md)
107
108
108
109
**Responsibility**: Customer
109
110
@@ -263,7 +264,7 @@ Depending on how security team responsibilities are structured, monitoring for s
263
264
264
265
Security Reader permissions can be applied broadly to an entire tenant (Root Management Group) or scoped to management groups or specific subscriptions.
265
266
266
-
Note: Additional permissions might be required to get visibility into workloads and services.
267
+
Additional permissions might be required to get visibility into workloads and services.
267
268
268
269
-[Overview of Security Reader Role](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#security-reader)
269
270
@@ -409,7 +410,7 @@ Many organizations choose to use Azure Sentinel for “hot” data that is used
409
410
410
411
**Guidance**: In Azure Monitor, set log retention period for Log Analytics workspaces associated with your Azure resources according to your organization's compliance regulations.
411
412
412
-
How to set log retention parameters/azure/azure-monitor/platform/manage-cost-storage#change-the-data-retention-period
413
+
-[How to set log retention parameters](/azure/azure-monitor/platform/manage-cost-storage#change-the-data-retention-period)
0 commit comments