← PCI DSS 4.0.1 · Req 2 — Secure configurations
2.2 — Secure configuration of system components
Requirement
System components are configured and managed securely: configuration standards address known vulnerabilities and are consistent with industry hardening standards, vendor default accounts are removed or have their passwords changed, and only necessary services are enabled.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.