Skip to main content

๐Ÿ’ผ 30 APRA-regulated entities record information assets in various ways, sometimes at a very granular level and sometimes at an aggregated level. For example, a system can be seen as an aggregation of the underlying components (such as applications, databases, operating systems, middleware and data sets) and treated as a single information asset for classification purposes. Alternatively, a regulated entity could choose to treat each ofthe underlying components as individual information assets in their own right. Ultimately, the level of granularity would be sufficient to determine the nature and strength of controls required to protect the information asset.

  • Contextual name: ๐Ÿ’ผ 30 APRA-regulated entities record information assets in various ways, sometimes at a very granular level and sometimes at an aggregated level. For example, a system can be seen as an aggregation of the underlying components (such as applications, databases, operating systems, middleware and data sets) and treated as a single information asset for classification purposes. Alternatively, a regulated entity could choose to treat each ofthe underlying components as individual information assets in their own right. Ultimately, the level of granularity would be sufficient to determine the nature and strength of controls required to protect the information asset.
  • ID: /frameworks/apra-cpg-234/12/30
  • Located in: ๐Ÿ’ผ 12 Information asset identification and classification - Classification methodology

Descriptionโ€‹

Empty...

Similarโ€‹

  • Internal
    • ID: dec-c-313b9454

Sub Sectionsโ€‹

SectionSub SectionsInternal RulesPoliciesFlags