Skip to main content

AST-23: Multi-Function Devices (MFD)

AST 8 — High Protect

Mechanisms exist to securely configure Multi-Function Devices (MFD) according to industry-recognized secure practices for the type of device.

Control Question: Does the organization securely configure Multi-Function Devices (MFD) according to industry-recognized secure practices for the type of device?

US (1)
Framework Mapping Values
US IRS 1075 3.3.5
APAC (3)
Framework Mapping Values
APAC Australia ISM June 2024 ISM-0245 ISM-0589 ISM-0590 ISM-1036
APAC New Zealand NZISM 3.6 11.2.3.C.01 11.2.4.C.01 11.2.4.C.02 11.2.5.C.01 11.2.6.C.01 11.2.7.C.01 11.2.7.C.02 11.2.8.C.01 11.2.9.C.01 11.2.10.C.01 11.2.11.C.01 11.2.11.C.02 11.2.11.C.03 11.2.11.C.04 11.2.11.C.05 11.2.12.C.01 11.2.12.C.02 11.2.13.C.01 11.2.13.C.02
APAC Singapore MAS TRM 2021 11.5.1

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to securely configure Multi-Function Devices (MFD) according to industry-recognized secure practices for the type of device.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to securely configure Multi-Function Devices (MFD) according to industry-recognized secure practices for the type of device.

Level 2 — Planned & Tracked

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.
Level 3 — Well Defined

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.
Level 4 — Quantitatively Controlled

See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to securely configure Multi-Function Devices (MFD) according to industry-recognized secure practices for the type of device.

Level 5 — Continuously Improving

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 securely configure Multi-Function Devices (MFD) according to industry-recognized secure practices for the type of device.

Assessment Objectives

  1. AST-23_A01 Multi-Function Devices (MFD) are securely configured according to industry-recognized secure practices for the type of device.

Evidence Requirements

E-TPM-01 Third-Party Contracts

Documented evidence of third-party contractual obligations for cybersecurity & data privacy protections.

Third-Party Management

Technology Recommendations

Micro/Small

  • Secure Baseline Configurations (SBC)
  • Network segmentation (logical and/or physical)

Small

  • Secure Baseline Configurations (SBC)
  • Network segmentation (logical and/or physical)

Medium

  • Secure Baseline Configurations (SBC)
  • Network segmentation (logical and/or physical)

Large

  • Secure Baseline Configurations (SBC)
  • Network segmentation (logical and/or physical)

Enterprise

  • Secure Baseline Configurations (SBC)
  • Network segmentation (logical and/or physical)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.