01 - IPsec Intro Flashcards

1
Q

Two primary IPsec protocols

A
Encapsulating Security Payload (ESP)
Authentication Header (AH)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

CET

A

Cisco Encryption Technology

IOS 11.2, August 2003

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

CET Features / Capabilities

A

Commercial grade in the sense that it was a major simplification over the former systems. It allowed a mere mortal to configure a very regular and relatively cheap router (Cisco 2500) to encrypt data across a public Layer 3 network. The cryptographic algorithms were very good: DES, then 3-DES, Diffie-Hellman key exchange. At 160 Kbps, the throughput was acceptable in those days (~2003)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

4 Steps of Technology Deployment

A
  1. Make it work.
  2. Make it work reliably.
  3. Make it work at speed.
  4. Make it work at scale.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What did CET evolve into?

A

CET evolved into IKE/ISAKMP + IPsec

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

RFC 2408

A

Internet Security Association and Key Management Protocol (ISAKMP)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Limits of Crypto Maps

A
  • the combinatory explosion of source/destination pairs on ever larger and complex networks
  • code complexity due to packets being stolen in OSI layer 2 and re-encapsulated into a new IP header (OSI layer 3)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Control plane issues which triggered many race conditions in IKE/ISAKMP implementations

A
  1. IKE itself and its rekey complexity

2. Differences in behavior between IKE SA rekeys and IPsec SA rekeys

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Effect of security policy size explosion

A

The security policy size explosion made mesh networks totally unmanageable.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Limitation of GRE protected by IPsec in order to run routing protocols on top of the tunnels

A

Scalability was relatively limited due to hardware performance.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Basic function of NHRP protocol

A

Establish circuits on demand

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

EasyVPN Summary

A

EasyVPN supported remote access (especially the software client) compact but the feature had grown organically and the UI was terrible; it was also crypto map based, and its quality was poor.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Enhanced EasyVPN Summary

A

Enhanced Easy VPN solved the crypto map problem and was a major improvement over Easy VPN, but it did not enjoy proper marketing and remained poorly adopted.
The UI was the same and hence difficult.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What caused GRE/IPsec to gradually disappear?

A

GRE/IPsec was slowly disappearing at the benefit of DMVPN and tunnel protection in the site-to-site scenarios.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

GET VPN Summary

A

GET VPN has lower security and limited scalability, but it is lighter on resources when used properly, if the use case is adequate. Notably, it allows native multicast.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Issue with DMVPN

A

DMVPN was growing in both the hub-and-spoke and partial mesh cases, but the routing protocol was a deterrent for Security Operations who preferred using EasyVPN.

17
Q

FlexVPN CLI

A

Clear, consistent, compact, and powerful CLI: simple things ought to be simple to configure, complex things ought to be possible.

18
Q

FlexVPN and Routing Protocols

A

Using routing protocols should be a customer choice, not mandatory.

19
Q

FlexVPN and NHRP

A

NHRP usage could decrease except for spoke-spoke tunnel creation.

20
Q

FlexVPN Scale

A

Increased scale to 10,000 tunnels per hub at least.

21
Q

FlexVPN and Remote Access Management

A

All the remote access management features had to be applicable to site-to-site and hub-and-spoke (AAA authorization in particular to apply per user QoS, ACLs, and so on.)

22
Q

FlexVPN and Reliance on PKI / Pre-Shared Keys

A

Reduce the reliance on PKI and make pre-shared keys more manageable.
Both had to be possible, at least for hub-and-spoke

23
Q

FlexVPN and the CLI

A

For the first time all VPN technologies could be configured under a single CLI construct.

24
Q

Effect of FlexVPN on IOS

A

FlexVPN has allowed IKEv2 and IPsec VPNs on Cisco IOS to become a lot more user friendly.

25
Q

Issues for IPsec VPNs

A
NAT traversal
fragmentation
segmentation
IP dual stack
multicast
non-IP protocols
26
Q

3 IPsec Databases

A
  1. Security Policy Database (SPD)
  2. Security Association Database (SADB)
  3. Peer Authorization Database (PAD)
27
Q

Two Modes of IPsec

A
  1. Tunnel Mode

2. Transport Mode

28
Q

Important IKE Packet Exchanges

A

SA_INIT
IKE_AUTH
INFORMATIONAL
CREATE_CHILD_SA