nerdexam
Cisco

352-001 · Question #597

You are designing dual-homed active/active ISP connections from an enterprise customer for internet services, and you have recommended BGP between the customer and ISP. When three security…

The correct answer is B. remote triggered black holes E. Routing protocol authentication F. uRPF in loose mode. Securing a dual-homed active/active BGP ISP connection requires routing protocol authentication, loose-mode uRPF to handle asymmetric paths, and remote triggered black holes for rapid DDoS mitigation.

Designing Security

Question

You are designing dual-homed active/active ISP connections from an enterprise customer for internet services, and you have recommended BGP between the customer and ISP. When three security mechanisms do you enable to secure the connection? (Choose three)

Options

  • AuRPF is strict mode
  • Bremote triggered black holes
  • CIDS
  • DGTSM
  • ERouting protocol authentication
  • FuRPF in loose mode

How the community answered

(23 responses)
  • A
    4% (1)
  • B
    78% (18)
  • C
    13% (3)
  • D
    4% (1)

Why each option

Securing a dual-homed active/active BGP ISP connection requires routing protocol authentication, loose-mode uRPF to handle asymmetric paths, and remote triggered black holes for rapid DDoS mitigation.

AuRPF is strict mode

uRPF in strict mode drops packets whose source address does not match the specific interface on which they arrive, which would cause legitimate traffic drops in an active/active dual-homed design due to asymmetric routing.

Bremote triggered black holesCorrect

Remote triggered black holes (RTBH) allow the enterprise or ISP to null-route attack source prefixes by advertising a /32 host route tagged with a blackhole community to upstream peers, enabling rapid traffic scrubbing at the ISP edge.

CIDS

IDS is a passive detection technology and is not a BGP session security or routing security mechanism applied directly to the ISP peering connection.

DGTSM

GTSM (Generalized TTL Security Mechanism) sets a minimum TTL on BGP packets to protect against off-link spoofing but is less applicable to standard multi-hop ISP peering and was not selected alongside the three core mechanisms.

ERouting protocol authenticationCorrect

Routing protocol authentication (MD5 or TCP-AO on BGP sessions) prevents unauthorized peers from forming sessions and protects against route injection or BGP session reset attacks.

FuRPF in loose modeCorrect

uRPF in loose mode verifies only that a source IP address exists anywhere in the routing table rather than on the arriving interface, making it safe for active/active dual-homed topologies where asymmetric routing is inherent.

Concept tested: BGP peering security using uRPF loose mode, RTBH, and MD5 authentication

Source: https://www.cisco.com/c/en/us/about/security-center/unicast-reverse-path-forwarding.html

Topics

#BGP security#uRPF#RTBH#routing authentication

Community Discussion

No community discussion yet for this question.

Full 352-001 Practice