Endpoint & Workload Protection · EP-Q02

Question: Are all endpoints and workloads protected by baseline security configurations and hardening standards?

Why This Matters

Consistent baseline configurations reduce exploitable weaknesses. Hardening ensures every device or VM starts from a trusted state, limiting privilege escalation and malware spread.

Maturity

0 — Unaware
No standard configurations; default settings left unchanged.
1 — Ad Hoc
Basic OS patches applied manually; hardening inconsistent.
2 — Defined
Baseline images or scripts defined for major platforms.
3 — Managed
Baseline compliance verified periodically; deviations tracked.
4 — Integrated
Automated configuration management with drift detection.
5 — Optimized
Continuous compliance enforced via policy-as-code and secure provisioning.

How to Level Up

From → To Actions
0 → 1 Adopt CIS Benchmarks for Windows/Linux; perform manual checks.
1 → 2 Develop hardened gold images; store hashes for integrity.
2 → 3 Schedule quarterly configuration audits; document exceptions.
3 → 4 Implement Ansible/Chef/SaltStack for automated enforcement.
4 → 5 Shift to immutable infrastructure or desired-state enforcement (e.g., Intune + Defender CSPM).

Enablers

Evidence

KPIs

Low-Cost / Open-Source Options (MSME)

Purpose Tool Notes
Hardening scripts CIS-Cat Lite / Lynis Automated benchmark scanning.
Config management Ansible Simple YAML-based enforcement.
Drift detection OSQuery / Wazuh Monitor deviations in real time.

Common Pitfalls

Compliance Mapping

Standard Clauses / Notes
ISO/IEC 27001:2022 A.8.9 Configuration Management
CERT-In 2022 Section 5 (Endpoint Hardening)
DPDP Act 2023 Sec 9(3) (Security Safeguards)
NIST CSF 2.0 PR.IP-01 to PR.IP-04
NIRMATA Mapping EP-Q02 requires ≥ Level 3 for Stage 1 audit readiness.