Cyber Monday 2024! 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 5 Question 13 Discussion

Actual exam question for Fortinet's NSE7_NST-7.2 exam
Question #: 13
Topic #: 5
[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:

Jenelle
2 months ago
Haha, this question is a real 'DoS-y' one, isn't it? I reckon it's B) IKE_SA_INIT, but I might be 'SYN-ing' the wrong thing.
upvoted 0 times
Arlette
1 months ago
No, it's actually B) IKE_SA_INIT for DoS protection.
upvoted 0 times
...
Alyce
2 months ago
I'm not sure, but I think it's A) IKE_Req_INIT.
upvoted 0 times
...
Eleni
2 months ago
Yeah, that's correct. It's important for security.
upvoted 0 times
...
Julene
2 months ago
I think it's B) IKE_SA_INIT too, it handles DoS protection.
upvoted 0 times
...
...
Freeman
2 months ago
I see your point, Gussie, but I still think B) IKE_SA_INIT is the correct answer.
upvoted 0 times
...
Jesusita
3 months ago
Hmm, I'm not so sure. Maybe D) Create_CHILD_SA? That's where the child SAs are created, and those could potentially help with DoS protection.
upvoted 0 times
Danica
2 months ago
I agree with you, D) Create_CHILD_SA does seem like it could help with DoS protection by creating child SAs.
upvoted 0 times
...
Vilma
2 months ago
I'm leaning towards A) IKE_Req_INIT, since it's the first step in the exchange process.
upvoted 0 times
...
Bulah
2 months ago
I think it might be B) IKE_SA_INIT, that's where the initial exchange of security parameters happens.
upvoted 0 times
...
...
Makeda
3 months ago
Definitely C) IKE_Auth. That's where the parties authenticate each other, which is crucial for preventing DoS attacks. I'm sure about this one.
upvoted 0 times
Carmen
2 months ago
It's good to know that IKE_Auth handles the authentication to prevent DoS attacks.
upvoted 0 times
...
Rochell
2 months ago
I agree, DoS protection is crucial and that's why IKE_Auth is important in IKEv2.
upvoted 0 times
...
Willodean
2 months ago
Yes, IKE_Auth is where the authentication process takes place to protect against DoS.
upvoted 0 times
...
Kris
2 months ago
I think you're right, C) IKE_Auth is responsible for preventing DoS attacks.
upvoted 0 times
...
...
Gussie
3 months ago
I'm not sure, but I think it could also be D) Create_CHILD_SA.
upvoted 0 times
...
Dan
3 months ago
I agree with Freeman, IKE_SA_INIT makes sense for DoS protection.
upvoted 0 times
...
Isadora
3 months ago
I think it's B) IKE_SA_INIT. That's where the initial key exchange and Diffie-Hellman negotiation takes place, which helps protect against DoS attacks.
upvoted 0 times
Kyoko
3 months ago
Yes, that's correct. It handles the initial key exchange and helps protect against DoS attacks.
upvoted 0 times
...
Derick
3 months ago
I think it's B) IKE_SA_INIT.
upvoted 0 times
...
...
Freeman
3 months ago
I think the answer is B) IKE_SA_INIT.
upvoted 0 times
...

Save Cancel