Protocol Security
Replace insecure protocols: Telnet → SSH. SNMPv1/v2c → SNMPv3. HTTP management → HTTPS. FTP → SFTP or SCP. TFTP → SCP for sensitive transfers. Rlogin/RSH → SSH. NTP: use authenticated NTP (NTPv4 with keys or NTS) to prevent NTP spoofing (which can manipulate timestamps and affect certificate validation and log correlation).
Disable unused protocols and features: CDP (Cisco Discovery Protocol) — disclose device type, IOS version on external ports. LLDP — similar to CDP, disable on external-facing interfaces. Unused routing protocols (RIP if OSPF is deployed). IP source routing — allows packets to specify their own route, exploited in attacks. Proxy ARP — can enable unauthorized traffic forwarding. Directed broadcasts — used in Smurf DDoS amplification attacks.
Management Plane Hardening
Control plane policing (CoPP): rate-limits traffic sent to the router/switch CPU, protecting against CPU exhaustion attacks. Without CoPP, a flood of routing protocol packets or management traffic can overwhelm the CPU and cause the device to stop forwarding. CoPP is implemented as QoS policies on the control plane interface.
Secure management access: use SSH v2 with strong key algorithms (RSA 4096 or ECDSA). Configure login retry limits and lockout. Use privilege levels and role-based access control (RBAC) — not all administrators need full access. Time-out idle sessions. Use OOB management network. AAA with TACACS+ for command logging.
Login banners: configure legal warning banners on all devices. Banners state that unauthorized access is prohibited and may be logged. Without a legal warning banner, prosecution of unauthorized access may be more difficult in some jurisdictions.
Data Plane Hardening
Port security: limits MAC addresses per switch port — prevents MAC flooding and unauthorized device connection. BPDU Guard: protects STP from rogue switches on access ports. Root Guard: prevents unauthorized root bridge election. Loop Guard: prevents forwarding loops if a port stops receiving BPDUs. Storm control: limits broadcast, multicast, or unicast flooding to a defined threshold — prevents broadcast storms from overwhelming links.
Private VLANs (PVLANs): prevent communication between ports in the same VLAN. Community ports can communicate with each other and the promiscuous port (uplink). Isolated ports can only communicate with the promiscuous port. Used in hosting environments where customer VMs in the same VLAN shouldn't communicate with each other.