APRA CPS 230 Operational Risk Management
Management of service provider arrangements (paras 46 to 61) – APRA CPS 230 Operational Risk Management

APRA CPS 230 Operational Risk Management 48: Para 48 Register of material service providers and management of their risks

The entity must identify its material service providers, keep a register of them and manage the material risks of using them. A material service provider (or material arrangement) is one the entity relies on to carry out a critical operation or one that exposes it to material operational risk; it may be an unrelated third party, a related party or a connected entity, and materiality may come from one arrangement or several taken together.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • F-16.33 Maintain a register of material third party arrangements and submit it annually

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Management of service provider arrangements (paras 46 to 61) – APRA CPS 230 Operational Risk Management

You are reading one control. How much of APRA CPS 230 Operational Risk Management have you already done?

APRA CPS 230 Operational Risk Management 48 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of APRA CPS 230 Operational Risk Management your existing evidence covers. Hold NIST Cybersecurity Framework 2.0 and 30 of 87 APRA CPS 230 Operational Risk Management controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 4 were rejected on the NIST Cybersecurity Framework 2.0 pair alone.

Query this from an agent

The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.