AST-02.4: Approved Baseline Deviations

There is no evidence of a capability to document and govern instances of approved deviations from established baseline configurations.

Asset Management (AST) efforts are ad hoc and inconsistent. CMM Level 1 control maturity would reasonably expect all, or at least most, the following criteria to exist:

• Asset management is informally assigned as an additional duty to existing IT/cybersecurity personnel.
• Asset inventories are performed in an ad hoc manner.
• Software licensing is tracked as part of IT asset inventories.
• Data process owners maintain limited network diagrams to document the flow of sensitive/regulated data that is specific to their initiative.
• IT personnel work with data/process owners to help ensure secure practices are implemented throughout the System Development Lifecycle (SDLC) for all high-value projects.
• System configurations loosely conform to industry-recognized standards for hardening (e.g., DISA STIGs, CIS Benchmarks or OEM security guides)
• Deviations from approved baseline configurations are handled on a case-by-case basis by IT/cybersecurity personnel. Acceptance of any deviations from baselines must be informed by performance of a risk assessment.

Asset Management (AST) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist:

• Asset management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
• IT/cybersecurity personnel identify cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements for asset management.
• Administrative processes and technologies focus on protecting High Value Assets (HVAs), including environments where sensitive/regulated data is stored, transmitted and processed.
• Asset management is formally assigned as an additional duty to existing IT/cybersecurity personnel.
• Technology assets are categorized according to data classification and business criticality.
• Inventories cover technology assets in scope for statutory, regulatory and/ or contractual compliance, which includes both physical and virtual assets.
• Software licensing is tracked as part of IT asset inventories.
• Users are educated on their responsibilities to protect technology assets assigned to them or under their supervision.
• IT/cybersecurity personnel maintain network diagrams to document the flow of sensitive/regulated data across the network.
• Documented procedures exist for requesting a deviation from approved deviations.
• Any deviations from approved baseline configurations must be formally reviewed, approved and documented (both approved and unapproved) in a repository by cybersecurity personnel.
• Deviations from approved software deployments are reviewed, approved and documented on a case-by-case basis by IT/cybersecurity personnel.

Asset Management (AST) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist:

• An IT Asset Management (ITAM) function, or similar function, governs asset management to help ensure compliance with requirements for asset management.
• An ITAM function, or similar function, maintains an inventory of IT assets, covering both physical and virtual assets, as well as centrally managed asset ownership assignments.
• Technology assets and data are categorized according to data classification and business criticality criteria.
• A Cybersecurity Supply Chain Risk Management (C-SCRM) function oversees supply chain risks including the removal and prevention of certain technology services and/ or equipment designated as supply chain threats by a statutory or regulatory body.
• Data/process owners document where sensitive/regulated data is stored, transmitted and processed, generating Data Flow Diagrams (DFDs) and network diagrams to document the flow of data.
• Formalized steps and requirements for requesting a deviation to a standard are published.
• The request for a deviation from approved baseline configurations is centrally managed and tracked by ITAM who routes the request to cybersecurity personnel for assessment.
• Deviations to baseline configurations are required to have a risk assessment performed and the appropriate business stakeholder accept any risk(s) associated with the deviation.

Asset Management (AST) efforts are metrics driven and provide sufficient management insight (based on a quantitative understanding of process capabilities) to predict optimal performance, ensure continued operations and identify areas for improvement.

• Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs).
• Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs).
• Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties.
• Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review).
• Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes.
• Both business and technical stakeholders are involved in reviewing and approving proposed changes.

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to document and govern instances of approved deviations from established baseline configurations.