|
+Remote Management of Embedded Technologies |
Remote Management of Embedded TechnologiesDescriptionMechanisms 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. Possible Solutions & ConsiderationsMicro-Small Business (<10 staff) / BLS Firm Size Classes 1-2∙ Disable remote management on IoT devices unless needed∙ Change default credentials and enable MFA where supported Small Business (10-49 staff) / BLS Firm Size Classes 3-4∙ VPN with MFA for remote device management∙ Remote access disabled by default and enabled on request ∙ Vendor remote access approved per session Medium Business (50-249 staff) / BLS Firm Size Classes 5-6∙ Jump host / bastion for OT/IoT management with MFA∙ Time-limited vendor access ∙ Session logging Large Business (250-999 staff) / BLS Firm Size Classes 7-8∙ Secure remote access for OT (e.g., Claroty SRA, Cyolo, BeyondTrust)∙ Privileged Access Management (PAM) session brokering and recording ∙ No persistent vendor connections Enterprise (> 1,000 staff) / BLS Firm Size Class 9∙ 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 SCR-CMMLevel 0 Not PerformedPractices 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 InformallyEmbedded 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 TrackedEmbedded 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 DefinedEmbedded 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 ControlledUtilize 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 ImprovingUtilize 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. 1. Oversigt
1.1 Referencer1.2 Identificerede krav1.3 Relaterede reguleringer2. Identificerede krav
3. Relaterede reguleringer
Linkede sager
|