Learning paths › CCNP Security › Device, routing and cryptographic hardening
Device, routing and cryptographic hardening
Hardening the device, then the routing that runs on it, then the cryptography under both: who can reach the management plane and how the router's own CPU is protected, a management path that survives an outage, authenticated EIGRP and OSPF adjacencies, a signed DNS answer, credential-protecting file transfer, an SNMP version that authenticates the manager, usable log severity and provable time sync — then algorithm separated from key, symmetric for bulk against asymmetric for exchange, a TLS handshake read with its certificate, the IKE phases, and a first policy-based site-to-site tunnel.
Lessons
- Restrict who can reach the management plane
- Verify an SSH host key before you trust it
- Protect the router's own CPU from its traffic
- Follow a packet through the forwarding path
- Keep a management path that survives an outage
- Reject routing updates that cannot prove themselves
- Authenticate EIGRP and OSPF adjacencies
- Decide where neighbour discovery should not be enabled
- Tell a forged DNS answer from a signed one
- Pick a file transfer that protects the credentials
- Choose an SNMP version that authenticates the manager
- Set a severity threshold that keeps the useful events
- Get clocks close enough to correlate logs
- Prove the device is actually synchronised
- Separate the algorithm from the key
- Choose symmetric for bulk, asymmetric for key exchange
- Prove a file did not change in transit
- Tell a private overlay from an encrypted one
- Choose between AH and ESP, and know why
- Derive a shared key over a channel someone watches
- Read a TLS handshake and check the certificate
- Match IKE phases to what each one negotiates
- Read a Phase 1 capture by purpose, not packet number
- Bring up a policy-based site-to-site tunnel