Policy 13 — Secure Configuration Policy

← All 21 policies

This page is the rule, not the implementation. It states what Revique must do, at or above the PCI DSS minimum. How Revique actually does it today — the real AWS configuration, the current values, and where an auditor logs in to verify them — is in Procedure 13. Values shown as [X] are placeholders still to be set.

Purpose

To ensure all system components are securely configured, with vendor defaults removed and hardening standards applied.

Scope

Applies to all servers, containers, databases, and services in all environments.

Policy statements

Each statement below is mandatory. The bolded must marks the obligation.

1Vendor default passwords and accounts must be changed or disabled before deployment.

2Unnecessary services, ports, and functionality must be removed or disabled.

3Documented hardening standards must be applied to all system components.

4System configurations must be reviewed for drift on a defined schedule.

Roles & responsibilities

Role	Responsibility
Security Officer	Define hardening standards.
DevOps / IT	Apply and maintain secure configurations.

Enforcement

This policy is issued under the authority of Policy 01 — Information Security Policy and is mandatory for everyone in scope. Compliance is verified through the controls and evidence described in the linked procedure. Failure to comply may result in withdrawal of access and disciplinary action. This policy is reviewed at least annually, or sooner on significant change.

⚙️See the Procedure for this policyHow Revique implements this rule today, the current values, the gaps, and the auditor verification path→