APRA CPS234: The pathway to compliance

Bringing security requirements into website scope

APRA CPS234: The pathway to compliance
OXOAK / Content and design

Practical notes

1 min read

Bringing security requirements into website scope

Inventory data, access roles, suppliers and processing flows, then have the responsible compliance team confirm applicable requirements. A general website brief cannot establish institutional compliance.

Putting data and access into practice

Define purpose, scope, access and retention before collection. Public display, internal processing and sensitive information need distinct permissions.

Checking the result

Complete a workflow with minimal data and identify owners for access, correction and deletion. Responsible specialists must separately confirm applicable legal or sector requirements.

Bringing security requirements into website scope · Working details

Financial services