Skip to main content

EMB-12: Restrict Communications

EMB 8 — High Protect

Mechanisms exist to require embedded technologies to initiate all communications and drop new, incoming communications.

Control Question: Does the organization require embedded technologies to initiate all communications and drop new, incoming communications?

General (1)
Framework Mapping Values
CSA IoT SCF 2 COM-10

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to require embedded technologies to initiate all communications and drop new, incoming communications.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to require embedded technologies to initiate all communications and drop new, incoming communications.

Level 2 — Planned & Tracked

C|P-CMM2 is N/A, since a well-defined process is required to require embedded technologies to initiate all communications and drop new, incoming communications.

Level 3 — Well Defined

Embedded Technology (EMB) 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, categorizes embedded technologies according to the data the asset stores, transmits and/ or processes to ensure that the appropriate technology controls are applied to protect the asset and the data it stores, transmits or processes.
  • An IT infrastructure team, or similar function, ensures that statutory, regulatory and contractual cybersecurity and data privacy obligations are addressed to ensure secure configurations for embedded technologies are designed, built and maintained for embedded technologies.
  • Cybersecurity personnel perform annual evaluations of deployed embedded technologies to identify necessary updates to mitigate any newly discovered risks associated with legacy embedded technologies.
  • Configurations for embedded technologies conform to industry-recognized standards for hardening (e.g., DISA STIGs, CIS Benchmarks or OEM security guides) for test, development, staging and production environments.
  • Configuration management of embedded technologies is centralized for all operating systems, applications, servers and other technologies that are capable of being configured.
  • Special baseline configurations for embedded technologies are created for higher-risk environments.
  • Deviations to baseline configurations for embedded technologies are required to have a risk assessment and the business process owner accepts the risk(s) associated with the deviation.
  • Unauthorized configuration changes to embedded technologies are responded to in accordance with an Incident Response Plan (IRP) to determine if the unauthorized configuration is malicious in nature.
  • A Data Protection Impact Assessment (DPIA) is used to help ensure the protection of sensitive/regulated data processed, stored or transmitted on embedded technologies, so that cybersecurity and data protection controls are implemented in accordance with applicable statutory, regulatory and contractual obligations.
  • Embedded technologies are restricted to communicate only with authorized peers and service endpoints.
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 require embedded technologies to initiate all communications and drop new, incoming communications.

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 require embedded technologies to initiate all communications and drop new, incoming communications.

Assessment Objectives

  1. EMB-12_A01 configurations for embedded technologies require the initiation of all communications and drop new, incoming communications.

Technology Recommendations

Micro/Small

  • Secure Baseline Configurations (SBC)
  • Network segmentation (logical and/or physical)
  • Access Control Lists (ACL)

Small

  • Secure Baseline Configurations (SBC)
  • Network segmentation (logical and/or physical)
  • Access Control Lists (ACL)

Medium

  • Secure Baseline Configurations (SBC)
  • Network segmentation (logical and/or physical)
  • Access Control Lists (ACL)

Large

  • Secure Baseline Configurations (SBC)
  • Network segmentation (logical and/or physical)
  • Access Control Lists (ACL)

Enterprise

  • Secure Baseline Configurations (SBC)
  • Network segmentation (logical and/or physical)
  • Access Control Lists (ACL)

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.