Skip to main content

πŸ’Ό 15 Implementation of controls - End-of-life and out-of-support issues

  • Contextual name: πŸ’Ό 15 Implementation of controls - End-of-life and out-of-support issues
  • ID: /frameworks/apra-cpg-234/15
  • Located in: πŸ’Ό APRA CPG 234

Description​

Empty...

Similar​

  • Internal
    • ID: dec-b-fa669c1b

Sub Sections​

SectionSub SectionsInternal RulesPoliciesFlags
πŸ’Ό 40 An important aspect of information asset life-cycle management involves minimising vulnerabilities and maintaining support. Information security exposures could arise from hardware and software which is outdated or has limited or no support (whether through a third party, a related party or in-house). Technology that is end-of-life5 , out-of-support or in extended support is typically less secure by design, has a dated security model and can take longer, or is unable, to be updated to address new threats.55
πŸ’Ό 41 Maintaining information assets therefore necessitates a disciplined approach to information asset life-cycle management, including a comprehensive understanding of assets that support the business, as well as the potential impacts of an information security compromise of these assets. Maintenance of information assets can be facilitated through the monitoring of end-of-support dates, where available, and the active identification of systems, including those that are internally-developed and which are no longer invested in or are not secure by design. A technology refresh plan with committed resourcing can also facilitate the timely replacement of hardware and software.
πŸ’Ό 42 Where extended support arrangements are in place, it is important that there is a clear understanding of the nature and effectiveness of these arrangements. Additionally, while extended or custom support arrangements may partially mitigate risk, they are often costly, could provide a false sense of security and can further delay remediation of ageing technology. Furthermore, support agreements of this nature typically provide hot-fixes or patches for critical vulnerabilities only, and remain constrained by the dated security model and design limitations of the technology.
πŸ’Ό 43 To minimise information security vulnerabilities, an APRA-regulated entity would typically decommission systems: a. that cannot be adequately updated as new security vulnerabilities or threats are identified; b. where the use of mitigating controls β€” such as segregation from other information assets β€” is not an option.