PCI Req 2: Secure Configuration & System Hardening

Tap to enlarge

Complete the Identity fields. Each value is validated against the schema before the next step unlocks.

• Domain entity ID (required)

  entityId

  The organisation or system this record is about — lowercase with dashes, e.g. acme-corp-hq. Pick one you have used before, or type a new id to create it.

Tap to enlarge

Complete the Technical controls fields. Each value is validated against the schema before the next step unlocks.

• Vendor Default Passwords Changedoptional

  vendorDefaultPasswordsChanged

  Enter vendor default passwords changed.

• System Hardening Standards Appliedoptional

  systemHardeningStandardsApplied

  Enter system hardening standards applied.

• Insecure Services and Protocols Disabledoptional

  insecureServicesDisabled

  Enter insecure services and protocols disabled.

• All Administrative Access Encrypted (SSH/TLS)optional

  adminAccessEncrypted

  Enter all administrative access encrypted (ssh/tls).

Tap to enlarge

Complete the Governance fields. Each value is validated against the schema before the next step unlocks.

• Compliance Approachoptional

  approachType

  Enter compliance approach.

• Customized Approach Risk Justificationoptional

  customizedApproachJustification

  Enter customized approach risk justification.

Tap to enlarge

Complete the Verdicts fields. Each value is validated against the schema before the next step unlocks.

• Total Controls Evaluatedoptional

  totalControlsEvaluated

  Enter total controls evaluated.

• Controls In Placeoptional

  controlsInPlace

  Enter controls in place.

• In Place with Compensating Controloptional

  controlsInPlaceWithCcw

  Enter in place with compensating control.

• Controls Not Applicableoptional

  controlsNotApplicable

  Enter controls not applicable.

• Controls Not In Placeoptional

  controlsNotInPlace

  Enter controls not in place.

• Controls Not Testedoptional

  controlsNotTested

  Enter controls not tested.