CIS Microsoft 365
Microsoft 365 · 160 controls- Microsoft 365 Foundations v7.0.0160
5 checks explained so far
Library
Check library
Every check ConfigCobra runs, by standard: what it looks at, why it matters, how to check it yourself and what changes when you fix it.
4standards
10CIS benchmarks
10checks explained
Browse by standard
CIS Microsoft Azure
Microsoft Azure · 339 controls- Microsoft Azure Foundations v6.0.0127
- Microsoft Azure Compute Services v2.0.099
- Microsoft Azure Database Services v2.0.049
- Microsoft Azure Storage Services v2.0.064
2 checks explained so far
CIS Google Cloud
Google Cloud · 93 controls- Google Cloud Platform Foundation v5.0.093
2 checks explained so far
CIS AWS
AWS · 306 controls- Amazon Web Services Foundations v7.0.070
- AWS Compute Services v2.0.082
- AWS Database Services v2.0.098
- AWS Storage Services v1.0.056
1 check explained so far
Explained checks
- Administrative accounts should be cloud-only, not synced from on-premises
- Two emergency access accounts have been defined
- The number of Global Administrators should be between two and four
- Administrative accounts should use a license with a reduced application footprint
- Microsoft 365 groups should not be publicly visible
- Ensure that Azure Databricks is deployed in a customer-managed virtual network (VNet)
- Ensure that Network Security Groups are Configured for Databricks Subnets
- Use corporate-managed login credentials instead of consumer accounts
- Enforce multi-factor authentication for all non-service accounts
- Maintain current AWS account contact details
What every check page covers
- Why it mattersThe risk behind the setting, with a cited source.
- How to check it yourselfThe portal path and a read-only command.
- How to fix itPortal steps and a script you run yourself.
- What changes when you fix itWho and what is affected before you apply it.
Run every check on your own cloud
ConfigCobra assesses Microsoft 365, Azure, Google Cloud and AWS against these CIS benchmarks, read-only.