NET-03.12: Network Processing Rules For Personal Data (PD)
Mechanisms exist to apply network-based processing rules to data elements of Personal Data (PD).
Renumbered: Formerly NET-03.4 in SCF 2025.4.
Control Question: Does the organization apply network-based processing rules to data elements of Personal Data (PD)?
General (3)
| Framework | Mapping Values |
|---|---|
| NIST 800-53 R5.2 | SC-07(24) |
| NIST 800-53B R5 (privacy) (source) | SC-07(24) |
| NIST 800-82 R3 | SC-07(24) |
EMEA (4)
| Framework | Mapping Values |
|---|---|
| EMEA UK DEFSTAN 05-138 2024 | 2316 |
| EMEA UK DEFSTAN 05-138 - L1 2024 | 2316 |
| EMEA UK DEFSTAN 05-138 - L2 2024 | 2316 |
| EMEA UK DEFSTAN 05-138 - L3 2024 | 2316 |
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
Network Security (NET) 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 NET domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with NET 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 NET domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Network security-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Network security management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ IT personnel define secure networking practices to protect the Confidentiality, Integrity, Availability and Safety (CIAS) of the organization's TAASD. ▪ Secure Baseline Configurations (SBC) enforce the principles of least privileges and least functionality for boundary protection technologies.
Level 3 — Well Defined
Network Security (NET) 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 NET 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 NET domain capabilities are well-documented and kept current by process owners. ▪ A network security management team, or similar function, is appropriately staffed and supported to implement and maintain NET domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of network security operations (e.g., network management solution and log aggregator). ▪ 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 NET 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 the principles of least privileges and least functionality for boundary protection technologies. ▪ An implemented and operational capability exists to apply network-based processing rules to data elements of Personal Data (PD).
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
- NET-03.12_A01 processing rules for systems that process Personal Data (PD) are defined.
- NET-03.12_A02 processing rules are applied to data elements of Personal Data (PD) on systems that process Personal Data (PD).
- NET-03.12_A03 permitted processing is monitored at the external interfaces to the systems that process Personal Data (PD).
- NET-03.12_A04 permitted processing is monitored at key internal boundaries within the systems that process Personal Data (PD).
- NET-03.12_A05 each processing exception is documented for systems that process Personal Data (PD).
- NET-03.12_A06 exceptions for systems that process Personal Data (PD) are reviewed.
- NET-03.12_A07 exceptions for systems that process Personal Data (PD) that are no longer supported are removed.
Technology Recommendations
Micro/Small
- Basic firewall
- Network security policy
Small
- Small business firewall (e.g., Cisco Meraki)
- Network security policy
Medium
- Data Loss Prevention (DLP)
Large
- Data Loss Prevention (DLP)
Enterprise
- Data Loss Prevention (DLP)