Skip to main content

NET-26.1: Remote Access Pathways

NET 9 — Critical Protect

Mechanisms exist to route all remote access pathways through managed network access control points (e.g., VPN concentrator).

Renumbered: Formerly NET-14.3 in SCF 2025.4.

Control Question: Does the organization route all remote accesses through managed network access control points (e.g., VPN concentrator)?

General (18)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC6.1-POF5 CC6.1-POF6 CC6.6-POF4
CIS CSC 8.1 12.7
CIS CSC 8.1 IG2 12.7
CIS CSC 8.1 IG3 12.7
GovRAMP AC-17(03)
GovRAMP Moderate AC-17(03)
GovRAMP High AC-17(03)
NIST 800-53 R4 AC-17(3)
NIST 800-53 R5.2 AC-17(03)
NIST 800-53B R5 (moderate) (source) AC-17(03)
NIST 800-53B R5 (high) (source) AC-17(03)
NIST 800-82 R3 AC-17(03)
NIST 800-82 R3 MODERATE OT Overlay AC-17(03)
NIST 800-82 R3 HIGH OT Overlay AC-17(03)
NIST 800-171 R2 (source) 3.1.14
NIST 800-171 R3 (source) 03.01.12.c
NIST 800-171A (source) 3.1.14[a] 3.1.14[b]
NIST 800-171A R3 (source) A.03.01.12.c[01] A.03.01.12.c[02]
US (10)
EMEA (5)
APAC (1)
Framework Mapping Values
APAC Malaysia RMiT 2025 A5-A3(c)
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 2025 03.01.12.C

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

Network Security (NET) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with NET domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Network security-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.

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 route all remote accesses through managed network access control points (e.g., VPN concentrator).

Level 4 — Quantitatively Controlled

Network Security (NET) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ 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. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

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. NET-26.1_A01 managed access control points are identified and implemented.
  2. NET-26.1_A02 remote access is routed through managed network access control points.

Evidence Requirements

E-NET-09 Network Access Control Points

Documented evidence of network access control points.

Network Security

Technology Recommendations

Micro/Small

  • Use a single, monitored VPN gateway for remote access

Small

  • Consolidated remote access through managed gateway
  • Access point documentation

Medium

  • Formal managed access control point policy
  • Centralized remote access gateway

Large

  • Enterprise centralized remote access with monitoring
  • Access control enforcement at gateway

Enterprise

  • Enterprise centralized remote access platform (ZTNA/VPN)
  • All remote access through managed control points
  • SIEM monitoring

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.