PCI DSS 4.0 Requirement 2: Apply Secure Configurations to All System Components
Apply Secure Configurations to All System Components is asked by 13 of the 48 carrier applications, through 20 questions. The evidence to have on file is A hardening baseline for each type of system component, with the date it was last updated. This page maps the control to the questions that reach it; it never says whether an applicant will be offered cover.
PCI DSS 4.0 is read as each entry here is one of the twelve PCI DSS requirement groups, our paraphrase of what the group requires under the PCI DSS title, read from the standard the PCI SSC publishes and never its sentences; a mapping to a requirement does not establish that an applicant is PCI DSS compliant. Every requirement here is our statement of its clause, cited to it, not the instrument verbatim.
Which carriers ask this control?
13 carrier applications reach this control: Aon, Arch Insurance, Aspen American Insurance Company, Beazley, BOXX Insurance, The Cincinnati Insurance Company, CNA, Discovery Insure Ltd, Emergence Insurance Pty Ltd, Encore Fiduciary, Everest Insurance, Markel, Munich Re. A carrier named here is a source document, never a customer or an endorsement.
What evidence should be on file for Requirement 2?
Evidence guidance is our wording, not a statement of any standard and not binding on a carrier or an assessor.
- A hardening baseline for each type of system component, with the date it was last updated
- A configuration scan or build check that compares each live system against its baseline
- A register of default and vendor-supplied accounts with evidence that the credentials were changed or the accounts removed
- The wireless configuration standard and the review that confirms each access point follows it
Common gaps an assessor names
- Default administrative credentials left in place on network gear and appliances
- New systems deployed before the hardened baseline is applied
- Wireless access points installed with the vendor defaults still active
- A baseline that exists on paper but is never checked against the running system
The one or two items a carrier would actually ask for
- A hardening baseline for each type of system component, with the date it was last updated
- A configuration scan or build check that compares each live system against its baseline
The application questions that reach Requirement 2 (20)
Controls reached by the same questions
11.2 (CIS Controls v8), 11.4 (CIS Controls v8), 11.5 (CIS Controls v8), 12.2 (CIS Controls v8), 12.4 (CIS Controls v8), 12.5 (CIS Controls v8), 6.3 (CIS Controls v8), 6.4 (CIS Controls v8), 6.5 (CIS Controls v8), A.5.17 (ISO 27001:2022), A.5.29 (ISO 27001:2022), A.5.9 (ISO 27001:2022), A.7.10 (ISO 27001:2022), A.8.1 (ISO 27001:2022).
This control on the island, all controls on the controls index, the framework on the PCI DSS 4.0 page, the carriers on sources. Map your own answers in the tool.