TL;DR
| Supported data types | 3rd party detection | Hunters detection | IOC search | Search | Table name | Log format | Collection method |
|---|---|---|---|---|---|---|---|
| Fortinet FortiSandbox Logs | ✅ | ✅ | fortinet_fortisandbox | Syslog (key=value) | S3 |
Overview
Fortinet FortiSandbox is a sandboxing appliance (hardware, VM or cloud) that receives suspicious files and URLs from FortiGate, FortiMail, FortiClient and other sources, runs them in isolated virtual machines and gives each job a risk rating. Its logs record every scan job and its verdict, network alerts raised by its sniffer (attacks, botnet traffic and malicious URLs), and system events such as administrator logins, configuration changes and resource usage. In Hunters you can search these logs, and IOC search matches their IP addresses, host names, URLs and file hashes (MD5, SHA-1, SHA-256) against threat intelligence.
Supported data types
Fortinet FortiSandbox Logs
Table name: fortinet_fortisandbox
All FortiSandbox log types land in this table:
- malware: one record per scan job, with the file name and type, MD5/SHA-1/SHA-256, risk rating, malware name and category, the submitting device, and the email or network context of the file.
- netalert (netattack, netbotnet, neturl): network alerts with source and destination IP and port, attack ID and name, botnet name or URL.
- event: system, administration, job, report and resource events (for example administrator logins, configuration changes, CPU, memory and disk usage).
event_time is converted to UTC from the device-local date and time fields, using the tzone offset (in seconds) that FortiSandbox adds to every record.
Expected format
Logs are expected as syslog lines, exactly as FortiSandbox sends them: a syslog header (<priority>timestamp host) followed by space-separated key=value fields. Values that contain spaces are quoted. One record per line.
<25>2026-07-28T10:15:22+02:00 10.116.234.192 devhost=hostname-2d1e269f devid=hostname-2d1e269f logver=25 tzone=7200 tz=CEST date=2026-07-28 time=10:15:22 logid=1015000205 type=malware subtype=malware level=alert jobid=8336128171580856702 scanstart=1785226521 scanend=1785226522 srcip=10.158.183.57 srcport=1 dstip=10.3.180.39 dstport=1 subtime=1785226521 ftype="pdf" rsrc="Customized Rating" emailsndr=user-fc9a5ac6@example.com emailrcvr=user-3be69f93@example.com subject="Invoice INV-000001" md5=9b44bfb536877b24bb64d6638f3caa6a sha1=7c1582a63f30c81ac020b45eff103de9f06a9de6 sha256=c0af65b80c6addfdc7f73043fb10e10f18b1d493ae8dd964c515334349f32d33 jstatus="Done" risk="Low Risk" mname="N/A" mcate="NotApplicable" fname="Invoice_000001.pdf" proto=TCP suser="user-e4b56d7e" stype="Device" clientdev="hostname-003d401d" clientname="hostname-deef7f71" clientvd="hostname-a379a6f6" url="Invoice_000001.pdf"
Send data to Hunters
Hunters supports the collection of Fortinet FortiSandbox logs using Amazon S3. FortiSandbox sends its logs over syslog, so you need a syslog collector (for example syslog-ng or Fluentd) that receives them and writes them to an S3 bucket.
To connect Fortinet FortiSandbox logs:
- In the FortiSandbox GUI, go to Log & Report > Log Servers and click Create New.
- Set Type to syslog, enter your collector's IP address or FQDN in Log Server Address, and set the Port your collector listens on (the default is 514). Set Status to enabled.
- Under Log Level, select the logs to forward. Enable Alert logs for scan verdicts and network alerts. By default FortiSandbox sends alert logs only for jobs that are not rated Clean; select Include job with Clean Rating to send those as well. Enable the event levels you want (Critical, Error, Warning, Information). Click OK. See Log Servers in the Fortinet documentation.
- Configure the collector to write each received line unchanged, including the syslog header, one record per line, into files with a suffix such as
.logor.txtin your S3 bucket. Keep files under 50 MB compressed. - Once the logs are in S3, follow the steps in this section to connect the bucket to Hunters.
For the full list of FortiSandbox log types and fields, see the FortiSandbox Log Message Reference.