CIS Controls v8·Control 4.1·critical·Component: Protect

What this control requires

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.
— CIS Controls v8, Control 4.1

In plain English

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). In practice, this means you can prove you establish and maintain end user-level controls on a defined cadence.

Why it matters

The CIS Controls are an industry-vetted, prioritised defence: skipping a safeguard widens the attack surface that the safeguards above and below it assume is closed. Audit frameworks (FedRAMP, PCI DSS, HIPAA) all cite CIS as evidence of due care.

This control is rated critical in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

What an auditor looks for

A CIS-aligned reviewer wants to see (a) which Implementation Group you are targeting, (b) a documented owner for the safeguard, and (c) a tooling or process artefact (config, scan output, ticket) that proves the safeguard runs on the cadence the control demands.

Within Protect, the assessor will trace your implementation back to the catalogue reference (Control 4.1) and look for objective evidence on the latest two assessment cycles.

How to implement

Endpoint Protection

MDM. Make MDM enrollment a hard gate for device access (Intune compliance + Conditional Access, or Jamf + Okta device trust). Unmanaged devices simply don't get a session token.

EDR. Deploy CrowdStrike / SentinelOne / Defender for Endpoint to every server and laptop; alert on any host that stops sending telemetry for >24h.

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Configuration Management

Policy-as-code. Codify the control as Service Control Policies (AWS), Azure Policy initiatives, or Organisation Policy (GCP) so the platform enforces what the document promises.

IaC. Gate Terraform / Pulumi / CloudFormation changes with Checkov / tfsec / OPA so misconfigurations never reach production.

Drift. Run a CSPM (Wiz / Prisma / Defender for Cloud / Security Command Center) over every account and route findings to a single risk register.

Operational checklist

  • Establish And Maintain. Document the trigger, the owner and the cadence.
  • Protect. Document the trigger, the owner and the cadence.
  • Scope: end user, portable, mobile, iot, secure configuration process, iot devices, servers, software.

Evidence to collect

  • User Device Scan. MDM compliance state per user device (Intune / Jamf / Workspace ONE).
  • Policy Document. A signed and version-controlled policy / standard / procedure document.

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

Common pitfalls

  • Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure.
  • Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.
  • Manual cloud-console changes that never make it back to Terraform — drift accumulates until the next outage forces a reconciliation.

Related controls in CIS Controls v8

References

Topics: governance riskendpoint securityapplication securityendpoint protectionpolicy managementconfiguration managementpatch management