nerdexam
Cisco

400-007 · Question #379

An organization is working on a design solution for a new Internet-based remote access virtual private network that has 1000 remote sites. A network administrator recommends GETVPN as the model…

The correct answer is B. GETVPN key servers would be on public hacker-reachable space and need higher security. GETVPN is designed for private MPLS or WAN environments, not the public Internet. Deploying it over the Internet places Key Servers in publicly accessible address space.

Designing Security

Question

An organization is working on a design solution for a new Internet-based remote access virtual private network that has 1000 remote sites. A network administrator recommends GETVPN as the model. What is a potential problem of using GETVPN in this situation?

Options

  • AGETVPN is not scalable to a large number of remote sites
  • BGETVPN key servers would be on public hacker-reachable space and need higher security
  • CGETVPN and DMVPN do not interoperate
  • DGETVPN requires a high level of background traffic to maintain its IPsec SAs

How the community answered

(40 responses)
  • A
    3% (1)
  • B
    83% (33)
  • C
    10% (4)
  • D
    5% (2)

Why each option

GETVPN is designed for private MPLS or WAN environments, not the public Internet. Deploying it over the Internet places Key Servers in publicly accessible address space.

AGETVPN is not scalable to a large number of remote sites

GETVPN is specifically designed to scale to thousands of sites using a group-based keying model, so lack of scalability is not a valid concern.

BGETVPN key servers would be on public hacker-reachable space and need higher securityCorrect

GETVPN requires Group Members to register with a Key Server (KS) to obtain IPsec group keys. When deployed over the public Internet, the KS must have a publicly routable IP address, exposing it to attack from any Internet-connected host. This is a fundamental architectural mismatch because GETVPN assumes a trusted private transport and lacks the endpoint authentication model needed to protect a publicly exposed KS.

CGETVPN and DMVPN do not interoperate

GETVPN and DMVPN can interoperate in certain hub-and-spoke designs; non-interoperability is not an inherent limitation.

DGETVPN requires a high level of background traffic to maintain its IPsec SAs

GETVPN uses periodic rekey messages rather than continuous background traffic, and it does not require excessive keepalive traffic to maintain its IPsec SAs.

Concept tested: GETVPN Key Server exposure on public Internet

Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_conn_getvpn/configuration/xe-16/sec-get-vpn-xe-16-book/sec-get-vpn.html

Topics

#GETVPN#key server security#Internet-based VPN#IPsec

Community Discussion

No community discussion yet for this question.

Full 400-007 Practice