For every material arrangement the entity must hold a formal, legally binding agreement that at least: (a) defines the services and their service levels; (b) sets each party's rights, duties and expectations, including asset ownership, data ownership and control, dispute resolution, audit access, indemnity and liability; (c) lets the entity satisfy its legal and compliance obligations; (d) obliges the provider to notify the entity when it materially relies on other material service providers through subcontracting or similar to deliver the service; (e) makes the provider responsible for any subcontractor's failure; (f) contains a force majeure clause stating which parts survive a force majeure event; and (g) gives termination rights over the whole arrangement or parts of it, and for an RSE licensee a right to terminate where continuing would breach the best financial interests duty (SIS Act s 52(2)(c)). Para 57 can exempt the arrangement (Attachment category provider on standardised terms or no formal agreement), and APRA can exempt it in writing under para 58.
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.
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.
APRA CPS 230 Operational Risk Management 53 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.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.