Skip to main content

๐Ÿ’ผ 16 Implementation of controls - Minimise exposure to plausible worst case scenarios

  • Contextual name: ๐Ÿ’ผ 16 Implementation of controls - Minimise exposure to plausible worst case scenarios
  • ID: /frameworks/apra-cpg-234/16
  • Located in: ๐Ÿ’ผ APRA CPG 234

Descriptionโ€‹

Empty...

Similarโ€‹

  • Internal
    • ID: dec-b-ee2c41da

Sub Sectionsโ€‹

SectionSub SectionsInternal RulesPoliciesFlags
๐Ÿ’ผ 44 APRA-regulated entities could consider low likelihood scenarios, which could result in an extreme impact to the regulated entity (i.e. plausible worst case). Extreme impacts can be financial or non-financial (e.g. reputational or regulatory), potentially threatening the ongoing ability of the APRA-regulated entity to meet its obligations.3
ย ย ย ย ๐Ÿ’ผ 44a malicious acts by an insider with highly-privileged access, potentially involving collusion with internal or external parties;11
ย ย ย ย ๐Ÿ’ผ 44b deletion or corruption of both production and backup data, either through malicious intent, user error or system malfunction;67
ย ย ย ย ๐Ÿ’ผ 44c loss of, or unauthorised access to, encryption keys safeguarding extremely critical or sensitive information assets.810
๐Ÿ’ผ 45 An understanding of plausible worst case scenarios can help regulated entities identify and implement additional controls to prevent or reduce the impact of such scenarios. One example is malware that infects computers and encrypts data, both on the infected computer and any connected storage, including (corporate) networks and cloud storage. Such attacks reinforce the importance of protecting the backup environment in the event that the production environment is compromised. Common techniques to achieve this include network segmentation, highly restricted and segregated access controls and network traffic flow restrictions.3436