Configuring FortiGate Intrusion Prevention via FortiManager

First step is to create the IPS Security Profile within Policy & Objects -> Object Configurations -> Security Profiles -> Intrusion Prevention.  The policy created below is a copy of the default IPS profile.  Let's go through each of the options.  

FortiManager IPS Profile



There are no specific IPS Signatures enabled for this profile.  Instead, an IPS filter is set for medium, high, and critical severity levels.  These signatures and associated severity levels are published via FortiGuard.  The Action is also set to Default which takes an action (block or pass) based on FortiGuard's recommendation.  If the particular signature has a high probability for false positives, it may be set to pass, for example.  

Be sure to keep an active FortiGuard subscription for IPS on your FortiGate!  Without this subscription, the FortiGate will not have the latest IPS signatures and, with how fast cybersecurity threats evolve, will not be effective as an IPS solution.  No reason to have the performance impact of IPS scanning with an old IPS signature database.

Once the IPS Security Profile is created, the next step is to apply the IPS profile to the relevant security policies.  Navigate to Policy & Objects -> Policy Packages and edit a Policy Package.  Within the Policy Package, edit the rules which you would like IPS applied to.  Select the new profile created above as the IPS profile for those rules.  Next follow the standard Installation Wizard on FortiManager to push these changes to the managed FortiGates.  

-A

Comments

Post a Comment

Popular posts from this blog

Fix Cisco ISE Messaging Service

Cisco Identity Services Engine 2.6 introduced the concept of the ISE Messaging Service as an encrypted, lightweight protocol to replace syslog communication between the ISE nodes for logging purposes.  The ISE Messaging Services runs over TCP/8671.  In 2.6 Patch 2 and later, the Cisco ISE Messaging Service is enabled by default.   The overall implementation of the ISE Messaging Service has been buggy (but has gotten much better in recent versions) in both new ISE builds and upgrades.  One solution is simply to disable the ISE Messaging Service within Administration > System > Logging.  But then the ISE logging traffic isn't encrypted and the legacy syslog delivery method is not as efficient as the ISE Messaging Service so we will focus the rest of this article on how to identity and fix the ISE Messaging Service. Problem Identification Usually problems with the ISE Messaging Service involve a blank Live Logs page.  You know authentication is...
Read more

ClearPass MPSK per Device Type with Profiling

Image
Multiple Pre-Shared Key or MPSK helps solve for IOT or other endpoint device types that are not 802.1X capable.  The Aruba ClearPass default implementation of MPSK (the configuration created by the wizard) requires manually registering, enrolling, and managing individual PSK keys per endpoint using the ClearPass Guest dashboard.  While the most secure approach, excluding any sort of API based automation, this can obviously be a nightmare to manage and support due to the sheer number of PSKs.  This approach instead delivers a unique PSK per device type (printer, thermostat, etc.) so that each flavor of endpoint would have its own PSK.  If one PSK was compromised, then only those endpoints would need to be manually re-configured.  PSK rotation would also be limited to only those specific device types allowing rotation to take place slowly over several weeks rather than all devices at the same time on the SSID with a traditional single PSK; lessoning the burde...
Read more

Cisco Designated VIP 2024

I'm pleased  to announce that I have been recognized as a Cisco Community Designated VIP for 2024 for my assistance in the Cisco Secure Network Access Control community focusing on Identity Services Engine.  Be sure to check out all of the   Cisco Community Designated VIPs .
Read more