Cloud Config Checks

Cloud Config Checks draait om één ding: misconfiguraties eruit halen. We controleren je Microsoft 365 / Azure (of vergelijkbare cloud) op instellingen die vaak misgaan en direct risico geven: identity, permissions, sharing, logging en baseline hardening.

Wat checken we (voorbeelden)?

  • Identity & MFA: MFA coverage, legacy auth, risky sign-ins.
  • Conditional Access: policies, uitzonderingen, admin flows.
  • Admin & rollen: privileged roles, least privilege, break-glass accounts.
  • Email security: anti-phishing/anti-spoofing, DMARC/SPF/DKIM (waar relevant).
  • Sharing & data: OneDrive/SharePoint extern delen, gastaccounts, link policies.
  • Logging & audit: audit/retention, alerts, incident-sporen.

Wat krijg je na afloop?

  • Een bevindingenlijst (kritiek/hoog/midden/laag) met uitleg in gewone taal.
  • Een prioriteitenlijst met “quick wins” die je meteen veiliger maken.
  • Concrete aanpak per bevinding (wat aanpassen, waar, en waarom).
  • Optioneel: evidence (screenshots/exports) voor je Evidence Vault.

Waarom dit belangrijk is

De meeste cloud-incidenten beginnen niet met “hackers zijn geniaal”, maar met instellingen die te open staan. Cloud Config Checks pakt dit structureel aan — en is perfect als basislaag onder jouw NIS2-aanpak.

Cloud Config Checks focus on one thing: removing risky misconfigurations. We review your Microsoft 365 / Azure (or similar cloud) for settings that commonly go wrong and create immediate risk: identity, permissions, sharing, logging and baseline hardening.

What we check (examples)

  • Identity & MFA: MFA coverage, legacy authentication, risky sign-ins.
  • Conditional Access: policies, exceptions, admin access flows.
  • Admins & roles: privileged roles, least privilege, break-glass accounts.
  • Email security: anti-phishing/anti-spoofing and DMARC/SPF/DKIM where relevant.
  • Sharing & data: external sharing, guest accounts, link policies.
  • Logging & audit: audit/retention, alerts, incident traceability.

What you receive

  • A findings list (critical/high/medium/low) in plain language.
  • A prioritised quick-win plan to improve security fast.
  • Concrete fix guidance per finding (what to change, where and why).
  • Optional evidence (exports/screenshots) for your Evidence Vault.

Why it matters

Many cloud incidents start with settings that are too open. Cloud Config Checks address this structurally — and provide a strong foundation for a practical NIS2 approach.