PCI 3DS Core Security Standard
Part 1 Requirement P1-3: Develop and maintain secure systems – PCI 3DS Core Security Standard

PCI 3DS Core Security Standard P1-3.2.5: P1-3.2.5 Build standards remove defaults, excess functions and mixed trust levels

Configuration standards and build procedures require three things: every vendor default account and system setting is changed; all functionality that is not needed is removed or disabled; and functions that need different security levels do not share one system component. The assessor examines the standards, the build procedures and live configurations, and interviews staff.

Maintained by Gerard Blokdyk

What else in your programme already covers this

This control maps to 3 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 3 controls

  • 2.2.2 2.2.2 Vendor default accounts managed
  • 2.2.3 2.2.3 Primary functions with different security levels managed
  • 2.2.4 2.2.4 Only necessary functionality enabled

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Part 1 Requirement P1-3: Develop and maintain secure systems – PCI 3DS Core Security Standard

Query this from an agent

The graph holds this control, the 3 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI 3DS Core Security Standard controls