Policy 16  

Risk Assessment Policy
PCI DSS Req 12.3  ·  the rule Revique must follow
← 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 16. Values shown as [X] are placeholders still to be set.

Purpose

To identify, evaluate, and manage risks to CHD/PHI and information assets through a formal, recurring process.

Scope

Applies to all Revique systems, processes, and data.

Policy statements

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

1A formal risk assessment must be performed at least annually and upon significant change.
2Identified risks must be documented, ranked, and assigned treatment actions.
3A cryptographic and asset inventory must be maintained and reviewed.
4Risk treatment progress must be tracked to closure.

Roles & responsibilities

RoleResponsibility
Security OfficerConduct and document risk assessments.
ManagementReview and accept or treat identified risks.

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→
Revique security documentation  ·  generated 2026-08-13  ·  all identifiers masked  ·  AWS facts collected read-only on 2026-08-13
Policies define the rule; procedures describe the implementation and how to verify it.