Skip to main content
Regulator guide · Australia

APRA CPS 234 reaches the assets your third parties hold

Prudential Standard CPS 234 keeps returning to one phrase: information assets, including those managed by related parties and third parties. This page takes three questions that phrase raises and shows what a dated, outside-in monitoring record supports for each.

Scope of this page

Monitoring evidence beside the standard’s own words

CPS 234 states its aim in its opening lines: 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.

The quotations on this page come from the July 2019 text of CPS 234 published by the Australian Prudential Regulation Authority, read on 18 November 2026. The page does not say which entities the standard applies to or what discharges any paragraph.

Three questions

What the standard asks about assets somebody else manages

01 Paragraph 16

Can you assess a third party’s capability without waiting for its answers?

What the standard says
“Where information assets are managed by a related party or third party, the APRA-regulated entity must assess the information security capability of that party, commensurate with the potential consequences of an information security incident affecting those assets.”
What most files hold
A questionnaire the third party completed and a certificate it supplied. Both describe the party in its own words, as at the date on the document.
What an outside-in record adds
A dated read of the third party’s internet-facing estate, produced without its participation and with the methodology applied to your own estate. It is one input to the assessment the paragraph describes. It is not the assessment.
02 Paragraphs 17 and 27

Do your controls keep pace with how threats and vulnerabilities change?

What the standard says
“An APRA-regulated entity must actively maintain its information security capability with respect to changes in vulnerabilities and threats, including those resulting from changes to information assets or its business environment.”
And on testing
Paragraph 27 says the nature and frequency of systematic testing must be commensurate with, among other things, “the rate at which the vulnerabilities and threats change”.
What an outside-in record adds
The external estate is rebuilt every 24 hours and compared with the previous run, so a new host, a newly opened service or a newly circulating credential is recorded on the day it becomes observable. Where it is safe and authorised, Continuous Automated Red-Teaming tests whether a finding can be used.
03 Paragraphs 22 and 28

When you rely on a third party’s own testing, what else can you look at?

What the standard says
“Where an APRA-regulated entity’s information assets are managed by a related party or third party, the APRA-regulated entity must evaluate the design of that party’s information security controls that protects the information assets of the APRA-regulated entity.”
And on reliance
Paragraph 28 covers the case where the entity is reliant on that party’s information security control testing: the entity must assess whether the nature and frequency of that testing is commensurate with paragraphs 27(a) to 27(e).
What an outside-in record adds
An independent observation to set beside the party’s test reports: what was reachable on its estate between its tests, and when that changed. Nothing on a third party’s systems is probed, so the record shows exposure and does not show how its controls are designed.

The capabilities behind these records are Third-Party Risk Management, Attack Surface Management and Continuous Automated Red-Teaming.

The boundary

What an outside-in record supports, and what it does not

Paragraph 20 has entities classify information assets, including those managed by related parties and third parties, by criticality and sensitivity. That classification is yours. The record below is evidence about exposure.

What an outside-in monitoring record supports under CPS 234
Kind of statementWhat the record holdsWhat you can do with it
Supported directly What was reachable from the public internet on your estate and on the third-party estates you nominate, on stated dates, and what changed between them. Cite it with its date and scope.
Supported as an operating record That monitoring ran, over which estates, what each finding was assigned to and what disposition it reached. Evidence that a control operated over a period.
Observed only Findings on a third party’s estate. They are seen from outside and not tested, because authorisation to test another company’s systems is not yours to give. Route to the third party to confirm and fix.
Not reachable from outside The design of a party’s internal controls, its classification of information assets, its incident response plans, its internal audit. Attestation, audit and contract. This record does not stand in for them.
Key
  • Dated observation
  • The control operating
  • A lead for the third party
  • Outside this record

Questions on CPS 234 and external monitoring

Does ShadowMap make an entity compliant with CPS 234?

No. CPS 234 covers roles and responsibilities, policy, classification, controls, incident management, testing, internal audit and notification to APRA. ShadowMap contributes a dated, outside-in monitoring record to the parts that concern external exposure and third parties. Whether that record is sufficient for any paragraph is a judgement for the entity and its advisers.

Does paragraph 16 only cover outsourced service providers?

The standard’s own footnote to paragraph 16 says it 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. Which of your arrangements that reaches is a question for your compliance function.

Is Continuous Automated Red-Teaming the systematic testing in paragraph 27?

It can be one part of a testing programme for the external estate. Paragraph 27 describes a systematic programme across the entity’s information security controls, and paragraph 30 says testing must be conducted by appropriately skilled and functionally independent specialists. Continuous Automated Red-Teaming is controlled, non-destructive validation of external findings, and the entity decides what place it has.

Which version of CPS 234 does this page quote?

The July 2019 text published by APRA, read on 18 November 2026. Check the current text on APRA’s website before relying on any quotation.

Other regimes: MAS TRM Guidelines, NYDFS 500, NIS2.

Nominate one third party and see what the record shows

A 30-minute demo walks through a third-party record from nomination to finding. Or send one apex domain, yours or a third party’s, and receive a written exposure snapshot in two business days.