4.2
IG1 IG2 IG3

Establish and Maintain a Secure Configuration Process for Network Infrastructure

Asset Type: Network
Security Function: Protect

Description

Establish and maintain a secure configuration process for network devices. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.

Implementation Checklist

1
Assess current protection controls in place
2
Configure and deploy required security controls
3
Test control effectiveness in non-production environment
4
Deploy to production and verify functionality
5
Document configuration and operational procedures
6
Draft policy/procedure document
7
Obtain stakeholder review and approval
8
Communicate to affected personnel
9
Schedule periodic review and updates
10
Select hardening benchmark (CIS Benchmarks, DISA STIGs)
11
Create baseline configuration templates
12
Deploy configurations using automation tools
13
Schedule compliance scanning to detect drift

Threats & Vulnerabilities (CIS RAM)

Threat Scenarios

Network Device Compromise via Default Credentials

Confidentiality

Attackers gain administrative access to routers, switches, and firewalls using well-known default credentials or SNMP community strings that were never changed from vendor defaults.

Router/Switch Misconfiguration Enabling Traffic Interception

Confidentiality

Network devices configured without security hardening allow traffic mirroring, unauthorized VLAN access, or routing manipulation enabling man-in-the-middle attacks.

Vulnerabilities (When Safeguard Absent)

Unhardened Network Infrastructure Devices

Without a secure configuration process for network devices, routers, switches, and firewalls run with default settings that expose management interfaces and unnecessary services.

No Compliance Verification Against Network Hardening Standards

Without documented configuration processes referencing standards like CIS Benchmarks or DISA STIGs, there is no way to verify network devices meet security requirements.

Evidence Requirements

Type Evidence Item Collection Frequency
Technical Configuration screenshots or exports showing protection controls enabled Captured quarterly
Document Procedure documentation for protection measures Reviewed annually
Technical Configuration compliance scan results against approved baseline Scanned monthly
Document Approved baseline configuration documentation Reviewed quarterly
Document Governing policy document (current, approved, communicated) Reviewed annually