BreachcraftStandards
Baseline
Entra identity and Conditional Access
Applies to: every tenant in scope. Derived from: CIS Microsoft 365 Foundations
ID-01 Security defaults off, Conditional Access on High
- Statement
- Security defaults are disabled and at least one enforcing Conditional Access policy covers all users.
- Why
- The two do not coexist well; leaving defaults on hides which controls are real.
- Check
- Entra → Properties → Manage security defaults; CA → policies, state
On.
- Evidence
- The property value and the list of enabled policies with their states.
- Remediation
- Disable defaults, publish the equivalent policies, keep one break-glass pair excluded and documented.
ID-02 Legacy authentication blocked Critical
- Statement
- A policy blocks
Other clients for all users except the documented break-glass pair.
- Why
- Legacy protocols ignore MFA and are the most common password-spray target.
- Check
- CA → the legacy-auth policy's client-apps condition.
- Evidence
- Policy id and the condition block.
- Remediation
- Publish the block policy; where a device needs a protocol, scope it to a named group with an owner.
ID-03 MFA required for every admin role Critical
- Statement
- Every role in the privileged-role list requires phishing-resistant MFA or, at minimum, MFA.
- Why
- An admin password alone must not be enough.
- Check
- CA → the admin policy's role condition; Authentication methods → policy.
- Evidence
- Policy id, the role list, and the methods allowed.
- Remediation
- Cover all privileged roles, not a sample; prefer FIDO2 for tier 0.
ID-04 PIM approval on privileged roles (ours) High
- Statement
- Eligible assignments for privileged roles require approval and a bounded activation window.
- Why
- Without approval, eligibility is a delay rather than a gate.
- Check
- PIM → role settings for each privileged role:
approvalRequired, maximum duration, approver list.
- Evidence
- The setting per role and the named approvers.
- Remediation
- Turn on approval, set 1-2 hours, name two approvers per role.
ID-05 Guest access reviewed and restricted Medium
- Statement
- Guest invitations are restricted to named domains or approved senders, and guest access reviews run at least quarterly.
- Why
- Open invitation turns a shared document into a tenant foothold.
- Check
- External collaboration settings; Identity Governance → access reviews.
- Evidence
- The settings, the review schedule, and the last completion.
- Remediation
- Restrict invitations, start a review with auto-remove on no response.
ID-06 Break-glass accounts exist and are tested (ours) High
- Statement
- Two cloud-only accounts hold Global Administrator, are excluded from CA, and the exclusion is recorded with a test date.
- Why
- Every enforcing policy needs a way back in that does not depend on the policy.
- Check
- Users → the two accounts; CA exclusions; the record's test date.
- Evidence
- Account ids, their credential type, the exclusion list, the last test.
- Remediation
- Create or document them, store credentials offline, test quarterly.
ID-07 Consent to applications restricted High
- Statement
- User consent is limited to verified publishers for low-impact scopes; admin consent workflow is enabled.
- Why
- Consent is a grant; an unrestricted user can widen their own access.
- Check
- Enterprise applications → Consent and permissions → user consent settings.
- Evidence
- The setting and the admin-consent workflow state.
- Remediation
- Set to verified publishers for low-impact scopes; enable the workflow.
ID-08 Stale accounts disabled Medium
- Statement
- Accounts with no sign-in in 90 days are disabled or reviewed, and the sign-in report is run monthly.
- Why
- A dormant account keeps its access and its old credential.
- Check
- Sign-in logs, 90-day filter; or
Get-MgAuditLogSignIn.
- Evidence
- The report, the accounts actioned, and the owner who approved.
- Remediation
- Disable, do not delete, so mailboxes and aliases can be recovered. ## Out of scope here Hybrid identity (Entra Connect health), device compliance, and application-level SSO configuration. Each has its own file.
All baselines →
Elsewhere · Services · Academy · Labs · Tools
Breachcraft Security · Evilsaint Ltd · Terms · Privacy