What this control covers

Establish and maintain a secure configuration process for enterprise assets (end-user devices, including portable and mobile, non-computing/IoT devices, and servers) and software (operating systems and applications). Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.

Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

How to implement

AWS

Codify the policy intent as SCPs, AWS Config conformance packs, and Security Hub standards so the cloud enforces what the document says.

Azure

Codify in Azure Policy initiatives (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

GCP

Org Policy Service for guardrails and Config Validator in CI to pre-check Terraform plans against policy as code (Rego).

Google Workspace

Endpoint Management (basic/advanced) for BYOD/COPE; require screen lock, disk encryption and OS minimum; block sign-in on jailbroken devices.

GitHub

Dependabot security updates + version updates, plus CodeQL for SAST and a renovate bot for major-version drift management.

On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

Evidence to collect

  • user_device_scan — Output from your MDM/EDR (Intune, Jamf, Kandji) showing managed-device count, posture and last-check-in.
  • policy_document — A signed, version-controlled policy stating leadership intent and the named owner.

Endpoint compliance telemetry (Intune, Jamf) proves managed coverage. Signed policy or standard documents the safeguard. Focus: Establish and Maintain a Secure Configuration Process.

Quick checklist

  • Establish And Maintain — End User / Portable
  • Protect — End User / Portable

Related articles on this site