Skip to main content

MON-34: Non-Repudiation

MON 8 — High Protect

Mechanisms exist to utilize a non-repudiation capability to protect against an individual falsely denying having performed a particular action.

Renumbered: Formerly MON-09 in SCF 2025.4.

Control Question: Does the organization utilize a non-repudiation capability to protect against an individual falsely denying having performed a particular action?

General (11)
Framework Mapping Values
GovRAMP AU-10
GovRAMP High AU-10
IEC 62443-3-3 2013 SR 2.12 SR 2.12 RE 1
IEC 62443-4-2 2019 CR 2.12 CR 2.12(1)
NIST 800-53 R4 AU-10
NIST 800-53 R5.2 AU-10
NIST 800-53B R5 (high) (source) AU-10
NIST 800-82 R3 AU-10
NIST 800-82 R3 HIGH OT Overlay AU-10
NIST 800-161 R1 AU-10
NIST 800-161 R1 Level 3 AU-10
US (2)
Framework Mapping Values
USA Federal CMS MARS-E 2.0 AU-10
USA Federal FedRAMP R5 (high) AU-10
EMEA (1)
Framework Mapping Values
EMEA Germany C5 2026 OPS-15.03B
APAC (1)
Framework Mapping Values
APAC Malaysia RMiT 2025 A3-4 A7-D2(b) A7-D2(b)(i)

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

SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.

Level 2 — Planned & Tracked

Continuous Monitoring (MON) 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 MON domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with MON 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 MON domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Continuous monitoring-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Continuous monitoring 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

Continuous Monitoring (MON) 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 MON domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Cybersecurity personnel use a structured process via Standardized Operating Procedures (SOP) to review and analyze logs. ▪ A Security Operations Center (SOC) team, or similar function, is appropriately staffed and supported to implement and maintain MON domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of continuous monitoring operations (e.g., Security Incident Event Manager (SIEM)). ▪ 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 MON 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). ▪ Secure Baseline Configurations (SBC) enforce security event logging to contain sufficient information to establish necessary details of activity and allow for forensics analysis. ▪ An implemented and operational capability exists to utilize a non-repudiation capability to protect against an individual falsely denying having performed a particular action.

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

  1. MON-34_A01 actions to be covered by non-repudiation are defined.
  2. MON-34_A02 irrefutable evidence is provided that an individual (or process acting on behalf of an individual) has performed organization-defined actions.

Evidence Requirements

E-MON-09 Event Logs

Documented evidence of event logs being generated by Technology Assets, Applications and/or Services (TAAS).

Event Log Monitoring

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.