Description This article describe how to use events and audit logs in
cases when a new issue arises on an existing setup that was previously
working normally. This also applies for an intermittent issue that
appear at specific time only. Scope FortiN...
Description This article describes that in authentications that include
MSCHAPv2, the Winbind tool needs to be configured and FortiNAC must be
joined to the domain for the authentications to succeed. Scope FortiNAC,
Windows Server AD. Solution In lat...
Description This article describes that since the product FortiNAC
Analytics Reporting is discontinued, FortiAnalyzer is recommended as a
reporting platform. These details are covered in the Administration
guide. Scope FortiNAC, FortiAnalyzer. Soluti...
Description This article describes that in FortiNAC integrations with
Meraki switches (cloud-managed) some RADIUS reauthentication may happen
randomly. This will disrupt the connection in the end hosts (a few
seconds between the re-authentication). S...
Description This article describes the configuration steps and some
troubleshooting commands used when integrating FortiClient EMS with
FortiNAC as a Service Connector. Scope FortiNAC. Solution Create the key
store (.keystore) in the user path (/home...
Based on your description, this setup is configured to do Device
Profiling with "Rule Confirmation Settings" checked. The point of
enabling "Confirm Device Rule on Connect" is to deregister the host as
soon as it is not compliant. Configuring a delay...
You don't have to use custom Actions. You will just need a Policy to
point to a Configuration and a Scan. Based on scan results the host
status will change to At-risk (+ sign) or normal. If the host is at risk
and the Remediation is enforced the host...