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 NSE6_FAC-6.4 Topic 3 Question 36 Discussion

Actual exam question for Fortinet's NSE6_FAC-6.4 exam
Question #: 36
Topic #: 3
[All NSE6_FAC-6.4 Questions]

Which method is the most secure way of delivering FortiToken data once the token has been seeded?

Show Suggested Answer Hide Answer
Suggested Answer: A

Online activation of the tokens through the FortiGuard network is the most secure way of delivering FortiToken data once the token has been seeded because it eliminates the risk of seed files being compromised during transit or storage. The other methods involve physical or manual delivery of seed files which can be intercepted, lost, or stolen. Reference: https://docs.fortinet.com/document/fortiauthenticator/6.4/administration-guide/372403/fortitoken


Contribute your Thoughts:

Johnna
2 days ago
Hmm, I'm not sure about Option A. Relying on the FortiGuard network for something this important seems risky to me.
upvoted 0 times
...
Shizue
3 days ago
I personally prefer C) Using the in-house token provisioning tool because it gives us more control over the process.
upvoted 0 times
...
Donte
3 days ago
I'd go with Option C. Using an in-house tool gives us more control over the process, you know?
upvoted 0 times
...
Keneth
8 days ago
I agree with Stephen, sending the seed files on a CD is more secure than online activation.
upvoted 0 times
...
Stephen
12 days ago
I think the most secure way is B) Shipment of the seed files on a CD using a tamper-evident envelope.
upvoted 0 times
...
Royce
12 days ago
Option B sounds like the most secure way to deliver the seed files. Can't go wrong with a tamper-evident envelope!
upvoted 0 times
Rebbeca
1 days ago
I agree, option B does sound like the most secure way to deliver the seed files.
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