Description
This article describes the options in FortiNAC endpoint compliance configuration that allows administrators to Restrict Host connections to only whitelisted SSIDs/APs and additionally check for Dual Homes connections when there are multiple connected adapters on the same host.
Scope
FortiNAC.
Solution
- Restrict Wireless Connections to Specific SSIDs.
Go to Policy&Object -> Endpoint Compliance -> Configuration.
When a host matches an Endpoint compliance policy where the configuration has the option 'Restrict Wireless Connections to Specific SSIDs' enabled, FortiNAC will check if the host is connected to an SSID/AP specified in the Group of allowed SSIDs and access points.
SSID information can be collected from sources such as the persistent agent or Device Profiler methods. This is the information that FortiNAC uses to compare against the Whitelisted SSID/AP group.
If the SSID/AP where they are connected is not part of this group, an event 'Adapter connected to a disallowed SSID' will be generated and an alarm created. This alarm sets a failure for a pre-created 'SSID-Check-Violation' admin scan and marks the host at risk.
When the host is marked at risk, FortiNAC applies State-based control, which will remediate the host irrelevant of the Network access policy they match.
To validate and check the admin scans, go to Policy&Objects -> Remediation Configuration.
The purpose of admin scans is to mark hosts at risk when they fail a scan and present to them a specific page informing users of remediation actions. The portal page is defined within the Admin scan.
In such cases, when a connection is detected to a disallowed SSI,D the Host will be marked at risk.
Disconnecting from that SSID and re-validation of the compliance policy will mark the host 'Safe' again.
The alarm mapping to the Trigger Event 'Adapter Connected to a Disallowed SSID' can be modified in Logs -> Event&Alarms -> Mappings.
Administrators can modify the settings depending on need or add additional tasks to be performed after the Primary one.
- Detect Multihoming.
This feature will detect multiple-connected adapters and generate a 'Multihomed Host Detected' event and Alarm.
If the host has an online wired adapter and the user connects additionally to wireless, they will be detected and marked at risk.
The alarm actions are by default configured to mark at risk for a 'Multihome-Detected' admin scan. The host will need to have only one connection (online adapter) in order to be marked Safe and get production access through Network Access policies. It is also possible to take Host Access actions, such as disabling the host when multihome is detected.
The 'Multihomed Host Detected' event to alarm mapping can be edited the same as in the previous example in Logs -> Event&Alarms -> Mappings.
When a host is disabled, FortiNAC will change the VLAN of the port where the host is connected to the 'Dead-End' VLAN.
The article below describes how to enforce 'Dead-End':
Technical Tip: Configuring Dead End as Enforcement
Related document:
