Question 380
A FortiSASE operator faces this issue: A compliance tag is successfully assigned but one sensitive application policy never checks the tag before permitting access. What corrective configuration or investigation is most appropriate?
Explanation
Correct Answer
Use the scoped intervention, bind the required compliant posture tag to the approved application access policy. The technical reason is that generating posture evidence is insufficient unless the consuming security rule enforces it. Verify that a noncompliant test device is denied the app even with valid identity credentials.
Incorrect Answers
The option would apply to “An employee changes from corporate LAN to public Wi-Fi and FortiClient does not switch to the intended off-net steering profile”. The corrective step is: Review on-net/off-net transition rules and test profile switching after network change. This question instead requires “Bind the required compliant posture tag to the approved application access policy”.
This shortcut is attractive but misses the underlying condition: Generating posture evidence is insufficient unless the consuming security rule enforces it. The case requires the targeted remedy: Bind the required compliant posture tag to the approved application access policy.
This option serves the scenario “A remote contractor uses an outdated FortiClient version that cannot apply a required current endpoint security setting”. The corrective step is: Plan an approved FortiClient update and test endpoint profile compatibility. The present scenario is distinguished by “Bind the required compliant posture tag to the approved application access policy”.