Skip to main content

MNT-05.3: Remote Maintenance Cryptographic Protection

MNT 9 — Critical Protect

Cryptographic mechanisms exist to protect the integrity and confidentiality of remote, non-local maintenance and diagnostic communications.

Control Question: Are cryptographic mechanisms utilized to protect the integrity and confidentiality of remote, non-local maintenance and diagnostic communications?

General (18)
Framework Mapping Values
CIS CSC 8.1 12.3
CIS CSC 8.1 IG2 12.3
CIS CSC 8.1 IG3 12.3
GovRAMP High MA-04(06)
NIST 800-53 R4 MA-4(6)
NIST 800-53 R5 (source) MA-4(6)
NIST 800-53 R5 (NOC) (source) MA-4(6)
NIST 800-171 R3 (source) 03.07.05.b
NIST 800-171A R3 (source) A.03.07.05.b[02]
PCI DSS 4.0.1 (source) 2.2.7
PCI DSS 4.0.1 SAQ A-EP (source) 2.2.7
PCI DSS 4.0.1 SAQ B-IP (source) 2.2.7
PCI DSS 4.0.1 SAQ C (source) 2.2.7
PCI DSS 4.0.1 SAQ C-VT (source) 2.2.7
PCI DSS 4.0.1 SAQ D Merchant (source) 2.2.7
PCI DSS 4.0.1 SAQ D Service Provider (source) 2.2.7
SCF CORE ESP Level 2 Critical Infrastructure MNT-05.3
SCF CORE ESP Level 3 Advanced Threats MNT-05.3
US (5)
Framework Mapping Values
US DHS CISA TIC 3.0 3.UNI.SADMI
US FedRAMP R4 MA-4(6)
US FedRAMP R4 (high) MA-4(6)
US HIPAA HICP Large Practice 5.L.A
US IRS 1075 MA-4(6)
EMEA (1)
Framework Mapping Values
EMEA Israel CDMO 1.0 4.20 12.7
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 03.07.05.B

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to Cryptographic protect the integrity and confidentiality of remote, non-local maintenance and diagnostic communications.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to Cryptographic protect the integrity and confidentiality of remote, non-local maintenance and diagnostic communications.

Level 2 — Planned & Tracked

Maintenance (MNT) 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: o Identify cybersecurity and data protection controls to appropriately address applicable statutory, regulatory and contractual requirements for technology asset maintenance. o Develop and disseminate formal guidance to facilitate a localized/regionalized process to implement secure and timely technology asset-specific maintenance operations, including preventative and reactionary maintenance operations.

  • Technology asset maintenance is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
  • IT/cybersecurity personnel:
  • Maintenance controls are primarily administrative in nature (e.g., policies & standards) to manage change control processes associated with maintenance operations.
  • Asset custodians develop and maintain formalized procedures to conduct controlled and timely maintenance activities throughout the lifecycle of the system, application or service.
  • Maintenance operations may be centralized for certain locations (e.g., datacenters) and decentralized for other locations, both in terms of change management and execution.
  • Facilities management uses a localized/regionalized process to facilitate the secure and timely implementation of non-IT maintenance operations, including preventative and reactionary maintenance operations.
  • Technologies are configured to use cryptographic mechanisms to protect the integrity and confidentiality of non-local maintenance and diagnostic communications.
Level 3 — Well Defined

Maintenance (MNT) 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:

  • IT/cybersecurity personnel develop and disseminate formal practices to implement enterprise-wide capability to conduct secure and timely technology asset-specific maintenance operations, including preventative and reactionary maintenance operations.
  • Technology asset-related maintenance operations are centralized in terms of change management and governance. Local/regional practices fall under the broader enterprise-wide technology asset maintenance program.
  • Facilities management uses an enterprise-wide process to facilitate the secure and timely implementation of non-IT maintenance operations, including preventative and reactionary maintenance operations. Local/regional practices fall under the broader enterprise-wide facilities management program.
  • A Change Control Board (CCB), or similar function, centrally manages the process of IT and non-IT maintenance operations to reduce the chance of business interruptions from maintenance operations.
  • Technologies are configured to use cryptographic mechanisms to protect the integrity and confidentiality of non-local maintenance and diagnostic communications.
Level 4 — Quantitatively Controlled

Maintenance (MNT) 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. In addition to CMM Level 3 criteria, CMM Level 4 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • 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.
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 Cryptographic protect the integrity and confidentiality of remote, non-local maintenance and diagnostic communications.

Assessment Objectives

  1. MNT-05.3_A01 cryptographic mechanisms to be implemented to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications are defined.
  2. MNT-05.3_A02 cryptographic mechanisms are implemented to protect the integrity of nonlocal maintenance and diagnostic communications.
  3. MNT-05.3_A03 cryptographic mechanisms are implemented to protect the confidentiality of nonlocal maintenance and diagnostic communications.
  4. MNT-05.3_A04 replay resistance is implemented in the establishment of nonlocal maintenance and diagnostic sessions.

Technology Recommendations

Micro/Small

  • Secure Baseline Configurations (SBC)

Small

  • Secure Baseline Configurations (SBC)

Medium

  • Secure Baseline Configurations (SBC)

Large

  • Secure Baseline Configurations (SBC)

Enterprise

  • Secure Baseline Configurations (SBC)

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.