EMB-15: Remote Management of Embedded Technologies
Mechanisms exist to restrict remote management of embedded technologies by: (1) Allowing access only when needed; (2) Eliminating "always on" connections; and (3) Requiring strong authentication.
Code reused: In SCF 2025.4 and earlier, EMB-15 was Safety Assessment. That control is now EMB-19.
Control Question: Does the organization restrict remote management of embedded technologies by: (1) Allowing access only when needed; (2) Eliminating "always on" connections; and (3) Requiring strong authentication?
US (1)
| Framework | Mapping Values |
|---|---|
| USA Federal DoW BaTB OT 2026 | 6 |
APAC (2)
| Framework | Mapping Values |
|---|---|
| APAC Australia CCM 2026 | PRO-20 |
| APAC Singapore CCOP CII 2026 | 5.7.2 |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
Embedded Technology (EMB) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with EMB domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Embedded technology management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Embedded technologies (e.g., Operational Technology (OT) and Internet of Things (IoT) are managed in the same manner as any other technology asset.
Level 2 — Planned & Tracked
Embedded Technology (EMB) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with EMB domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with EMB domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with EMB domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Embedded technology-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Embedded technology management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
Level 3 — Well Defined
Embedded Technology (EMB) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with EMB domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with EMB domain capabilities are well-documented and kept current by process owners. ▪ An embedded systems team, or similar function, is appropriately staffed and supported to implement and maintain EMB domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of embedded technology operations (e.g., Configuration Management Database (CMBD) Asset Management solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with EMB domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls).
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- EMB-15_A01 requests for remote management access to embedded technologies are approved by designated personnel before access is enabled.
- EMB-15_A02 remote management access to embedded technologies is enabled only for the duration of an approved need and is disabled when the need ends.
- EMB-15_A03 persistent ("always on") remote management connections to embedded technologies are eliminated, with remote sessions established on demand and terminated on completion.
- EMB-15_A04 remote management of embedded technologies requires strong authentication (e.g., multi-factor authentication).
- EMB-15_A05 remote management sessions to embedded technologies are logged and the logs are reviewed at a defined frequency for unapproved or anomalous access.
Evidence Requirements
- E-EMB-03 Embedded Technology Remote Management & Maintenance Records
-
Documented evidence of remote management restrictions and maintenance records for embedded technologies.
Asset Management
Technology Recommendations
Micro/Small
- Disable remote management on IoT devices unless needed
- Change default credentials and enable MFA where supported
Small
- VPN with MFA for remote device management
- Remote access disabled by default and enabled on request
- Vendor remote access approved per session
Medium
- Jump host / bastion for OT/IoT management with MFA
- Time-limited vendor access
- Session logging
Large
- Secure remote access for OT (e.g., Claroty SRA, Cyolo, BeyondTrust)
- Privileged Access Management (PAM) session brokering and recording
- No persistent vendor connections
Enterprise
- Enterprise OT secure remote access platform (e.g., Claroty SRA, Dragos, Cyolo)
- PAM with session recording and just-in-time access
- Continuous monitoring of remote sessions in the SOC