Question 330
A FortiOS 7.6 team examines: A client connects through a shared terminal and simple IP identity mapping cannot reliably distinguish users. Select TWO complementary choices: the most appropriate corrective action AND the specific evidence confirming success.
Explanation
Correct Answers
The reported FortiOS 7.6 condition is: A client connects through a shared terminal and simple IP identity mapping cannot reliably distinguish users. The targeted administrative response is: Integrate Fortinet Single Sign-On collector information so observed directory logon events map validated user identities to current client IP addresses. The relevant failure risk is: Incorrect or stale user-to-IP correlation can assign the wrong identity-based firewall privileges to shared addresses. Validate with: A test logon appears with the expected user and client IP, and the corresponding policy match is confirmed.
For the observed situation (A client connects through a shared terminal and simple IP identity mapping cannot reliably distinguish users), the most specific acceptance evidence is: A test logon appears with the expected user and client IP, and the corresponding policy match is confirmed. It validates the recommended response: Integrate Fortinet Single Sign-On collector information so observed directory logon events map validated user identities to current client IP addresses. This addresses the documented risk: Incorrect or stale user-to-IP correlation can assign the wrong identity-based firewall privileges to shared addresses.
Incorrect Answers
Interactive user authentication policy design (2.3) would demonstrate or implement: Unmatched authentication rules can permit access before identity validation or repeatedly prompt permitted users. The case states: A client connects through a shared terminal and simple IP identity mapping cannot reliably distinguish users. The most direct paired action and test is: Integrate Fortinet Single Sign-On collector information so observed directory logon events map validated user identities to current client IP addresses.
Firewall policy logging and traceability (2.1) would demonstrate or implement: An approved representative flow generates a retained event showing matched rule ID and expected enforcement action. This choice can be useful for that problem, but it does not establish the Fsso collector agent mapping control being assessed here.
Central snat versus policy nat selection (2.2) addresses another technical failure: Changing only firewall-policy NAT settings when central NAT is authoritative can leave the source address unchanged. This case instead tests Fsso collector agent mapping; the choice measures or changes another part of the system.