Core Answer: FortiGate firewall log analysis provides deep visibility into all network activities, including allowed/denied traffic, administrator access, VPN usage, and threat events, helping to detect and respond to potential security threats early. By checking logs via FortiGate's GUI and CLI and configuring Syslog remote logging, logs can be centrally collected into a SIEM for long-term storage, enabling the establishment of a comprehensive MDR and security monitoring system through sophisticated detection rules and MITRE ATT&CK mapping.
What Information Can Be Obtained from Firewall Logs
Firewalls are critical devices that monitor all traffic at the network's forefront and enforce security policies. Logs generated by firewalls such as FortiGate provide essential information for understanding various security events and trends occurring within the network, going beyond mere records. By analyzing these logs, the following key information can be obtained.
- Allowed and Denied Traffic: All communication records that have been allowed or denied according to network policies enable the distinction between normal service flow and abnormal access attempts. This is crucial for identifying potential attack attempts or detecting policy-violating traffic.
- Administrator Access Records: Records of administrators accessing the firewall device, including their accounts, time, and IP addresses, allow for the detection of unauthorized administrator access attempts or misuse by insiders. Repeated login failures may signal a Brute-Force attack.
- VPN Access Activity: Login and logout records of VPN users for remote access, success/failure status, used accounts, and source IP addresses can be checked to detect VPN account compromise or abnormal remote access.
- Threat Events: Various security threat events detected by UTM (Unified Threat Management) functions such as IPS (Intrusion Prevention System), AntiVirus, and Web Filtering, including malware, exploit attacks, and malicious website access, can be identified to plan immediate responses.
FortiGate Log Verification: GUI Menus and CLI
Logs generated by FortiGate firewalls play a crucial role in ensuring administrator visibility and troubleshooting. FortiGate supports the verification and management of various logs through both GUI (Graphical User Interface) and CLI (Command Line Interface). It is important to note that menu names or options may vary depending on the FortiOS version.
2.1. Log Verification and Configuration via GUI
After accessing the FortiGate administration GUI, various types of logs can typically be verified under the 'Log & Report' menu. Key log types include 'Forward Traffic' and 'System Events'. This menu allows for the visual understanding of important information such as network traffic flow, administrator activities, and system alerts.
Log settings are managed within the 'Log Settings' menu. Here, one can configure whether logs are stored internally on the FortiGate device (disk logging) or forwarded remotely to external systems such as FortiAnalyzer or a Syslog server. It is crucial to enable the necessary log types and adjust detailed logging levels to ensure that important security events are recorded without omission.
2.2. Log Verification via CLI
The CLI provides detailed log filtering and verification capabilities not available in the GUI, which is useful for quickly and accurately locating logs that meet specific conditions. The method for verifying logs in the FortiGate CLI may vary by version, but the following commands are generally utilized.
execute log filter category: This command sets filtering conditions based on log category. For example, logs can be filtered by traffic logs or event logs.execute log display: This command displays logs that match the filtering conditions on the screen.
By utilizing these CLI commands, logs can be precisely searched based on specific Source IP, Destination IP, policy ID, or time ranges, contributing to rapid analysis in the event of a security incident.
FortiGate Syslog Remote Logging Configuration
To centrally manage, long-term store, and deeply analyze FortiGate logs, configuring remote logging using Syslog is essential. This overcomes the storage limitations of FortiGate devices and enables correlation analysis and threat detection to be performed on external SIEM or log management systems.
FortiGate supports various log formats when configuring Syslog remote logging. Generally, one of the following formats can be selected.
- default: This is FortiGate's default log format, which is text-based and human-readable.
- csv: This is a Comma Separated Values format, which makes data parsing relatively easy.
- cef: Common Event Format is a standard log format developed by ArcSight, which is highly effective for automatically classifying and parsing log fields in various SIEM solutions. It is one of the most recommended formats for SIEM integration.
The following is an example of Syslog remote logging configuration using FortiGate CLI. Supported formats may vary depending on the FortiOS version.
config log syslogd setting
set status enable
set server "<수집 서버 IP>"
set port 514
set format default
end
In the example above, `set server` should be populated with the IP address of the SIEM or Syslog server that will collect the logs, and `set port` uses 514, which is the default Syslog port. For `set format`, one of the previously described formats can be selected. This configuration ensures that all important logs generated by FortiGate are transmitted to the specified external server in real-time.
FortiGate Log Retention Period
Log retention policies are essential not only for legal and regulatory compliance but also for forensic analysis and threat hunting in the event of potential security breaches. FortiGate provides two primary log storage methods: on-device disk logging and remote storage to external systems.
4.1. Comparison of Disk Logging and Remote Storage
- Disk Logging: This method stores logs using the FortiGate device's internal disk or storage. The `config log disk setting` command can be used to configure disk logging usage and retention options (e.g., `maximum-log-age` in days). However, some FortiGate models may not have a disk, and the internal storage space of the device is limited, thus presenting limitations for long-term retention. Additionally, there is a risk of log loss if the device itself experiences an issue.
- Remote Storage (Syslog/FortiAnalyzer): This method involves transmitting logs generated by FortiGate in real-time to external systems such as a Syslog server, FortiAnalyzer, or SIEM for storage. This offers the advantages of overcoming device storage capacity limitations, centrally managing logs, and securely preserving logs even in the event of device failure.
4.2. Long-Term Retention to External Collection Servers and SIEM
Access records for personal information processing systems must be retained for at least one year (and over two years for some systems) according to personal information security measures, and accident analysis often requires logs for an even longer period. To meet these long-term retention requirements and conduct in-depth analysis of advanced threats, it is advisable to transmit and store FortiGate logs on external collection servers or SIEMs.
External SIEMs efficiently collect, store, and index large volumes of logs, providing powerful search and correlation analysis capabilities. This allows for the discovery of compromise traces in logs from several months or even years ago, or the acquisition of information necessary to reconstruct the entire flow of a specific attack. Therefore, for long-term retention, it is recommended to utilize specialized log management systems or SIEMs rather than the internal FortiGate disk.
Methods for Verifying FortiGate Login Failures
Abnormal login attempts to FortiGate devices are highly likely to be Brute-Force Attacks aimed at administrator account compromise or unauthorized access attempts by insiders, making continuous monitoring essential. FortiGate records login failure events through 'System Events' logs.
By checking the 'System Events' log in the 'Log & Report' menu of the FortiGate GUI, events related to administrator login failures can be found. Additionally, login failure records can be queried by applying specific filters via the CLI. Login failure logs typically include the following information.
- Timestamp: Indicates when the login attempt occurred.
- Source IP: Crucial information indicating where the login attempt originated.
- Username: Shows which account the login attempt was made for.
- Result: Indicates failure through messages such as 'fail' or 'authentication failure'.
Detecting patterns where repeated login failures occur for a specific user account from multiple source IPs, or login failures occur for multiple user accounts from a specific source IP, is a key indicator for identifying Brute-Force attacks. These logs can be most effectively utilized when collected by a SIEM and detected in real-time through correlation rules.
Firewall Log Analysis Scenario Table
To effectively analyze FortiGate firewall logs and detect threats, it is crucial to understand common attack scenarios and their corresponding log signals. The following table presents key firewall log analysis scenarios, the signals that can be observed in each scenario, and recommended response measures.
| Scenario | Signals in Logs | Response |
|---|---|---|
| Spike in Deny Traffic | Abnormally high number of 'deny' logs from a specific source IP or destination IP. Large volume of denials for a specific port or protocol. | Detailed analysis of the affected IP/port/protocol. If deemed an attack, strengthen source IP blocking policies. Verify for DDoS attacks. |
| Abnormal Internal-to-External Port Communication | Internal systems attempting 'allow' or 'deny' traffic to unknown or non-standard external ports (e.g., C2 communication ports). | Identify and isolate infected internal systems. Block external IP suspected of being a C2 server. Analyze with endpoint EDR integration. |
| Repeated Administrator Login Failures | Repeated login failures for FortiGate administrator accounts from the same source IP. Attempts with multiple accounts. | Block the source IP. Change administrator account passwords and enforce MFA (Multi-Factor Authentication). |
| Abnormal VPN Access | VPN login attempts from unusual times, regions, or abnormal IPs. Repeated VPN account login failures. | Temporarily lock the account and verify the user. Block the source IP. Reset VPN account passwords and strengthen policies. |
SIEM Integration: Collection → Normalization → Sigma Rule Detection → MITRE ATT&CK Mapping
Integrating FortiGate logs with a SIEM is a crucial step that goes beyond simple log collection, enabling the detection of complex threats and efficient security monitoring. SIEM integration involves collecting and normalizing FortiGate logs into a format understandable by the SIEM, and then applying sophisticated detection rules based on this data to map them to the MITRE ATT&CK framework.
7.1. Collection and Normalization
When FortiGate transmits logs via Syslog, the SIEM collects these logs through a Collector or Agent. The raw logs collected are then separated and normalized by the SIEM's Parser into standardized fields (e.g., Source IP, Destination IP, Action, Protocol, Event Type, etc.). Utilizing standard formats like CEF (Common Event Format) at this stage allows the SIEM to parse logs more accurately and efficiently, thereby solidifying the analytical foundation.
7.2. Sigma Rule Detection and MITRE ATT&CK Mapping
Based on normalized logs, the SIEM applies various detection rules to identify threat events. Sigma rules are vendor-agnostic, generic detection rules used to share and apply threat detection scenarios across diverse security solutions. By applying Sigma rules to FortiGate logs, abnormal behaviors exceeding specific patterns or thresholds can be detected.
Furthermore, by mapping detected threat events to the Tactics and Techniques of the MITRE ATT&CK framework, the attacker's intent, tactics, and techniques used can be systematically understood, and the attack flow can be analyzed from an integrated perspective. This forms a crucial foundation for effective threat hunting and incident response strategy development.
The following is a simple Sigma rule example for detecting administrator login failures in FortiGate logs.
title: FortiGate Admin Login Failure Spike
id: abcdefgh-1234-5678-90ab-cdefghijkl
status: experimental
description: Detects a sudden increase in failed admin login attempts on FortiGate.
logsource:
product: fortigate
service: firewall
detection:
selection:
subtype: 'event'
action: 'authenticate'
status: 'fail'
msg|contains: 'User authentication failure'
timeframe: 5m
condition: selection | count() by srcip > 5
falsepositives:
- User typo errors
level: medium
tags:
- attack.t1110.003 # Brute Force: Password Spraying
The Flow of Detecting and Responding to FortiGate Syslog with KYRA MDR Collector
KYRA MDR is SeekersLab's AI-powered MDR (Managed Detection & Response) platform, which integrates SIEM, NDR, EASM, and SOAR into a single platform to provide 24/7 security monitoring. The flow for collecting FortiGate syslog with KYRA MDR Collector to detect and respond to threats is as follows.
First, FortiGate transmits logs such as network traffic, system events, and threat events to the KYRA MDR Collector via Syslog. The KYRA MDR Collector is responsible for collecting logs from various sources, including firewalls, servers, and clouds, via Syslog or files. It can be easily installed with a single command in a Linux environment.
The collected FortiGate logs are then forwarded to the KYRA MDR platform and analyzed by its detection engine. KYRA MDR utilizes over 3,200 Sigma rule engines to detect various attack scenarios. Detected events are mapped to the MITRE ATT&CK framework's 14 tactics and over 200 techniques, helping to understand the full context of an attack. Furthermore, detection accuracy is enhanced through behavioral analysis, multi-stage attack correlation analysis, and threat intelligence IOC (Indicator of Compromise) enrichment.
When a threat is detected, KYRA MDR's AI capabilities, based on Large Language Models (LLM), classify alerts and provide analytical summaries, reducing the initial triage time for security analysts. Critical judgments undergo final review by human analysts through a HITL (Human-In-The-Loop) structure, which minimizes false positives and ensures accurate decisions.
For detected threats, automated responses are executed based on SOAR (Security Orchestration, Automation, and Response) playbooks. This includes host isolation, blocking actions, and supports rapid and efficient incident response through investigation workflows. In this manner, KYRA MDR integrates diverse security data, including FortiGate logs, to provide comprehensive security monitoring services from threat detection to response.
Frequently Asked Questions
Q1. What is the primary reason for sending FortiGate logs to a SIEM?
A1. The primary reasons for sending FortiGate logs to a SIEM are for centralized log management, long-term retention, and the detection of complex threats through correlation analysis across logs from various sources. A SIEM plays an essential role in efficiently processing large volumes of logs, automating reports for regulatory compliance (e.g., ISMS-P), and enhancing real-time threat monitoring and response.
Q2. Which log format is best to choose when transmitting FortiGate Syslog?
A2. The most recommended log format for FortiGate Syslog transmission is CEF (Common Event Format). CEF is a standardized format highly effective for automatically parsing and classifying log fields across various SIEM solutions. This enables SIEMs to analyze FortiGate logs more accurately and efficiently.
Q3. How should the FortiGate log retention period be determined?
A3. The FortiGate log retention period should be determined by comprehensively considering legal and regulatory requirements of the industry (e.g., personal information access records must be retained for at least one year, and over two years for some systems), internal security policies, and anticipated threat hunting and incident analysis cycles. For long-term retention, it is generally more efficient to utilize external SIEMs or log management systems rather than the FortiGate's internal disk.
Q4. Can SIEM integration affect the performance of FortiGate devices?
A4. Transmitting logs via Syslog can impose a slight load on the FortiGate device's CPU and network bandwidth. However, FortiGate is designed with optimized log transmission capabilities, so the impact is typically minimal in normal environments. In environments with a large volume of logs, settings such as Syslog transmission rate limits (`max-log-rate`) can be reviewed to manage the load.
Q5. How does KYRA MDR assist with security monitoring through FortiGate log analysis?
A5. KYRA MDR efficiently collects FortiGate Syslog and analyzes it on a platform that integrates SIEM, NDR, EASM, and SOAR functionalities. This enables sophisticated detection of FortiGate logs based on Sigma rules, mapping to MITRE ATT&CK to understand attack tactics, and significantly enhances the efficiency of security monitoring operations and threat response speed through AI-based alert classification and SOAR playbooks for automated response.
Related Articles
- What is MDR? Differences from Security Monitoring and MDR Service Selection Criteria
- How SMEs Can Start Security Monitoring and Cost Structure
- ISMS-P Obligation Scope and Access Record Management
- MDR Threat Detection Based on Apache Logs
- What is SIEM? The Difference Between SIEM and SOAR
- Seekurity SIEM
Start Security Monitoring with KYRA MDR
Experience next-generation MDR and security monitoring services beyond FortiGate log analysis immediately. KYRA MDR is an AI-powered integrated platform that provides 24/7 threat detection and response, elevating your organization's security capabilities. Discover advanced security monitoring services with an easy start.







