CPS 234: what APRA's information security standard says about testing, and what a web application test can evidence
Paragraph 27 of Prudential Standard CPS 234 says an APRA-regulated entity must test the effectiveness of its information security controls through a systematic testing program.
This guide reads paragraphs 27 to 31 from the instrument on the Federal Register of Legislation, shows how the standard reaches information assets that suppliers manage, marks where APRA's guidance in CPG 234 fits, and sets out what a website or web application test can and cannot add to an entity's testing record. It comes with a control-testing calendar you can fill in.
In this guide
CPS 234 control-testing calendar for web-facing applications
A calendar of dated records built from CPS 234 paragraphs 27 to 31 and the paragraphs on information assets that related parties and third parties manage. Rows C1 to C11 make one testing cycle: the inventory of applications, then for each application its frequency, assets other parties manage, tester choice, scope, a check after change, the report, remediation, a developer check and the retest, and finally the sufficiency review that paragraph 31 sets at least annually or on a material change.
How to use itHide the instructions
Row C12 is for a supplier answering a regulated customer. Copy the table into a spreadsheet, keep C1, C11 and C12 once for the whole register, repeat rows C2 to C10 for each application, and put real dates in the "When it falls" column. Rows C6 and C9 send requests, and each spells out its limits in its last column: they are for systems your business runs or holds written authorisation to test, on a staging copy if there is one, with test accounts and invented records. Every other row reads or writes records and sends no requests. The paragraph column gives the standard as made, in its words or a close short form with the paragraph number, and any CPG 234 text in it is guidance, not a requirement. The calendar records evidence. Whether testing meets CPS 234 is for the regulated entity, its Board and internal audit, and APRA, and for a supplier, its regulated customer.
12 rows
Row and record
When it falls
C1. Application inventory
- When it falls
- At the start of each testing cycle, and whenever an application is added, retired or materially changed.
- CPS 234 paragraph, in its words
- Paragraph 27(b): the nature and frequency of testing must be commensurate with the criticality and sensitivity of the information asset. Paragraph 20: the entity must classify its information assets, including those managed by related parties and third parties, by criticality and sensitivity.
- What to record
- One line for each website, portal, API and integration: its name and address, what it does, the data it holds, who runs it (your own team, a related party or a third party), whether it can be reached from the internet, the criticality and sensitivity rating the entity has given it, and the date of its last material change.
- What a website or web application test can supply
- In a Clever Ops web application test, older API versions that still answer are reported, which can show an address or API path the inventory left out.
- Outside what a test shows, and who decides
- The classification. Criticality and sensitivity are the entity's ratings under paragraph 20, not the tester's.
- Limits of this row
- Read-only row: it lists and classifies applications from your own records and sends no requests.
C2. Testing frequency and depth for each application
- When it falls
- Once the application is in C1, at the start of each cycle, and again when any factor in paragraph 27 changes for it.
- CPS 234 paragraph, in its words
- Paragraph 27: test the effectiveness of information security controls through a systematic testing program, with nature and frequency commensurate with (a) the rate at which the vulnerabilities and threats change; (b) the criticality and sensitivity of the information asset; (c) the consequences of an information security incident; (d) the risks associated with exposure to environments where the entity is unable to enforce its information security policies; and (e) the materiality and frequency of change to information assets.
- What to record
- A note against each of (a) to (e) saying how it shaped the plan for this application, the depth chosen (unauthenticated, authenticated or code-assisted, as the methodology guide uses those terms), and the next test date. CPG 234, as guidance, says controls protecting information assets exposed to untrusted environments would typically be tested throughout the year.
- What a website or web application test can supply
- The written scope of an earlier test shows which depth and which roles were used, which helps decide whether the next test needs to go further.
- Outside what a test shows, and who decides
- Whether the frequency and depth are commensurate with 27(a) to 27(e). That is the entity's judgement, and C11 reviews it.
- Limits of this row
- Read-only row: it records planning decisions and sends no requests.
C3. Applications a related party or third party manages
- When it falls
- When C1 shows an application another party runs, at each contract signing or renewal, and before the entity relies on that party's testing.
- CPS 234 paragraph, in its words
- Paragraph 28: where information assets are managed by a related party or a third party, and the entity is reliant on that party's information security control testing, it must assess whether the nature and frequency of testing of controls in respect of those information assets is commensurate with paragraphs 27(a) to 27(e). Paragraph 16: assess that party's information security capability, commensurate with the potential consequences of an information security incident affecting those assets. Paragraph 22: evaluate the design of that party's information security controls that protects the entity's information assets.
- What to record
- The party's name; whether the entity relies on its testing; what it has supplied (report date, scope as tested, who tested, retest status); the date the entity assessed that testing against 27(a) to 27(e) and the outcome; and what the agreement says about testing and reporting.
- What a website or web application test can supply
- From the supplier: its own test report and retest results, shared on the terms the agreement allows. From the entity: a test of its own test accounts and settings inside the supplier's system, only as far as the supplier's terms permit.
- Outside what a test shows, and who decides
- How the party's platform behaves for its other customers, or whether its testing is commensurate. The entity makes that assessment; CPG 234, as guidance, says it could also consider the scope, depth and independence of certifications, attestations and assurance provided and take steps to address any limitations identified.
- Limits of this row
- Read-only row: no requests go out from it; it works from agreements, reports and assessments. A test of the party's own system is a separate piece of work, agreed with that party first after reading its terms and asking it about anything they leave open, and run under the limits set out in rows C6 and C9.
C4. Tester skill and functional independence
- When it falls
- Before each test is booked, and again if the tester, or the tester's relationship to the system, changes.
- CPS 234 paragraph, in its words
- Paragraph 30: the entity must ensure that testing is conducted by appropriately skilled and functionally independent specialists.
- What to record
- The tester's name and organisation; the evidence of skill the entity has decided to rely on; whether the tester built, hosts or runs the system, or has operational responsibility for any control in scope; any accreditation an agreement, policy or tender requires, in its exact wording; and who at the entity approved the choice, and when.
- What a website or web application test can supply
- The tester's written statement of its relationship to the system. Where the system is one Clever Ops built or hosts, its report says so, and the work is a security review, not an independent test.
- Outside what a test shows, and who decides
- Whether the tester is appropriately skilled and functionally independent for this test. CPG 234, as guidance, says the level of functional independence required would typically be determined by the nature and importance of the testing. The entity decides.
- Limits of this row
- Read-only row: it records a selection decision and sends no requests.
C5. Scope, authorisation and test window
- When it falls
- Before testing starts on each application.
- CPS 234 paragraph, in its words
- Paragraph 27: the nature of the systematic testing must be commensurate with 27(a) to 27(e). CPG 234, as guidance, says it is important that success criteria for tests are clearly defined, including the circumstances under which re-testing would be required.
- What to record
- The written scope (targets, roles and test accounts, environment, depth, exclusions and testing window), the signed authorisation from the owner of each target, the hosting provider's testing policy as checked, the terms read for any vendor-run system, and the success criteria agreed for the test.
- What a website or web application test can supply
- The report's scope as tested, and in a Clever Ops report the test cases that could not run with the reason, let anyone compare what was planned with what ran.
- Outside what a test shows, and who decides
- Anything the scope left out. An exclusion is untested, and the C11 review should treat it as a gap or a recorded decision.
- Limits of this row
- Read-only row: it gathers documents before testing and sends no requests.
C6. Check after a material change
- When it falls
- After a material change to an application is released, and before its next scheduled test.
- CPS 234 paragraph, in its words
- Paragraph 27(e): the nature and frequency of testing must be commensurate with the materiality and frequency of change to information assets. CPG 234, as guidance, says additional testing could be triggered by changes to vulnerabilities and threats, information assets or the threat landscape.
- What to record
- The change and its release date, then the response to each of three requests, with the date and time: as test customer B, request one record that test customer A owns, by its id; as test customer A, request one staff-only page or API route; and signed out, request A's record again.
- What a website or web application test can supply
- Nothing from a tester: this row is a narrow check by your own team. A refusal recorded for each request shows that those controls refused those requests on that build.
- Outside what a test shows, and who decides
- Anything beyond the three requests. A material change may need a scoped test, and whether to bring the next test forward is the entity's decision.
- Limits of this row
- This row sends requests. Send them only to an application your business runs or holds written authorisation to test, on a staging copy if there is one, from test accounts that carry invented records and never a real customer's. Send nothing beyond the requests named at the end of this cell, one after another, and put no load on the application. If a request sets off an email or a text, it goes to an address or number your business controls. Record the status and what came back, and keep any password, key, token or link that works for whoever holds it (a reset, payment or shared-file link) out of the record; open such a link only for the invented record. For an application a vendor runs, check the vendor's terms before you start, take anything they leave open to the vendor, and keep within what the terms or the vendor's reply permit. Should a response show a real person's data, stop at once: note the page address and the clock time, open no other record, and tell whoever handles privacy and incidents in your business. Requests in this row: a sign-in for test customer A and one for test customer B, then the three listed, one of each kind, with the signed-out request sent from a private browser window that holds no session.
C7. Test report received
- When it falls
- On the day the report arrives.
- CPS 234 paragraph, in its words
- Paragraph 27: the entity must test the effectiveness of its information security controls through a systematic testing program. Paragraph 31: it must review the sufficiency of the testing program at least annually or when there is a material change to information assets or the business environment.
- What to record
- Report date and version, the build and dates tested, the scope as tested, the roles and accounts used, each finding with its ratings, the negative results, test cases that could not run, and where the report is kept and who may read it.
- What a website or web application test can supply
- Dated evidence about one application's controls on the build tested, with its findings and the limits of the test. A Clever Ops report also lists the checks that found nothing, for the build and accounts tested.
- Outside what a test shows, and who decides
- That a program exists or is sufficient, or anything about controls outside the scope, such as networks, staff devices, backups and response plans.
- Limits of this row
- Read-only row: it files a report and sends no requests. The full report holds reproduction steps for open findings, so share it only with the people your process names.
C8. Remediation owner, target date and escalation
- When it falls
- When the report arrives, then at each target date.
- CPS 234 paragraph, in its words
- Paragraph 29: the entity must escalate and report to the Board or senior management any testing results that identify information security control deficiencies that cannot be remediated in a timely manner. Paragraph 36 may also bear on a finding: notify APRA as soon as possible and, in any case, no later than 10 business days, after the entity becomes aware of a material information security control weakness which it expects it will not be able to remediate in a timely manner.
- What to record
- For each finding: its owner, its target fix date, the entity's decision on whether it can be remediated in a timely manner, and, where it cannot, the date and forum it was escalated to and any decision taken under paragraph 36.
- What a website or web application test can supply
- In a Clever Ops report: each finding's description, redacted evidence, fix and retest criteria, and for each rated finding a CVSS v3.1 score and a business-risk rating.
- Outside what a test shows, and who decides
- Whether a delay is timely, whether a weakness is material, or whether paragraph 36 is engaged. Those are the entity's decisions.
- Limits of this row
- Read-only row: it records owners, dates and decisions and sends no requests.
C9. Developer check before the retest
- When it falls
- Once fixes reach an identified build, before you ask for the retest.
- CPS 234 paragraph, in its words
- Paragraph 29, as in C8. CPG 234, as guidance, says test results would be reported to the appropriate governing body or individual, with associated follow-up actions formally tracked and reported.
- What to record
- The build identifier, and for each finding the result of running its retest criteria once on that build, with the date and time.
- What a website or web application test can supply
- In a Clever Ops report, the retest criteria written into each finding, which say what the retest will check.
- Outside what a test shows, and who decides
- An independent result. A developer's check of their own fix is a readiness step; the tester's retest is the record that C10 keeps.
- Limits of this row
- This row sends requests. Send them only to an application your business runs or holds written authorisation to test, on a staging copy if there is one, from test accounts that carry invented records and never a real customer's. Send nothing beyond the requests named at the end of this cell, one after another, and put no load on the application. If a request sets off an email or a text, it goes to an address or number your business controls. Record the status and what came back, and keep any password, key, token or link that works for whoever holds it (a reset, payment or shared-file link) out of the record; open such a link only for the invented record. For an application a vendor runs, check the vendor's terms before you start, take anything they leave open to the vendor, and keep within what the terms or the vendor's reply permit. Should a response show a real person's data, stop at once: note the page address and the clock time, open no other record, and tell whoever handles privacy and incidents in your business. Requests in this row: a sign-in for each test account the original test used, then only the requests each finding's retest criteria list, once each.
C10. Retest date and status for each finding
- When it falls
- On the retest date, within any window the tester's agreement sets.
- CPS 234 paragraph, in its words
- Paragraph 29, as in C8: testing results that identify deficiencies that cannot be remediated in a timely manner go to the Board or senior management.
- What to record
- The retest date, the build retested, and each finding's status as the retest report gives it. In a Clever Ops retest, every finding ends as fixed, partially fixed, still reproducible or not retested. Carry every finding that is not fixed back to C8.
- What a website or web application test can supply
- From a Clever Ops retest: a status for each finding on the retested build, including findings left out of the retest, which are marked not retested rather than passed.
- Outside what a test shows, and who decides
- Anything outside the reported findings, and any change released after the retest.
- Limits of this row
- Read-only row: it records the retest result and sends no requests.
C11. Sufficiency review
- When it falls
- At least annually, and when there is a material change to information assets or the business environment.
- CPS 234 paragraph, in its words
- Paragraph 31: the entity must review the sufficiency of the testing program at least annually or when there is a material change to information assets or the business environment.
- What to record
- Who reviewed and when; applications in C1 with no test in the period; exclusions from C5; assessments still outstanding in C3; changes checked in C6; findings escalated in C8 and their status in C10; and the decisions taken.
- What a website or web application test can supply
- The scope, dates, exclusions and retest statuses of each test in the period, which show what was tested and what was not.
- Outside what a test shows, and who decides
- Whether the program is sufficient. That review is the entity's, and the internal audit and assurance work in paragraphs 32 to 34 is separate from it.
- Limits of this row
- Read-only row: it compares the register with itself and sends no requests.
C12. Supplier: answering a regulated customer
- When it falls
- When a regulated customer sends a questionnaire, a due diligence request or contract terms about testing.
- CPS 234 paragraph, in its words
- Paragraphs 16, 22 and 28, set out in C3, are addressed to the APRA-regulated entity, not to the supplier. Paragraph 34: the entity's internal audit function must assess the information security control assurance a related party or third party provides where an information security incident affecting the information assets has the potential to materially affect, financially or non-financially, the entity or the interests of depositors, policyholders, beneficiaries or other customers, and internal audit intends to rely on that assurance.
- What to record
- The customer's exact wording; the evidence you sent for each question (report date, scope as tested, retest status and the tester's statement from C4); what the agreement lets you share; and the date sent.
- What a website or web application test can supply
- Dated, scoped evidence about the systems you run for that customer, with a retest status for each finding.
- Outside what a test shows, and who decides
- Whether your evidence is enough for the customer, or what your contract requires of you. The customer judges the first, and your own adviser is the person to ask about the second.
- Limits of this row
- Read-only row: it pairs your documents with the customer's questions and sends nothing to any system.
CPS 234 at a glance: the instrument, its date and its aim
CPS 234 is Prudential Standard CPS 234 Information Security.
It is set out in a legislative instrument called Banking, Insurance, Life Insurance, Health Insurance and Superannuation (prudential standard) determination No. 1 of 2018, in which a delegate of the Australian Prudential Regulation Authority (APRA) determines the standard under subsection 11AF(1) of the Banking Act 1959, subsection 32(1) of the Insurance Act 1973, subsection 230A(1) of the Life Insurance Act 1995, subsection 92(1) of the Private Health Insurance (Prudential Supervision) Act 2015 and subsection 34C(1) of the Superannuation Industry (Supervision) Act 1993. The determination is dated 30 November 2018 and says it commences on 1 July 2019.
The Federal Register of Legislation lists the determination under title ID F2018L01745 as an in-force legislative instrument of type Principal, As Made, registered on 12 December 2018. On APRA's own page for the standard, CPS 234 carries the status In force beside the date 1 July 2019. This guide quotes the text as made, by paragraph number. Before you rely on a paragraph, check the register for a later version.
The standard opens with its aim: to ensure that an APRA-regulated entity takes measures to be resilient against information security incidents (including cyber-attacks) by maintaining an information security capability commensurate with information security vulnerabilities and threats. Among the key requirements the opening lists, the entity must implement controls to protect its information assets commensurate with the criticality and sensitivity of those information assets, and undertake systematic testing and assurance regarding the effectiveness of those controls.
The opening also places ultimate responsibility on the Board of an APRA-regulated entity for ensuring that the entity maintains its information security.
Definitions (d), (g) and (k) in paragraph 12 bear on how far that reaches. An information asset is information and information technology, including software, hardware and data (both soft and hard copy). An information security control is a prevention, detection or response measure to reduce the likelihood or impact of an information security incident.
An information security vulnerability is a weakness in an information asset or information security control that could be exploited to compromise information security. This guide reads those definitions as taking in a customer portal, the API behind it and the records it holds, with its sign-in, access checks and logging among its controls.
Which systems an entity treats as information assets, and how it classifies them, is the entity's own work.
CPS 234 also has a neighbour. In the text of CPS 230 Operational Risk Management on APRA's page, paragraph 24 says an APRA-regulated entity must maintain appropriate and sound information and information technology (IT) capability to meet its current and projected business requirements and to support its critical operations and risk management, and that in managing technology risks it must monitor the age and health of its information assets and meet the requirements for information security in CPS 234.
This page is written for the technology or risk lead at an APRA-regulated entity who has to show what was tested, and for the owner or technical manager of a supplier that has been asked about CPS 234 in a questionnaire, a due diligence request or a contract.
Nothing here is legal advice or an audit. It states what the text says and leaves every decision about meeting it to the people the standard names.
Who CPS 234 applies to, and why its suppliers hear about it
Paragraph 2 sets the reach of APRA CPS 234.
It applies to all APRA-regulated entities, a term the paragraph defines through the classes in 2(a) to 2(e): authorised deposit-taking institutions (ADIs), including foreign ADIs, and authorised banking NOHCs; general insurers, including Category C insurers, authorised insurance NOHCs and parent entities of Level 2 insurance groups; life companies, including friendly societies, eligible foreign life insurance companies (EFLICs) and registered life NOHCs; private health insurers registered under the PHIPS Act; and RSE licensees under the SIS Act in respect of their business operations.
Paragraphs 3, 4 and 11 adjust that reach. Paragraph 3 confines the obligations on a foreign ADI, a Category C insurer or an EFLIC to the Australian branch operations of that entity. Paragraph 4 has an APRA-regulated entity that is the Head of a group comply in its capacity as an APRA-regulated entity, by ensuring that each requirement is applied appropriately throughout the group, including in relation to entities that are not APRA-regulated, and on a group basis.
Paragraph 11 says APRA may adjust or exclude a specific prudential requirement in the standard in relation to an APRA-regulated entity.
Whether a business is in one of those classes, and whether APRA has adjusted or excluded a requirement for it under paragraph 11, is for that business to settle with its own adviser or with APRA. A business outside the classes can still be asked about CPS 234, because several paragraphs deal with information assets that a related party or third party manages for the entity, and the next section sets them out.
Every duty this page quotes from the standard falls on the APRA-regulated entity, its Board or its internal audit function.
For a supplier, the place to look is its agreement with that customer: read what it says about testing and reporting with the customer, and put any question about what it requires of you to your own adviser.
Information assets that a supplier manages
CPS 234 reaches information assets that other parties manage for the entity.
Paragraph 20 says an APRA-regulated entity must classify its information assets, including those managed by related parties and third parties, by criticality and sensitivity. Paragraph 21 says it must have information security controls to protect its information assets, including those managed by related parties and third parties, that are implemented in a timely manner and that are commensurate with (a) vulnerabilities and threats to the information assets, (b) the criticality and sensitivity of the information assets, (c) the stage at which the information assets are within their life-cycle, and (d) the potential consequences of an information security incident.
Paragraphs 16 and 22 then turn to the party that manages the asset. Under paragraph 16, where information assets are managed by a related party or third party, the entity must assess the information security capability of that party, commensurate with the potential consequences of an information security incident affecting those assets.
Under paragraph 22, it must evaluate the design of that party's information security controls that protects the entity's information assets. Paragraph 28, set out with the testing paragraphs below, turns to that party's control testing. Footnotes to paragraphs 16, 22 and 28 each say, for the avoidance of doubt, that the paragraph applies to all information assets managed by related parties and third parties, not only those captured under agreements with service providers of outsourced material business activities under Prudential Standard CPS 231 Outsourcing or Prudential Standard SPS 231 Outsourcing.
Internal audit has paragraphs of its own. Paragraph 32 says the entity's internal audit activities must include a review of the design and operating effectiveness of information security controls, including those maintained by related parties and third parties, which the standard calls information security control assurance.
Paragraph 34 says the internal audit function must assess the information security control assurance provided by a related party or third party where (a) an information security incident affecting the information assets has the potential to materially affect, financially or non-financially, the entity or the interests of depositors, policyholders, beneficiaries or other customers; and (b) internal audit intends to rely on the assurance that party provides.
APRA's prudential practice guide CPG 234 describes, as guidance, how an entity might form these views. It says entities would have a view as to the sufficiency of resources, skills and controls of third parties and related parties, and that this could be achieved through a combination of interviews, service reporting, control testing, certifications, attestations, referrals and independent assurance assessments.
It adds that an entity could also consider the scope, depth and independence of certifications, attestations and assurance provided and take steps to address any limitations identified.
For vendor-provided software, including software as a service, its Attachment D lists among the considerations when selecting and configuring vendor supplied software due diligence as to the security testing conducted to identify vulnerabilities (either intended or deliberate).
This guide's reading for a supplier follows from that. Your test reports, your answers and your contract terms are material the entity may weigh when it makes the assessments paragraphs 16, 22 and 28 give it, and, where the conditions in 34(a) and 34(b) are met, the assessment its internal audit function makes under paragraph 34.
Whether that material is enough is the entity's judgement. The security questionnaires guide covers how to answer a customer's questions without saying more than your evidence shows.
Paragraphs 27 to 31: CPS 234 information security testing in the standard's words
The standard groups paragraphs 27 to 31 under the heading Testing control effectiveness, and each one is addressed to the APRA-regulated entity.
The text of CPS 234 as made does not use the words penetration test. Paragraph 27 asks for a systematic testing program and requires its nature and frequency to be commensurate with the factors it lists. Here they are as the instrument states them.
- Paragraph 27:an APRA-regulated entity must test the effectiveness of its information security controls through a systematic testing program. The nature and frequency of the systematic testing must be commensurate with (a) the rate at which the vulnerabilities and threats change; (b) the criticality and sensitivity of the information asset; (c) the consequences of an information security incident; (d) the risks associated with exposure to environments where the APRA-regulated entity is unable to enforce its information security policies; and (e) the materiality and frequency of change to information assets. A footnote to (d) says such an environment is also referred to as an untrusted environment.
- Paragraph 28:where an APRA-regulated entity's information assets are managed by a related party or a third party, and the entity is reliant on that party's information security control testing, the entity must assess whether the nature and frequency of testing of controls in respect of those information assets is commensurate with paragraphs 27(a) to 27(e).
- Paragraph 29:an APRA-regulated entity must escalate and report to the Board or senior management any testing results that identify information security control deficiencies that cannot be remediated in a timely manner.
- Paragraph 30:an APRA-regulated entity must ensure that testing is conducted by appropriately skilled and functionally independent specialists.
- Paragraph 31:an APRA-regulated entity must review the sufficiency of the testing program at least annually or when there is a material change to information assets or the business environment.
Where a website meets paragraph 27(d)
Factor 27(d) is written about exposure. CPS 234 gives the environments it describes a second name in its footnote, untrusted, and APRA's guidance explains that word. Footnote 7 of CPG 234 says untrusted environments refers to environments where an APRA-regulated entity is unable to enforce its information security policies, including exposures to the internet and connections to service providers and customers.
On that reading, a website, portal or API that customers reach over the internet sits in an untrusted environment, and that exposure is one of the factors the entity weighs when it sets the nature and frequency of testing for the asset.
Factors 27(b) and 27(e) bear on a web application as well: how critical and sensitive it is, and how materially and how often it changes. The weighing itself is the entity's.
When a finding cannot be fixed in time
Paragraph 29 ties escalation to testing results. A separate paragraph deals with notice to APRA: paragraph 36 says an APRA-regulated entity must notify APRA as soon as possible and, in any case, no later than 10 business days, after it becomes aware of a material information security control weakness which the entity expects it will not be able to remediate in a timely manner. CPG 234 lists control testing among the mechanisms through which a material control weakness could be identified.
Paragraph 12, the definitions paragraph, does not define timely or material. This page offers no view on either for any finding; the entity makes those calls, with its own advisers where it needs them. Row C8 of the calendar records each of those calls with its owner and date, and row C10 sends every finding that is not fixed back to it.
What CPG 234 adds, and why it is guidance rather than a requirement
APRA publishes a prudential practice guide beside the standard, CPG 234 Information Security.
APRA's page marks it as current, beside the date 1 June 2019, and says it provides guidance to all entities on CPS 234. APRA says prudential practice guides provide guidance on APRA's view of sound practice in particular areas, and that they frequently discuss statutory requirements from legislation, regulations or APRA's prudential standards, but do not themselves create enforceable requirements.
CPG 234 adds that not all of the practices it outlines will be relevant for every regulated entity, and that some aspects may vary depending upon the size and nature of the entity. Where this page draws on CPG 234, its "would" and "could" stay as the guide wrote them.
On testing, the guide describes a program rather than a single test:
- The program: an APRA-regulated entity would normally outline the population of information security controls across the regulated entity, including any group of which it is a part, and maintain a program of testing which validates the design and operating effectiveness of controls over time. Additional testing could be triggered by changes to vulnerabilities and threats, information assets or the threat landscape.
- How often: in APRA's view, the frequency and scope of testing would ensure that a sufficient set of information security controls are tested, at least annually, in order to validate that information security controls remain effective, and controls protecting information assets exposed to untrusted environments would typically be tested throughout the year.
- What kind: the nature of testing would be a function of the type of control, and would typically consider a variety of testing approaches informed by contemporary industry practices.
- Success criteria: the guide says it is important that success criteria for tests are clearly defined, including the circumstances under which re-testing would be required, and that test results would be reported to the appropriate governing body or individual, with associated follow-up actions formally tracked and reported.
- Independence: for an entity to have confidence in the quality of testing, the guide says it is important that testers are sufficiently independent in order to provide a bias-free assessment of controls, unimpeded by a conflict of interest. That includes the use of testers who do not have operational responsibility for the controls being validated, and the level of functional independence required would typically be determined by the nature and importance of the testing.
- Internal audit: where internal audit relies on control testing performed by other areas, APRA would expect the internal audit function to assess the scope and quality of the testing conducted in order to determine how much reliance can be placed upon it.
Where penetration tests appear in the guide
Attachment G of CPG 234, Testing techniques, is a table of control objectives, example controls and practices, and example testing approaches. Penetration tests appear among the example testing approaches, including in these rows. For Implement secure software, the examples are design reviews, penetration tests, code review and scanning, network traffic analysis, fault testing and fuzzing.
For Timely identification and remediation of new vulnerabilities, they are vulnerability scans and penetration testing. For Protect networks from unauthorised network traffic, the example is penetration tests, and for Timely detection of unauthorised access and use, it is penetration tests including more advanced techniques commonly referred to as "red team" tests.
The same table gives a social engineering test as the example for limiting access to what has been authorised based on job role and the principle of least privilege, and audits of user access for authenticating users with strength of authentication commensurate with sensitivity of the information asset being accessed.
A web application test, as this library describes it, sits closest to the secure software and new vulnerability rows. It does not stand in for the social engineering tests or user access audits the table names for those access objectives.
What a web application test can add to an entity's testing record
A test of a website or web application is evidence about one information asset: the build that was tested, in the window it ran, using the accounts and roles supplied for it, against a written scope.
Inside those limits it can show how particular controls behaved: whether sign-in and sessions ended access when they should, whether one customer's account could reach another customer's records, whether a lower role could reach a staff function, and whether the API kept the same rules when it was called directly. The web application penetration testing guide sets out those areas one by one.
Matched against the testing paragraphs, a report can supply the following, and no more:
- Towards paragraph 27: a dated record that one asset's controls were tested, with the scope and depth used. It does not show that a program exists across the entity, or that the nature and frequency of testing for that asset are commensurate with 27(a) to 27(e).
- Towards paragraph 28: where a supplier manages the asset, has it tested, and the entity is reliant on that testing, the report is part of the testing the entity assesses. The report states what was tested and when; whether the nature and frequency of that testing are commensurate with 27(a) to 27(e) is the entity's assessment.
- Towards paragraph 29: each finding's ratings, the remediation plan and the retest status show which deficiencies remain open on the tested build. Whether a fix was timely, and whether to escalate, is decided inside the entity.
- Towards paragraph 30: the tester's own statement of who did the work and whether it built, hosts or runs the system. Whether the testers were appropriately skilled and functionally independent is the entity's judgement.
- Towards paragraph 31: the scope, dates and exclusions of each test, which show a sufficiency review which assets were tested in the period and which were not.
What it cannot speak for
A web application test says nothing about how the entity classifies its assets under paragraph 20; about its information security response plans, which paragraph 26 says an APRA-regulated entity must annually review and test to ensure they remain effective and fit-for-purpose; about the internal audit and assurance work in paragraphs 32 to 34; or about controls outside its scope, such as office networks, staff devices, backups and the vendor platforms the application depends on.
It does not decide whether anything is material, and it is not a notification to APRA.
It is also not a finding that an entity or a supplier meets CPS 234. The methodology guide explains why a report states what was tested, rather than issuing a certificate.
How to use the control-testing calendar
The calendar on this page turns paragraphs 27 to 31, with the paragraphs on assets other parties manage, into dated records for each web-facing application.
An APRA-regulated entity can keep it as a working register for its websites, portals and APIs. A supplier can use rows C3, C4, C7 to C10 and C12 to get ready for a regulated customer's questions. It does not replace an entity's own testing program.
Paragraph 27 ties the nature and frequency of the systematic testing to factors 27(a) to 27(e), and paragraph 31 sets the review in row C11 at least annually or when there is a material change to information assets or the business environment.
- Start with row C1 and list every website, portal and API before you set a single date. An application left off the inventory has no row to schedule it.
- Copy the table into a spreadsheet, keep C1, C11 and C12 once for the whole register, and repeat rows C2 to C10 for each application.
- Put real dates in the "When it falls" column. Where a row says a date or a judgement is the entity's, write down who made it and when.
- Only rows C6 and C9 send requests to a running application, and each states its own limits in its last column. The rest read or write records.
- Before C6 or C9 touches an application a vendor runs, check the vendor's terms and take anything they leave open to the vendor. What a vendor permits is for its own terms to say, and this page makes no claim about it.
- Keep the evidence for checks that pass as well as those that fail. A dated pass is what lets the review in C11 say that an asset was tested.
- Should any row turn up a real person's data, go no further: write down the address and the time, leave everything else unopened, and tell whoever handles privacy and incidents in your business.
Who judges the testing: the Board, internal audit, APRA and the customer
The standard names the deciders.
Paragraph 13 says the Board of an APRA-regulated entity is ultimately responsible for the information security of the entity. Paragraphs 29 to 31 give the entity the escalation, the duty to ensure testing is conducted by appropriately skilled and functionally independent specialists, and the sufficiency review.
Paragraph 32 has the entity's internal audit activities include a review of the design and operating effectiveness of information security controls, and paragraph 34 has its internal audit function assess a related party's or third party's assurance where that paragraph's conditions are met.
And paragraph 11 says APRA may adjust or exclude a specific requirement in relation to an entity. None of those decisions belongs to the tester.
For a supplier, the decision sits with the customer. A regulated customer decides what evidence it needs from you, how recent it must be and whether your tester meets its policy. A test report helps you answer accurately. It does not settle the question for the customer, and any question about what your contract requires is for your own adviser.
CPS 234 penetration testing: what a Clever Ops test can add, and what it leaves to others
Each Clever Ops service tests something customers use through a browser or an API: an external website security check, a WordPress security audit, a web application and API penetration test of a custom application that staff or customers sign in to, a vibe-coded app security check, and an AI chatbot and agent security test.
For an entity or a supplier keeping a CPS 234 testing record, one of those tests can supply dated evidence about one web-facing asset for rows C7 to C10 of the calendar. The report records the scope as tested, findings with redacted evidence, a CVSS v3.1 score and a business-risk rating for each rated finding, negative results limited to the build and accounts tested, and a remediation plan.
One consolidated retest comes with every test, and it gives each finding a status of fixed, partially fixed, still reproducible or not retested.
Clever Ops does not hold any security certification or accreditation, and nothing on this page is regulatory assurance. The report feeds a decision that the entity or its customer makes; it certifies nothing and gives no opinion on compliance. Clever Ops is not CREST accredited. If an entity's policy, an agreement or a tender requires a CREST-accredited provider, that work is referred to a provider that holds the accreditation.
Whether a tester is appropriately skilled and functionally independent for a given test is the regulated entity's judgement under paragraph 30. An application that Clever Ops built or hosts gets a security review, not an independent test, and its report names who built the application and who hosts it.
An entity or customer that wants a tester independent of building and running the system should engage a provider that did neither.
Some testing a CPS 234 program may call for sits outside every Clever Ops service. Internal networks, servers, Active Directory, staff devices, red teaming, phishing and physical testing go to a network or red team specialist, and Clever Ops does not offer denial-of-service, load or volumetric testing in any service.
A vendor's own product or platform, such as the system behind a portal the vendor runs, is not something Clever Ops tests.
Frequently asked questions
The text of CPS 234 as made does not use the words penetration test. Paragraph 27 says an APRA-regulated entity must test the effectiveness of its information security controls through a systematic testing program, with the nature and frequency of that testing commensurate with the factors in paragraphs 27(a) to 27(e). APRA's guide CPG 234 lists penetration tests among the example testing approaches in its Attachment G, including for implementing secure software and for the timely identification and remediation of new vulnerabilities, and APRA says its practice guides do not themselves create enforceable requirements. Which tests make up a program is the entity's decision.
Paragraph 2 lists the classes of APRA-regulated entity the standard applies to, and a software supplier outside those classes is not on the list. You can still be asked about it. Paragraphs 16, 22 and 28 are about a related party or third party that manages the entity's information assets: the entity assesses that party's information security capability, commensurate with the potential consequences of an information security incident affecting those assets; evaluates the design of that party's information security controls that protect the entity's information assets; and, where it is reliant on that party's information security control testing, assesses whether the nature and frequency of testing of controls in respect of those information assets is commensurate with paragraphs 27(a) to 27(e). Footnotes to each say the paragraph applies to all information assets managed by related parties and third parties, not only those captured under agreements with service providers of outsourced material business activities under CPS 231 or SPS 231. Whether your business sits in any of those classes is for you to confirm with your own adviser. For what the bank expects of you, look to your agreement with it: check it with the bank, and ask your own adviser what it requires of you.
CPS 234 does not define the phrase. Paragraph 30 says an APRA-regulated entity must ensure that testing is conducted by appropriately skilled and functionally independent specialists. CPG 234, which is guidance, says it is important that testers are sufficiently independent to provide a bias-free assessment of controls, unimpeded by a conflict of interest, that this includes the use of testers who do not have operational responsibility for the controls being validated, and that the level of functional independence required would typically be determined by the nature and importance of the testing. The entity decides whether a given tester meets paragraph 30. If Clever Ops built or hosts a system, its work on that system is a security review, not an independent test, and its builder and host are named in the report.
Paragraph 27 sets no fixed interval. It ties the nature and frequency of the systematic testing to the factors listed in paragraphs 27(a) to 27(e), quoted above. Paragraph 31 does give an interval, for reviewing the program rather than for testing: it says an APRA-regulated entity must review the sufficiency of the testing program at least annually or when there is a material change to information assets or the business environment. Paragraph 26 sets a separate interval for one kind of testing: an APRA-regulated entity must annually review and test its information security response plans to ensure they remain effective and fit-for-purpose. CPG 234, as guidance, gives APRA's view that a sufficient set of controls would be tested at least annually, and that controls protecting information assets exposed to untrusted environments would typically be tested throughout the year.
Paragraphs 29 and 36 deal with this, and both are addressed to the entity. Paragraph 29 says it must escalate and report to the Board or senior management any testing results that identify information security control deficiencies that cannot be remediated in a timely manner. Paragraph 36 says it must notify APRA as soon as possible and, in any case, no later than 10 business days, after it becomes aware of a material information security control weakness which it expects it will not be able to remediate in a timely manner. Whether a finding is material, and what timely means for it, are the entity's judgements. Row C8 of the calendar records those decisions with an owner and a date, and row C10 returns any finding that is not fixed to C8.
No test does that. A report is dated evidence about the asset, build and scope that were tested, and it is one input to the systematic testing program paragraph 27 describes. Whether a program meets the standard is for the entity, its Board, its internal audit function and APRA to consider; for a supplier, whether your evidence is enough is for your regulated customer. A Clever Ops report sets out the tested scope, the findings and the retest result. It certifies nothing and gives no opinion on compliance.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.