Agreed.
(pg 238) "Captive portal, for both wired and Wi-Fi networks, is enabled at the interface level—regardless of the firewall policy that allows it or the port that it ultimately leaves by (authentication being enabled or disabled on the policy is not a factor).
(pg 239)...Restricted Groups: Only groups configured under the Admission Control section can successfully authenticate and access resources."
D is correct. Because port3 has captive portal enable for HR group, no mater which destination they try to reach, they will have to authenticate.
A) There is no fall-through policy because "auth-on-demand always"
B) Sales group will authenticate ONLY if they try to go to internet though wan1. If Sales group traffic enters port3 but with destination different from wan1, then they will not have to authenticate.
C) Authentication is enforced at a policy level only for Sales group and, again, ONLY if they try to reach internet though wan1.
I think the key here is the wording "when traffic arrives".
If you're using policy based authentication (with auth-on-demand set to enable AND you have a policy with active authentication enabled), fortinet says "traffic is allowed until authentication is successful."
But, if you authenticate through the interface, "all devices must authenticate before they are allowed to access any resources."
Let alone that they say "Captive portal, for both wired and Wi-Fi networks, is enabled at the interface level—regardless of the firewall policy that allows it or the port that it ultimately leaves by (authentication being enabled or disabled on the policy is not a factor)."
Fortigate security 7.0 pg 243
Fortigate security 7.0 pg 248-249
Yeah I've gone back through this and I think it's C.
Because authentication is set at the interface, everyone will be prompted and HR will be granted access.
I think C. The question is not asking who will be granted access but rather what will happen when someone tries to access. They will all be prompted but only HR will be granted. The rest will fail
Answer is C. D cannot be correct. Yes only HR can successfully authenticate, but the ForitGate doesn't know if you are HR until you authenticate. ALL users will be prompted to authenticated, only HR will be allowed access.
I vote for C. Auth is enforced in policy, but also on interface so because of this all users will have to authenticate.
D i think is not ok because it says to authenticate with credentials, but the method used is based on certificates.
A is the correct Answer because as pointed out by all;
configure on Fortigate:
- captive portal authentication required
- Authentication failed message for Sales users
- Authentication success for HR users
- second policy used by HR users
I vote for C because,
Captive Portal is activate on interface level, All Users will be prompted for authentication but only members of HR group will authenticate succesfully. Cause of this formulation i think D in not correct
Interface : All Users will Be prompted HR group -->pass
Policy : If HR group User is member of sales group too --> pass
I tell you that I did a test, what I saw is that the configuration made in config user settings has less priority in relation to the configuration made in the captive portal of the interface. After my experiment I can determine that the answer is the letter D because it authenticates with the HR group and for the traffic to go out it matches the auth users policy.
For my understanding, the best practice is to have the same groups on both the interface and on the policies. Is that right? In the described scenario, what will happen? The Sales team is not explicetely included in the interface, so I think that they will never authenticate.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
kkkvo
Highly Voted 3 years, 8 months agoprenominal
3 years, 8 months ago2021gene
3 years, 8 months agomorningstar
Highly Voted 3 years, 6 months agoNicolaeEast
Most Recent 2 years, 8 months agoNicolaeEast
2 years, 8 months agoChuckC
2 years, 10 months agoBluey
2 years, 11 months agommhhll
3 years, 1 month agoGycu
3 years, 1 month agothiagomacedodonascimento
3 years, 1 month agokemi01
3 years, 1 month agojccxx
3 years, 1 month agoDaniloDJ72
3 years, 1 month agodarkangelinos
3 years, 2 months agodarkangelinos
3 years, 1 month agopaulTT
3 years, 2 months agomario156090
3 years, 2 months agodaxrob
3 years, 3 months agolrosadini
3 years, 3 months agovdmuhovskis
3 years, 3 months agoblahblah1234567890000
3 years, 3 months ago