|
Description |
This article describes how to use a custom event handler in FortiAnalyzer to raise alerts for incident responses related to attacks that attempt to leverage the BURNTCIGAR Microsoft Signed driver malware. A report is also provided to gain historical visibility into logs.
Note that this article provides alpha files which are automatically generated. The article will be continually updated as more information becomes available. |
|
Scope |
This article contains the files necessary to load an event handler and report into FortiAnalyzer for either a Fabric ADOM or a FortiGate ADOM. The Fabric report and event handler leverage logs from other Fortinet products that can be used to detect the attack when cross-referenced with FortiGate logs. For more information about this attack, see the following FortiGuard Outbreak Alert: https://www.fortiguard.com/outbreak-alert/burntcigar-malware |
|
Solution |
What is included in Fortinet_BURNTCIGAR_malware.zip?
1) BURNTCIGAR_malware_event-handler.json This event handler helps identify Microsoft Signed driver malware detected by FortiGates and other Fortinet products.
2) BURNTCIGAR_malware_report.dat This report displays the findings on Microsoft Signed driver malware attacks from FortiGates and other Fortinet products.
3) fgt_BURNTCIGAR_malware_event-handler.json The event handler for FortiGate ADOMs is configured for FortiGate logs only.
4) fgt_BURNTCIGAR_malware_report.dat The report for FortiGate ADOMs includes FortiGate charts only.
Steps
1) Download the Fortinet_BURNTCIGAR_malware.zip file (contains 4 files).
2) Unzip Fortinet_BURNTCIGAR_malware.zip.
3) Import BURNTCIGAR_malware_event-handler.json or the fgt_BURNTCIGAR_malware_event-handler.json event handler:
- Choose an ADOM (if ADOMs are enabled). The ADOM type may be Fabric or FortiGate: - Choose the FortiSOC module. - Select Event Handler List. - Select the Import option under More. - Select the appropriate event handler depending on the ADOM type.
Result: The event handler is enabled and will be triggered if the appropriate logs are received, following the import of the event handler. Edit the event handler to customize the notification section.
4) Import BURNTCIGAR_malware_report.dat or fgt_ BURNTCIGAR_malware_report.dat to Reports:
- Choose an ADOM (if ADOMs are enabled). ADOM may be of type Fabric or FortiGate. - Select the appropriate file for the ADOM type to add the report to the ADOM.
Result: The BURNTCIGAR_malware_report can be run at any time as determined by an admin user. |
