Skip to content

Security Content Pack

The SecurityContentPack contains two standard security control catalogs: the NIST Cybersecurity Framework (CSF) 2.0 and NIST SP 800-53 Revision 5. They give a security team a ready-made set of controls to link to a statement of applicability, to use as mitigations in a threat model, or to map the organization's own controls to.

Unlike the Core Content Pack, it is not loaded automatically. Load it into a metadata access store with the Runtime Manager API when it is needed, or add it to the server's start-up archives. It depends on the Core Content Pack.

The content pack is found in the SecurityContentPack.omarchive file in the content-packs directory of the distribution, and is built by the core-content-pack module.

Contents

Each catalog is a RootCollection with a CollectionFolder for each part of the catalog. Each control is a GovernanceControl in the Security governance domain, so it can be linked to a statement of applicability with the ControlApplicability relationship.

Catalog Qualified name of the root Structure Controls
NIST Cybersecurity Framework (CSF) 2.0 NIST CSF 2.0 6 function folders, such as NIST CSF 2.0::GV, each holding a folder for each of its categories, such as NIST CSF 2.0::GV.OC (22 category folders in all) 106 subcategories, such as NIST CSF 2.0::GV.OC-01
NIST SP 800-53 Rev. 5 Security and Privacy Controls (catalog version 5.2.0) NIST SP 800-53 Rev 5 20 control family folders 300 controls, such as NIST SP 800-53 Rev 5::AC-2, and 714 control enhancements, such as NIST SP 800-53 Rev 5::AC-2(1)

In all, the content pack holds 2 RootCollections, 48 CollectionFolders and 1,120 GovernanceControls.

  • CSF subcategories carry their identifier, their outcome statement as the summary and description, and NIST's implementation examples as the usage.
  • SP 800-53 controls and enhancements carry their NIST label as the identifier, the label and title as the display name, the control statement as the description and the discussion as the usage. Parameters that the organization defines are shown as NIST publishes them, for example [Assignment: organization-defined time period]. Each control enhancement is linked to the control it strengthens with the GovernanceControlLink relationship, rather than being a member of the control family folder.
  • Withdrawn controls are left out of both catalogs.

The following diagram illustrates the structure of the catalogs, using a few of their elements as examples. (The Security Content Pack is not loaded in Egeria's quickstart, so this diagram is drawn by hand rather than generated.)

flowchart TD
    CSF(["*Root Collection*<br/>**NIST CSF 2.0**"])
    GV["*Collection Folder*<br/>**NIST CSF 2.0::GV**<br/>Govern function"]
    GVOC["*Collection Folder*<br/>**NIST CSF 2.0::GV.OC**<br/>Organizational Context category"]
    GVOC01["*Governance Control*<br/>**NIST CSF 2.0::GV.OC-01**"]
    GVOC02["*Governance Control*<br/>**NIST CSF 2.0::GV.OC-02**"]
    CSF -->|Collection Membership| GV
    GV -->|Collection Membership| GVOC
    GVOC -->|Collection Membership| GVOC01
    GVOC -->|Collection Membership| GVOC02

    SP(["*Root Collection*<br/>**NIST SP 800-53 Rev 5**"])
    AC["*Collection Folder*<br/>**NIST SP 800-53 Rev 5::AC**<br/>Access Control family"]
    AC2["*Governance Control*<br/>**NIST SP 800-53 Rev 5::AC-2**"]
    AC21["*Governance Control*<br/>**NIST SP 800-53 Rev 5::AC-2(1)**"]
    AC22["*Governance Control*<br/>**NIST SP 800-53 Rev 5::AC-2(2)**"]
    SP -->|Collection Membership| AC
    AC -->|Collection Membership| AC2
    AC2 -->|Governance Control Link| AC21
    AC2 -->|Governance Control Link| AC22

The catalogs are generated from NIST's OSCAL catalogs, which are works of the U.S. Government in the public domain. The source, version and license of each catalog are recorded in the additional properties of its root collection.

Further information

  • The Threat Modelling solution uses these controls as mitigations.
  • The six STRIDE threats and the CertificationType for ISO/IEC 27001:2022 are in the Core Content Pack, since they are small and widely used. The text of ISO/IEC 27001 belongs to ISO, so its Annex A controls are not supplied.

Raise an issue or comment below