Cis Azure Foundations 5.1.1
DevOps & Securitycis-azure-foundations-5.1.1Cis Azure Foundations 5.1.1 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Ensure 'security defaults' is enabled in Microsoft Entra ID
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/Microsoft_Azure/CIS_Microsoft_Azure_Foundations_Benchmark_v5.0.0/cis-azure-foundations-5.1.1/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-azure-foundations-5-1-1, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Ensure 'security defaults' is enabled in Microsoft Entra ID
Description
[IMPORTANT - Please read the section overview: If your organization pays for Microsoft Entra ID licensing (included in Microsoft 365 E3, E5, F5, or Business Premium, and EM&S E3 or E5 licenses) and CAN use Conditional Access, ignore the recommendations in this section and proceed to the Conditional Access section.]
Security defaults in Microsoft Entra ID make it easier to be secure and help protect your organization. Security defaults contain preconfigured security settings for common attacks.
Security defaults is available to everyone. The goal is to ensure that all organizations have a basic level of security enabled at no extra cost. You may turn on security defaults in the Azure portal.
Rationale
Security defaults provide secure default settings that we manage on behalf of organizations to keep customers safe until they are ready to manage their own identity security settings.
For example, doing the following:
- Requiring all users and admins to register for MFA.
- Challenging users with MFA - when necessary, based on factors such as location, device, role, and task.
- Disabling authentication from legacy authentication clients, which cannot do MFA.
Impact
This recommendation should be implemented initially and then may be overridden by other service/product specific CIS Benchmarks. Administrators should also be aware that certain configurations in Microsoft Entra ID may impact other Microsoft services such as Microsoft 365.
Audit Procedure
Using Azure Portal
- From Azure Home select the Portal Menu.
- Browse to
Microsoft Entra ID>Properties. - Select
Manage security defaults. - Under
Security defaults, verify thatEnabled (recommended)is selected.
Using PowerShell
Connect-MgGraph -Scopes "Policy.Read.All"
(Get-MgPolicyIdentitySecurityDefaultEnforcementPolicy).IsEnabled
Returned value should be true.
Using Azure CLI
az login
az rest --method get --url 'https://graph.microsoft.com/v1.0/policies/identitySecurityDefaultsEnforcementPolicy' --query "isEnabled"
Returned value should be true.
Expected Result
Security defaults should be enabled (IsEnabled = true). The Azure Portal should show Enabled (recommended) selected under Security defaults.
Remediation
Remediate from Azure Portal
- From Azure Home select the Portal Menu.
- Browse to
Microsoft Entra ID>Properties. - Select
Manage security defaults. - Under
Security defaults, selectEnabled (recommended). - Select
Save.
Remediate from PowerShell
Connect-MgGraph -Scopes "Policy.ReadWrite.ApplicationConfiguration"
Update-MgPolicyIdentitySecurityDefaultEnforcementPolicy -IsEnabled $true
(Get-MgPolicyIdentitySecurityDefaultEnforcementPolicy).IsEnabled
Remediate from Azure CLI
az rest --method patch --url 'https://graph.microsoft.com/v1.0/policies/identitySecurityDefaultsEnforcementPolicy' --body '{"isEnabled":true}'
az rest --method get --url 'https://graph.microsoft.com/v1.0/policies/identitySecurityDefaultsEnforcementPolicy' --query "isEnabled"
Default Value
If your tenant was created on or after October 22, 2019, security defaults may already be enabled in your tenant.
References
- https://learn.microsoft.com/en-us/entra/fundamentals/security-defaults
- https://techcommunity.microsoft.com/t5/azure-active-directory-identity/introducing-security-defaults/ba-p/1061414
- https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-identity-management#im-2-protect-identity-and-authentication-systems
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 4.1 Establish and Maintain a Secure Configuration Process | x | x | x |
| v7 | 5.1 Establish Secure Configurations | x | x | x |
Profile
Level 1 | Automated