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
Copy file name to clipboardExpand all lines: articles/security/fundamentals/identity-management-best-practices.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,7 +110,7 @@ To balance security and productivity, you need to think about how a resource is
110
110
111
111
Security is always evolving, and it is important to build into your cloud and identity management framework a way to regularly show growth and discover new ways to secure your environment.
112
112
113
-
Identity Secure Score is a set of recommended security controls that Microsoft publishes that works to provide you a numerical score to objectively measure your security posture and help plan future security improvements. You can also view your score in comparison to those in other industries as well as your own trends over time.
113
+
Identity Secure Score is a set of recommended security controls that Microsoft publishes that works to provide you with a numerical score to objectively measure your security posture and help plan future security improvements. You can also view your score in comparison to those in other industries as well as your own trends over time.
114
114
115
115
-**Plan routine security reviews and improvements based on best practices in your industry.**: Use the Identity Secure Score feature to rank your improvements over time.
116
116
@@ -149,7 +149,7 @@ Following are options and benefits for enabling multifactor authentication:
149
149
This method is available to all licensing tiers but is not able to be mixed with existing Conditional Access policies. You can find more information in [Microsoft Entra Security Defaults](/entra/fundamentals/security-defaults)
150
150
151
151
**Option 2**: [Enable multifactor authentication by changing user state](/entra/identity/authentication/howto-mfa-userstates).
152
-
**Benefit**: This is the traditional method for requiring two-step verification. It works with both [Microsoft Entra multifactor authentication in the cloud and Azure Multi-Factor Authentication Server](/entra/identity/authentication/concept-mfa-howitworks). Using this method requires users to perform two-step verification every time they sign in and overrides Conditional Access policies.
152
+
**Benefit**: This is the traditional method for requiring two-step verification. It works with both [Microsoft Entra multifactor authentication in the cloud and Azure Multifactor Authentication server](/entra/identity/authentication/concept-mfa-howitworks). Using this method requires users to perform two-step verification every time they sign in and overrides Conditional Access policies.
153
153
154
154
To determine where multifactor authentication needs to be enabled, see [Which version of Microsoft Entra multifactor authentication is right for my organization?](/entra/identity/authentication/concept-mfa-howitworks)
155
155
@@ -218,12 +218,12 @@ The following summarizes the best practices found in [Securing privileged access
218
218
219
219
-**Identify and categorize accounts that are in highly privileged roles.**: After turning on Microsoft Entra Privileged Identity Management, view the users who are in the global administrator, privileged role administrator, and other highly privileged roles. Remove any accounts that are no longer needed in those roles, and categorize the remaining accounts that are assigned to admin roles:
220
220
221
-
* Individually assigned to administrative users and can be used for non-administrative purposes (for example, personal email)
222
-
* Individually assigned to administrative users and designated for administrative purposes only
223
-
* Shared across multiple users
224
-
* For emergency access scenarios
225
-
* For automated scripts
226
-
* For external users
221
+
* Individually assigned to administrative users and can be used for non-administrative purposes (for example, personal email)
222
+
* Individually assigned to administrative users and designated for administrative purposes only
223
+
* Shared across multiple users
224
+
* For emergency access scenarios
225
+
* For automated scripts
226
+
* For external users
227
227
228
228
-**Implement “just in time” (JIT) access to further lower the exposure time of privileges and increase your visibility into the use of privileged accounts.**: Microsoft Entra Privileged Identity Management lets you:
**Deploy Microsoft Defender XDR** as your primary unified security platform. Defender XDR automatically correlates alerts from endpoints, identities, email, and cloud apps into unified incidents, providing automated investigation and response at machine speed. For more information, see [Microsoft Defender XDR](/defender-xdr/microsoft-365-defender).
46
46
47
-
**Configure Microsoft Defender for Cloud** with appropriate Defender plans for your workloads (Servers, Storage, Containers, Key Vault). Tune alert thresholds and create suppression rules for known false positives while maintaining threat coverage. For more information, see [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction).
47
+
**Configure Microsoft Defender for Cloud** with appropriate Defender plans for your workloads (Servers, Storage, Containers, Key Vault). Tune alert thresholds and create suppression rules for known false positives, while maintaining threat coverage. For more information, see [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction).
48
48
49
49
**Implement Microsoft Sentinel** for centralized SIEM and SOAR capabilities. Configure analytics rules for automated incident creation with intelligent alert grouping and entity enrichment. Use the investigation graph and entity behavior analytics for comprehensive investigation. For more information, see [Microsoft Sentinel](/azure/sentinel/overview).
Copy file name to clipboardExpand all lines: articles/security/fundamentals/operational-best-practices.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ Azure operational security refers to the services, controls, and features availa
31
31
32
32
We recommend that you require two-step verification for all of your users. This includes administrators and others in your organization who can have a significant impact if their account is compromised (for example, financial officers).
33
33
34
-
There are multiple options for requiring two-step verification. The best option for you depends on your goals, the Microsoft Entra edition you're running, and your licensing program. See [How to require two-step verification for a user](/entra/identity/authentication/howto-mfa-userstates) to determine the best option for you. See the [Microsoft Entra ID](https://www.microsoft.com/security/business/microsoft-entra-pricing) and [Microsoft Entra multifactor authentication](https://azure.microsoft.com/pricing/details/multi-factor-authentication/) pricing pages for more information about licenses and pricing.
34
+
There are multiple options for requiring two-step verification. The best option for you depends on your goals, the Microsoft Entra edition you're running, and your licensing program. See [How to require two-step verification for a user](/entra/identity/authentication/howto-mfa-userstates) to determine the best option for you. See the [Microsoft Entra ID](https://www.microsoft.com/security/business/microsoft-entra-pricing) and [Microsoft Entra Multifactor Authentication](https://azure.microsoft.com/pricing/details/multi-factor-authentication/) pricing pages for more information about licenses and pricing.
35
35
36
36
Following are options and benefits for enabling two-step verification:
37
37
@@ -45,7 +45,7 @@ Following are options and benefits for enabling two-step verification:
45
45
This method is available to all licensing tiers but is not able to be mixed with existing Conditional Access policies. You can find more information in [Microsoft Entra Security Defaults](/entra/fundamentals/security-defaults)
46
46
47
47
**Option 2**: [Enable multifactor authentication by changing user state](/entra/identity/authentication/howto-mfa-userstates).
48
-
**Benefit**: This is the traditional method for requiring two-step verification. It works with both [Microsoft Entra multifactor authentication in the cloud and Azure Multifactor Authentication Server](/entra/identity/authentication/concept-mfa-howitworks). Using this method requires users to perform two-step verification every time they sign in and overrides Conditional Access policies.
48
+
**Benefit**: This is the traditional method for requiring two-step verification. It works with both [Microsoft Entra multifactor authentication in the cloud and Azure Multifactor Authentication server](/entra/identity/authentication/concept-mfa-howitworks). Using this method requires users to perform two-step verification every time they sign in and overrides Conditional Access policies.
49
49
50
50
To determine where multifactor authentication needs to be enabled, see [Which version of Microsoft Entra multifactor authentication is right for my organization?](/entra/identity/authentication/concept-mfa-howitworks)
51
51
@@ -223,7 +223,7 @@ Here are some security best practices to follow after you adopt Azure Policy:
223
223
224
224
-**Policy supports several types of effects. You can read about them in [Azure Policy definition structure](../../governance/policy/concepts/definition-structure.md#policy-rule). Business operations can be negatively affected by the **deny** effect and the **remediate** effect, so start with the **audit** effect to limit the risk of negative impact from policy.**: [Start policy deployments in audit mode](../../governance/policy/concepts/definition-structure.md#policy-rule) and then later progress to **deny** or **remediate**. Test and review the results of the audit effect before you move to **deny** or **remediate**.
225
225
226
-
For more information, see [Create and manage policies to enforce compliance](../../governance/policy/tutorials/create-and-manage.md).
226
+
For more information, see [Create and manage policies to enforce compliance](../../governance/policy/tutorials/create-and-manage.md).
227
227
228
228
-**Identify the roles responsible for monitoring for policy violations and ensuring the right remediation action is taken quickly.**: Have the assigned role monitor compliance through the [Azure portal](../../governance/policy/how-to/get-compliance-data.md#portal) or via the [command line](../../governance/policy/how-to/get-compliance-data.md#command-line).
0 commit comments