Fortigate Correlation rules thread

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Fortigate Correlation rules thread

L4 Transporter

Hi All,

With Fortigate FW logs ingesting into XSIAM, even with the forti content pack installed, there is no real method for detection apart from the analytics engine that will use the '3rd party firewalls' analytic rules to natively detect issues/alerts on Fortigate FWs that i am aware off..

 

As such one will be required to do additional correlation rules for extra detection.

Has anyone done these and willing to share the XQL content of these rules you have created?

I am in the process to design my own and have a number of use cases i want to build out like the following:

Possible Data Exfiltration
Exploit Public Facing
Deserialization Vulnerability
BotC2-Allow
Malicious network traffic from LAN to WAN
Compromised Host
Unwanted or malicious applications detected
Admin Failure
SSL login failure followed by successful

will share once they are tested.

rgds

2 REPLIES 2

L1 Bithead

Are you ingesting data directly from the Fortigate FWs or are you ingesting the firewall data from the FortiAnalyzer?

We have both direct from FW > broker-VM  and also via FW > FortiAnalyzer > Broker-VM

 

  • 219 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!