Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Fortinet Exam NSE7_NST-7.2 Topic 1 Question 9 Discussion

Actual exam question for Fortinet's NSE7_NST-7.2 exam
Question #: 9
Topic #: 1
[All NSE7_NST-7.2 Questions]

Which exchange lakes care of DoS protection in IKEv2?

Show Suggested Answer Hide Answer
Suggested Answer: B

IKE_SA_INIT Exchange:

The IKE_SA_INIT exchange is the first step in the IKEv2 negotiation process. It is responsible for setting up the initial security association (SA) and performing Diffie-Hellman key exchange.

During this exchange, the responder may employ various measures to protect against Denial of Service (DoS) attacks, such as rate limiting and the use of puzzles to increase the computational cost for an attacker.

DoS Protection Mechanisms:

One key method involves limiting the number of half-open SAs from any single IP address or subnet.

The IKE_SA_INIT exchange can also incorporate the use of stateless cookies, which help to verify the initiator's legitimacy without requiring extensive resource allocation by the responder until the initiator is verified.


RFC 5996: Internet Key Exchange Protocol Version 2 (IKEv2) (RFC Editor).

RFC 8019: Protecting Internet Key Exchange Protocol Version 2 (IKEv2) Implementations from Distributed Denial-of-Service Attacks (IETF Datatracker).

Contribute your Thoughts:

Kerry
2 months ago
A) IKE_Req_INIT? Really? That's just the initial request, how would that handle DoS protection? I think you're all overthinking this.
upvoted 0 times
...
Almeta
2 months ago
Yeah, that's a good point. Maybe the real answer is a black hole where all the DoS attacks get sucked in. That would be the ultimate DoS protection!
upvoted 0 times
Elvis
28 days ago
D) Create_CHILD_SA
upvoted 0 times
...
Tammy
29 days ago
D) Create_CHILD_SA
upvoted 0 times
...
Johnna
29 days ago
C) IKE_Auth
upvoted 0 times
...
Alayna
1 months ago
C) IKE_Auth
upvoted 0 times
...
Avery
1 months ago
B) IKE_SA_INIT
upvoted 0 times
...
Geraldo
1 months ago
B) IKE_SA_INIT
upvoted 0 times
...
Bettina
1 months ago
A) IKE_Req_INIT
upvoted 0 times
...
Nydia
2 months ago
A) IKE_Req_INIT
upvoted 0 times
...
...
Alaine
2 months ago
I believe it's D) Create_CHILD_SA because it establishes the secure channel for data exchange.
upvoted 0 times
...
Alease
2 months ago
I'm not sure, but I think it might be C) IKE_Auth.
upvoted 0 times
...
Vincenza
2 months ago
I agree with Burma, IKE_SA_INIT is responsible for DoS protection in IKEv2.
upvoted 0 times
...
Burma
2 months ago
I think the answer is B) IKE_SA_INIT.
upvoted 0 times
...
Edison
2 months ago
Hmm, I'm not so sure. Wouldn't it be more like C) IKE_Auth? That's where the authentication takes place, which is key for DoS protection.
upvoted 0 times
Annabelle
1 months ago
You might be right, C) IKE_Auth does seem like a crucial step for authentication and therefore DoS protection.
upvoted 0 times
...
Solange
1 months ago
I'm not sure, but A) IKE_Req_INIT might also play a role in DoS protection by handling the initial request.
upvoted 0 times
...
Sheron
2 months ago
Actually, I believe it's D) Create_CHILD_SA, as that's where the actual child SA is created for secure communication.
upvoted 0 times
...
Edgar
2 months ago
I think it's B) IKE_SA_INIT, that's where the initial exchange of security parameters happens.
upvoted 0 times
...
...
Felicia
3 months ago
You know, if I was a hacker, I'd probably just try DoS'ing the whole exchange. See if I can crash the system before it even gets to the IKE stuff.
upvoted 0 times
Bernardine
2 months ago
B) IKE_SA_INIT
upvoted 0 times
...
Annette
2 months ago
A) IKE_Req_INIT
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77