In this video, you will learn how to enforce a FortiClient Profile on an internal network so that only internal devices registered with FortiClient can access the Internet and the corporate network. You will enable FortiHeartBeat on an interface to enforce FortiClient registration, edit the default FortiClient Profile to enforce realtime antivirus protection and malicious website blocking, and register FortiClient with your FortiGate.
This recipe was tested using FortiClient version 5.4 and FortiOS (FOS) version 5.4.
There was a change in the FortiClient security profile from FOS 5.4 to FOS 5.4.1. The VPN, Advanced and Mobile tabs do not appear in FOS versions 5.4.1 and above. Features emphasizing compliance of the endpoint devices have been added. These enhancements facilitate integration with the Cooperative Security Fabric (called “Security Fabric” in FOS 5.6). Read more in the What’s New for Security Profiles 5.4.1.
The recipe for this video is available here.
Latest posts by Adam Bristow (see all)
- FortiAuthenticator user self-registration - November 9, 2017
- Fortinet Support Portal Authentication Process Change FAQ - October 1, 2017
- SAML FSSO with FortiAuthenticator and Okta - June 15, 2017