index
int64 0
4.08k
| text
stringlengths 34
4.9k
⌀ | url
stringclasses 38
values |
|---|---|---|
3,855
|
Log and Report
When viewing event logs in the Logs tab, use the event log subtype dropdown list on the to navigate between event log
types.
System Events Always available.
Router Events Always available.
VPN Events Available when VPN is enabled in System > Feature Visibility.
SD-WAN Events Always available.
User Events Always available.
FortiOS 7.6.2 Administration Guide 3856
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,856
|
Log and Report
Endpoint Events Available when Endpoint Control is enabled in System > Feature Visibility.
HA Events Always available.
Security Rating Events Always available, but logs are only generated when a Surface Attack Security
Rating License is registered.
WAN Opt. & Cache Events Available on devices with two hard disks by default. On devices with one hard
disk, the disk usage must be set to wanopt and then WAN Opt. & Cache must be
enabled in System > Feature Visibility.
WiFi Events Available on hardware devices when WiFi Controller is enabled in System >
Feature Visibility.
FortiExtender Events Available when FortiExtender is enabled in System > Feature Visibility.
SDN Connector Events Always available.
FortiSwitch Events Available when Switch Controller is enabled in System > Feature Visibility.
CIFS Events Always available.
REST API Events Always available.
Logs can be filtered by date and time in the Log & Report > System Events page. The log viewer can be filtered with a
custom range or with specific time frames.
UTM logs can also be filtered by date and time in Log & Report > Security Events. See
Security Events log page on page 3863.
The time frame available is dependent on the source:
l Logs sourced from FortiAnalyzer, FortiGate Cloud, and FortiAnalyzer Cloud have the same time frame options as
FortiView (5 minutes, 1 hour, 24 hours, or 7 days).
l Logs sourced from the Disk have the time frame options of 5 minutes, 1 hour, 24 hours, 7 days, or None.
l Logs source from Memory do not have time frame filters.
A custom time frame can be applied using the Date/Time filter. If the Date/Time filter is applied, the time frame will be
disabled and set to custom.
FortiOS 7.6.2 Administration Guide 3857
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,857
|
Log and Report
Time frame settings for each Log & Report page are independent of each other. For example,
if you change the time frame on the System Events page, the time frame will be different than
that of the Security Events page unless it is also changed to match.
System Events log page
The Log & Report > System Events page includes:
l A Summary tab that displays the top five most frequent events in each type of event log and a line chart to show
aggregated events by each severity level. Clicking on a peak in the line chart will display the specific event count for
the selected severity level.
l A Logs tab that displays individual, detailed log views for event type.
The Summary tab includes the following:
l Event list footers show a count of the events that relate to the type.
l A count of the total events is shown at the top of the Summary. Hovering over the count shows the number of events
with a time stamp.
FortiOS 7.6.2 Administration Guide 3858
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,858
|
Log and Report
l Hovering over the Total Events By Level shows the shows the number of events with a time stamp.
l Clicking on any event type title opens the Logs page for that event type filtered by the selected time span.
For example, clicking VPN Events opens the following page:
l Clicking on any event entry opens the Logs page for that event type filtered by the selected time span and log
description.
For example, in the General System Events box, clicking Admin logout successful opens the following page:
FortiOS 7.6.2 Administration Guide 3859
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,859
|
Log and Report
Disk logging and historical FortiView must be enabled for the Summary tab to display valid
data. See Log settings and targets on page 3870 for more information.
A FortiOS Event Log trigger can be created using the shortcut on any Logs tab. Select a log,
then right-click and select Create Automation Trigger. See System Events page shortcut on
page 3634 for more information.
A time frame can be selected from the dropdown.
The line chart will display all of the system events, and the non-empty event cards will list up to five Top Event entries
within the time frame set.
Data is retrieved from FortiView with the 5 minutes range updated first. When selecting either
the 1 hour or 24 hours time range, there may be a delay to update Top Event entries.
Up to 100 Top Event entries can be listed in the CLI using the diagnose fortiview result event-log
command.
To view filtered log information:
1. Go to Log & Report > System Events.
2. Select the Logs tab.
FortiOS 7.6.2 Administration Guide 3860
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,860
|
Log and Report
3. Hover over the leftmost column and click the gear icon. A list of column you can filter is displayed.
4. Select the columns you want displayed.
5. Click Apply. The selected columns are displayed.
6. Click the filter icon for the column you want to filter. The filter dialog is displayed and the number of logs for each
filter type is listed.
7. Select the filters you want and click Apply. The logs that match the set filters are displayed and the filter is listed in
the search bar.
8. Select the log you want to see more information on.
9. Click Details. The Log Details pane is displayed.
FortiOS 7.6.2 Administration Guide 3861
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,861
|
Log and Report
To list system events in the CLI:
# diagnose fortiview result event-log
data(1646760000-1646846401):
0). subtype-ha | eventname-HA device interface failed | level-warning | count-1 |
1). subtype-system | eventname-DHCP statistics | level-information | count-40 |
2). subtype-system | eventname-Super admin left VDOM | level-information | count-13 |
3). subtype-system | eventname-Admin performed an action from GUI | level-warning |
count-5 |
4). subtype-system | eventname-Super admin entered VDOM | level-information | count-4 |
5). subtype-system | eventname-Global setting changed | level-notice | count-3 |
6). subtype-system | eventname-Attribute configured | level-information | count-2 |
7). subtype-system | eventname-Clear active sessions | level-warning | count-2 |
8). subtype-system | eventname-Disk log rolled | level-notice | count-2 |
9). subtype-system | eventname-Log rotation requested by FortiCron | level-notice |
count-1 |
10). subtype-system | eventname-Report generated successfully | level-notice | count-1 |
11). subtype-system | eventname-Test | level-warning | count-1 |
12). subtype-system | eventname-VDOM added | level-notice | count-1 |
13). subtype-user | eventname-Authentication failed | level-notice | count-1 |
14). subtype-user | eventname-Authentication lockout | level-warning | count-1 |
15). subtype-user | eventname-FortiGuard override failed | level-warning | count-1 |
The data is collected from FortiView for the last 24 hours by default. To specify a specific time range, customize the time
filter using the diagnose fortiview time command.
To filter the time range of system events in the CLI:
# diagnose fortiview time <arg1> <arg2>
Where <arg1> is the start time in YYYY-MM-DD HH:MM:SS and <arg2> is the end time in YYYY-MM-DD HH:MM:SS.
FortiOS 7.6.2 Administration Guide 3862
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,862
|
Log and Report
Security Events log page
The Log & Report > Security Events log page includes:
l A Summary tab that displays the five most frequent events for all of the enabled UTM security events.
l A Logs tab that displays individual, detailed logs for each UTM type.
The Summary tab includes the following:
l Event list footers show a count of the events that relate to the type.
l A count of the total events is shown at the top of the Summary. Hovering over the count shows the number of events
with a time stamp.
l Clicking on any event type title opens the Logs page for that event type filtered by the selected time span.
For example, clicking Application Control opens the following page:
The security event type can be changed in the top-right dropdown list.
FortiOS 7.6.2 Administration Guide 3863
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,863
|
Log and Report
l Clicking on any event entry opens the Logs page for that event type filtered by the selected time span and log
description.
For example, in the Application Control box, clicking Network.Service opens the following page:
Disk logging and historical FortiView must be enabled for the Summary tab to display valid
data. See Log settings and targets on page 3870 for more information.
A time frame can be selected from the dropdown.
FortiOS 7.6.2 Administration Guide 3864
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,864
|
Log and Report
The non-empty security event cards will list up to five top entries within the time range set.
Data is retrieved from FortiView with the 5 minutes range updated first. When selecting either
the 1 hour or 24 hours time range, there may be a delay to update top security event entries.
Logs sourced from the Disk have different time frames available for filtering. See Viewing
event logs on page 3855.
Up to 100 top security event entries can be listed in the CLI using the diagnose fortiview result securitylog command.
To list security events in the CLI:
# diagnose fortiview result security-log [<filters>]
To list security events in the CLI with no filters applied:
# diagnose fortiview result security-log
data(1646862300-1646948701):
0). logcat-2 | logcatname-virus | logid-0211008192 | eventname-EICAR_TEST_FILE |
eventname_field-virus | action-blocked | count-1 |
1). logcat-2 | logcatname-virus | logid-0211008192 | eventname-virus_test3 | eventname_
field-virus | action-passthrough | count-1 |
2). logcat-2 | logcatname-virus | logid-0212008448 | eventname-filename | eventname_
field-virus | action-passthrough | count-1 |
3). logcat-3 | logcatname-webfilter | logid-0318012800 | eventname- | eventname_fieldcatdesc | action-blocked | count-2 |
4). logcat-3 | logcatname-webfilter | logid-0316013056 | eventname-Information
Technology | eventname_field-catdesc | action-blocked | count-1 |
5). logcat-3 | logcatname-webfilter | logid-0316013056 | eventname-Malicious Websites |
eventname_field-catdesc | action-blocked | count-1 |
6). logcat-4 | logcatname-ips | logid-0419016384 | eventname-Eicar.Virus.Test.File |
eventname_field-attack | action-dropped | count-3 |
7). logcat-4 | logcatname-ips | logid-0422016400 | eventname-test_botnet | eventname_
field-attack | action-detected | count-1 |
8). logcat-7 | logcatname-anomaly | logid-0720018432 | eventname-tcp_syn_flood |
eventname_field-attack | action-clear_session | count-1 |
9). logcat-10 | logcatname-app-ctrl | logid-1059028704 | eventname-Storage.Backup |
eventname_field-appcat | action-pass | count-9 |
10). logcat-10 | logcatname-app-ctrl | logid-1059028704 | eventname-Video/Audio |
eventname_field-appcat | action-pass | count-3 |
11). logcat-10 | logcatname-app-ctrl | logid-1059028672 | eventname-im | eventname_
field-appcat | action-pass | count-1 |
12). logcat-10 | logcatname-app-ctrl | logid-1059028704 | eventname-P2P | eventname_
field-appcat | action-pass | count-1 |
13). logcat-15 | logcatname-dns | logid-1501054400 | eventname-Domain blocked because it
is in the domain-filter list | eventname_field-logid | action-block | count-1 |
14). logcat-17 | logcatname-ssl | logid-1700062300 | eventname-SSL connection is blocked
due to the server certificate is blocklisted | eventname_field-logid | action-blocked |
count-1 |
15). logcat-16 | logcatname-ssh | logid-1600061002 | eventname-SSH shell command is
detected | eventname_field-logid | action-passthrough | count-1 |
16). logcat-16 | logcatname-ssh | logid-1601061010 | eventname-SSH channel is blocked |
eventname_field-logid | action-blocked | count-1 |
FortiOS 7.6.2 Administration Guide 3865
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,865
|
Log and Report
17). logcat-12 | logcatname-waf | logid-1200030248 | eventname-Web application firewall
blocked application by signature | eventname_field-logid | action-blocked | count-1 |
18). logcat-8 | logcatname-voip | logid-0814044032 | eventname-Logid_44032 | eventname_
field-logid | action-permit | count-1 |
19). logcat-5 | logcatname-emailfilter | logid-0513020480 | eventname-SPAM notification
| eventname_field-logid | action-blocked | count-1 |
To list blocked security events in the CLI:
# diagnose fortiview result security-log action=blocked
data(1646862600-1646949001):
0). logcat-2 | logcatname-virus | logid-0211008192 | eventname-EICAR_TEST_FILE |
eventname_field-virus | action-blocked | count-1 |
1). logcat-3 | logcatname-webfilter | logid-0318012800 | eventname- | eventname_fieldcatdesc | action-blocked | count-2 |
2). logcat-3 | logcatname-webfilter | logid-0316013056 | eventname-Information
Technology | eventname_field-catdesc | action-blocked | count-1 |
3). logcat-3 | logcatname-webfilter | logid-0316013056 | eventname-Malicious Websites |
eventname_field-catdesc | action-blocked | count-1 |
4). logcat-17 | logcatname-ssl | logid-1700062300 | eventname-SSL connection is blocked
due to the server certificate is blocklisted | eventname_field-logid | action-blocked |
count-1 |
5). logcat-16 | logcatname-ssh | logid-1601061010 | eventname-SSH channel is blocked |
eventname_field-logid | action-blocked | count-1 |
6). logcat-12 | logcatname-waf | logid-1200030248 | eventname-Web application firewall
blocked application by signature | eventname_field-logid | action-blocked | count-1 |
7). logcat-5 | logcatname-emailfilter | logid-0513020480 | eventname-SPAM notification |
eventname_field-logid | action-blocked | count-1 |
Reports page
The Log & Report > Reports page consolidates FortiAnalyzer, FortiGate Cloud, and Local log reports. Administrators
can generate, delete, and edit report schedules, and view and download generated reports. The Reports page is
organized into dedicated tabs:
l FortiAnalyzer on page 3866
l FortiGate Cloud on page 3868
l Local on page 3869
FortiAnalyzer
FortiAnalyzer reports can be viewed in the FortiAnalyzer tab.
FortiAnalyzer must be configured in FortiOS. If the FortiGate is unauthorized on
FortiAnalyzer, or the connection to FortiAnalyzer is down, the FortiAnalyzer tab loads with No
results.
FortiOS 7.6.2 Administration Guide 3866
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,866
|
Log and Report
When the Security Fabric is enabled, only the root FortiGate can run, edit, and delete FortiAnalyzer reports. Downstream
FortiGates can only view the generated reports.
To edit a report schedule:
1. Go to Log & Report > Reports and select the FortiAnalyzer tab.
2. Select Scheduled.
3. Select a report and click Edit Schedule. The Edit Schedule pane opens. In this example, the schedule for the
Bandwidth and Applications report is changed to run from every week to every two weeks.
4. In the Schedule section, set the values for Generate report every to 2 week(s).
5. Click OK.
The schedule is also updated automatically in FortiAnalyzer for the same report (go to Reports > Report Definitions
> All Reports and edit the report to view the settings).
FortiOS 7.6.2 Administration Guide 3867
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,867
|
Log and Report
To view and download reports:
1. Go to Log & Report > Reports and select the FortiAnalyzer tab.
A pie chart displays the total count of FortiAnalyzer reports, categorized by report title. Generated reports are listed
below and arranged by title, which includes reports from all VDOMs.
2. In the pie chart, click the a segment to filter reports.
3. In the filtered results, select the report. Right-click and select Download.
4. Select a file format. The report is saved to the default download location.
FortiGate Cloud
Reports can be viewed and downloaded from the FortiGate Cloud tab. Select Refresh to regenerate the available
reports.
To download a report:
1. Go to Log & Report > Reports and select the FortiGate Cloud tab.
2. Select the report.
3. Click Download. The report is saved to the default download location.
FortiOS 7.6.2 Administration Guide 3868
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,868
|
Log and Report
To view a report:
1. Go to Log & Report > Reports and select the FortiGate Cloud tab.
2. Select the report.
3. Click View. The report is displayed.
You can launch the FortiGate Cloud portal from the FortiGate Cloud tab.
To launch the FortiGate Cloud portal:
1. Go to Log & Report > Reports and select the FortiGate Cloud tab.
2. Select Launch Portal. The FortiGate Cloud landing page opens.
Local
Reports can be generated, scheduled, viewed, and downloaded in the Local tab.
To generate a report:
1. Go to Log & Report > Reports and select the Local tab.
2. Select Generate Now. The Confirm pane opens.
3. Click OK.
To view a report:
1. Go to Log & Report > Reports and select the Local tab.
2. Select the report.
3. Click View. The report is displayed.
To download a report:
1. Go to Log & Report > Reports and select the Local tab.
2. Select the report.
3. Click Download. The report is saved to the default download location.
To schedule reports:
1. Go to Log & Report > Reports and select the Local tab.
2. Click Report Schedule. The Report Schedule pane opens.
FortiOS 7.6.2 Administration Guide 3869
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,869
|
Log and Report
3. Set the schedule details.
4. Click OK.
Log settings and targets
Log settings determine what information is recorded in logs, where the logs are stored, and how often storage occurs.
Log settings can be configured in the GUI and CLI. In the GUI, Log & Report > Log Settings provides the settings for local
and remote logging.
Log & Report > Log Settings is organized into tabs:
l Global Settings on page 3870
l Local Logs on page 3871
l Threat Weight on page 3872
Global Settings
Settings available in the Global Settings tab include:
UUIDs in Traffic Log
Policy Define the use of policy UUIDs in traffic logs:
l Enable: Policy UUIDs are stored in traffic logs. UUIDs can be matched for
each source and destination that match a policy in the traffic log. See Source
and destination UUID logging on page 3889 for more information.
l Disable: Policy UUIDs are excluded from the traffic logs.
Address Define the use of address UUIDs in traffic logs:
l Enable: Address UUIDs are stored in traffic logs. When viewing Forward
Traffic logs, a filter is automatically set based on UUID.
l Disable: Address UUIDs are excluded from traffic logs.
Log Settings
Event Logging Define the allowed set of event logs to be recorded:
l All: All event logs will be recorded.
l Customize: Select specific event log types to be recorded. Deselect all
options to disable event logging.
Local Traffic
Logging
Define the allowed set of traffic logs to be recorded:
l All: All traffic logs to and from the FortiGate will be recorded.
FortiOS 7.6.2 Administration Guide 3870
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,870
|
Log and Report
l Specify: Select specific traffic logs to be recorded. Deselect all options to
disable traffic logging. Local traffic logging is disabled by default due to the
high volume of logs generated.
Enable Log local-in traffic to log local traffic for local-in policies globally or per
policy. See Local-in policy on page 1480.
GUI Preferences
Resolve
Hostnames
Define the translation of IP addresses to host names:
l Enable: IP addresses are translated to host names using reverse DNS
lookup. If the DNS server is not available or is slow to reply, requests may
time out.
l Disable: IP addresses are not translated to host names.
Resolve Unknown
Applications
Define the resolution of unknown applications:
l Enable: Unknown applications are resolved using the Internet Service
Database.
l Disable: Unknown applications are not resolved.
Local Logs
Settings available in the Local Logs tab include:
Local Logs
Disk logging Define local log storage on the FortiGate:
l Enable: Logs will be stored on a local disk. Local disk logging is not available
in the GUI if the Security Fabric is enabled. When the Security Fabric is
enabled, disk logging can still be configured on the root FortiGate in the CLI
but is not available for downstream FortiGates.
l Disable: Logs will be stored remotely to FortiAnalyzer/FortiManager or to a
Cloud logging device.
Local Reports Define log reporting on the FortiGate:
l Enable: Local reports will be available on the FortiGate. Reports can be
reviewed in Log & Report > Reports in the Local tab.
l Disable: Local reports will not be available on the FortiGate.
Historical FortiView Define the presentation of log information on FortiView:
l Enable: Historical log data will be available on a FortiView monitor. By
default, logs older than seven days are deleted. Disk logging must be
enabled.
l Disable: Historical log data will not be available on FortiView.
Disk Usage Presents the disk space used and the total disk space available on the disk.
FortiOS 7.6.2 Administration Guide 3871
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,871
|
Log and Report
Threat Weight
Threat weight helps aggregate and score threats based on user-defined severity levels. It adds several fields such as
threat level (crlevel), threat score (crscore), and threat type (craction) to traffic logs. Threat weight logging is
enabled by default and the settings can be customized. Threats can be viewed from the Top Threats FortiView
dashboard.
To configure threat weight settings:
1. Go to Log & Report > Log Settings and select the Threat Weight tab.
2. Adjust the settings as needed, such as individual weights per threat type and risk level values.
3. Click Apply.
To add the Top Threats monitor to the dashboard:
1. In the tree menu, click Dashboard and in the FortiView section, click the + sign (Add Monitor).
2. In the Security section, enable Show More and click Top Threats.
3. Configure the settings as needed.
4. Click Add Monitor.
5. Go to Dashboard > Top Threats. The Top Threats monitor displays threats based on the scores in the traffic logs.
6. Double-click a threat to view the summary.
7. Click Sources, Destinations, Countries/Regions, or Sessions to view more information. Double-click an entry to
FortiOS 7.6.2 Administration Guide 3872
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,872
|
Log and Report
view the log details.
Configuring logs in the CLI
The FortiGate can store logs locally to its system memory or a local disk. Logs can also be stored externally on a storage
device, such as FortiAnalyzer, FortiAnalyzer Cloud, FortiGate Cloud, or a syslog server.
Disk logging
Disk logging must be enabled for logs to be stored locally on the FortiGate. By default, logs older than seven days are
deleted from the disk. Log age can be configured in the CLI. Approximately 75% of disk space is available for log
storage. Log storage space can be determined using the diagnose sys logdisk usage command.
To configure local disk logging:
config log disk setting
set status enable
set maximum-log-age <integer>
set max-log-file-size <integer>
end
Remote logging
The process to configure FortiGate to send logs to FortiAnalyzer or FortiManager is identical. Remote logging to
FortiAnalyzer and FortiManager can be configured using both the GUI and CLI. When using the CLI, use the config
log fortianalyzer setting command for both FortiAnalyzer and FortiManager.
FortiOS 7.6.2 Administration Guide 3873
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,873
|
Log and Report
If VDOMs are configured on the FortiGate, multiple FortiAnalyzers and syslog servers can be added globally. See
Configuring multiple FortiAnalyzers (or syslog servers) per VDOM on page 3878 and Configuring multiple FortiAnalyzers
on a FortiGate in multi-VDOM mode on page 3879 for more information.
To configure remote logging to FortiAnalyzer:
config log fortianalyzer setting
set status enable
set server <server_IP>
set upload option {store-and-upload | realtime | 1-minute | 5-minute}
end
Remote logging can also be configured to FortiCloud, FortiSIEM, and syslog servers. Up to four syslog servers or
FortiSIEM devices can be configured using the config log syslogd command and can send logs to syslog in CSV
and CEF formats.
To configure remote logging to FortiCloud:
config log fortiguard setting
set status enable
set source-ip <source IP used to connect FortiCloud>
end
To configure remote logging to a syslog server:
config log syslogd setting
set status enable
set server <syslog_IP>
set format {default | csv | cef | rfc5424 | json}
end
Log filters
Log filter settings can be configured to determine which logs are recorded to the FortiAnalyzer, FortiManager, and syslog
servers. This allows certain logging levels and types of logs to be directed to specific log devices.
To configure log filters for FortiAnalyzer:
config log fortianalyzer filter
set severity <level>
set forward-traffic {enable | disable}
set local-traffic {enable | disable}
set multicast-traffic {enable | disable}
set sniffer-traffic {enable | disable}
end
To configure log filters for a syslog server:
config log syslogd filter
set severity <level>
set forward-traffic {enable | disable}
set local-traffic {enable | disable}
set multicast-traffic {enable | disable}
FortiOS 7.6.2 Administration Guide 3874
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,874
|
Log and Report
set sniffer-traffic {enable | disable}
end
Email alerts
FortiGate events can be monitored at all times using email alerts. Email alerts send notifications to up to three recipients
and can be triggered based on log event and severity level. Email alerts will be sent every five minutes by default but this
can be configured in the CLI.
To configure email alerts:
config alertemail setting
set username <name>
set mailto1 <email>
set filter-mode {category | threshold}
set email-interval <integer>
set IPS-logs {enable | disable}
set HA-logs {enable | disable}
set antivirus-logs {enable | disable}
set webfilter-logs {enable | disable}
set log-disk-usage-warning {enable | disable}
end
Logging to FortiAnalyzer
The following topics provide instructions on logging to FortiAnalyzer:
l FortiAnalyzer log caching on page 3875
l Configuring multiple FortiAnalyzers (or syslog servers) per VDOM on page 3878
l Configuring multiple FortiAnalyzers on a FortiGate in multi-VDOM mode on page 3879
l Switching to an alternate FortiAnalyzer if the main FortiAnalyzer is unavailable on page 3882
FortiAnalyzer log caching
Reliable logging to FortiAnalyzer prevents lost logs when the connection between FortiOS and FortiAnalyzer is
disrupted. When reliable mode is enabled:
1. Logs are cached in a FortiOS memory queue.
2. FortiOS sends logs to FortiAnalyzer, and FortiAnalyzer uses seq_no to track received logs.
3. After FortiOS sends logs to FortiAnalyzer, logs are moved to a confirm queue in FortiOS.
4. FortiOS periodically queries FortiAnalyzer for the latest seq_no of the last log received, and clears logs from the
confirm queue up to the seq_no.
5. If the connection between FortiOS and FortiAnalyzer is disrupted, FortiOS resends the logs in the confirm queue to
FortiAnalyzer when the connection is reestablished.
FortiOS 7.6.2 Administration Guide 3875
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,875
|
Log and Report
FortiAnalyzer 7.2.0 and later is required.
To enable reliable mode:
config log fortianalyzer setting
set reliable enable
end
To view the memory and confirm queues:
1. Verify that log synchronization is enabled for FortiAnalyzer:
# diagnose test application fgtlogd 1
vdom-admin=0
mgmt=root
fortilog:
faz: global , enabled
server=172.16.200.251, realtime=1, ssl=1, state=connected
server_log_status=Log is allowed.,
src=, mgmt_name=FGh_Log_root_172.16.200.251, reliable=1, sni_prefix_type=none,
required_entitlement=none, region=ca-west-1,,
logsync_enabled:1, logsync_conn_id:65535, seq_no:790
...
2. When a network disruption disconnects FortiOS from FortiAnalyzer and FortiOS continues to generate logs, the
logs are cached in the memory queue.
l View the number of logs in the cache and queue:
# diagnose test application fgtlogd 41
cache maximum: 189516595(180MB) objects: 40 used: 27051(0MB) allocated: 29568(0MB)
VDOM:root
Memory queue for: global-faz
queue:
num:9 size:6976(0MB) total size:26068(0MB) max:189516595(180MB) logs:28
Confirm queue for: global-faz
queue:
num:29 size:19092(0MB) total size:27051(0MB) max:189516595(180MB) logs:7
# diagnose test application fgtlogd 30
VDOM:root
Memory queue for: global-faz
queue:
num:9 size:6976(0MB) total size:26068(0MB) max:189516595(180MB)
type:3, cat=1, log_count=1, seq_no=0, data len=359 size:435
type:3, cat=1, log_count=1, seq_no=0, data len=307 size:383
......
type:3, cat=0, log_count=4, seq_no=0, data len=1347 size:1423
type:3, cat=4, log_count=1, seq_no=0, data len=653 size:729
'total log count':28, 'total data len':6292
FortiOS 7.6.2 Administration Guide 3876
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,876
|
Log and Report
Confirm queue for: global-faz
queue:
num:29 size:19092(0MB) total size:26068(0MB) max:189516595(180MB)
type:3, cat=1, log_count=1, seq_no=1, data len=290 size:366
type:3, cat=1, log_count=1, seq_no=2, data len=233 size:309
......
type:3, cat=0, log_count=1, seq_no=28, data len=524 size:600
type:3, cat=1, log_count=1, seq_no=29, data len=307 size:383
'total log count':76, 'total data len':16888
There are nine OFTP items cached to the memory queue, and 29 OFTP items to send from FortiOS to FortiAnalyzer
that are waiting for confirmation from FortiAnalyzer.
l Go to Log & Report > Log Settings to view the queue in the GUI:
3. Re-establish the connection between FortiOS and FortiAnalyzer and confirm that the queue has cleared by
checking the seq_no, which indicates the latest confirmation log from FortiAnalyzer:
# diagnose test application fgtlogd 30
VDOM:root
Memory queue for: global-faz
queue:
num:0 size:0(0MB) total size:0(0MB) max:189516595(180MB)
'total log count':0, 'total data len':0
Confirm queue for: global-faz
queue:
num:0 size:0(0MB) total size:0(0MB) max:189516595(180MB)
'total log count':0, 'total data len':0
The queue has been cleared, meaning that FortiOS received confirmation from FortiAnalyzer and cleared the
confirm queue.
# diagnose test application fgtlogd 1
vdom-admin=0
mgmt=root
FortiOS 7.6.2 Administration Guide 3877
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,877
|
Log and Report
fortilog:
faz: global , enabled
server=172.16.200.251, realtime=1, ssl=1, state=connected
server_log_status=Log is allowed.,
src=, mgmt_name=FGh_Log_root_172.16.200.251, reliable=1, sni_prefix_type=none,
required_entitlement=none, region=ca-west-1,
logsync_enabled:1, logsync_conn_id:65535, seq_no:67
status: ver=6, used_disk=0, total_disk=0, global=0, vfid=0 conn_verified=Y
SNs: last sn update:38 seconds ago.
Sn list:
(FAZ-VMTM21000000,age=38s)
queue: qlen=0.
OFTP items with a seq_no lower than 67 have been sent to FortiAnalyzer and were confirmed.
Configuring multiple FortiAnalyzers (or syslog servers) per VDOM
In a VDOM, multiple FortiAnalyzer and syslog servers can be configured as follows:
l Up to three override FortiAnalyzer servers
l Up to four override syslog servers
If the VDOM faz-override and/or syslog-override setting is enabled or disabled (default) before upgrading, the
setting remains the same after upgrading.
If the override setting is disabled, the GUI displays the global FortiAnalyzer1 or syslog1 setting. If the override setting is
enabled, the GUI displays the VDOM override FortiAnalyzer1 or syslog1 setting.
You can only use CLI to enable the override to support multiple log servers.
To enable FortiAnalyzer and syslog server override under VDOM:
config log setting
set faz-override enable
set syslog-override enable
end
When faz-override and/or syslog-override is enabled, the following CLI commands are available for configuring
VDOM override:
To configure VDOM override for FortiAnalyzer:
1. Configure the FortiAnalyzer override settings:
config log fortianalyzer/fortianalyzer2/fortianalyzer3 override-setting
set status enable
set server "123.12.123.123"
set reliable enable
end
2. Configure the override filters:
config log fortianalyzer/fortianalyzer2/fortianalyzer3 override-filter
set severity information
set forward-traffic enable
FortiOS 7.6.2 Administration Guide 3878
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,878
|
Log and Report
set local-traffic enable
set multicast-traffic enable
set sniffer-traffic enable
set anomaly enable
set voip enable
set dlp-archive enable
set dns enable
set ssh enable
set ssl enable
end
To configure VDOM override for a syslog server:
1. Configure the syslog override settings:
config log syslogd/syslogd2/syslogd3/syslogd4 override-setting
set status enable
set server "123.12.123.12"
set facility local1
end
2. Configure the override filters:
config log syslogd/syslogd2/syslogd3/syslogd4 override-filter
set severity information
set forward-traffic enable
set local-traffic enable
set multicast-traffic enable
set sniffer-traffic enable
set anomaly enable
set voip enable
set dns enable
set ssh enable
set ssl enable
end
Configuring multiple FortiAnalyzers on a FortiGate in multi-VDOM mode
This topic shows a sample configuration of multiple FortiAnalyzers on a FortiGate in multi-VDOM mode.
In this example:
l The FortiGate has three VDOMs:
l Root (management VDOM)
l VDOM1
l VDOM2
l There are four FortiAnalyzers.
These IP addresses are used as examples in the instructions below.
l FAZ1: 172.16.200.55
l FAZ2: 172.18.60.25
l FAZ3: 192.168.1.253
l FAZ4: 192.168.1.254
l Set up FAZ1 and FAZ2 under global.
FortiOS 7.6.2 Administration Guide 3879
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,879
|
Log and Report
l These two collect logs from the root VDOM and VDOM2.
l FAZ1 and FAZ2 must be accessible from management VDOM root.
l Set up FAZ3 and FAZ4 under VDOM1.
l These two collect logs from VDOM1.
l FAZ3 and FAZ4 must be accessible from VDOM1.
To set up FAZ1 as global FortiAnalyzer 1 from the GUI:
Prerequisite: FAZ1 must be reachable from the management root VDOM.
1. Go to Global > Log & Report > Log Settings.
2. Enable Send logs to FortiAnalyzer/FortiManager.
3. Enter the FortiAnalyzer IP.
In this example: 172.16.200.55.
4. For Upload option, select Real Time.
5. Click Apply.
To set up FAZ2 as global FortiAnalyzer 2 from the CLI:
Prerequisite: FAZ2 must be reachable from the management root VDOM.
config log fortianalyzer2 setting
set status enable
set server "172.18.60.25"
set upload-option realtime
end
To set up FAZ3 and FAZ4 as VDOM1 FortiAnalyzer 1 and FortiAnalyzer 2:
Prerequisite: FAZ3 and FAZ4 must be reachable from VDOM1.
config log setting
set faz-override enable
end
config log fortianalyzer override-setting
set status enable
set server "192.168.1.253"
set upload-option realtime
end
config log fortianalyzer2 override-setting
set status enable
set server "192.168.1.254"
set upload-option realtime
end
FortiOS 7.6.2 Administration Guide 3880
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,880
|
Log and Report
Checking FortiAnalyzer connectivity
To use the diagnose command to check FortiAnalyzer connectivity:
1. Check the global FortiAnalyzer status:
FGTA(global) # diagnose test application fgtlogd 1
vdom-admin=1
mgmt=root
faz: global , enabled
server=172.16.200.55, realtime=1, ssl=1, state=connected
server_log_status=Log is allowed.,
src=, mgmt_name=FGh_Log_root_172.16.200.55, reliable=0, sni_prefix_type=none,
required_entitlement=none, region=ca-west-1,
logsync_enabled:1, logsync_conn_id:65535, seq_no:0
status: ver=6, used_disk=0, total_disk=0, global=0, vfid=0 conn_
verified=Y
SNs: last sn update:383 seconds ago.
Sn list:
(FAZ-VMTM2200****,age=383s)
queue: qlen=0.
filter: severity=6, sz_exclude_list=0
traffic virus webfilter ips emailfilter anomaly voip dlp app-ctrl waf dns ssh
ssl file-filter icap sctp-filter
subcategory:
traffic: forward local multicast sniffer ztna
anomaly:all subcategories are enabled.
server: global, id=0, ready=1, name=172.16.200.55 addr=172.16.200.55:514
oftp-state=connected
faz2: global , enabled
server=172.18.60.25, realtime=3, ssl=1, state=connected
server_log_status=Log is allowed.,
src=, mgmt_name=FGh_Log_root_172.18.60.25, reliable=0, sni_prefix_type=none,
required_entitlement=none, region=ca-west-1,
logsync_enabled:1, logsync_conn_id:131071, seq_no:0
status: ver=6, used_disk=0, total_disk=0, global=0, vfid=0 conn_
verified=Y
SNs: last sn update:383 seconds ago.
Sn list:
(FAZ-VMTM2201****,age=383s)
queue: qlen=0.
filter: severity=6, sz_exclude_list=0
traffic virus webfilter ips emailfilter anomaly voip dlp app-ctrl waf dns ssh
ssl file-filter icap sctp-filter
subcategory:
traffic: forward local multicast sniffer ztna
anomaly:all subcategories are enabled.
server: global, id=1, ready=1, name=172.18.60.25 addr=172.18.60.25:514
oftp-state=connected
2. Check the VDOM1 override FortiAnalyzer status:
FGTA(global) # diagnose test application fgtlogd 3101
vdom VDOM1: id=3
event filter:
event
system vpn user router wireless wanopt endpoint ha security-rating fortiextender
FortiOS 7.6.2 Administration Guide 3881
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,881
|
Log and Report
connector sdwan cifs-auth-fail switch-controller rest-api webproxy
faz: vdom, enabled, override
server=192.168.1.253, realtime=3, ssl=1, state=connected
server_log_status=Log is allowed.,
src=, mgmt_name=FGh_Log_VDOM1_192.168.1.253, reliable=0, sni_prefix_type=none,
required_entitlement=none, region=ca-west-1,
logsync_enabled:1, logsync_conn_id:3, seq_no:0
status: ver=6, used_disk=0, total_disk=0, global=0, vfid=0 conn_
verified=Y
SNs: last sn update:16 seconds ago.
Sn list:
(FAZ-VMTM2200****,age=16s)
queue: qlen=0.
filter: severity=6, sz_exclude_list=0
traffic virus webfilter ips emailfilter anomaly voip dlp app-ctrl waf dns ssh
ssl file-filter icap sctp-filter
subcategory:
traffic: forward local multicast sniffer ztna
anomaly:all subcategories are enabled.
server: vdom, id=0, ready=1, name=192.168.1.253 addr=192.168.1.253:514
oftp-state=connected
faz2: vdom, enabled, override
server=192.168.1.254, realtime=3, ssl=1, state=connected
server_log_status=Log is allowed.,
src=, mgmt_name=FGh_Log_VDOM1_192.168.1.254, reliable=0, sni_prefix_type=none,
required_entitlement=none, region=ca-west-1,
logsync_enabled:1, logsync_conn_id:65539, seq_no:0
status: ver=6, used_disk=0, total_disk=0, global=0, vfid=0 conn_
verified=Y
SNs: last sn update:16 seconds ago.
Sn list:
(FAZ-VMTM2201****,age=16s)
queue: qlen=0.
filter: severity=6, sz_exclude_list=0
traffic virus webfilter ips emailfilter anomaly voip dlp app-ctrl waf dns ssh
ssl file-filter icap sctp-filter
subcategory:
traffic: forward local multicast sniffer ztna
anomaly:all subcategories are enabled.
server: vdom, id=1, ready=1, name=192.168.1.254 addr=192.168.1.254:514
oftp-state=connected
faz3: vdom, disabled, override
Switching to an alternate FortiAnalyzer if the main FortiAnalyzer is unavailable
FortiOS supports switching to an alternate FortiAnalyzer if the main FortiAnalyzer is unavailable. Once the connectivity is
restored, it will automatically fall back to the primary FortiAnalyzer.
This feature can be used in multi-VDOM mode when FortiAnalyzer override settings are
configured.
FortiOS 7.6.2 Administration Guide 3882
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,882
|
Log and Report
To configure switching to an alternate FortiAnalyzer when the main FortiAnalyzer is unavailable:
1. Configure primary and alternate FortiAnalyzer servers:
config log fortianalyzer setting
set status enable
set server "172.16.200.250"
set alt-server "172.16.200.251"
set fallback-to-primary enable
set serial "FAZ-VMTM22000000" "FAZ-VMTM23000003"
end
2. Verify the primary and alternate FortiAnalyzer server IPs:
# diagnose test application fgtlogd 1
vdom-admin=1
mgmt=vdom1
fortilog:
faz: global , enabled
server=172.16.200.250, alt-server=172.16.200.251, active-server=172.16.200.250,
realtime=3, ssl=1, state=connected
server_log_status=Log is allowed.,
src=, mgmt_name=FGh_Log_vdom1_172.16.200.250, reliable=0, sni_prefix_type=none,
required_entitlement=none, region=ca-west-1,
logsync_enabled:1, logsync_conn_id:65535, seq_no:0
disconnect_jiffies:0
status: ver=6, used_disk=0, total_disk=0, global=0, vfid=0 conn_
verified=Y
SNs: last sn update:11 seconds ago.
Sn list:
(FAZ-VMTM22000000,age=11s) (FAZ-VMTM23000003,age=12s)
queue: qlen=0.
filter: severity=6, sz_exclude_list=0
traffic virus webfilter ips emailfilter anomaly voip dlp app-ctrl waf dns ssh
ssl file-filter icap sctp-filter virtual-patch
subcategory:
traffic: forward local multicast sniffer ztna
virus:all subcategories are enabled.
webfilter:all subcategories are enabled.
ips:all subcategories are enabled.
emailfilter:all subcategories are enabled.
anomaly:all subcategories are enabled.
voip:all subcategories are enabled.
dlp:all subcategories are enabled.
app-ctrl:all subcategories are enabled.
FortiOS 7.6.2 Administration Guide 3883
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,883
|
Log and Report
waf:all subcategories are enabled.
dns:all subcategories are enabled.
ssh:all subcategories are enabled.
ssl:all subcategories are enabled.
file-filter:all subcategories are enabled.
icap:all subcategories are enabled.
sctp-filter:all subcategories are enabled.
virtual-patch:all subcategories are enabled.
server: global, id=0, ready=1, name=172.16.200.250 addr=172.16.200.250:514
oftp-state=connected
primary oftp status:null
probe oftp status:null, 442
The 172.16.200.250 server is currently active and acting as the primary FortiAnalyzer.
3. Make the primary FortiAnalyzer server go down. The FortiGate will automatically connect to the alternate
FortiAnalyzer server.
4. Verify the FortiAnalyzer server status information:
# diagnose test application fgtlogd 1
vdom-admin=1
mgmt=vdom1
fortilog:
faz: global , enabled
server=172.16.200.250, alt-server=172.16.200.251, active-server=172.16.200.251,
realtime=3, ssl=1, state=connected
server_log_status=Log is allowed.,
src=, mgmt_name=FGh_Log_vdom1_172.16.200.250, reliable=0, sni_prefix_type=none,
required_entitlement=none, region=ca-west-1,
logsync_enabled:1, logsync_conn_id:65535, seq_no:0
disconnect_jiffies:0
status: ver=6, used_disk=0, total_disk=0, global=0, vfid=0 conn_
verified=Y
SNs: last sn update:30 seconds ago.
Sn list:
(FAZ-VMTM22000000,age=30s) (FAZ-VMTM23000003,age=31s)
queue: qlen=0.
filter: severity=6, sz_exclude_list=0
traffic virus webfilter ips emailfilter anomaly voip dlp app-ctrl waf dns ssh
ssl file-filter icap sctp-filter virtual-patch
subcategory:
traffic: forward local multicast sniffer ztna
virus:all subcategories are enabled.
webfilter:all subcategories are enabled.
ips:all subcategories are enabled.
emailfilter:all subcategories are enabled.
anomaly:all subcategories are enabled.
voip:all subcategories are enabled.
dlp:all subcategories are enabled.
app-ctrl:all subcategories are enabled.
waf:all subcategories are enabled.
dns:all subcategories are enabled.
ssh:all subcategories are enabled.
ssl:all subcategories are enabled.
file-filter:all subcategories are enabled.
FortiOS 7.6.2 Administration Guide 3884
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,884
|
Log and Report
icap:all subcategories are enabled.
sctp-filter:all subcategories are enabled.
virtual-patch:all subcategories are enabled.
server: global, id=0, ready=1, name=172.16.200.250 addr=172.16.200.250:514
oftp-state=connected
probe oftp status:null, 38
The 172.16.200.251 server is currently active and acting as the primary FortiAnalyzer.
5. Restore the connection to the 172.16.200.250 server. The FortiGate will automatically reconnect to this
FortiAnalyzer server.
6. Verify the FortiAnalyzer server status information:
# diagnose test application fgtlogd 1
vdom-admin=1
mgmt=vdom1
fortilog:
faz: global , enabled
server=172.16.200.250, alt-server=172.16.200.251, active-server=172.16.200.250,
realtime=3, ssl=1, state=connected
server_log_status=Log is allowed.,
src=, mgmt_name=FGh_Log_vdom1_172.16.200.250, reliable=0, sni_prefix_type=none,
required_entitlement=none, region=ca-west-1,
logsync_enabled:1, logsync_conn_id:65535, seq_no:0
disconnect_jiffies:0
status: ver=6, used_disk=0, total_disk=0, global=0, vfid=0 conn_
verified=Y
SNs: last sn update:11 seconds ago.
Sn list:
(FAZ-VMTM22000000,age=58s) (FAZ-VMTM23000003,age=59s)
queue: qlen=0.
filter: severity=6, sz_exclude_list=0
traffic virus webfilter ips emailfilter anomaly voip dlp app-ctrl waf dns ssh
ssl file-filter icap sctp-filter virtual-patch
subcategory:
traffic: forward local multicast sniffer ztna
virus:all subcategories are enabled.
webfilter:all subcategories are enabled.
ips:all subcategories are enabled.
emailfilter:all subcategories are enabled.
anomaly:all subcategories are enabled.
voip:all subcategories are enabled.
dlp:all subcategories are enabled.
app-ctrl:all subcategories are enabled.
waf:all subcategories are enabled.
dns:all subcategories are enabled.
ssh:all subcategories are enabled.
ssl:all subcategories are enabled.
file-filter:all subcategories are enabled.
icap:all subcategories are enabled.
sctp-filter:all subcategories are enabled.
virtual-patch:all subcategories are enabled.
server: global, id=0, ready=1, name=172.16.200.250 addr=172.16.200.250:514
oftp-state=connected
FortiOS 7.6.2 Administration Guide 3885
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,885
|
Log and Report
primary oftp status:null
probe oftp status:null, 530
The 172.16.200.250 server is currently active and acting as the primary FortiAnalyzer again.
To manually switch from the primary to alternate FortiAnalyzer (and vice-versa):
# execute log {fortianalyzer | fortianalyzer2 | fortianalyzer3} manual-failover
If the primary server is still up, the behavior resulting from running this command is based on the fallback-toprimary setting configured in the global FortiAnalyzer log settings.
l If fallback-to-primary is enabled (default), running execute log fortianalyzer manual-failover
will switch to the alternate FortiAnalyzer, but it will switch back to the primary since it is not actually down.
l If fallback-to-primary is disabled, running execute log fortianalyzer manual-failover will switch
to the alternate FortiAnalyzer, and it will not switch back to the primary.
Advanced and specialized logging
The following topics provide information on advanced and specialized logging:
l Logs for the execution of CLI commands on page 3886
l Log buffer on FortiGates with an SSD disk on page 3888
l Source and destination UUID logging on page 3889
l Configuring and debugging the free-style filter on page 3891
l Logging the signal-to-noise ratio and signal strength per client on page 3893
l RSSO information for authenticated destination users in logs on page 3895
l Destination user information in UTM logs on page 3898
l Message ID in UTM logs on page 3902
l Log fields for long-live sessions on page 3903
l Generate unique user name for anonymized logs on page 3904
l Configuring syslog overrides for VDOMs on page 3907
l Logging MAC address flapping events on page 3910
l Incorporating endpoint device data in the web filter UTM logs on page 3911
l Logging detection of duplicate IPv4 addresses on page 3912
Logs for the execution of CLI commands
The cli-audit-log option records the execution of CLI commands in system event logs (log ID 44548). In addition to
execute and config commands, show, get, and diagnose commands are recorded in the system event logs.
The cli-audit-log data can be recorded on memory or disk, and can be uploaded to FortiAnalyzer, FortiGate Cloud,
or a syslog server.
FortiOS 7.6.2 Administration Guide 3886
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,886
|
Log and Report
To enable the CLI audit log option:
config system global
set cli-audit-log enable
end
To view system event logs in the GUI:
1. Run the command in the CLI (# show log fortianalyzer setting).
2. Go to Log & Report > System Events.
3. Select General System Events.
4. Select the log entry and click Details.
To display the logs:
# execute log filter device disk
# execute log filter category event
# execute log filter field subtype system
# execute log filter field logid 0100044548
# execute log display
Sample log:
1: date=2020-11-16 time=10:43:00 eventtime=1605552179970875703 tz="-0800" logid="0100044548"
type="event" subtype="system" level="information" vd="root" logdesc="Action performed"
user="admin" ui="jsconsole(2.0.225.112)" action="Show" msg="show log fortianalyzer setting"
2: date=2020-11-16 time=10:42:43 eventtime=1605552163502003054 tz="-0800" logid="0100044548"
type="event" subtype="system" level="information" vd="root" logdesc="Action performed"
user="admin" ui="jsconsole(2.0.225.112)" action="Get" msg="get sys status"
FortiOS 7.6.2 Administration Guide 3887
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,887
|
Log and Report
3: date=2020-11-16 time=09:47:04 eventtime=1605548824762387718 tz="-0800" logid="0100044548"
type="event" subtype="system" level="information" vd="root" logdesc="Action performed"
user="admin" ui="jsconsole(2.0.228.202)" action="Diagnose" msg="diagnose log test"
Log buffer on FortiGates with an SSD disk
FortiGates with an SSD disk have a configurable log buffer. When the connection to FortiAnalyzer is unreachable, the
FortiGate is able to buffer logs on disk if the memory log buffer is full. The logs queued on the disk buffer can be sent
successfully once the connection to FortiAnalyzer is restored.
The queued logs are buffered to the memory first and then disk. If the total buffer is full, new logs will overwrite the old
logs.
To configure the log buffer:
1. Allocate disk space (MB) to temporarily store logs to FortiAnalyzer:
config system global
set faz-disk-buffer-size 200
end
2. Check the fgtlogd statistics. The 200 MB disk buffer has been set, and there are currently no logs buffered in
memory or on disk when FortiAnalyzer is reachable:
# diagnose test application fgtlogd 41
cache maximum: 19569745(18MB) objects: 0 used: 0(0MB) allocated: 0(0MB)
VDOM:root
Memory queue for: global-faz
queue:
num:0 size:0(0MB) total size:0(0MB) max:15375441(14MB) logs:0
queue disk total size:0MB, max size:200MB
total items:0
devid:-1-13-0-0
buffer path:/var/log/log/qbuf/13.0/0
saved size:0MB, lost files: 0
save roll:0 restore roll:0
Confirm queue for: global-faz
queue:
num:0 size:0(0MB) total size:0(0MB) max:15375441(14MB) logs:0
3. Disable the connection between the FortiGate and FortiAnalyzer. For example, delete the FortiGate from the
FortiAnalyzer authorized device list.
Assuming a massive number of logs (~ 300000) are recorded during this downtime, the logs will be queued in the
memory buffer first. If the memory buffer is full, then the remaining logs will be queued on the disk buffer.
4. Recheck the fgtlogd statistics. Currently, there are logs buffered in both memory and disk:
# diagnose test application fgtlogd 41
cache maximum: 19569745(18MB) objects: 14391 used: 10450754(9MB) allocated: 12089088
(11MB)
VDOM:root
Memory queue for: global-faz
queue:
num:14245 size:9306505(8MB) total size:10450754(9MB) max:15375441(14MB)
logs:14245
queue disk total size:199MB, max size:200MB
FortiOS 7.6.2 Administration Guide 3888
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,888
|
Log and Report
total items:321085
devid:-1-13-0-0
buffer path:/var/log/log/qbuf/13.0/0
saved size:199MB, lost files: 10
save roll:60 restore roll:10
Confirm queue for: global-faz
queue:
num:0 size:0(0MB) total size:10450754(9MB) max:15375441(14MB) logs:0
The overall fgtlogd statistics shows the total cached logs is the sum of the logs buffered in memory and on disk:
# diagnose test application fgtlogd 4
Queues in all miglogds: cur:1 total-so-far:727973
global log dev statistics:
faz=399411, faz_cloud=0, fds_log=399411
faz 0: sent=0, failed=0, cached=335480, dropped=0
Num of REST URLs: 0
5. Enable the connection between FortiAnalyzer and the FortiGate.
6. After a while, check the fgtlogd statistics to confirm that all buffered logs are being sent to FortiAnalyzer
successfully:
# diagnose test application fgtlogd 4
Queues in all miglogds: cur:1 total-so-far:727973
global log dev statistics:
faz=399411, faz_cloud=0, fds_log=399411
faz 0: sent=335487, failed=0, cached=0, dropped=0
Num of REST URLs: 0
# diagnose test application fgtlogd 41
cache maximum: 19569745(18MB) objects: 0 used: 0(0MB) allocated: 0(0MB)
VDOM:root
Memory queue for: global-faz
queue:
num:0 size:0(0MB) total size:0(0MB) max:15375441(14MB) logs:0
queue disk total size:0MB, max size:200MB
total items:0
devid:-1-13-0-0
buffer path:/var/log/log/qbuf/13.0/0
saved size:0MB, lost files: 10
save roll:60 restore roll:60
Confirm queue for: global-faz
queue:
num:0 size:0(0MB) total size:0(0MB) max:15375441(14MB) logs:0
Source and destination UUID logging
The traffic log setting includes three UUID fields: Source UUID (srcuuid), Destination UUID (dstuuid), and Policy UUID
(poluuid). It also includes two internet-service name fields: Source Internet Service (srcinetsvc) and
Destination Internet Service (dstinetsvc).
Log UUIDs
All policy types have a UUID field that is auto-generated by FortiOS when the policy is created, and can be viewed in the
CLI using the show command. For example:
FortiOS 7.6.2 Administration Guide 3889
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,889
|
Log and Report
# show firewall policy 1
config firewall policy
edit 1
set name "client_yt_v4"
set uuid f4fe48a4-938c-51ee-8856-3e84e3b24af4
...
next
end
UUIDs can be matched for each source and destination that match a policy that is added to the traffic log. This allows the
address objects to be referenced in log analysis and reporting.
As this may consume a significant amount of storage space, this feature is optional. By default, address UUID insertion
is disabled.
To enable address UUID insertion in traffic logs in the GUI:
1. Go to Log & Report > Log Settings.
2. Under UUIDs in Traffic Log, enable Address.
3. Click Apply.
To enable address UUID insertion in traffic logs in the CLI:
config system global
set log-uuid-address enable
end
Sample log
date=2019-01-25 time=11:32:55 logid="0000000013" type="traffic" subtype="forward"
level="notice" vd="vdom1" eventtime=1528223575srcip=192.168.1.183 srcname="PC24"
srcport=33709 srcintf="lan" srcintfrole="lan" dstip=192.168.70.184 dstport=80 dstintf="wan1"
dstintfrole="wan" srcuuid="27dd503e 883c 51e7-ade1-7e015d46494f" dstuuid="27dd503e-883c51e7-ade1-7e015d46494f" poluuid="9e0fe24c-1808-51e8-1257-68ce4245572c" sessionid=5181
FortiOS 7.6.2 Administration Guide 3890
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,890
|
Log and Report
proto=6 action="client-rst" policyid=4 policytype="policy" service="HTTP" trandisp="snat"
transip=192.168.70.228 transport=33709 appid=38783 app="Wget" appcat="General.Interest"
apprisk="low" applist="default" duration=5 sentbyte=450 rcvdbyte=2305 sentpkt=6 wanin=368
wanout=130 lanin=130 lanout=130 utmaction="block" countav=2 countapp=1 crscore=50 craction=2
devtype="Linux PC" devcategory="None" osname="Linux" mastersrcmac="00:0c:29:36:5c:c3"
srcmac="00:0c:29:36:5c:c3" srcserver=0 utmref=65523-1018
Internet service name fields
Traffic logs for internet-service include two fields: Source Internet Service and Destination Internet Service.
To view the internet service fields using the GUI:
1. Go to Log & Report > Forward Traffic.
2. Double-click on an entry to view the Log Details. The Source Internet Service and Destination Internet Service fields
are visible in the Log Details pane.
Sample log
date=2019-01-25 time=14:17:04 logid="0000000013" type="traffic" subtype="forward"
level="notice" vd="vdom1" eventtime=1548454622
srcip=10.1.100.11 srcport=51112 srcintf="port3" srcintfrole="undefined" dstip=172.217.14.228
dstport=80 dstintf="port1" dstintfrole="undefined" poluuid="af519380-2094-51e9-391cb78e8edbddfc" srcinetsvc="isdb-875099" dstinetsvc="Google.Gmail" sessionid=6930 proto=6
action="close" policyid=2 policytype="policy" service="HTTP" dstcountry="United States"
srccountry="Reserved" trandisp="snat" transip=172.16.200.2 transport=51112 duration=11
sentbyte=398 rcvdbyte=756 sentpkt=6 rcvdpkt=4 appcat="unscanned" devtype="Router/NAT Device"
devcategory="Fortinet Device" mastersrcmac="90:6c:ac:41:7a:24" srcmac="90:6c:ac:41:7a:24"
srcserver=0 dstdevtype="Unknown" dstdevcategory="Fortinet Device"
masterdstmac="08:5b:0e:1f:ed:ed" dstmac="08:5b:0e:1f:ed:ed" dstserver=0
Configuring and debugging the free-style filter
Free-style filters allow users to define a filter for logs that are captured to each individual logging device type. Filters can
include log categories and specific log fields. The filters can be created as an inclusive list or exclusive list.
FortiOS 7.6.2 Administration Guide 3891
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,891
|
Log and Report
Free-style filters can also be used to filter logs that have been captured on logging devices already to narrow down the
list of logs to view.
config log syslogd filter
config free-style
edit <id>
set category <option>
set filter <string>
set filter-type {include | exclude}
next
end
end
category <option> Set the log category. The following options are available: traffic, event,
virus, webfilter, attack, spam, anomaly, voip, dlp, app-ctrl, waf,
dns, ssh, ssl, file-filter, icap, and ztna.
filter <string> Enter the filter criteria. Multiple values can be added, for example:
set filter "logid <id> <id>"
filter-type {include
| exclude}
Include/exclude logs that match the filter.
Use the following commands to view the results when multiple fields are used:
# execute log filter free-style "logid <id> <id>"
# execute log filter free-style "srcip <IP_address> <IP_address>"
# execute log filter free-style "(logid <id>) or (srcip <IP_address> <IP_address>)"
# execute log filter free-style "(srcip <IP_address>) and (dstip <IP_address>)"
In this example, the free-style filter is set to filter log IDs 0102043039 and 0102043040. The source IPs, 192.168.2.5 and
192.168.2.205, are also checked.
To configure the syslogd free-style filter with multiple values:
config log syslogd filter
config free-style
edit 1
set category event
set filter "logid 0102043039 0102043040"
next
end
end
To view the syslogd free-style filter results:
# execute log filter free-style "logid 0102043039 0102043040"
# execute log filter dump
category: event
device: disk
start-line: 1
view-lines: 10
max-checklines: 0
HA member:
log search mode: on-demand
FortiOS 7.6.2 Administration Guide 3892
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,892
|
Log and Report
pre-fetch-pages: 2
Filter: logid 0102043039 0102043040
Oftp search string: (and (or logid=="0102043039" not-exact logid=="0102043040" not-exact))
# execute log filter free-style "(logid 0102043039) or (srcip 192.168.2.5 192.168.2.205)"
# execute log filter dump
category: event
device: disk
start-line: 1
view-lines: 10
max-checklines: 0
HA member:
log search mode: on-demand
pre-fetch-pages: 2
Filter: (logid 0102043039) or (srcip 192.168.2.5 192.168.2.205)
Oftp search string: (or (or (or srcip==192.168.2.5) (or srcip==192.168.2.205)) (or
logid=="0102043039" not-exact))
Logging the signal-to-noise ratio and signal strength per client
The signal-to-noise ratio (snr) and signal strength (signal) are logged per client in the WiFi event and traffic logs.
When a WiFi client connects to a tunnel or local-bridge mode SSID on an FortiAP that is managed by a FortiGate, signalto-noise ratio and signal strength details are included in WiFi event logs for local-bridge traffic statistics and
authentication, and in forward traffic logs for tunnel traffic. This allows you to store and view clients' historical signal
strength and signal-to-noise ratio information.
To verify when a client is connecting to an SSID:
1. Go to Log & Report > System Events and select WiFi Events.
The Signal and Signal/Noise columns show the signal strength and signal-to-noise ratio for each applicable client.
2. WiFi event log messages include the signal and snr values:
FortiOS 7.6.2 Administration Guide 3893
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,893
|
Log and Report
date=2020-05-27 time=11:26:28 logid="0104043579" type="event" subtype="wireless"
level="notice" vd="vdom1" eventtime=1590603988877156921 tz="-0700" logdesc="Wireless
client IP assigned" sn="FP231ETF20000455" ap="FP231ETF20000455" vap="stability3"
ssid="FOS_QA_Starr_140E_Guest-11" radioid=1 user="N/A" group="N/A"
stamac="1c:87:2c:b6:a8:49" srcip=11.10.80.2 channel=6 radioband="802.11n,g-only"
signal=-45 snr=50 security="WPA2 Personal" encryption="AES" action="client-ip-detected"
reason="Reserved 0" mpsk="N/A" msg="Client 1c:87:2c:b6:a8:49 had an IP address detected
(by DHCP packets)."
date=2020-05-27 time=11:26:11 logid="0104043573" type="event" subtype="wireless"
level="notice" vd="vdom1" eventtime=1590603970962702892 tz="-0700" logdesc="Wireless
client authenticated" sn="FP231ETF20000455" ap="FP231ETF20000455" vap="stability3"
ssid="FOS_QA_Starr_140E_Guest-11" radioid=1 user="N/A" group="N/A"
stamac="1c:87:2c:b6:a8:49" srcip=0.0.0.0 channel=6 radioband="802.11n,g-only" signal=-45
snr=50 security="WPA2 Personal" encryption="AES" action="client-authentication"
reason="Reserved 0" mpsk="N/A" msg="Client 1c:87:2c:b6:a8:49 authenticated."
To verify tunnel traffic when a client is connecting to a tunnel mode SSID:
1. Go to Log & Report > Forward Traffic.
The Signal and Signal/Noise columns show the signal strength and signal-to-noise ratio for each applicable client.
2. Forward traffic log messages include the signal and snr values:
date=2020-05-27 time=11:30:26 logid="0000000013" type="traffic" subtype="forward"
level="notice" vd="vdom1" eventtime=1590604226533016978 tz="-0700" srcip=11.10.80.2
srcname="WIFI23" srcport=53926 srcintf="stability3" srcintfrole="lan" srcssid="FOS_QA_
Starr_140E_Guest-11" apsn="FP231ETF20000455" ap="FP231ETF20000455" channel=6
radioband="802.11n,g-only" signal=-31 snr=64 dstip=91.189.91.157 dstport=123
dstintf="wan1" dstintfrole="wan" srccountry="United States" dstcountry="United States"
sessionid=322069 proto=17 action="accept" policyid=13 policytype="policy"
poluuid="7c14770c-1456-51e9-4c57-806e9c499782" policyname="wmm" service="NTP"
trandisp="snat" transip=172.16.200.111 transport=53926 appid=16270 app="NTP"
appcat="Network.Service" apprisk="elevated" applist="g-default" duration=180 sentbyte=76
rcvdbyte=76 sentpkt=1 rcvdpkt=1 utmaction="allow" countapp=1 osname="Linux"
mastersrcmac="1c:87:2c:b6:a8:49" srcmac="1c:87:2c:b6:a8:49" srcserver=0 utmref=65534-66
FortiOS 7.6.2 Administration Guide 3894
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,894
|
Log and Report
To verify local-bridge traffic statistics when a client is connecting to a local-bridge mode SSID:
1. Go to Log & Report > System Events and select WiFi Events.
The Signal and Signal/Noise columns show the signal strength and signal-to-noise ratio for each applicable client.
2. WiFi event log messages include the signal and snr values:
date=2020-05-26 time=17:48:57 logid="0104043687" type="event" subtype="wireless"
level="information" vd="vdom1" eventtime=1590540537841497433 tz="-0700" logdesc="Traffic
stats for station with bridge wlan" sn="FP231ETF20000455" ap="FP231ETF20000455"
vap="wifi.fap.01" ssid="FOS_QA_Starr-140E-LB-cap-2" srcip=10.128.100.4 user="N/A"
stamac="00:1e:e5:df:b1:63" signal=-53 snr=52 sentbyte=8970016 rcvdbyte=985910
nextstat=300 action="sta-wl-bridge-traffic-stats" msg="Traffic stats for bridge ssid
client 00:1e:e5:df:b1:63"
RSSO information for authenticated destination users in logs
FortiGate can use RSSO accounting information from authenticated RSSO users to populate destination users and
groups, along with source users and groups.
RSSO user login information can be forwarded by the RADIUS server to the FortiGate that is listening for incoming
RADIUS accounting start messages on the RADIUS accounting port. Accounting start messages usually contain the
IP address, user name, and user group information. FortiGate uses this information in traffic logs, which include dstuser
and dstgroup fields for user and group destination information .
For instructions on configuring RSSO, see RADIUS single sign-on agent on page 3786.
The three following scenarios show traffic between pc1 and the internet, and pc1 and pc2.
Scenario 1
In this scenario, RSSO user test2 in group rsso-grp1 is authenticated on pc1. Traffic flows from pc1 to the internet.
Expected result:
In the logs, user test2 is shown as the source user in the rsso-grp1 group.
FortiOS 7.6.2 Administration Guide 3895
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,895
|
Log and Report
To verify the results:
1. In the GUI, go to Log & Report > Forward Traffic and view the details of an entry with test2 as the source.
2. In the Source section, User is test2 and Group is the rsso-grp1.
3. The log message shows the user and group:
10: date=2020-05-25 time=15:34:43 logid="0000000013" type="traffic" subtype="forward"
level="notice" vd="vdom1" eventtime=1590446083718007055 tz="-0700" srcip=10.1.100.188
srcname="win7-2-A.Fortinet-FSSO.COM" srcport=56982 srcintf="port10"
srcintfrole="undefined" dstip=172.217.3.195 dstport=443 dstintf="port9"
dstintfrole="undefined" srccountry="Reserved" dstcountry="United States"
sessionid=120651 proto=17 action="accept" policyid=1 policytype="policy"
poluuid="d130f886-9ec6-51ea-206e-8c561c5244c6" policyname="pol1" user="test2"
group="rsso-grp1" authserver="vdom1" service="udp/443" trandisp="snat"
transip=172.16.200.1 transport=56982 duration=181 sentbyte=2001 rcvdbyte=1820 sentpkt=6
rcvdpkt=4 appcat="unscanned" sentdelta=0 rcvddelta=0 srchwvendor="VMware"
osname="Windows" srcswversion="7" mastersrcmac="00:0c:29:44:be:b9"
srcmac="00:0c:29:44:be:b9" srcserver=0
Scenario 2
In this scenario, RSSO user test2 is authenticated on pc1. Traffic is initialized on pc2 (172.16.200.185) going to pc1
(10.1.100.188).
Expected result:
In the logs, user test2 is shown as the destination user (dstuser). No destination group (dstgroup) is logged because
no RSSO user is logged in on pc2, so the traffic from pc2 is unauthenticated.
To verify the results:
1. In the GUI, go to Log & Report > Forward Traffic and view the details of an entry with 172.16.200.185 (pc2) as the
source.
FortiOS 7.6.2 Administration Guide 3896
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,896
|
Log and Report
2. In the Other section, Destination User is test2 and no destination group is shown.
3. The log message shows the destination user:
1: date=2020-05-22 time=07:38:06 logid="0000000020" type="traffic" subtype="forward"
level="notice" vd="root" eventtime=1590158286585506922 tz="-0700" srcip=172.16.200.185
identifier=1 srcintf="port9" srcintfrole="undefined" dstip=10.1.100.188 dstintf="port10"
dstintfrole="undefined" srccountry="Reserved" dstcountry="Reserved" sessionid=4395
proto=1 action="accept" policyid=3 policytype="policy" poluuid="d4f18e1e-9c36-51ea-6ec0-
3a354d5910ee" policyname="pol2" dstuser="test2" dstauthserver="root" service="PING"
trandisp="snat" transip=10.1.100.1 transport=0 duration=128 sentbyte=7620 rcvdbyte=5220
sentpkt=127 rcvdpkt=87 appcat="unscanned" sentdelta=7620 rcvddelta=5220
Scenario 3
In this scenario, RSSO user test2 in group rsso-grp1 is authenticated on pc1, and user test3 in group rsso-grp2 is
authenticated on pc2. Traffic flows from pc2 to pc1.
Expected result:
In the logs, user test3 is shown as the source user in the rsso-grp1 group. User test2 is shown as destination user
(dstuser) in the rsso-grp1 destination group (dstgroup). The destination group is logged because an RSSO user is
logged in to pc2.
To verify the results:
1. In the GUI, go to Log & Report > Forward Traffic and view the details of an entry with 172.16.200.185 (pc2) as the
source.
2. In the Source section, User is test3 and Group is the rsso-grp2. In the Other section, Destination User is test2 and
Destination Group is rsso-grp1.
FortiOS 7.6.2 Administration Guide 3897
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,897
|
Log and Report
3. The log message shows both the source and the destination users and groups:
8: date=2020-05-25 time=14:23:07 logid="0000000013" type="traffic" subtype="forward"
level="notice" vd="vdom1" eventtime=1590441786958007914 tz="-0700" srcip=172.16.200.185
srcport=64096 srcintf="port9" srcintfrole="undefined" dstip=10.1.100.188 dstport=80
dstintf="port10" dstintfrole="undefined" srccountry="Reserved" dstcountry="Reserved"
sessionid=112445 proto=6 action="close" policyid=3 policytype="policy"
poluuid="5894c368-9eca-51ea-fb4c-ec5a6c1d5043" policyname="pol2" user="test3"
group="rsso-grp2" authserver="vdom1" dstuser="test2" dstgroup="rsso-grp1"
dstauthserver="vdom1" service="HTTP" trandisp="snat" transip=10.1.100.1 transport=64096
duration=1 sentbyte=328 rcvdbyte=563 sentpkt=6 rcvdpkt=5 appcat="unscanned"
dsthwvendor="VMware" dstosname="Windows" dstswversion="7"
masterdstmac="00:0c:29:44:be:b9" dstmac="00:0c:29:44:be:b9" dstserver=0
Destination user information in UTM logs
The dstuser field in UTM logs records the username of a destination device when that user has been authenticated on
the FortiGate.
In the following example topology, the user, bob, is authenticated on a client computer. The user, guest, is authenticated
on the server. Log are collected for AV and IPS in flow inspection mode. Logs are collected for application control and
web filter in proxy mode.
FortiOS 7.6.2 Administration Guide 3898
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,898
|
Log and Report
To configure the RADIUS user and user groups:
1. Configure the RADIUS server:
config user radius
edit "Ubuntu_docker"
set server "172.16.200.240"
set secret ************
next
end
2. Configure the local user:
config user local
edit "guest"
set type password
set passwd ************
next
end
3. Configure the RADIUS user groups:
config user group
edit "RADIUS_User_Group"
set member "Ubuntu_docker"
next
edit "Local_User"
set member "guest"
next
end
Flow inspection mode
To verify AV and IPS logs in flow mode:
1. Configure the firewall policies:
config firewall policy
edit 1
set name "WAN_out"
set srcintf "dmz"
set dstintf "wan1"
set action accept
set srcaddr "all"
set dstaddr "all"
set schedule "always"
set service "ALL"
set utm-status enable
set ssl-ssh-profile "deep-inspection"
set av-profile "g-default"
set ips-sensor "sensor-11"
set nat enable
set groups "RADIUS_User_Group" "Local_User"
next
edit 3
set name "WAN_in"
set srcintf "wan1"
FortiOS 7.6.2 Administration Guide 3899
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,899
|
Log and Report
set dstintf "dmz"
set action accept
set srcaddr "all"
set dstaddr "all"
set schedule "always"
set service "ALL"
set logtraffic all
set nat enable
set groups "RADIUS_User_Group" "Local_User"
next
end
2. Verify the AV log:
date=2021-09-14 time=16:37:25 eventtime=1631662646131356720 tz="-0700"
logid="0211008192" type="utm" subtype="virus" eventtype="infected" level="warning"
vd="vdom1" policyid=1 msg="File is infected." action="blocked" service="HTTP"
sessionid=4613 srcip=10.1.100.72 dstip=172.16.200.75 srcport=60086 dstport=80
srcintf="dmz" srcintfrole="undefined" dstintf="wan1" dstintfrole="undefined"
srcuuid="877d43a4-c2f9-51eb-f78f-e09794924d8a" dstuuid="877d43a4-c2f9-51eb-f78fe09794924d8a" proto=6 direction="incoming" filename="eicar.com" quarskip="Quarantinedisabled" virus="EICAR_TEST_FILE" viruscat="Virus" dtype="av-engine"
ref="http://www.fortinet.com/ve?vn=EICAR_TEST_FILE" virusid=2172
url="http://172.16.200.75/eicar.com" profile="g-default" user="bob" group="RADIUS_User_
Group" authserver="Ubuntu_docker" dstuser="guest" agent="Wget/1.17.1"
analyticscksum="275a021bbfb6489e54d471899f7db9d1663fc695ec2fe2a2c4538aabf651fd0f"
analyticssubmit="false" crscore=50 craction=2 crlevel="critical"
3. Verify the IPS log:
date=2021-09-14 time=16:56:06 eventtime=1631663765992499880 tz="-0700"
logid="0419016384" type="utm" subtype="ips" eventtype="signature" level="alert"
vd="vdom1" severity="info" srcip=10.1.100.72 srccountry="Reserved" dstip=172.16.200.75
srcintf="dmz" srcintfrole="undefined" dstintf="wan1" dstintfrole="undefined"
sessionid=7881 action="dropped" proto=6 service="HTTP" policyid=1
attack="Eicar.Virus.Test.File" srcport=60092 dstport=80 direction="incoming"
attackid=29844 profile="sensor-11" ref="http://www.fortinet.com/ids/VID29844" user="bob"
group="RADIUS_User_Group" authserver="Ubuntu_docker" dstuser="guest"
incidentserialno=17825794 attackcontextid="2/2"
attackcontext="dGVudC1MZW5ndGg6IDY4DQpLZWVwLUFsaXZlOiB0aW1lb3V0PTUsIG1heD0xMDANCkNvbm5lY
3Rpb246IEtlZXAtQWxpdmUNCkNvbnRlbnQtVHlwZTogYXBwbGljYXRpb24veC1tc2Rvcy1wcm9ncmFtDQoNClg1T
yFQJUBBUFs0XFBaWDU0KFBeKTdDQyk3fSRFSUNBUi1TVEFOREFSRC1BTlRJVklSVVMtVEVTVC1GSUxFISRIK0gqP
C9QQUNLRVQ+"
Proxy inspection mode
To verify application control and web filter logs in proxy mode:
1. Configure the firewall policies:
config firewall policy
edit 1
set name "WAN_out"
set srcintf "dmz"
set dstintf "wan1"
set action accept
set srcaddr "all"
FortiOS 7.6.2 Administration Guide 3900
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,900
|
Log and Report
set dstaddr "all"
set schedule "always"
set service "ALL"
set utm-status enable
set inspection-mode proxy
set ssl-ssh-profile "deep-inspection"
set av-profile "g-default"
set application-list "g-default"
set webfilter-profile "1"
set nat enable
set groups "RADIUS_User_Group" "Local_User"
next
edit 3
set name "WAN_in"
set srcintf "wan1"
set dstintf "dmz"
set action accept
set srcaddr "all"
set dstaddr "all"
set schedule "always"
set service "ALL"
set inspection-mode proxy
set logtraffic all
set nat enable
set groups "RADIUS_User_Group" "Local_User"
next
end
2. Verify the application control log:
date=2021-09-14 time=17:05:45 eventtime=1631664345570951500 tz="-0700"
logid="1059028704" type="utm" subtype="app-ctrl" eventtype="signature"
level="information" vd="vdom1" appid=38783 user="bob" group="RADIUS_User_Group"
authserver="Ubuntu_docker" dstuser="guest" srcip=10.1.100.72 dstip=172.16.200.75
srcport=60098 dstport=80 srcintf="dmz" srcintfrole="undefined" dstintf="wan1"
dstintfrole="undefined" proto=6 service="HTTP" direction="outgoing" policyid=1
sessionid=10871 applist="g-default" action="pass" appcat="General.Interest" app="Wget"
hostname="172.16.200.75" incidentserialno=17825796 url="/eicar.com"
msg="General.Interest: Wget," apprisk="low"
3. Verify the web filter log:
date=2021-09-14 time=17:14:46 eventtime=1631664886585770420 tz="-0700"
logid="0315012546" type="utm" subtype="webfilter" eventtype="urlfilter"
level="information" vd="vdom1" urlfilteridx=1 urlfilterlist="Auto-webfilter-urlfilter_
caex0ojl5" policyid=1 sessionid=15251 user="bob" group="RADIUS_User_Group"
authserver="Ubuntu_docker" dstuser="guest" srcip=10.1.100.72 srcport=60106 srcintf="dmz"
srcintfrole="undefined" srcuuid="877d43a4-c2f9-51eb-f78f-e09794924d8a"
dstip=172.16.200.75 dstport=80 dstintf="wan1" dstintfrole="undefined" dstuuid="877d43a4-
c2f9-51eb-f78f-e09794924d8a" proto=6 service="HTTP" hostname="172.16.200.75" profile="1"
action="passthrough" reqtype="direct" url="http://172.16.200.75/eicar.com" sentbyte=149
rcvdbyte=0 direction="outgoing" msg="URL was allowed because it is in the URL filter
list"
FortiOS 7.6.2 Administration Guide 3901
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,901
|
Log and Report
Message ID in UTM logs
FortiOS logs the message ID (messageid) field in UTM logs under the email filter, file filter, and DLP subtypes. The
message ID can be used with FortiMail to locate an undesired email. The message ID can also be used with
FortiAnalyzer to trace the email and locate the device that sent the undesired traffic.
To view the message ID:
1. Go to Log & Report > Security Events and select Logs.
2. Set the filters to display the email filter, file filter, or DLP subtypes. In this example, the Anti-Spam and Disk filters are
set to display an entry with the Message ID field.
3. Select the log, and click Details. The Message ID field is displayed.
Following are examples of the message ID (messageid) field in email filter, file filter, and DLP logs:
l Email filter logs:
1: date=2024-05-27 time=15:20:30 eventtime=1716848430551966694 tz="-0700"
logid="0512020481" type="utm" subtype="emailfilter" eventtype="email"
level="information" vd="vdom1" policyid=1 poluuid="12c1682e-18a5-51ef-dc3d-459a4231c9e6"
policytype="policy" sessionid=162 srcip=10.1.100.22 srcport=41344 srccountry="Reserved"
srcintf="port21" srcintfrole="undefined" srcuuid="f29a920a-18a4-51ef-4fca-8c6dc5db9e26"
dstip=172.16.200.55 dstport=25 dstcountry="Reserved" dstintf="port17"
dstintfrole="undefined" dstuuid="f29a920a-18a4-51ef-4fca-8c6dc5db9e26" proto=6
service="SMTP" profile="730866" action="log-only" from="testpc3@qa.fortinet.com"
to="testpc3@qa.fortinet.com" sender="testpc3@qa.fortinet.com"
recipient="testpc3@qa.fortinet.com" messageid="<20240527222030.000384@spam_pc1>"
direction="outgoing" msg="general email log" subject="testcase215001" size="246"
attachment="no"
l File filter logs:
FortiOS 7.6.2 Administration Guide 3902
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,902
|
Log and Report
1: date=2024-05-27 time=18:52:21 eventtime=1716861141191537397 tz="-0700"
logid="1900064001" type="utm" subtype="file-filter" eventtype="file-filter"
level="notice" vd="vdom1" policyid=1 poluuid="12c1682e-18a5-51ef-dc3d-459a4231c9e6"
policytype="policy" sessionid=536 srcip=10.1.100.22 srcport=55966 srccountry="Reserved"
srcintf="port21" srcintfrole="undefined" srcuuid="f29a920a-18a4-51ef-4fca-8c6dc5db9e26"
dstip=172.16.200.55 dstport=25 dstcountry="Reserved" dstintf="port17"
dstintfrole="undefined" dstuuid="f29a920a-18a4-51ef-4fca-8c6dc5db9e26" proto=6
service="SMTP" profile="msgId_test" direction="outgoing" action="log-only"
from="testpc3@qa.fortinet.com" to="testpc3@qa.fortinet.com"
sender="testpc3@qa.fortinet.com" recipient="testpc3@qa.fortinet.com"
messageid="<20240528015221.001679@spam_pc1>" subject="703400" attachment="no"
rulename="bannedFiles" filesize=105749 filetype="jpeg" msg="File was detected by file
filter."
l DLP logs:
1: date=2024-05-28 time=11:59:50 eventtime=1716922790136310107 tz="-0700"
logid="0954024576" type="utm" subtype="dlp" eventtype="dlp" level="warning" vd="vdom1"
ruleid=1 rulename="test_exe" dlpextra="Sensor 'test' matching any: ('Test-Dictionary'=1)
>= 1; match." filtertype="sensor" filtercat="message" severity="medium" policyid=1
poluuid="12c1682e-18a5-51ef-dc3d-459a4231c9e6" policytype="policy" sessionid=1976
epoch=1523674618 eventid=2 srcip=10.1.100.22 srcport=52998 srccountry="Reserved"
srcintf="port21" srcintfrole="undefined" srcuuid="f29a920a-18a4-51ef-4fca-8c6dc5db9e26"
dstip=172.16.200.55 dstport=25 dstcountry="Reserved" dstintf="port17"
dstintfrole="undefined" dstuuid="f29a920a-18a4-51ef-4fca-8c6dc5db9e26" proto=6
service="SMTP" filetype="N/A" direction="outgoing" action="block"
from="testpc3@qa.fortinet.com" to="testpc3@qa.fortinet.com"
sender="testpc3@qa.fortinet.com" recipient="testpc3@qa.fortinet.com"
messageid="<20240528185950.007871@spam_pc1>" subject="731047" attachment="no"
profile="testing"
Log fields for long-live sessions
Logging of long-live session statistics can be enabled or disabled in traffic logs.
config log setting
set long-live-session-stat {enable | disable}
end
When enabled, traffic logs include the following fields of statistics for long-live sessions:
Duration delta
(durationdelta)
Displays the time in seconds between the last session log and the current session
log.
Sent packet delta
(sentpktdelta)
Displays the number of sent packets.
When the number of packets reported in the sentpktdelta field matches the
number of bytes reported in the sentpkt field, it shows no missing logs.
Received packet delta
(rcvdpktdelta)
Displays the number of received packets.
When the number of packets reported in the rcvdpktdelta field matches the
number of bytes reported in the rcvdpkt field, it shows no missing logs.
The long-live session fields enhance the granularity and accuracy of traffic longs to aid troubleshooting and analysis.
FortiOS 7.6.2 Administration Guide 3903
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,903
|
Log and Report
Example
In this example, logging is enabled for long-live session statistics. Log ID 20 includes the new fields for long-live
sessions.
To log long-live session statistics:
1. Enable logging of long-live session statistics:
config log setting
set long-live-session-stat enable
end
2. View information in the logs:
In the following example, log fields are filtered for log ID 0000000020 to displays the new fields of data.
The sentpkt field displays 205 bytes, and the rcvdpkt field displays 1130 bytes. The new fields
(sentpktdelta=205 and rcvdpktdelta=1130) display the same number of packets, which shows no logs
have been lost. The durationdelta shows 120 seconds between the last session log and the current session
log.
# execute log filter device Disk
# execute log filter category 0
# execute log filter field subtype forward
# execute log filter field logid 0000000020
# execute log display
1 logs found.
1 logs returned.
1: date=2023-12-07 time=14:19:59 eventtime=1701987599439429340 tz="-0800"
logid="0000000020" type="traffic" subtype="forward" level="notice" vd="vdom1"
srcip=10.1.100.22 srcport=53540 srcintf="wan2" srcintfrole="undefined"
dstip=172.16.200.55 dstport=80 dstintf="wan1" dstintfrole="undefined"
srccountry="Reserved" dstcountry="Reserved" sessionid=296 proto=6 action="accept"
policyid=1 policytype="policy" poluuid="e538d622-53eb-51ee-8adc-f8fbb0f22fdd"
policyname="B-out" service="HTTP" trandisp="snat" transip=172.16.200.2 transport=53540
duration=120 sentbyte=10855 rcvdbyte=1397640 sentpkt=205 rcvdpkt=1130 appcat="unscanned"
sentdelta=10855 rcvddelta=1397640 durationdelta=120 sentpktdelta=205 rcvdpktdelta=1130
Generate unique user name for anonymized logs
With the anonymization-hash option, user fields in logs can be anonymized by generating a hash based on the user
name and salt value. The hash for the same user will generate the same hash value, allowing the anonymized user to be
correlated between logs.
config log setting
set user-anonymize enable
set anonymization-hash <salt string>
end
FortiOS 7.6.2 Administration Guide 3904
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,904
|
Log and Report
Example
In this example, user names are encrypted in traffic and event logs using the anonymization-hash option.
To encrypt the user name for logs in the GUI:
1. Configure the hash anonymization in the CLI:
config log setting
set user-anonymize enable
set anonymization-hash "random"
end
2. Configure a firewall policy with a user as a source:
a. Go to Policy & Objects > Firewall Policy and click Create New.
b. For Source, select a user.
c. In the Security Profiles section, enable AntiVirus and select a profile.
d. Configure the other settings as needed.
e. Click OK.
3. Verify the forward traffic log:
a. Go to Log & Report > Forward Traffic.
b. Select an entry and double-click to view the log details.
The user name has a hashed value of e8557d12f6551b2d.
4. Verify the antivirus traffic log:
a. Go to Log & Report > AntiVirus.
b. Select an entry and double-click to view the log details.
The user name has the same hashed value. Hovering over the user name displays a No user information
tooltip.
5. Verify the event log:
a. Go to Log & Report > Events > System Events.
b. Select an entry and double-click to view the log details.
The administrative user has a hashed value of 6a4d668735f5517a.
To encrypt the user name for logs in the CLI:
1. Configure the hash anonymization:
config log setting
set user-anonymize enable
set anonymization-hash "random"
end
2. Configure a firewall policy with a user as a source:
config firewall policy
edit 1
set name "WAN_out"
set srcintf "dmz"
set dstintf "wan1"
set action accept
set srcaddr "all"
FortiOS 7.6.2 Administration Guide 3905
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,905
|
Log and Report
set dstaddr "all"
set srcaddr6 "all"
set dstaddr6 "all"
set schedule "always"
set service "ALL"
set utm-status enable
set inspection-mode proxy
set ssl-ssh-profile "deep-inspection"
set av-profile "g-default"
set nat enable
set users "bob"
next
end
3. Verify the forward traffic log. The user name has a hashed value of e8557d12f6551b2d:
date=2021-09-09 time=15:24:52 eventtime=1631226292981803646 tz="-0700"
logid="0000000013" type="traffic" subtype="forward" level="notice" vd="vdom1"
srcip=10.1.100.72 srcport=33250 srcintf="dmz" srcintfrole="undefined"
dstip=172.16.200.75 dstport=80 dstintf="wan1" dstintfrole="undefined"
srccountry="Reserved" dstcountry="Reserved" sessionid=383 proto=6 action="client-rst"
policyid=1 policytype="policy" poluuid="12f6f924-c2fb-51eb-6e06-3b997d55d5f4"
policyname="WAN_out" user="e8557d12f6551b2d" dstuser="e8557d12f6551b2d" service="HTTP"
trandisp="snat" transip=172.16.200.7 transport=33250 duration=1 sentbyte=469
rcvdbyte=6331 sentpkt=6 rcvdpkt=8 appcat="unscanned" wanin=369 wanout=149 lanin=149
lanout=149 utmaction="block" countav=1 crscore=50 craction=2 srchwvendor="VMware"
osname="Linux" mastersrcmac="**:**:**:**:**:**" srcmac="**:**:**:**:**:**" srcserver=0
dsthwvendor="VMware" dstosname="Linux" masterdstmac="**:**:**:**:**:**"
dstmac="**:**:**:**:**:**" dstserver=0 utmref=0-28
4. Verify the antivirus traffic log. The user name has the same hashed value:
date=2021-09-09 time=15:24:51 eventtime=1631226291945007723 tz="-0700"
logid="0211008192" type="utm" subtype="virus" eventtype="infected" level="warning"
vd="vdom1" policyid=1 msg="File is infected." action="blocked" service="HTTP"
sessionid=383 srcip=10.1.100.72 dstip=172.16.200.75 srcport=33250 dstport=80
srcintf="dmz" srcintfrole="undefined" dstintf="wan1" dstintfrole="undefined"
srcuuid="877d43a4-c2f9-51eb-f78f-e09794924d8a" dstuuid="877d43a4-c2f9-51eb-f78fe09794924d8a" proto=6 direction="incoming" filename="eicar.com" quarskip="File-was-notquarantined" virus="EICAR_TEST_FILE" viruscat="Virus" dtype="av-engine"
ref="http://www.fortinet.com/ve?vn=EICAR_TEST_FILE" virusid=2172
url="http://172.16.200.75/eicar.com" profile="g-default" user="e8557d12f6551b2d"
dstuser="e8557d12f6551b2d" agent="Wget/1.17.1" analyticssubmit="false" crscore=50
craction=2 crlevel="critical"
5. Verify the event log. The administrative user has a hashed value of 6a4d668735f5517a:
date=2021-09-09 time=09:59:09 eventtime=1631206750109938510 tz="-0700"
logid="0100032001" type="event" subtype="system" level="information" vd="vdom1"
logdesc="Admin login successful" sn="**********" user="6a4d668735f5517a" ui="https
(10.6.30.254)" method="https" srcip=10.6.30.254 dstip=10.6.30.107 action="login"
status="success" reason="none" profile="super_admin" msg="Administrator 6a4d668735f5517a
logged in successfully from https(10.6.30.254)"
If user-anonymize is enabled in the log settings and anonymization-hash is left blank, the user name is displayed
as anonymous in the logs.
FortiOS 7.6.2 Administration Guide 3906
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,906
|
Log and Report
Sample traffic log:
date=2021-09-09 time=11:27:44 eventtime=1631212064444723180 tz="-0700" logid="0000000013"
type="traffic" subtype="forward" level="notice" vd="vdom1" srcip=10.1.100.72 srcport=33246
srcintf="dmz" srcintfrole="undefined" dstip=172.16.200.75 dstport=80 dstintf="wan1"
dstintfrole="undefined" srccountry="Reserved" dstcountry="Reserved" sessionid=1337 proto=6
action="client-rst" policyid=1 policytype="policy" poluuid="12f6f924-c2fb-51eb-6e06-
3b997d55d5f4" policyname="WAN_out" user="anonymous" dstuser="anonymous" service="HTTP"
trandisp="snat" transip=172.16.200.7 transport=33246 duration=1 sentbyte=469 rcvdbyte=6331
sentpkt=6 rcvdpkt=8 appcat="unscanned" wanin=369 wanout=149 lanin=149 lanout=149
utmaction="block" countav=1 crscore=50 craction=2 srchwvendor="VMware" osname="Linux"
mastersrcmac="**:**:**:**:**:**" srcmac="**:**:**:**:**:**" srcserver=0 dsthwvendor="VMware"
dstosname="Linux" masterdstmac="**:**:**:**:**:**" dstmac="**:**:**:**:**:**" dstserver=0
utmref=0-14
Sample UTM log:
date=2021-09-09 time=11:27:43 eventtime=1631212063400129220 tz="-0700" logid="0211008192"
type="utm" subtype="virus" eventtype="infected" level="warning" vd="vdom1" policyid=1
msg="File is infected." action="blocked" service="HTTP" sessionid=1337 srcip=10.1.100.72
dstip=172.16.200.75 srcport=33246 dstport=80 srcintf="dmz" srcintfrole="undefined"
dstintf="wan1" dstintfrole="undefined" srcuuid="877d43a4-c2f9-51eb-f78f-e09794924d8a"
dstuuid="877d43a4-c2f9-51eb-f78f-e09794924d8a" proto=6 direction="incoming"
filename="eicar.com" quarskip="File-was-not-quarantined" virus="EICAR_TEST_FILE"
viruscat="Virus" dtype="av-engine" ref="http://www.fortinet.com/ve?vn=EICAR_TEST_FILE"
virusid=2172 url="http://172.16.200.75/eicar.com" profile="g-default" user="anonymous"
dstuser="anonymous" agent="Wget/1.17.1" analyticssubmit="false" crscore=50 craction=2
crlevel="critical"
Sample event log:
date=2021-09-09 time=11:27:26 eventtime=1631212046861637260 tz="-0700" logid="0100032102"
type="event" subtype="system" level="alert" vd="vdom1" logdesc="Configuration changed"
user="anonymous" ui="jsconsole" msg="Configuration is changed in the anonymous session"
Configuring syslog overrides for VDOMs
Logs can be sent from non-management VDOMs to both global and VDOM-override syslog servers.
config log syslogd override-setting
set use-management-vdom {enable | disable}
end
set use-management-vdom
{enable | disable}
Enable/disable use of management VDOM as source VDOM for logs sent to
syslog server.
l enable: Send logs through the management VDOM.
l disable: Do not send logs through the management VDOM.
When use-management-vdom is enabled under non-management VDOM, only the
management VDOM is used to forward logs to configured syslog servers. Non-management
VDOM override syslog servers must be reachable through the management VDOM.
FortiOS 7.6.2 Administration Guide 3907
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,907
|
Log and Report
Example
This example covers the following scenarios:
l Non-management VDOM with use-management-vdom disabled on page 3908
l Non-management VDOM with use-management-vdom enabled on page 3908
l Non-management VDOM with mix of use-management-vdom enabled and disabled on page 3909
All scenarios use the following IP addresses:
l Global syslog server: 10.6.30.22
l Root VDOM gateway: 192.168.5.254
l Management VDOM (vdom1) gateway: 172.16.200.254
Non-management VDOM with use-management-vdom disabled
In this example, a global syslog server is enabled. For the root VDOM, an override syslog server is enabled with usemanagement-vdom disabled. For the management VDOM, an override syslog server is enabled. With this
configuration, logs are sent to the following locations:
l All VDOMs, except the root and management VDOMs, send logs to the global syslog server (10.6.30.22).
l The root VDOM sends logs to its override syslog server at 192.168.5.44.
l The management VDOM sends logs to its override syslog server at 172.16.200.55.
To configure syslog servers:
1. Enable the global syslog server:
config log syslogd setting
set status enable
set server "10.6.30.22"
set facility local6
end
2. For the root VDOM, enable an override syslog server and disable use-management-vdom:
config log syslogd override-setting
set status enable
set server "192.168.5.44"
set use-management-vdom disable
set facility local6
end
3. For the management VDOM (vdom1), enable an override syslog server:
config log syslogd override-setting
set status enable
set server "172.16.200.55"
set facility local6
end
Non-management VDOM with use-management-vdom enabled
In this example, a global syslog server is enabled. For the root VDOM, an override syslog server and usemanagement-vdom are enabled. For the management VDOM, two override syslog servers are enabled. With this
FortiOS 7.6.2 Administration Guide 3908
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,908
|
Log and Report
configuration, logs are sent to the following locations:
l All VDOMs, except root and management VDOMs, send logs to the global syslog server (10.6.30.22).
l The root VDOM cannot send logs to syslog servers because the servers are not reachable through the
management VDOM.
To send logs to 192.168.5.44, set use-management-vdom to disable for the root VDOM. Alternately, configure the
root VDOM to use an override syslog server that is reachable through the management VDOM.
l The management VDOM sends logs to the override syslog server at 172.16.200.55.
To configure syslog servers:
1. Enable the global syslog server:
config log syslogd setting
set status enable
set server "10.6.30.22"
set facility local6
end
2. For the root VDOM, enable an override syslog server and enable use-management-vdom:
config log syslogd override-setting
set status enable
set server "192.168.5.44"
set use-management-vdom enable
set facility local6
end
3. For the management VDOM, enable an override syslog server:
config log syslogd override-setting
set status enable
set server "172.16.200.55"
set facility local6
end
Non-management VDOM with mix of use-management-vdom enabled and disabled
In this example, a global syslog server is enabled. For the root VDOM, three override syslog servers are enabled with a
mix of use-management-vdom set to enabled and disabled. For the management VDOM, an override syslog
server is enabled. With this configuration, logs are sent from non-management VDOMs to both global and VDOMoverride syslog servers. The logs are sent to the following locations:
l All VDOMs, except the root and management VDOMs, send logs to the global syslog server (10.6.30.22).
l The root VDOM sends logs to the following syslog servers:
l For syslogd, logs are sent to the root VDOM override server at 192.168.5.44 because use-managementvdom is disabled.
l For syslogd2, logs are sent through the management VDOM to the root VDOM override server at
172.16.200.55 and to the syslog server reachable by the management VDOM because use-managementvdom is enabled.
l For syslogd3, logs are sent through the management VDOM to the root VDOM override syslog server at
10.6.30.22 and to the syslog server reachable by the management VDOM because use-management-vdom
is enabled.
l The management VDOM (vdom1) sends logs to the override syslog server at 172.16.200.55.
FortiOS 7.6.2 Administration Guide 3909
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,909
|
Log and Report
To configure syslog servers:
1. Enable the global syslog server:
config log syslogd setting
set status enable
set server "10.6.30.22"
set facility local6
end
2. For root, configure three override syslog servers:
a. For syslogd, enable an override syslog server and disable use-management-vdom:
config log syslogd override-setting
set status enable
set server "192.168.5.44"
set use-management-vdom disable
set facility local6
end
b. For syslog2, enable an override syslog server and enable use-management-vdom:
config log syslogd2 override-setting
set status enable
set server "172.16.200.55"
set use-management-vdom enable
set facility local6
end
c. For syslog3, enable an override syslog server and enable use-management-vdom:
config log syslogd3 override-setting
set status enable
set server "10.6.30.22"
set use-management-vdom enable
end
3. For the management VDOM, configure an override syslog server:
config log syslogd override-setting
set status enable
set server "172.16.200.55"
set facility local6
end
Logging MAC address flapping events
FortiOS logs MAC address flapping events when a device’s MAC address is learned on different interfaces within the
MAC address table in transparent mode. The log provides comprehensive details about the event, such as the specific
MAC address involved, the ports where the flapping occurred, and the exact time of the event. This enhancement assists
network administrators in quickly identifying and addressing related issues, thereby enhancing network stability and
performance.
FortiOS 7.6.2 Administration Guide 3910
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,910
|
Log and Report
Example
In this example, the end user initiates internet traffic from PC1, which has an authentic MAC address. Subsequently, the
user generates internet traffic from PC2 using a packet manipulation tool, such as Scapy, but with the spoofed MAC
address of PC1. This event is successfully identified and logged by FortiGate running in transparent (TP) mode.
To view the logs:
# execute log filter category 1
# execute log filter start-line 1
# execute log display
36 logs found.
10 logs returned.
1: date=2024-03-26 time=14:05:33 eventtime=1711487133347757075 tz="-0700" logid="0100022970"
type="event" subtype="system" level="information" vd="vdom1" logdesc="MAC flapping"
service="kernel" mac="00:0c:29:90:21:c3" src_int="port1" msg="The incoming port of MAC
address 00:0c:29:90:21:c3 has been switched from port2 to port1"
Incorporating endpoint device data in the web filter UTM logs
Endpoint device data, including hostname and MAC address, have been incorporated in the web filter UTM logs.
Endpoint device data can be incorporated in the logs using the following:
config log setting
set extended-utm-log {enable | disable}
end
To incorporate endpoint device data in the web filter UTM logs, ensure a firewall policy with a
web filter profile is configured and Device detection is configured on the interfaces. Device
detection can be configured in Network > Interfaces and the CLI.
When this command is enabled, the srcmac and srcname fields are included in the web filter UTM logs:
1: date=2024-04-04 time=09:34:31 eventtime=1712248470720798942 tz="-0700" logid="0316013056"
type="utm" subtype="webfilter" eventtype="ftgd_blk" level="warning" vd="vdom1" policyid=1
poluuid="9f550138-ed67-51ee-b593-e4c9c3cd549f" policytype="policy" sessionid=20910
srcip=10.1.100.123 srcport=59705 srccountry="Reserved" srcintf="port2"
srcintfrole="undefined" srcuuid="04df25b6-ed67-51ee-3006-8c2d12813f90"
srcmac="00:0c:29:06:7e:5b" srcname="AVPC3" dstip=52.201.199.27 dstport=443
dstcountry="United States" dstintf="port1" dstintfrole="undefined" dstuuid="04df25b6-ed67-
FortiOS 7.6.2 Administration Guide 3911
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,911
|
Log and Report
51ee-3006-8c2d12813f90" proto=6 httpmethod="GET" service="HTTPS" hostname="www.httpbin.org"
agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KH" profile="webfilter"
action="blocked" reqtype="referral" url="https://www.httpbin.org/favicon.ico"
referralurl="https://www.httpbin.org/" sentbyte=2088 rcvdbyte=5709 direction="outgoing"
msg="URL belongs to a denied category in policy" ratemethod="domain" cat=52
catdesc="Information Technology"
Likewise, the Device column is populated with the endpoint hostname information in the Log & Report > Security Events
> Logs table:
When this command is disabled, the new fields are excluded from the web filter UTM logs and
the Device column does not display the client hostname information. The command is
disabled by default.
Logging detection of duplicate IPv4 addresses
FortiOS can log each detection of duplicate IPv4 addresses on physical interfaces and VLAN interfaces in the event log
under the new log ID 32701.
config system global
set ip-conflict-detection {enable | disable}
end
set ip-conflict-detection
{enable | disable}
Enable/disable logging of IPv4 address conflict detection.
FortiOS uses the following methods to detect duplicate IPv4 addresses, and can generate a log for each detection:
Detection method Description
Active Detection of duplicate physical and VLAN IPv4 addresses on FortiGate is
triggered when:
l FortiOS starts
l The miglogd daemon restarts
l A new physical interface is created
l A physical interface status changes to up
l A physical interface configuration changes
l The diagnose test app miglogd 55 command is run
Passive Detection of duplicate IPv4 address on a client is triggered when a device
connected to FortiGate attempts to use an IPv4 address that is already in use.
FortiOS 7.6.2 Administration Guide 3912
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,912
|
Log and Report
Detection method Description
FortiOS identifies duplicate IPv4 addresses by monitoring the Gratuitous
ARP packet. When the source IP in the Gratuitous ARP packet is duplicated in the
cache, but the source MAC address is different, then the IP address is considered
a duplicate.
In addition to physical interfaces, passive detection is also valid for VLAN.
In addition, a packet can be sent to the SNMP host when the SNMP event is set to interface.
The config system snmp community command includes a new interface event:
config system snmp community
edit 1
set name "test"
config hosts
edit 1
set ip 172.18.71.107 255.255.255.0
next
end
config hosts6
edit 1
next
end
set events {interface}
next
end
set events {interface} Send a trap for interface events.
The following new debug commands are also available:
diagnose test application
miglogd 54
Shows the cache for IPv4 address conflict detection.
diagnose test application
miglogd 55
Executes a IPv4 address conflict detection.
To enable logging of IPv4 address conflicts:
config system global
set ip-conflict-detection enable
end
To trigger an active detection and log of IPv4 conflicts:
1. In FortiOS, go to Network > Interfaces, and double-click an interface, such as wan1, to open it for editing.
2. In the IP/Netmask box, change the IP address from 172.16.200.2/24 to 172.16.200.55/24. The following warning is
displayed: This IP address is already in use by device <MAC address>.
FortiOS 7.6.2 Administration Guide 3913
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,913
|
Log and Report
3. Go to Log & Report > System Events. A Duplicate IP address log entry is displayed.
The same information is visible in the raw log
date=2024-04-30 time=18:08:56 eventtime=1714525736800388800 tz="-0700"
logid="0100032701" type="event" subtype="system" level="error" vd="vdom1"
logdesc="Detected IP conflicts on FGT interfaces." msg="Duplicate IP address
172.16.200.55 of MAC 02:42:ac:10:c8:37 was detected on interface wan1, also in use by
wan1 (e8:1c:ba:f2:65:b6)"
FortiOS 7.6.2 Administration Guide 3914
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,914
|
Log and Report
To trigger a passive detection and log of IPv4 conflicts:
1. On a client, change the interface. For example, change the interface from 192.168.5.44 to 192.168.5.100/24.
2. Go to Log & Report > System Events. A Duplicate IP address log entry is displayed.
The same information is visible in the raw log
date=2024-04-30 time=18:00:08 eventtime=1714525207888886460 tz="-0700"
logid="0100032701" type="event" subtype="system" level="error" vd="vdom1"
logdesc="Detected IP conflicts on FGT interfaces." msg="Duplicate IP address
192.168.5.100 of MAC 00:0c:29:d3:30:4e was detected on interface dmz, also in use by
dmzVLAN (e8:1c:ba:f2:65:b4)"
To configure SNMP traps for interfaces:
1. Configure an SNMP host and set up an event trap for interface.
config system snmp community
edit 1
set name "test"
FortiOS 7.6.2 Administration Guide 3915
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,915
|
Log and Report
config hosts
edit 1
set ip 172.16.200.55 255.255.255.0
next
end
set events interface
next
end
To show the IPv4 address conflict detection cache:
# diagnose test application miglogd 54
index IPv4 address MAC dev vlanid
50 10.10.100.2 00:00:00:00:00:00 Loopback2
58 192.168.5.44 e8:1c:ba:f2:65:b4 dmzVLAN 50
48 10.255.1.1 00:00:00:00:00:00 fortilink
51 10.1.10.3 00:00:00:00:00:00 Loopback3
8 10.1.100.2 e8:1c:ba:f2:65:b7 wan2
49 10.10.10.2 00:00:00:00:00:00 loopback
6 10.6.30.107 e8:1c:ba:f2:65:b5 mgmt
52 192.168.100.99 e8:1c:ba:f2:65:bb lan
23 10.2.2.2 e8:1c:ba:f2:65:c6 x1
7 172.16.200.2 e8:1c:ba:f2:65:b6 wan1
To execute an IPv4 address conflict detection:
# diagnose test application miglogd 55
Sending probe for 10.10.100.2 via Loopback2.
Sending probe for 192.168.5.44 via dmzVLAN.
Sending probe for 10.255.1.1 via fortilink.
Sending probe for 10.1.10.3 via Loopback3.
Sending probe for 10.1.100.2 via wan2.
Sending probe for 10.10.10.2 via loopback.
Sending probe for 10.6.30.107 via mgmt.
Sending probe for 192.168.100.99 via lan.
Sending probe for 10.2.2.2 via x1.
Sending probe for 172.16.200.2 via wan1.
To verify the trap has been sent:
# diagnose debug application snmp -1
# diagnose debug enable
snmpd: queue is 2 entries long.
snmpd: queueing trap 8008000000000000@4295121097 (4295121097)
snmpd: queue is 3 entries long.
snmpd: dequeueing trap 8008000000000000@4295121097 (4295121097)
snmpd: sending to hosts: interface(1601)
snmpd: attempting v1 trap: interface(1601)
snmpd: trap from (172.16.200.1 -> 172.16.200.55)
snmpd: trap send(172.16.200.1:162 -> 172.16.200.55:162) bytes sent=264 total=264
snmpd: attempting v2c trap: interface(1601)
snmpd: get : system.3.0 -> () -> 0
snmpd: trap send(172.16.200.1:162 -> 172.16.200.55:162) bytes sent=288 total=288
FortiOS 7.6.2 Administration Guide 3916
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,916
|
Log and Report
Sample logs by log type
This topic provides a sample raw log for each subtype and the configuration requirements.
Traffic Logs > Forward Traffic
Log configuration requirements
config firewall policy
edit 1
set srcintf "port12"
set dstintf "port11"
set srcaddr "all"
set dstaddr "all"
set action accept
set schedule "always"
set service "ALL"
set utm-status enable
set logtraffic all
set application-list "g-default"
set ssl-ssh-profile "certificate-inspection"
set nat enable
next
end
Sample log
date=2019-05-10 time=11:37:47 logid="0000000013" type="traffic" subtype="forward"
level="notice" vd="vdom1" eventtime=1557513467369913239 srcip=10.1.100.11 srcport=58012
srcintf="port12" srcintfrole="undefined" dstip=23.59.154.35 dstport=80 dstintf="port11"
dstintfrole="undefined" srcuuid="ae28f494-5735-51e9-f247-d1d2ce663f4b" dstuuid="ae28f494-
5735-51e9-f247-d1d2ce663f4b" poluuid="ccb269e0-5735-51e9-a218-a397dd08b7eb" sessionid=105048
proto=6 action="close" policyid=1 policytype="policy" service="HTTP" dstcountry="Canada"
srccountry="Reserved" trandisp="snat" transip=172.16.200.2 transport=58012 appid=34050
app="HTTP.BROWSER_Firefox" appcat="Web.Client" apprisk="elevated" applist="g-default"
duration=116 sentbyte=1188 rcvdbyte=1224 sentpkt=17 rcvdpkt=16 utmaction="allow" countapp=1
osname="Ubuntu" mastersrcmac="a2:e9:00:ec:40:01" srcmac="a2:e9:00:ec:40:01" srcserver=0
utmref=65500-742
Traffic Logs > Local Traffic
Log configuration requirements
config log setting
set local-in-allow enable
set local-in-deny-unicast enable
set local-in-deny-broadcast enable
set local-out enable
end
FortiOS 7.6.2 Administration Guide 3917
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,917
|
Log and Report
Sample log
date=2019-05-10 time=11:50:48 logid="0001000014" type="traffic" subtype="local"
level="notice" vd="vdom1" eventtime=1557514248379911176 srcip=172.16.200.254 srcport=62024
srcintf="port11" srcintfrole="undefined" dstip=172.16.200.2 dstport=443 dstintf="vdom1"
dstintfrole="undefined" sessionid=107478 proto=6 action="server-rst" policyid=0
policytype="local-in-policy" service="HTTPS" dstcountry="Reserved" srccountry="Reserved"
trandisp="noop" app="Web Management(HTTPS)" duration=5 sentbyte=1247 rcvdbyte=1719 sentpkt=5
rcvdpkt=6 appcat="unscanned"
Traffic Logs > Multicast Traffic
Log configuration requirements
config firewall multicast-policy
edit 1
set dstaddr 230-1-0-0
set dstintf port3
set srcaddr 172-16-200-0
set srcintf port25
set action accept
set logtraffic all
next
end
config system setting
set multicast-forward enable
end
Sample log
date=2019-03-31 time=06:42:54 logid="0002000012" type="traffic" subtype="multicast"
level="notice" vd="vdom1" eventtime=1554039772 srcip=172.16.200.55 srcport=60660
srcintf="port25" srcintfrole="undefined" dstip=230.1.1.2 dstport=7878 dstintf="port3"
dstintfrole="undefined" sessionid=1162 proto=17 action="accept" policyid=1
policytype="multicast-policy" service="udp/7878" dstcountry="Reserved" srccountry="Reserved"
trandisp="noop" duration=22 sentbyte=5940 rcvdbyte=0 sentpkt=11 rcvdpkt=0 appcat="unscanned"
Traffic Logs > Sniffer Traffic
Log configuration requirements
config firewall sniffer
edit 3
set logtraffic all
set interface "port1"
set ips-sensor-status enable
set ips-sensor "sniffer-profile"
next
end
FortiOS 7.6.2 Administration Guide 3918
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,918
|
Log and Report
Sample log
date=2019-05-10 time=14:18:54 logid="0004000017" type="traffic" subtype="sniffer"
level="notice" vd="root" eventtime=1557523134021045897 srcip=208.91.114.4 srcport=50463
srcintf="port1" srcintfrole="undefined" dstip=104.80.88.154 dstport=443 dstintf="port1"
dstintfrole="undefined" sessionid=2193276 proto=6 action="accept" policyid=3
policytype="sniffer" service="HTTPS" dstcountry="United States" srccountry="Canada"
trandisp="snat" transip=0.0.0.0 transport=0 duration=10 sentbyte=0 rcvdbyte=0 sentpkt=0
rcvdpkt=0 appcat="unscanned" utmaction="allow" countips=1 crscore=5 craction=32768
sentdelta=0 rcvddelta=0 utmref=65162-7772
config system global
set log-uuid-address enable
end
config firewall sniffer
edit 1
set logtraffic all
set ipv6 enable
set interface "port3"
set ip-threatfeed-status enable
set ip-threatfeed "g-source"
next
end
Sample log
1: date=2021-01-26 time=15:51:37 eventtime=1611705097880421908 tz="-0800" logid="0004000017"
type="traffic" subtype="sniffer" level="notice" vd="vd1" srcip=10.1.100.12 srcport=34604
srcintf="port3" srcintfrole="undefined" dstip=172.16.200.55 dstport=80 dstintf="port3"
dstintfrole="undefined" srcthreatfeed="g-source" srccountry="Reserved" dstcountry="Reserved"
sessionid=30384 proto=6 action="accept" policyid=1 policytype="sniffer" service="HTTP"
trandisp="snat" transip=0.0.0.0 transport=0 duration=0 sentbyte=0 rcvdbyte=0 sentpkt=0
rcvdpkt=0 appcat="unscanned"
Event Logs > SD-WAN Events
Log configuration requirements
config log eventfilter
set event enable
set sdwan enable
end
Sample log
date=2020-03-29 time=16:41:30 logid="0113022923" type="event" subtype="sdwan" level="notice"
vd="root" eventtime=1585525290513555981 tz="-0700" logdesc="Virtual WAN Link status"
eventtype="Health Check" healthcheck="ping1" slatargetid=1 oldvalue="1" newvalue="2"
msg="Number of pass member changed."
date=2020-03-29 time=16:51:27 logid="0113022925" type="event" subtype="sdwan" level="notice"
vd="root" eventtime=1585525888177637570 tz="-0700" logdesc="Virtual WAN Link SLA
information" eventtype="SLA" healthcheck="ping1" slatargetid=1 interface="R150" status="up"
latency="0.013" jitter="0.001" packetloss="100.000%" inbandwidth="0kbps"
FortiOS 7.6.2 Administration Guide 3919
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,919
|
Log and Report
outbandwidth="0kbps" bibandwidth="0kbps" slamap="0x0" metric="packetloss" msg="Health Check
SLA status. SLA failed due to being over the performance metric threshold."
Event Logs > System Events
Log configuration requirements
config log eventfilter
set event enable
set system enable
end
Sample log
date=2019-05-13 time=11:20:54 logid="0100032001" type="event" subtype="system"
level="information" vd="vdom1" eventtime=1557771654587081441 logdesc="Admin login
successful" sn="1557771654" user="admin" ui="ssh(172.16.200.254)" method="ssh"
srcip=172.16.200.254 dstip=172.16.200.2 action="login" status="success" reason="none"
profile="super_admin" msg="Administrator admin logged in successfully from ssh
(172.16.200.254)"
Event Logs > Router Events
Log configuration requirements
config log eventfilter
set event enable
set router enable
end
config router bgp
set log-neighbour-changes enable
end
config router ospf
set log-neighbour-changes enable
end
Sample log
date=2019-05-13 time=14:12:26 logid="0103020301" type="event" subtype="router"
level="warning" vd="root" eventtime=1557781946677737955 logdesc="Routing log" msg="OSPF:
RECV[Hello]: From 31.1.1.1 via port9:172.16.200.1: Invalid Area ID 0.0.0.0"
Event Logs > VPN Events
Log configuration requirements
config log eventfilter
set event enable
set vpn enable
end
FortiOS 7.6.2 Administration Guide 3920
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,920
|
Log and Report
Sample log
date=2019-05-13 time=14:21:42 logid="0101037127" type="event" subtype="vpn" level="notice"
vd="root" eventtime=1557782502722231889 logdesc="Progress IPsec phase 1" msg="progress IPsec
phase 1" action="negotiate" remip=50.1.1.101 locip=50.1.1.100 remport=500 locport=500
outintf="port14" cookies="9091f4d4837ea71c/0000000000000000" user="N/A" group="N/A"
xauthuser="N/A" xauthgroup="N/A" assignip=N/A vpntunnel="test" status="success" init="local"
mode="main" dir="outbound" stage=1 role="initiator" result="OK"
Event Logs > User Events
Log configuration requirements
config log eventfilter
set event enable
set user enable
end
Sample log
date=2019-05-13 time=15:55:56 logid="0102043008" type="event" subtype="user" level="notice"
vd="root" eventtime=1557788156913809277 logdesc="Authentication success" srcip=10.1.100.11
dstip=172.16.200.55 policyid=1 interface="port10" user="bob" group="local-group1"
authproto="TELNET(10.1.100.11)" action="authentication" status="success" reason="N/A"
msg="User bob succeeded in authentication"
Event Logs > Endpoint Events
Log configuration requirements
config log eventfilter
set event enable
set endpoint enable
end
Sample log
date=2019-05-14 time=08:32:13 logid="0107045057" type="event" subtype="endpoint"
level="information" vd="root" eventtime=1557847933900764210 logdesc="FortiClient connection
added" action="add" status="success" license_limit="unlimited" used_for_type=4 connection_
type="sslvpn" count=1 user="skubas" ip=172.18.64.250 name="VAN-200957-PC"
fctuid="52C66FE08F724FE0B116DAD5062C96CD" msg="Add a FortiClient Connection."
date=2019-05-14 time=08:19:38 logid="0107045058" type="event" subtype="endpoint"
level="information" vd="root" eventtime=1557847179037488154 logdesc="FortiClient connection
closed" action="close" status="success" license_limit="unlimited" used_for_type=5
connection_type="sslvpn" count=1 user="skubas" ip=172.18.64.250 name="VAN-200957-PC"
fctuid="52C66FE08F724FE0B116DAD5062C96CD" msg="Close a FortiClient Connection."
FortiOS 7.6.2 Administration Guide 3921
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,921
|
Log and Report
Event Logs > HA Events
Log configuration requirements
config log eventfilter
set event enable
set ha enable
end
Sample log
date=2019-05-10 time=09:53:18 logid="0108037894" type="event" subtype="ha" level="critical"
vd="root" eventtime=1557507199208575235 logdesc="Virtual cluster member joined" msg="Virtual
cluster detected member join" vcluster=1 ha_group=0 sn="FG2K5E3916900286"
Event Logs > Security Rating Events
Log configuration requirements
config log eventfilter
set event enable
set security-rating enable
end
Sample log
date=2019-05-13 time=14:40:59 logid="0110052000" type="event" subtype="security-rating"
level="notice" vd="root" eventtime=1557783659536252389 logdesc="Security Rating summary"
auditid=1557783648 audittime=1557783659 auditscore="5.0" criticalcount=1 highcount=6
mediumcount=8 lowcount=0 passedcount=38
Event Logs > WAN Opt & Cache Events
Log configuration requirements
config log eventfilter
set event enable
set wan-opt enable
end
Sample log
date=2019-05-14 time=09:37:46 logid="0105048039" type="event" subtype="wad" level="error"
vd="root" eventtime=1557851867382676560 logdesc="SSL fatal alert sent" session_id=0
policyid=0 srcip=0.0.0.0 srcport=0 dstip=208.91.113.83 dstport=636 action="send" alert="2"
desc="certificate unknown" msg="SSL Alert sent"
date=2019-05-10 time=15:48:31 logid="0105048038" type="event" subtype="wad" level="error"
vd="root" eventtime=1557528511221374615 logdesc="SSL Fatal Alert received" session_
id=5f88ddd1 policyid=0 srcip=172.18.70.15 srcport=59880 dstip=91.189.89.223 dstport=443
action="receive" alert="2" desc="unknown ca" msg="SSL Alert received"
FortiOS 7.6.2 Administration Guide 3922
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,922
|
Log and Report
Event Logs > Wireless
Log configuration requirements
config log eventfilter
set event enable
set wireless-activity enable
end
config wireless-controller log
set status enable
end
Sample log
date=2019-05-13 time=11:30:08 logid="0104043568" type="event" subtype="wireless"
level="warning" vd="vdom1" eventtime=1557772208134721423 logdesc="Fake AP on air"
ssid="fortinet" bssid="90:6c:ac:89:e1:fa" aptype=0 rate=130 radioband="802.11n" channel=6
action="fake-ap-on-air" manuf="Fortinet, Inc." security="WPA2 Personal" encryption="AES"
signal=-93 noise=-95 live=353938 age=505 onwire="no" detectionmethod="N/A" stamac="N/A"
apscan="N/A" sndetected="N/A" radioiddetected=0 stacount=0 snclosest="FP320C3X17001909"
radioidclosest=0 apstatus=0 msg="Fake AP On-air fortinet 90:6c:ac:89:e1:fa chan 6 live
353938 age 505"
Event Logs > SDN Connector
Log configuration requirements
config log eventfilter
set event enable
set connector enable
end
Sample log
date=2019-05-13 time=16:09:43 logid="0112053200" type="event" subtype="connector"
level="information" vd="root" eventtime=1557788982 logdesc="IP address added" cfgobj="aws1"
action="object-add" addr="54.210.36.196" cldobjid="i-0fe5a1ef16bb94796" netid="vpc-97e81cee"
msg="connector object discovered in addr-obj aws1, 54.210.36.196"
date=2019-05-13 time=16:09:43 logid="0112053201" type="event" subtype="connector"
level="information" vd="root" eventtime=1557788982 logdesc="IP address removed"
cfgobj="aws1" action="object-remove" addr="172.31.31.101" cldobjid="i-0fe5a1ef16bb94796"
netid="vpc-97e81cee" msg="connector object removed in addr-obj aws1, 172.31.31.101"
Event Logs > FortiExtender Events
Log configuration requirements
config log eventfilter
set event enable
set fortiextender enable
end
FortiOS 7.6.2 Administration Guide 3923
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,923
|
Log and Report
Sample log
date=2019-02-20 time=09:57:22 logid="0111046400" type="event" subtype="fortiextender"
level="notice" vd="root" eventtime=1550685442 logdesc="FortiExtender system activity"
action="FortiExtender Authorized" msg="ext SN:FX04DN4N16002352 authorized"
date=2019-02-20 time=09:51:42 logid="0111046401" type="event" subtype="fortiextender"
level="notice" vd="root" eventtime=1550685102 logdesc="FortiExtender controller activity"
sn="FX04DN4N16002352" ip=11.11.11.2 action="ext session-deauthed" msg="ext
SN:FX04DN4N16002352 deauthorized"
date=2019-02-20 time=10:02:26 logid="0111046409" type="event" subtype="fortiextender"
level="information" vd="root" eventtime=1550685746 logdesc="Remote FortiExtender info
activity" sn="FX04DN4N16002352" ip=11.11.11.2 action="Cellular Connected"
imei="359376060442770" imsi="302720502331361" iccid="89302720403038146410"
phonenumber="+16045067526" carrier="Rogers" plan="Rogers-plan" apn="N/A" service="LTE"
msg="FX04DN4N16002352 STATE: sim with imsi:302720502331361 in slot:2 on carrier:Rogers
connected"
date=2019-02-20 time=10:33:57 logid="0111046407" type="event" subtype="fortiextender"
level="warning" vd="root" eventtime=1550687636 logdesc="Remote FortiExtender warning
activity" sn="FX04DN4N16002352" ip=11.11.11.2 action="Cellular Disconnected"
imei="359376060442770" imsi="N/A" iccid="N/A" phonenumber="N/A" carrier="N/A" plan="N/A"
apn="N/A" service="LTE" msg="FX04DN4N16002352 STATE: sim with imsi: in slot:2 on carrier:N/A
disconnected"
date=2019-02-20 time=10:02:24 logid="0111046409" type="event" subtype="fortiextender"
level="information" vd="root" eventtime=1550685744 logdesc="Remote FortiExtender info
activity" sn="FX04DN4N16002352" ip=11.11.11.2 action="Cellular Connecting"
imei="359376060442770" imsi="302720502331361" iccid="89302720403038146410"
phonenumber="+16045067526" carrier="Rogers" plan="Rogers-plan" apn="N/A" service="N/A"
msg="FX04DN4N16002352 STATE: sim with imsi:302720502331361 in slot:2 on carrier:Rogers
connecting
date=2019-02-20 time=10:47:19 logid="0111046407" type="event" subtype="fortiextender"
level="warning" vd="root" eventtime=1550688438 logdesc="Remote FortiExtender warning
activity" sn="FX04DN4N16002352" ip=11.11.11.2 action="SIM Change" imei="N/A" slot=2
msg="FX04DN4N16002352 SIM: SIM2 is inserted"
date=2019-02-20 time=10:57:50 logid="0111046407" type="event" subtype="fortiextender"
level="warning" vd="root" eventtime=1550689069 logdesc="Remote FortiExtender warning
activity" sn="FX04DN4N16002352" ip=11.11.11.2 action="SIM Change" imei="359376060442770"
slot=1 msg="FX04DN4N16002352 SIM: SIM2 is plucked out"
date=2019-02-20 time=12:02:24 logid="0111046407" type="event" subtype="fortiextender"
level="warning" vd="root" eventtime=1550692942 logdesc="Remote FortiExtender warning
activity" sn="FX04DN4N16002352" ip=11.11.11.2 action="SIM Switch" imei="359376060442770"
reason="sim-switch can't take effect due to unavailability of 2 sim cards"
msg="FX04DN4N16002352 SIM: sim-switch can't take effect due to unavailability of 2 sim
cards"
date=2019-02-19 time=18:08:46 logid="0111046409" type="event" subtype="fortiextender"
level="information" vd="root" eventtime=1550628524 logdesc="Remote FortiExtender info
activity" sn="FX04DN4N16002352" ip=11.11.11.2 action="Cellular Signal Statistics"
imei="359376060442770" imsi="302720502331361" iccid="89302720403038146410"
phonenumber="+16045067526" carrier="Rogers" plan="Rogers-plan" service="LTE" sinr="7.0 dB"
rsrp="-89 dBm" rsrq="-16 dB" signalstrength="92 dBm" rssi="-54" temperature="40 C" apn="N/A"
msg="FX04DN4N16002352 INFO: LTE RSSI=-54dBm,RSRP=-89dBm,RSRQ=-
16dB,SINR=7.0dB,BAND=B2,CELLID=061C700F,BW=15MHz,RXCH=1025,TXCH=19025,TAC=8AAC,TEMPERATURE=4
0 C"
FortiOS 7.6.2 Administration Guide 3924
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,924
|
Log and Report
date=2019-02-19 time=18:09:46 logid="0111046409" type="event" subtype="fortiextender"
level="information" vd="root" eventtime=1550628585 logdesc="Remote FortiExtender info
activity" sn="FX04DN4N16002352" ip=11.11.11.2 action="Cellular Data Statistics"
imei="359376060442770" imsi="302720502331361" iccid="89302720403038146410"
phonenumber="+16045067526" carrier="Rogers" plan="Rogers-plan" service="LTE" rcvdbyte=7760
sentbyte=3315 msg="FX04DN4N16002352 INFO: SIM2 LTE, rx=7760, tx=3315, rx_diff=2538, tx_
diff=567"
Event Logs > FortiSwitch Events
Log configuration requirements
config log eventfilter
set event enable
set switch-controller enable
end
Sample log
date=2020-09-28 time=15:37:02 eventtime=1601332622257714795 tz="-0700" logid="0114032695"
type="event" subtype="switch-controller" level="notice" vd="vdom1" logdesc="FortiSwitch
link" user="Fortilink" sn="S248EPTF18001384" name="S248EPTF18001384" msg="port51 Module reinitialized to recover from ERROR state."
date=2020-09-28 time=15:37:02 eventtime=1601332622255619520 tz="-0700" logid="0114032697"
type="event" subtype="switch-controller" level="warning" vd="vdom1" logdesc="FortiSwitch
switch" user="Fortilink" sn="S248EPTF18001384" name="S248EPTF18001384" msg="FortiLink:
internal echo reply timed out"
date=2020-09-28 time=15:37:01 eventtime=1601332621664809633 tz="-0700" logid="0114032605"
type="event" subtype="switch-controller" level="information" vd="vdom1" logdesc="SwitchController Tunnel Up" user="Switch-Controller" ui="cu_acd" sn="S248EPTF18001384"
name="S248EPTF18001384" msg="CAPWAP Tunnel Up (169.254.1.3)"
date=2020-09-28 time=15:36:59 eventtime=1601332619501461995 tz="-0700" logid="0114022904"
type="event" subtype="switch-controller" level="notice" vd="vdom1" logdesc="CAPUTP session
status notification" user="Switch-Controller" ui="cu_acd" sn="S248EPTF18001384"
name="S248EPTF18001384" msg="S248EPTF18001384 Connected via session join" action="sessionjoin" srcip=169.254.1.3
date=2020-09-28 time=15:36:26 eventtime=1601332560434649361 tz="-0700" logid="0114032601"
type="event" subtype="switch-controller" level="information" vd="vdom1" logdesc="SwitchController discovered" user="daemon_admin" ui="cmdbsvr" sn="S524DN4K16000116"
name="S524DN4K16000116" msg="S524DN4K16000116 Discovered"
date=2020-09-28 time=15:36:26 eventtime=1601332560405228924 tz="-0700" logid="0114032601"
type="event" subtype="switch-controller" level="information" vd="vdom1" logdesc="SwitchController discovered" user="daemon_admin" ui="cmdbsvr" sn="S248EPTF18001827"
name="S248EPTF18001827" msg="S248EPTF18001827 Discovered"
date=2020-09-28 time=15:36:26 eventtime=1601332560336851635 tz="-0700" logid="0114032601"
type="event" subtype="switch-controller" level="information" vd="vdom1" logdesc="SwitchController discovered" user="daemon_admin" ui="cmdbsvr" sn="S248EPTF18001384"
name="S248EPTF18001384" msg="S248EPTF18001384 Discovered"
FortiOS 7.6.2 Administration Guide 3925
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,925
|
Log and Report
Event Logs > REST API Events
Log configuration requirements
config log setting
set rest-api-set enable
set rest-api-get enable
end
Sample log
date=2022-02-02 time=15:52:09 eventtime=1643845930263415066 tz="-0800" logid="0116047301"
type="event" subtype="rest-api" level="information" vd="root" logdesc="REST API request
success" user="admin" ui="GUI(192.168.1.69)" method="GET" path="system.usb-log" status="200"
url="/api/v2/monitor/system/usb-log?vdom=root"
date=2022-02-02 time=15:52:06 eventtime=1643845926774931021 tz="-0800" logid="0116047301"
type="event" subtype="rest-api" level="information" vd="root" logdesc="REST API request
success" user="admin" ui="GUI(192.168.1.69)" method="GET" path="license.status" status="200"
url="/api/v2/monitor/license/status?vdom=root"
date=2022-02-02 time=15:52:06 eventtime=1643845926764579729 tz="-0800" logid="0116047301"
type="event" subtype="rest-api" level="information" vd="root" logdesc="REST API request
success" user="admin" ui="GUI(192.168.1.69)" method="GET" path="log.fortianalyzer.setting"
status="200" url="/api/v2/cmdb/log.fortianalyzer/setting?vdom=root"
date=2022-02-02 time=15:52:06 eventtime=1643845926762372766 tz="-0800" logid="0116047301"
type="event" subtype="rest-api" level="information" vd="root" logdesc="REST API request
success" user="admin" ui="GUI(192.168.1.69)" method="GET" path="system.sandbox"
action="connection" status="200" url="/api/v2/monitor/system/sandbox/connection?vdom=root"
date=2022-02-02 time=15:52:06 eventtime=1643845926755869998 tz="-0800" logid="0116047301"
type="event" subtype="rest-api" level="information" vd="root" logdesc="REST API request
success" user="admin" ui="GUI(192.168.1.69)" method="GET" path="system.firmware"
status="200" url="/api/v2/monitor/system/firmware?vdom=root"
Event Logs > IOC Detection
Log configuration requirements
config log setting
set local-out enable
set local-out-ioc-detection enable
end
Sample log
date=2021-12-20 time=16:43:54 eventtime=1640047434839814226 tz="-0800" logid="0100020214"
type="event" subtype="system" level="warning" vd="root" logdesc="Locally generated traffic
goes to IoC location" srcip=172.16.200.2 srcport=18047 dstip=223.205.1.54 dstport=514
session_id=23563 proto=6
# Corresponding Traffic Log #
date=2021-12-20 time=16:45:18 eventtime=1640047518959313316 tz="-0800" logid="0001000014"
type="traffic" subtype="local" level="notice" vd="root" srcip=172.16.200.2 srcport=18047
srcintf="unknown-0" srcintfrole="undefined" dstip=223.205.1.54 dstport=514 dstintf="port2"
FortiOS 7.6.2 Administration Guide 3926
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,926
|
Log and Report
dstintfrole="undefined" srccountry="Reserved" dstcountry="Thailand" sessionid=23632 proto=6
action="timeout" policyid=0 service="tcp/514" trandisp="noop" app="tcp/514" duration=17
sentbyte=240 rcvdbyte=0 sentpkt=4 rcvdpkt=0 appcat="unscanned" dsthwvendor="Fortinet"
masterdstmac="e8:1c:ba:c2:86:63" dstmac="e8:1c:ba:c2:86:63" dstserver=0
Security Logs > Antivirus
Log configuration requirements
config antivirus profile
edit "test-av"
config http
set av-scan block
end
set av-virus-log enable
set av-block-log enable
next
end
config firewall policy
edit 1
set srcintf "port12"
set dstintf "port11"
set srcaddr "all"
set dstaddr "all"
set action accept
set schedule "always"
set service "ALL"
set utm-status enable
set av-profile "test-av"
set logtraffic utm
set nat enable
next
end
Sample log
date=2019-05-13 time=11:45:03 logid="0211008192" type="utm" subtype="virus"
eventtype="infected" level="warning" vd="vdom1" eventtime=1557773103767393505 msg="File is
infected." action="blocked" service="HTTP" sessionid=359260 srcip=10.1.100.11
dstip=172.16.200.55 srcport=60446 dstport=80 srcintf="port12" srcintfrole="undefined"
dstintf="port11" dstintfrole="undefined" policyid=4 proto=6 direction="incoming"
filename="eicar.com" quarskip="File-was-not-quarantined." virus="EICAR_TEST_FILE"
dtype="Virus" ref="http://www.fortinet.com/ve?vn=EICAR_TEST_FILE" virusid=2172
url="http://172.16.200.55/virus/eicar.com" profile="g-default" agent="curl/7.47.0"
analyticscksum="275a021bbfb6489e54d471899f7db9d1663fc695ec2fe2a2c4538aabf651fd0f"
analyticssubmit="false" crscore=50 craction=2 crlevel="critical"
# Corresponding Traffic Log #
date=2019-05-13 time=11:45:04 logid="0000000013" type="traffic" subtype="forward"
level="notice" vd="vdom1" eventtime=1557773104815101919 srcip=10.1.100.11 srcport=60446
srcintf="port12" srcintfrole="undefined" dstip=172.16.200.55 dstport=80 dstintf="port11"
dstintfrole="undefined" srcuuid="48420c8a-5c88-51e9-0424-a37f9e74621e" dstuuid="187d6f46-
5c86-51e9-70a0-fadcfc349c3e" poluuid="3888b41a-5c88-51e9-cb32-1c32c66b4edf" sessionid=359260
proto=6 action="close" policyid=4 policytype="policy" service="HTTP" dstcountry="Reserved"
srccountry="Reserved" trandisp="snat" transip=172.16.200.2 transport=60446 appid=15893
FortiOS 7.6.2 Administration Guide 3927
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,927
|
Log and Report
app="HTTP.BROWSER" appcat="Web.Client" apprisk="medium" applist="g-default" duration=1
sentbyte=412 rcvdbyte=2286 sentpkt=6 rcvdpkt=6 wanin=313 wanout=92 lanin=92 lanout=92
utmaction="block" countav=1 countapp=1 crscore=50 craction=2 osname="Ubuntu"
mastersrcmac="a2:e9:00:ec:40:01" srcmac="a2:e9:00:ec:40:01" srcserver=0 utmref=65497-770
Security Logs > Web Filter
Log configuration requirements
config webfilter profile
edit "test-webfilter"
set web-content-log enable
set web-filter-activex-log enable
set web-filter-command-block-log enable
set web-filter-cookie-log enable
set web-filter-applet-log enable
set web-filter-jscript-log enable
set web-filter-js-log enable
set web-filter-vbs-log enable
set web-filter-unknown-log enable
set web-filter-referer-log enable
set web-filter-cookie-removal-log enable
set web-url-log enable
set web-invalid-domain-log enable
set web-ftgd-err-log enable
set web-ftgd-quota-usage enable
next
end
config firewall policy
edit 1
set name "v4-out"
set srcintf "port12"
set dstintf "port11"
set srcaddr "all"
set dstaddr "all"
set action accept
set schedule "always"
set service "ALL"
set logtraffic utm
set utm-status enable
set webfilter-profile "test-webfilter"
set nat enable
next
end
Sample log
date=2019-05-13 time=16:29:45 logid="0316013056" type="utm" subtype="webfilter"
eventtype="ftgd_blk" level="warning" vd="vdom1" eventtime=1557790184975119738 policyid=1
sessionid=381780 srcip=10.1.100.11 srcport=44258 srcintf="port12" srcintfrole="undefined"
dstip=185.244.31.158 dstport=80 dstintf="port11" dstintfrole="undefined" proto=6
service="HTTP" hostname="morrishittu.ddns.net" profile="test-webfilter" action="blocked"
reqtype="direct" url="/" sentbyte=84 rcvdbyte=0 direction="outgoing" msg="URL belongs to a
FortiOS 7.6.2 Administration Guide 3928
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,928
|
Log and Report
denied category in policy" method="domain" cat=26 catdesc="Malicious Websites" crscore=30
craction=4194304 crlevel="high"
# Corresponding traffic log #
date=2019-05-13 time=16:29:50 logid="0000000013" type="traffic" subtype="forward"
level="notice" vd="vdom1" eventtime=1557790190452146185 srcip=10.1.100.11 srcport=44258
srcintf="port12" srcintfrole="undefined" dstip=185.244.31.158 dstport=80 dstintf="port11"
dstintfrole="undefined" srcuuid="ae28f494-5735-51e9-f247-d1d2ce663f4b" dstuuid="ae28f494-
5735-51e9-f247-d1d2ce663f4b" poluuid="ccb269e0-5735-51e9-a218-a397dd08b7eb" sessionid=381780
proto=6 action="close" policyid=1 policytype="policy" service="HTTP" dstcountry="Germany"
srccountry="Reserved" trandisp="snat" transip=172.16.200.2 transport=44258 duration=5
sentbyte=736 rcvdbyte=3138 sentpkt=14 rcvdpkt=5 appcat="unscanned" utmaction="block"
countweb=1 crscore=30 craction=4194304 osname="Ubuntu" mastersrcmac="a2:e9:00:ec:40:01"
srcmac="a2:e9:00:ec:40:01" srcserver=0 utmref=65497-796
Security Logs > DNS Query
Log configuration requirements
config dnsfilter profile
edit "dnsfilter_fgd"
config ftgd-dns
set options error-allow
end
set log-all-domain enable
set block-botnet enable
next
end
config firewall policy
edit 1
set srcintf "port12"
set dstintf "port11"
set srcaddr "all"
set dstaddr "all"
set action accept
set schedule "always"
set service "ALL"
set utm-status enable
set dnsfilter-profile "dnsfilter_fgd"
set logtraffic utm
set nat enable
next
end
Sample log
date=2019-05-15 time=15:05:49 logid="1501054802" type="utm" subtype="dns" eventtype="dnsresponse" level="notice" vd="vdom1" eventtime=1557957949740931155 policyid=1 sessionid=6887
srcip=10.1.100.22 srcport=50002 srcintf="port12" srcintfrole="undefined"
dstip=172.16.100.100 dstport=53 dstintf="port11" dstintfrole="undefined" proto=17
profile="dnsfilter_fgd" srcmac="a2:e9:00:ec:40:41" xid=57945 qname="changelogs.ubuntu.com"
qtype="AAAA" qtypeval=28 qclass="IN" ipaddr="2001:67c:1560:8008::11" msg="Domain is
monitored" action="pass" cat=52 catdesc="Information Technology"
FortiOS 7.6.2 Administration Guide 3929
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,929
|
Log and Report
date=2019-05-15 time=15:05:49 logid="1500054000" type="utm" subtype="dns" eventtype="dnsquery" level="information" vd="vdom1" eventtime=1557957949653103543 policyid=1
sessionid=6887 srcip=10.1.100.22 srcport=50002 srcintf="port12" srcintfrole="undefined"
dstip=172.16.100.100 dstport=53 dstintf="port11" dstintfrole="undefined" proto=17
profile="dnsfilter_fgd" srcmac="a2:e9:00:ec:40:41" xid=57945 qname="changelogs.ubuntu.com"
qtype="AAAA" qtypeval=28 qclass="IN"
# Corresponding traffic log #
date=2019-05-15 time=15:08:49 logid="0000000013" type="traffic" subtype="forward"
level="notice" vd="vdom1" eventtime=1557958129950003945 srcip=10.1.100.22 srcport=50002
srcintf="port12" srcintfrole="undefined" dstip=172.16.100.100 dstport=53 dstintf="port11"
dstintfrole="undefined" srcuuid="ae28f494-5735-51e9-f247-d1d2ce663f4b" dstuuid="ae28f494-
5735-51e9-f247-d1d2ce663f4b" poluuid="ccb269e0-5735-51e9-a218-a397dd08b7eb" sessionid=6887
proto=17 action="accept" policyid=1 policytype="policy" service="DNS" dstcountry="Reserved"
srccountry="Reserved" trandisp="snat" transip=172.16.200.2 transport=50002 duration=180
sentbyte=67 rcvdbyte=207 sentpkt=1 rcvdpkt=1 appcat="unscanned" utmaction="allow" countdns=1
osname="Linux" mastersrcmac="a2:e9:00:ec:40:41" srcmac="a2:e9:00:ec:40:41" srcserver=0
utmref=65495-306
Security Logs > Application Control
Log configuration requirements
# log enabled by default in application profile entry
config application list
edit "block-social.media"
set other-application-log enable
config entries
edit 1
set category 2 5 6 23
set log enable
next
end
next
end
config firewall policy
edit 1
set name "to_Internet"
set srcintf "port10"
set dstintf "port9"
set srcaddr "all"
set dstaddr "all"
set action accept
set schedule "always"
set service "ALL"
set utm-status enable
set logtraffic utm
set application-list "block-social.media"
set ssl-ssh-profile "deep-inspection"
set nat enable
next
end
FortiOS 7.6.2 Administration Guide 3930
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,930
|
Log and Report
Sample log
date=2019-05-15 time=18:03:36 logid="1059028704" type="utm" subtype="app-ctrl"
eventtype="app-ctrl-all" level="information" vd="root" eventtime=1557968615 appid=40568
srcip=10.1.100.22 dstip=195.8.215.136 srcport=50798 dstport=443 srcintf="port10"
srcintfrole="lan" dstintf="port9" dstintfrole="wan" proto=6 service="HTTPS"
direction="outgoing" policyid=1 sessionid=4414 applist="block-social.media"
appcat="Web.Client" app="HTTPS.BROWSER" action="pass" hostname="www.dailymotion.com"
incidentserialno=1962906680 url="/" msg="Web.Client: HTTPS.BROWSER," apprisk="medium"
scertcname="*.dailymotion.com" scertissuer="DigiCert SHA2 High Assurance Server CA"
date=2019-05-15 time=18:03:35 logid="1059028705" type="utm" subtype="app-ctrl"
eventtype="app-ctrl-all" level="warning" vd="root" eventtime=1557968615 appid=16072
srcip=10.1.100.22 dstip=195.8.215.136 srcport=50798 dstport=443 srcintf="port10"
srcintfrole="lan" dstintf="port9" dstintfrole="wan" proto=6 service="HTTPS"
direction="incoming" policyid=1 sessionid=4414 applist="block-social.media"
appcat="Video/Audio" app="Dailymotion" action="block" hostname="www.dailymotion.com"
incidentserialno=1962906682 url="/" msg="Video/Audio: Dailymotion," apprisk="elevated"
date=2019-05-15 time=18:03:35 logid="1059028705" type="utm" subtype="app-ctrl"
eventtype="app-ctrl-all" level="warning" vd="root" eventtime=1557968615 appid=16072
srcip=10.1.100.22 dstip=195.8.215.136 srcport=50798 dstport=443 srcintf="port10"
srcintfrole="lan" dstintf="port9" dstintfrole="wan" proto=6 service="HTTPS"
direction="incoming" policyid=1 sessionid=4414 applist="block-social.media"
appcat="Video/Audio" app="Dailymotion" action="block" hostname="www.dailymotion.com"
incidentserialno=1962906681 url="/" msg="Video/Audio: Dailymotion," apprisk="elevated"
# Corresponding Traffic Log # date=2019-05-15 time=18:03:41 logid="0000000013"
type="traffic" subtype="forward" level="notice" vd="root" eventtime=1557968619
srcip=10.1.100.22 srcport=50798 srcintf="port10" srcintfrole="lan" dstip=195.8.215.136
dstport=443 dstintf="port9" dstintfrole="wan" poluuid="d8ce7a90-7763-51e9-e2be-741294c96f31"
sessionid=4414 proto=6 action="client-rst" policyid=1 policytype="policy" service="HTTPS"
dstcountry="France" srccountry="Reserved" trandisp="snat" transip=172.16.200.10
transport=50798 appid=16072 app="Dailymotion" appcat="Video/Audio" apprisk="elevated"
applist="block-social.media" appact="drop-session" duration=5 sentbyte=1150 rcvdbyte=7039
sentpkt=13 utmaction="block" countapp=3 devtype="Unknown" devcategory="None"
mastersrcmac="00:0c:29:51:38:5e" srcmac="00:0c:29:51:38:5e" srcserver=0 utmref=0-330
Security Logs > Intrusion Prevention
Log configuration requirements
# log enabled by default in ips sensor
config ips sensor
edit "block-critical-ips"
config entries
edit 1
set severity critical
set status enable
set action block
set log enable
next
end
next
end
FortiOS 7.6.2 Administration Guide 3931
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,931
|
Log and Report
config firewall policy
edit 1
set name "to_Internet"
set srcintf "port10"
set dstintf "port9"
set srcaddr "all"
set dstaddr "all"
set action accept
set schedule "always"
set service "ALL"
set utm-status enable
set logtraffic utm
set ips-sensor "block-critical-ips"
set nat enable
next
end
Sample log
date=2019-05-15 time=17:56:41 logid="0419016384" type="utm" subtype="ips"
eventtype="signature" level="alert" vd="root" eventtime=1557968201 severity="critical"
srcip=10.1.100.22 srccountry="Reserved" dstip=172.16.200.55 srcintf="port10"
srcintfrole="lan" dstintf="port9" dstintfrole="wan" sessionid=4017 action="dropped" proto=6
service="HTTP" policyid=1 attack="Adobe.Flash.newfunction.Handling.Code.Execution"
srcport=46810 dstport=80 hostname="172.16.200.55" url="/ips/sig1.pdf" direction="incoming"
attackid=23305 profile="block-critical-ips" ref="http://www.fortinet.com/ids/VID23305"
incidentserialno=582633933 msg="applications3:
Adobe.Flash.newfunction.Handling.Code.Execution," crscore=50 craction=4096
crlevel="critical"
# Corresponding Traffic Log # date=2019-05-15 time=17:58:10 logid="0000000013"
type="traffic" subtype="forward" level="notice" vd="root" eventtime=1557968289
srcip=10.1.100.22 srcport=46810 srcintf="port10" srcintfrole="lan" dstip=172.16.200.55
dstport=80 dstintf="port9" dstintfrole="wan" poluuid="d8ce7a90-7763-51e9-e2be-741294c96f31"
sessionid=4017 proto=6 action="close" policyid=1 policytype="policy" service="HTTP"
dstcountry="Reserved" srccountry="Reserved" trandisp="snat" transip=172.16.200.10
transport=46810 duration=89 sentbyte=565 rcvdbyte=9112 sentpkt=9 rcvdpkt=8
appcat="unscanned" utmaction="block" countips=1 crscore=50 craction=4096 devtype="Unknown"
devcategory="None" mastersrcmac="00:0c:29:51:38:5e" srcmac="00:0c:29:51:38:5e" srcserver=0
utmref=0-302
Security Logs > Anomaly
Log configuration requirements
config firewall DoS-policy
edit 1
set interface "port12"
set srcaddr "all"
set dstaddr "all"
set service "ALL"
config anomaly
edit "icmp_flood"
set status enable
set log enable
FortiOS 7.6.2 Administration Guide 3932
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,932
|
Log and Report
set action block
set threshold 50
next
end
next
end
Sample log
date=2019-05-13 time=17:05:59 logid="0720018433" type="utm" subtype="anomaly"
eventtype="anomaly" level="alert" vd="vdom1" eventtime=1557792359461869329
severity="critical" srcip=10.1.100.11 srccountry="Reserved" dstip=172.16.200.55
srcintf="port12" srcintfrole="undefined" sessionid=0 action="clear_session" proto=1
service="PING" count=1 attack="icmp_flood" icmpid="0x1474" icmptype="0x08" icmpcode="0x00"
attackid=16777316 policyid=1 policytype="DoS-policy"
ref="http://www.fortinet.com/ids/VID16777316" msg="anomaly: icmp_flood, 51 > threshold 50"
crscore=50 craction=4096 crlevel="critical"
Security Logs > Data Loss Prevention
Log configuration requirements
config dlp profile
edit "dlp-file-type-test"
set comment ''
set replacemsg-group ''
config filter
edit 1
set name ''
set severity medium
set type file
set proto http-get http-post ftp
set filter-by file-type
set file-type 1
set archive enable
set action block
next
end
set dlp-log enable
next
end
config firewall policy
edit 1
set name "to_Internet"
set srcintf "port10"
set dstintf "port9"
set srcaddr "all"
set dstaddr "all"
set action accept
set schedule "always"
set service "ALL"
set utm-status enable
set inspection-mode proxy
set logtraffic utm
FortiOS 7.6.2 Administration Guide 3933
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,933
|
Log and Report
set dlp-profile "dlp-file-type-test"
set ssl-ssh-profile "deep-inspection"
set nat enable
next
end
Sample log
date=2022-02-03 time=17:45:30 eventtime=1643938572487964255 tz="-0800" logid="0954024576"
type="utm" subtype="dlp" eventtype="dlp" level="warning" vd="root" filteridx=1
dlpextra="dlp-file-size11" filtertype="file-type" filtercat="file" severity="medium"
policyid=1 policytype="policy" sessionid=156237 epoch=300501327 eventid=0 srcip=10.1.100.22
srcport=50354 srccountry="Reserved" srcintf="port10" srcintfrole="lan" dstip=52.216.177.83
dstport=443 dstcountry="United States" dstintf="port9" dstintfrole="wan" proto=6
service="HTTPS" filetype="pdf" direction="incoming" action="block"
hostname="fortinetweb.s3.amazonaws.com" url="https://172.16.200.88/dlp/files/fortiauto.pdf"
forwardedfor="192.168.0.99" agent="curl/7.56.0" httpmethod="GET"
referralurl="https://example.com/referer.html" filename="fortiauto.pdf" filesize=285442
profile="dlp-file-type-test" rawdata="x-forwarded-for=192.168.0.99|Response-ContentType=application/pdf"
# Corresponding Traffic Log #
date=2022-02-03 time=17:45:34 logid="0000000013" type="traffic" subtype="forward"
level="notice" vd="root" eventtime=1557967534 srcip=10.1.100.22 srcport=50354
srcintf="port10" srcintfrole="lan" dstip=52.216.177.83 dstport=443 dstintf="port9"
dstintfrole="wan" poluuid="d8ce7a90-7763-51e9-e2be-741294c96f31" sessionid=3423 proto=6
action="server-rst" policyid=1 policytype="policy" service="HTTPS" dstcountry="United
States" srccountry="Reserved" trandisp="snat" transip=172.16.200.10 transport=50354
duration=5 sentbyte=2314 rcvdbyte=5266 sentpkt=33 rcvdpkt=12 appcat="unscanned" wanin=43936
wanout=710 lanin=753 lanout=753 utmaction="block" countdlp=1 crscore=5 craction=262144
crlevel="low" devtype="Unknown" devcategory="None" mastersrcmac="00:0c:29:51:38:5e"
srcmac="00:0c:29:51:38:5e" srcserver=0 utmref=0-152
Security Logs > SSH and Security Logs > SSL
Log configuration requirements
config ssh-filter profile
edit "ssh-deepscan"
set block shell
set log shell
set default-command-log disable
next
end
config firewall policy
edit 1
set srcintf "port21"
set dstintf "port23"
set srcaddr "all"
set dstaddr "all"
set action accept
set schedule "always"
set service "ALL"
set utm-status enable
set inspection-mode proxy
FortiOS 7.6.2 Administration Guide 3934
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,934
|
Log and Report
set ssh-filter-profile "ssh-deepscan"
set profile-protocol-options "protocol"
set ssl-ssh-profile "ssl"
set nat enable
next
end
For SSL-Traffic-log, enable logtraffic all
config firewall policy
edit 1
set srcintf "dmz"
set dstintf "wan1"
set srcaddr "all"
set dstaddr "all"
set action accept
set schedule "always"
set service "ALL"
set utm-status enable
set inspection-mode proxy
set logtraffic all
set ssl-ssh-profile "deep-inspection"
set nat enable
next
end
For SSL-UTM-log
#EVENTTYPE="SSL-ANOMALIES"
By default, ssl-anomaly-log is enabled.
config firewall ssl-ssh-profile
edit "deep-inspection"
set comment "Read-only deep inspection profile."
set server-cert-mode re-sign
set caname "Fortinet_CA_SSL"
set untrusted-caname "Fortinet_CA_Untrusted"
set ssl-anomaly-log enable
set ssl-exemption-log disable
set ssl-negotiation-log disable
set rpc-over-https disable
set mapi-over-https disable
set use-ssl-server disable
next
end
# EVENTTYPE="SSL-EXEMPT"
Enable ssl-exemption-log to generate ssl-utm-exempt log.
config firewall ssl-ssh-profile
edit "deep-inspection"
set comment "Read-only deep inspection profile."
set server-cert-mode re-sign
set caname "Fortinet_CA_SSL"
set untrusted-caname "Fortinet_CA_Untrusted"
set ssl-anomaly-log enable
FortiOS 7.6.2 Administration Guide 3935
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,935
|
Log and Report
set ssl-exemption-log enable
set ssl-negotiation-log disable
set rpc-over-https disable
set mapi-over-https disable
set use-ssl-server disable
next
end
# EVENTTYPE="SSL-negotiation"
Enable ssl-negotiation-log to log SSL negotiation. Enable ssl-server-cert-log to log server certificate
information. Enable ssl-handshake-log to log TLS handshakes.
config firewall ssl-ssh-profile
edit "deep-inspection"
set comment "Read-only deep inspection profile."
set server-cert-mode re-sign
set caname "Fortinet_CA_SSL"
set untrusted-caname "Fortinet_CA_Untrusted"
set ssl-anomaly-log enable
set ssl-exemption-log enable
set ssl-negotiation-log enable
set rpc-over-https disable
set mapi-over-https disable
set use-ssl-server disable
set ssl-server-cert-log enable
set ssl-handshake-log enable
next
end
Sample log for SSH
date=2019-05-15 time=16:18:17 logid="1601061010" type="utm" subtype="ssh" eventtype="sshchannel" level="warning" vd="vdom1" eventtime=1557962296 policyid=1 sessionid=344
profile="ssh-deepscan" srcip=10.1.100.11 srcport=43580 dstip=172.16.200.44 dstport=22
srcintf="port21" srcintfrole="undefined" dstintf="port23" dstintfrole="undefined" proto=6
action="blocked" direction="outgoing" login="root" channeltype="shell"
# Corresponding Traffic Log #
date=2019-05-15 time=16:18:18 logid="0000000013" type="traffic" subtype="forward"
level="notice" vd="vdom1" eventtime=1557962298 srcip=10.1.100.11 srcport=43580
srcintf="port21" srcintfrole="undefined" dstip=172.16.200.44 dstport=22 dstintf="port23"
dstintfrole="undefined" poluuid="49871fae-7371-51e9-17b4-43c7ff119195" sessionid=344 proto=6
action="close" policyid=1 policytype="policy" service="SSH" dstcountry="Reserved"
srccountry="Reserved" trandisp="snat" transip=172.16.200.171 transport=43580 duration=8
sentbyte=3093 rcvdbyte=2973 sentpkt=18 rcvdpkt=16 appcat="unscanned" utmaction="block"
countssh=1 utmref=65535-0
Sample log for SSL
For SSL-Traffic-log
date=2019-05-16 time=10:08:26 logid="0000000013" type="traffic" subtype="forward"
level="notice" vd="root" eventtime=1558026506763925658 srcip=10.1.100.66 srcport=38572
srcintf="dmz" srcintfrole="dmz" dstip=104.154.89.105 dstport=443 dstintf="wan1"
dstintfrole="wan" poluuid="a17c0a38-75c6-51e9-4c0d-d547347b63e5" sessionid=100 proto=6
action="server-rst" policyid=1 policytype="policy" service="HTTPS" dstcountry="United
FortiOS 7.6.2 Administration Guide 3936
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,936
|
Log and Report
States" srccountry="Reserved" trandisp="snat" transip=172.16.200.11 transport=38572
duration=5 sentbyte=930 rcvdbyte=6832 sentpkt=11 rcvdpkt=19 appcat="unscanned" wanin=1779
wanout=350 lanin=754 lanout=754 utmaction="block" countssl=1 crscore=5 craction=262144
crlevel="low" utmref=65467-0
For SSL-UTM-log
#EVENTTYPE="SSL-ANOMALIES"
date=2019-03-28 time=10:44:53 logid="1700062002" type="utm" subtype="ssl" eventtype="sslanomalies" level="warning" vd="vdom1" eventtime=1553795092 policyid=1 sessionid=10796
service="HTTPS" srcip=10.1.100.66 srcport=43602 dstip=104.154.89.105 dstport=443
srcintf="port2" srcintfrole="undefined" dstintf="port3" dstintfrole="undefined" proto=6
action="blocked" msg="Server certificate blocked" reason="block-cert-invalid"
date=2019-03-28 time=10:51:17 logid="1700062002" type="utm" subtype="ssl" eventtype="sslanomalies" level="warning" vd="vdom1" eventtime=1553795476 policyid=1 sessionid=11110
service="HTTPS" srcip=10.1.100.66 srcport=49076 dstip=172.16.200.99 dstport=443
srcintf="port2" srcintfrole="undefined" dstintf="port3" dstintfrole="undefined" proto=6
action="blocked" msg="Server certificate blocked" reason="block-cert-untrusted"
date=2019-03-28 time=10:55:43 logid="1700062002" type="utm" subtype="ssl" eventtype="sslanomalies" level="warning" vd="vdom1" eventtime=1553795742 policyid=1 sessionid=11334
service="HTTPS" srcip=10.1.100.66 srcport=49082 dstip=172.16.200.99 dstport=443
srcintf="port2" srcintfrole="undefined" dstintf="port3" dstintfrole="undefined" proto=6
action="blocked" msg="Server certificate blocked" reason="block-cert-req"
date=2019-03-28 time=10:57:42 logid="1700062053" type="utm" subtype="ssl" eventtype="sslanomalies" level="warning" vd="vdom1" eventtime=1553795861 policyid=1 sessionid=11424
service="SMTPS" profile="block-unsupported-ssl" srcip=10.1.100.66 srcport=41296
dstip=172.16.200.99 dstport=8080 srcintf="port2" srcintfrole="undefined" dstintf=unknown-0
dstintfrole="undefined" proto=6 action="blocked" msg="Connection is blocked due to
unsupported SSL traffic" reason="malformed input"
date=2019-03-28 time=11:00:17 logid="1700062002" type="utm" subtype="ssl" eventtype="sslanomalies" level="warning" vd="vdom1" eventtime=1553796016 policyid=1 sessionid=11554
service="HTTPS" srcip=10.1.100.66 srcport=49088 dstip=172.16.200.99 dstport=443
srcintf="port2" srcintfrole="undefined" dstintf="port3" dstintfrole="undefined" proto=6
action="blocked" msg="Server certificate blocked" reason="block-cert-sni-mismatch"
# EVENTTYPE="SSL-EXEMPT"
date=2019-03-28 time=11:09:14 logid="1701062003" type="utm" subtype="ssl" eventtype="sslexempt" level="notice" vd="vdom1" eventtime=1553796553 policyid=1 sessionid=12079
service="HTTPS" srcip=10.1.100.66 srcport=49102 dstip=172.16.200.99 dstport=443
srcintf="port2" srcintfrole="undefined" dstintf="port3" dstintfrole="undefined" proto=6
action="exempt" msg="SSL connection exempted" reason="exempt-addr"
date=2019-03-28 time=11:10:55 logid="1701062003" type="utm" subtype="ssl" eventtype="sslexempt" level="notice" vd="vdom1" eventtime=1553796654 policyid=1 sessionid=12171
service="HTTPS" srcip=10.1.100.66 srcport=47390 dstip=50.18.221.132 dstport=443
srcintf="port2" srcintfrole="undefined" dstintf="port3" dstintfrole="undefined" proto=6
action="exempt" msg="SSL connection exempted" reason="exempt-ftgd-cat"
# EVENTYPE="SSL-NEGOTIATION"
date=2020-02-07 time=11:10:58 logid="1702062101" type="utm" subtype="ssl" eventtype="sslnegotiation" level="warning" vd="vdom1" eventtime=1581102658589415731 tz="-0800"
action="blocked" policyid=1 sessionid=141224 service="HTTPS" profile="deep-inspection-clone"
srcip=10.1.100.66 srcport=33666 dstip=172.16.200.99 dstport=8080 srcintf="port2"
FortiOS 7.6.2 Administration Guide 3937
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,937
|
Log and Report
srcintfrole="undefined" dstintf="port3" dstintfrole="undefined" proto=6
eventsubtype="unexpected-protocol" msg="SSL connection is blocked."
date=2021-06-17 time=16:55:26 eventtime=1623974126384215772 tz="-0700" logid="1702062103"
type="utm" subtype="ssl" eventtype="ssl-negotiation" level="information" vd="vdom1"
action="info" policyid=1 sessionid=6361 service="HTTPS" profile="deep-inspection-clone"
srcip=10.1.100.11 srcport=48892 dstip=18.140.21.233 dstport=443 srcintf="port2"
srcintfrole="undefined" dstintf="port3" dstintfrole="undefined" srcuuid="8666f70e-cfb9-51eb4991-9012417d69da" dstuuid="8666f70e-cfb9-51eb-4991-9012417d69da" proto=6
sni="www.fortinet.com" eventsubtype="server-cert-info" hostname="www.fortinet.com"
notbefore="2021-03-13T00:00:00Z" notafter="2022-04-13T23:59:59Z" issuer="DigiCert TLS RSA
SHA256 2020 CA1" cn="*.fortinet.com" san="*.fortinet.com;www.fortinet.com;fortinet.com"
sn="000aa00a00000a00000a00a00aa000a0" ski="df9152b605cc18b346efb34de6907275dbdb2b3c"
certhash="1d55cd34a1ed5d3f69bd825a45e04fbd2efba937" keyalgo="rsa" keysize=2048
date=2021-06-17 time=16:55:26 eventtime=1623974126411127210 tz="-0700" logid="1702062103"
type="utm" subtype="ssl" eventtype="ssl-negotiation" level="information" vd="vdom1"
action="info" policyid=1 sessionid=6361 service="HTTPS" profile="deep-inspection-clone"
srcip=10.1.100.11 srcport=48892 dstip=18.140.21.233 dstport=443 srcintf="port2"
srcintfrole="undefined" dstintf="port3" dstintfrole="undefined" srcuuid="8666f70e-cfb9-51eb4991-9012417d69da" dstuuid="8666f70e-cfb9-51eb-4991-9012417d69da" proto=6 tlsver="tls1.3"
sni="www.fortinet.com" cipher="0x1302" authalgo="rsa" kxproto="ecdhe" kxcurve="secp256r1"
eventsubtype="handshake-done" hostname="www.fortinet.com" handshake="full" mitm="yes"
Troubleshooting
The following topics provide information about troubleshooting logging and reporting:
l Log-related diagnostic commands on page 3938
l Backing up log files or dumping log messages on page 3943
l SNMP OID for logs that failed to send on page 3945
Log-related diagnostic commands
This topic contains examples of commonly used log-related diagnostic commands. Local logging is handled by the
locallogd daemon, and remote logging is handled by the fgtlogd daemon.
Log search debugging
The diagnose debug application miglogd 0x1000 command is used is to show log filter strings used by the
log search backend. It also shows which log files are searched.
To run log search debugging:
# diagnose debug application miglogd 0x1000
Debug messages will be on for 28 minutes.
# diagnose debug enable
# Files to be searched:
file_no=65422, start line=0, end_line=805
FortiOS 7.6.2 Administration Guide 3938
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,938
|
Log and Report
file_no=65423, start line=0, end_line=221
session ID=2, total logs=1028
back ground search. process ID=2913, session_id=2
start line=1 view line=10 pre-fetch-pages=2
back ground search. next log file roll number is: 65422
ID=2, total=1028, checked=806, found=806
on-demand back ground search exit. process ID=2913, session_id=2, status=process_on-demand_
pending
Log filtering
The execute log filter command can be used to define and display specific log messages based on the
parameters entered.
To display all login system event logs:
# execute log filter device disk
# execute log filter category event
# execute log filter field action login
# execute log display
Files to be searched:
file_no=65523, start line=0, end_line=237
file_no=65524, start line=0, end_line=429
file_no=65525, start line=0, end_line=411
file_no=65526, start line=0, end_line=381
file_no=65527, start line=0, end_line=395
file_no=65528, start line=0, end_line=458
file_no=65529, start line=0, end_line=604
file_no=65530, start line=0, end_line=389
file_no=65531, start line=0, end_line=384
session ID=1, total logs=3697
back ground search. process ID=26240, session_id=1
start line=1 view line=10
( action "login" )
ID=1, total=3697, checked=238, found=5
ID=1, total=3697, checked=668, found=13
ID=1, total=3697, checked=1080, found=23
ID=1, total=3697, checked=1462, found=23
ID=1, total=3697, checked=1858, found=23
ID=1, total=3697, checked=2317, found=54
ID=1, total=3697, checked=2922, found=106
ID=1, total=3697, checked=3312, found=111
ID=1, total=3697, checked=3697, found=114
Checking the FortiGate to FortiAnalyzer connection
To check the FortiGate to FortiAnalyzer connection status:
# diagnose test application fgtlogd 1
faz: global , enabled
server=172.16.200.251, realtime=3, ssl=1, state=connected
FortiOS 7.6.2 Administration Guide 3939
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,939
|
Log and Report
server_log_status=Log is allowed.,
src=, mgmt_name=FGh_Log_vdom1_172.16.200.251, reliable=0, sni_prefix_type=none,
required_entitlement=none, region=ca-west-1,
logsync_enabled:1, logsync_conn_id:65535, seq_no:0
status: ver=6, used_disk=0, total_disk=0, global=0, vfid=0 conn_verified=Y
SNs: last sn update:56 seconds ago.
Sn list:
(FAZ-VMTM2200****,age=56s)
queue: qlen=0.
filter: severity=6, sz_exclude_list=0
traffic virus webfilter ips emailfilter anomaly voip dlp app-ctrl waf dns ssh ssl
file-filter icap sctp-f
ilter
subcategory:
traffic: forward local multicast sniffer ztna
virus:all subcategories are enabled.
webfilter:all subcategories are enabled.
ips:all subcategories are enabled.
emailfilter:all subcategories are enabled.
anomaly:all subcategories are enabled.
voip:all subcategories are enabled.
dlp:all subcategories are enabled.
app-ctrl:all subcategories are enabled.
waf:all subcategories are enabled.
dns:all subcategories are enabled.
ssh:all subcategories are enabled.
ssl:all subcategories are enabled.
file-filter:all subcategories are enabled.
icap:all subcategories are enabled.
sctp-filter:all subcategories are enabled.
server: global, id=0, ready=1, name=172.16.200.251 addr=172.16.200.251:514
oftp-state=connected
To collect debug information when FortiAnalyzer is enabled:
# diagnose debug application fgtlogd 0x100
# <2026> __fgtlog_parse_featset()-1680: No featset data in login packet,init the device with
default value
<2026> __on_connect()-1620: oftp is ready.
<2026> __on_connect()-1621: status connected for global-faz.
<2026> _check_oftp_certificate()-206: checking sn:FAZVMSTM2200**** vs cert
sn:FAZVMSTM2200****
<2026> _check_oftp_certificate()-208: Verified the certificate of peer (10.100.88.2) to
match sn=FAZVMSTM2200****
<2026> _faz_post_connection()-249: Certificate verification:enabled, Faz verified:1
<2026> _send_queue_item()-549: Disconnect global-faz until receiving disk usage response.
<2026> _send_queue_item()-555: type=0, cat=0, logcount=0, len=0
<2026> __on_pkt_recv()-1590: dev=global-faz type=252 pkt_len=1099
<2026> __on_pkt_recv()-1590: opt=204, opt_len=91
<2026> __on_pkt_recv()-1590: opt=252, opt_len=996
<2026> _process_hainfo_response()-1206: hainfo opt code=204
<2026> _faz_process_oftp_resp_hainfo_json()-447: ha mode: standalone
<2026> __is_sn_known()-315: MATCHED: idx:0 sn:FAZVMSTM2200****
<2026> _faz_process_oftp_resp_hainfo_json()-481: Received SN:FAZVMSTM2200**** should
FortiOS 7.6.2 Administration Guide 3940
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,940
|
Log and Report
update:0
<2026> _process_hainfo_response()-1206: hainfo opt code=252
<2026> _faz_process_oftp_resp_hainfo_struct()-553: ha nmember:1 nvcluster:0 mode:1
<2026> __is_sn_known()-315: MATCHED: idx:0 sn:FAZVMSTM2200****
<2026> _faz_process_oftp_resp_hainfo_struct()-559: Received SN:FAZVMSTM2200**** should
update:0
<2026> __on_pkt_recv()-1590: dev=global-faz type=1 pkt_len=1356
<2026> __on_pkt_recv()-1590: opt=12, opt_len=16
<2026> __on_pkt_recv()-1590: opt=51, opt_len=9
...
<2026> _build_ack()-867: global-faz ready to send data.
<2026> _process_response()-1152: checking opt code=81
<2026> _process_response()-1152: checking opt code=81
<2026> _process_response()-1152: checking opt code=81
...
<2026> _send_queue_item()-555: type=1, cat=0, logcount=0, len=0
<2026> _send_queue_item()-555: type=7, cat=0, logcount=0, len=58
<2026> _send_queue_item()-555: type=3, cat=10, logcount=1, len=790
<2026> _send_queue_item()-555: type=3, cat=10, logcount=1, len=807
<2026> __on_pkt_recv()-1590: dev=global-faz type=60 pkt_len=474
...
<2026> __on_pkt_recv()-1590: opt=80, opt_len=16
<2026> __on_pkt_recv()-1590: opt=7, opt_len=446
<2026> __on_pkt_recv()-1590: dev=global-faz type=11 pkt_len=37
...
<2026> _send_queue_item()-555: type=3, cat=0, logcount=1, len=1037
<2026> _send_queue_item()-555: type=3, cat=0, logcount=1, len=1033
To check the FortiGate to FortiGate Cloud connection status:
# diagnose test application fgtlogd 20
Home log server:
Address: 173.243.132.57:514
Alternative log server:
Address: 173.243.132.121:514
FazCloud log server:
Address:
oftp status: connected
Debug zone info:
Server IP: 173.243.132.57
Server port: 514
Server status: up
Server log status: enabled
Log quota: 500000000MB
Log used: 599MB
Daily volume: 1000000MB
FDS arch pause: 0
fams archive pause: 0
locallogd diagnostics
To check real-time log statistics by log type since the locallogd daemon start:
# diagnose test application locallogd 3
info for vdom: root
FortiOS 7.6.2 Administration Guide 3941
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,941
|
Log and Report
memory
traffic: logs=18289 len=15921725, Sun=0 Mon=18289 Tue=0 Wed=0 Thu=0 Fri=0 Sat=0
event: logs=286 len=115729, Sun=0 Mon=286 Tue=0 Wed=0 Thu=0 Fri=0 Sat=0
app-ctrl: logs=10018 len=7051278, Sun=0 Mon=10018 Tue=0 Wed=0 Thu=0 Fri=0 Sat=0
disk
traffic: logs=18289 len=15921725, Sun=0 Mon=18289 Tue=0 Wed=0 Thu=0 Fri=0 Sat=0
compressed=1620003
event: logs=280 len=112390, Sun=0 Mon=280 Tue=0 Wed=0 Thu=0 Fri=0 Sat=0 compressed=13157
app-ctrl: logs=10018 len=7051278, Sun=0 Mon=10018 Tue=0 Wed=0 Thu=0 Fri=0 Sat=0
compressed=836906
fgtlogd diagnostics
To check real-time log statistics by log type since the fgtlogd daemon start:
# diagnose test application fgtlogd 3
info for vdom: root
faz
traffic: logs=11763 len=6528820, Sun=2698 Mon=3738 Tue=0 Wed=0 Thu=0 Fri=2523 Sat=2804
compressed=1851354
event: logs=2190 len=891772, Sun=500 Mon=400 Tue=0 Wed=0 Thu=0 Fri=786 Sat=504
compressed=713129
app-ctrl: logs=1 len=692, Sun=0 Mon=0 Tue=0 Wed=0 Thu=0 Fri=1 Sat=0 compressed=384
faz-cloud
traffic: logs=11763 len=6528820, Sun=2698 Mon=3738 Tue=0 Wed=0 Thu=0 Fri=2523 Sat=2804
event: logs=2190 len=891772, Sun=500 Mon=400 Tue=0 Wed=0 Thu=0 Fri=786 Sat=504
app-ctrl: logs=1 len=692, Sun=0 Mon=0 Tue=0 Wed=0 Thu=0 Fri=1 Sat=0
To check the remote queue and see the maximum buffered memory size:
# diagnose test application fgtlogd 41
cache maximum: 19569745(18MB) objects: 0 used: 0(0MB) allocated: 0(0MB)
VDOM:root
Memory queue for: global-faz
queue:
num:0 size:0(0MB) total size:0(0MB) max:19569745(18MB) logs:0
Confirm queue for: global-faz
queue:
num:0 size:0(0MB) total size:0(0MB) max:19569745(18MB) logs:0
Memory queue for: fds
queue:
num:0 size:0(0MB) total size:0(0MB) max:19569745(18MB) logs:0
Confirm queue for: fds
queue:
num:0 size:0(0MB) total size:0(0MB) max:19569745(18MB) logs:0
miglogd diagnostics
The miglogd daemon includes a publisher/subscriber framework that separates functions into different daemons. The
miglogd daemon is responsible for building and publishing logs, while device-related details are managed by subscriber
daemons.
FortiOS 7.6.2 Administration Guide 3942
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,942
|
Log and Report
To enable debugging the miglogd (log daemon) at the proper debug level:
# diagnose debug application miglogd <integer>
# diagnose debug enable
To display the status or statistics at the proper debug level:
# diagnose test application miglogd <integer>
# diagnose debug enable
When using the preceding commands, press Enter after diagnose debug application
miglogd or diagnose test application miglogd to view the list of available levels.
To check log statistics to the local/remote log device since the miglogd daemon start:
# diagnose test application miglogd 6
mem=4288, disk=4070, alert=0, alarm=0, sys=5513, faz=4307, webt=0, fds=0
interface-missed=208
To check the miglogd daemon number:
# diagnose test application miglogd 15
Main miglogd: ID=0, children=2, active-children=2
ID=1, duration=70465.
ID=2, duration=70465.
To increase one miglogd child:
# diagnose test application miglogd 13
# diagnose test application miglogd 15
Main miglogd: ID=0, children=3, active-children=3
ID=1, duration=70486.
ID=2, duration=70486.
ID=3, duration=1.
To decrease one miglogd child:
# diagnose test application miglogd 14
# diagnose test application miglogd 15
Main miglogd: ID=0, children=2, active-children=2
ID=1, duration=70604.
ID=2, duration=70604.
Backing up log files or dumping log messages
When a log issue is caused by a particular log message, it is very help to get logs from that FortiGate. This topic provides
steps for using execute log backup or dumping log messages to a USB drive.
FortiOS 7.6.2 Administration Guide 3943
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,943
|
Log and Report
Backing up full logs using execute log backup
This command backs up all disk log files and is only available on FortiGates with an SSD disk.
Before running execute log backup, we recommend temporarily stopping miglogd and reportd.
To stop and kill miglogd and reportd:
diagnose sys process daemon-auto-restart disable miglogd
diagnose sys process daemon-auto-restart disable reportd
Or
1. Determine the process, or thread, ID (PID) of miglogd and reportd:
# diagnose sys top 10 99
2. Kill each process:
# diagnose sys kill 9 <PID>
To store the log file on a USB drive:
1. Plug in a USB drive into the FortiGate.
2. Run this command:
execute log backup /usb/log.tar
To restart miglogd and reportd:
diagnose sys process daemon-auto-restart enable miglogd
diagnose sys process daemon-auto-restart enable reportd
Dumping log messages
To dump log messages:
1. Enable log dumping for miglogd daemon:
(global) # diagnose test application miglogd 26 1
miglogd(1) log dumping is enabled
2. Display all miglogd dumping status:
global) # diagnose test application miglogd 26 0 255
miglogd(0) log dumping is disabled
miglogd(1) log dumping is enabled
miglogd(2) log dumping is disabled
(global) # diagnose test application miglogd 26 2
miglogd(2) log dumping is enabled
(global) # diagnose test application miglogd 26 0
miglogd(0) log dumping is enabled
(global) # diagnose test application miglogd 26 0 255
miglogd(0) log dumping is enabled
FortiOS 7.6.2 Administration Guide 3944
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,944
|
Log and Report
miglogd(1) log dumping is enabled
miglogd(2) log dumping is enabled
3. Let the FortiGate run and collect log messages.
4. List the log dump files:
(global) # diagnose test application miglogd 33
2019-04-17 15:50:02 20828 log-1-0.dat
2019-04-17 15:48:31 4892 log-2-0.dat
5. Back up log dump files to the USB drive:
(global) # diagnose test application miglogd 34
Dumping file miglog1_index0.dat copied to USB disk OK.
Dumping file miglog2_index0.dat copied to USB disk OK.
6. Disable log dumping for miglogd daemon:
(global) # diagnose test application miglogd 26 0
miglogd(0) log dumping is disabled
(global) # diagnose test application miglogd 26 1
miglogd(1) log dumping is disabled
(global) # diagnose test application miglogd 26 2
miglogd(2) log dumping is disabled
(global) # diagnose test application miglogd 26 0 255
miglogd(0) log dumping is disabled
miglogd(1) log dumping is disabled
miglogd(2) log dumping is disabled
SNMP OID for logs that failed to send
When a syslog server encounters low-performance conditions and slows down to respond, the buffered syslog
messages in the kernel might overflow after a certain number of retransmissions, causing the overflowed messages to
be lost. OIDs track the lost messages or failed logs.
SNMP query OIDs include log statistics for global log devices:
l FORTINET-FORTIGATE-MIB:fortinet.fnFortiGateMib.fgLog.fgLogDeviceNumber 1.3.6.1.4.1.12356.101.21.1.1
l FORTINET-FORTIGATEMIB:fortinet.fnFortiGateMib.fgLog.fgLogDevices.fgLogDeviceTable.fgLogDeviceEntry.fgLogDeviceEntryIndex
1.3.6.1.4.1.12356.101.21.2.1.1.1
l FORTINET-FORTIGATEMIB:fortinet.fnFortiGateMib.fgLog.fgLogDevices.fgLogDeviceTable.fgLogDeviceEntry.fgLogDeviceEnabled
1.3.6.1.4.1.12356.101.21.2.1.1.2
l FORTINET-FORTIGATEMIB:fortinet.fnFortiGateMib.fgLog.fgLogDevices.fgLogDeviceTable.fgLogDeviceEntry.fgLogDeviceName
1.3.6.1.4.1.12356.101.21.2.1.1.3
l FORTINET-FORTIGATEMIB:fortinet.fnFortiGateMib.fgLog.fgLogDevices.fgLogDeviceTable.fgLogDeviceEntry.fgLogDeviceSentCount
1.3.6.1.4.1.12356.101.21.2.1.1.4
FortiOS 7.6.2 Administration Guide 3945
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,945
|
Log and Report
l FORTINET-FORTIGATEMIB:fortinet.fnFortiGateMib.fgLog.fgLogDevices.fgLogDeviceTable.fgLogDeviceEntry.fgLogDeviceRelayedCount
1.3.6.1.4.1.12356.101.21.2.1.1.5
l FORTINET-FORTIGATEMIB:fortinet.fnFortiGateMib.fgLog.fgLogDevices.fgLogDeviceTable.fgLogDeviceEntry.fgLogDeviceCachedCount
1.3.6.1.4.1.12356.101.21.2.1.1.6
l FORTINET-FORTIGATEMIB:fortinet.fnFortiGateMib.fgLog.fgLogDevices.fgLogDeviceTable.fgLogDeviceEntry.fgLogDeviceFailedCount
1.3.6.1.4.1.12356.101.21.2.1.1.7
l FORTINET-FORTIGATEMIB:fortinet.fnFortiGateMib.fgLog.fgLogDevices.fgLogDeviceTable.fgLogDeviceEntry.fgLogDeviceDroppedCount
1.3.6.1.4.1.12356.101.21.2.1.1.8
Where:
l fgLogDeviceNumber is the number of devices in the table.
l fgLogDeviceEnabled is either 1 or 0, indicating whether the device is enabled.
l fgLogDeviceName is the name of the device.
A FortiGate connected to a syslog server or FortiAnalyzer generates statistics that can be seen using the diagnose
test application syslogd command:
(global) # diagnose test application syslogd 4
syslog=437, nulldev=0, webtrends=0, localout_ioc=258, alarms=0
global log dev statistics:
syslog 0: sent=222, failed=0, cached=0, dropped=0
syslog 1: sent=215, failed=0, cached=0, dropped=0
syslog 2: sent=95, failed=0, cached=0, dropped=0
The same statistics are also available in snmpwalk/snmpget on the OID 1.3.6.1.4.1.12356.101.21.
snmpwalk -v2c -c REGR-SYS 172.16.200.1 1.3.6.1.4.1.12356.101.21
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.1.1.0 = INTEGER: 9
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.1.0 = INTEGER: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.1.1 = INTEGER: 1
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.1.2 = INTEGER: 2
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.1.3 = INTEGER: 3
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.1.4 = INTEGER: 4
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.1.5 = INTEGER: 5
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.1.6 = INTEGER: 6
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.1.7 = INTEGER: 7
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.1.8 = INTEGER: 8
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.0 = INTEGER: 1
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.1 = INTEGER: 1
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.2 = INTEGER: 1
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.3 = INTEGER: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.4 = INTEGER: 1
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.5 = INTEGER: 1
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.6 = INTEGER: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.7 = INTEGER: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.8 = INTEGER: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.0 = STRING: "syslog"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.1 = STRING: "syslog2"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.2 = STRING: "syslog3"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.3 = STRING: "syslog4"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.4 = STRING: "faz"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.5 = STRING: "faz2"
FortiOS 7.6.2 Administration Guide 3946
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,946
|
Log and Report
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.6 = STRING: "faz3"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.7 = STRING: "webtrends"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.8 = STRING: "fds"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.4.0 = Counter32: 254
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.4.1 = Counter32: 220
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.4.2 = Counter32: 95
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.4.3 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.4.4 = Counter32: 282
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.4.5 = Counter32: 272
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.4.6 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.4.7 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.4.8 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.5.0 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.5.1 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.5.2 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.5.3 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.5.4 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.5.5 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.5.6 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.5.7 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.5.8 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.6.0 = Gauge32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.6.1 = Gauge32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.6.2 = Gauge32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.6.3 = Gauge32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.6.4 = Gauge32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.6.5 = Gauge32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.6.6 = Gauge32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.6.7 = Gauge32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.6.8 = Gauge32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.0 = Counter32: 139
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.1 = Counter32: 139
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.2 = Counter32: 73
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.3 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.4 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.5 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.6 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.7 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.8 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.8.0 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.8.1 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.8.2 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.8.3 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.8.4 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.8.5 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.8.6 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.8.7 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.8.8 = Counter32: 0
To get the type of logging device that is attached to the FortiGate:
root@PC05:/home/tester/autolib/trunk# snmpwalk -v2c -c REGR-SYS 172.16.200.1
1.3.6.1.4.1.12356.101.21.2.1.1.3
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.0 = STRING: "syslog"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.1 = STRING: "syslog2"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.2 = STRING: "syslog3"
FortiOS 7.6.2 Administration Guide 3947
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,947
|
Log and Report
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.3 = STRING: "syslog4"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.4 = STRING: "faz"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.5 = STRING: "faz2"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.6 = STRING: "faz3"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.7 = STRING: "webtrends"
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.3.8 = STRING: "fds"
To get the present state of the logging device that is attached to the FortiGate:
root@PC05:/home/tester/autolib/trunk# snmpwalk -v2c -c REGR-SYS 172.16.200.1
1.3.6.1.4.1.12356.101.21.2.1.1.2
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.0 = INTEGER: 1
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.1 = INTEGER: 1
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.2 = INTEGER: 1
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.3 = INTEGER: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.4 = INTEGER: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.5 = INTEGER: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.6 = INTEGER: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.7 = INTEGER: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.2.8 = INTEGER: 0
To get the failed log count value:
root@PC05:/home/tester/autolib/trunk# snmpwalk -v2c -c REGR-SYS 172.16.200.1
1.3.6.1.4.1.12356.101.21.2.1.1.7
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.0 = Counter32: 139
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.1 = Counter32: 139
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.2 = Counter32: 73
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.3 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.4 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.5 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.6 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.7 = Counter32: 0
FORTINET-FORTIGATE-MIB::fnFortiGateMib.21.2.1.1.7.8 = Counter32: 0
FortiOS 7.6.2 Administration Guide 3948
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,948
|
WAN optimization
Many multi-location enterprise environments reduce costs and consolidate resources by centralizing applications or
providing applications in the cloud. Applications that work fine on a local LAN, such as Windows File Sharing (CIFS),
email exchange (MAPI), and many others, suffer from bandwidth limitations and latency issues when accessed over a
WAN. This results in a loss of productivity and a perceived need for expensive network upgrades. WAN optimization
reduces your network overhead and removes unnecessary traffic for a better overall performance experience and
eliminates the need for costly WAN link upgrades between data centers and other expensive solutions for your network
traffic growth.
FortiOS WAN optimization provides an inexpensive and comprehensive solution that maximizes your WAN performance
and provides intelligent bandwidth management and unmatched consolidated security performance.
FortiOS includes license-free WAN optimization on most current FortiGate devices with internal storage that also
support SSL offloading.
This feature is not supported on FortiGate models with 2 GB RAM or less. See Proxy-related features not supported on
FortiGate 2 GB RAM models on page 104 for more information.
Features
The following features are available through WAN optimization:
Protocol optimization
Protocol optimization is effective for applications designed for the LAN that do not function well on low bandwidth, high
latency networks. See Protocol optimization on page 3957 for more information.
Byte caching
Byte caching improves caching by accelerating the transfer of similar, but not identical content. See Byte caching on
page 3957 for more information.
SSL offloading
SSL is used by many organizations to keep WAN communications private. WAN optimization utilizes the SSL offloading
capabilities of the FortiGate FortiASIC hardware to accelerate SSL traffic across the WAN. The FortiGate unit handles
SSL encryption and decryption for corporate servers providing SSL encrypted connections over the WAN. See SSL
Offloading on page 3953 for more information.
FortiOS 7.6.2 Administration Guide 3949
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,949
|
WAN optimization
WAN optimization and HA
You can configure WAN optimization on a FortiGate HA cluster. See HA on page 3961 for more information.
Secure tunneling
FortiOS WAN optimization supports secure SSL-encrypted tunnels between FortiGate units on the WAN. See Secure
tunneling on page 3955 for more information.
Prerequisites
FortiGate WAN optimization is proprietary to Fortinet Inc.. It will not work with other vendors’ WAN optimization or
offloading features.
Before you begin to configure WAN optimization, please go through the following steps:
1. To use WAN optimization, your FortiGate unit must support it and not all FortiGate units do. In general, your
FortiGate unit must include a hard disk to support these features. See Feature Platform Matrix.
2. If the physical FortiGate has only one hard disk, make sure it is selected for WAN optimization. See Disk usage on
page 3950 for more information.
3. For FortiGate-VM, ensure you create two virtual disks besides the boot disk for WAN optimization to work.
4. To be able to configure WAN optimization from the GUI you should begin by going to System > Feature Visibility and
turning on WAN Opt. & Cache.
5. If you enable virtual domains (VDOMs) on the FortiGate unit, WAN optimization is available separately for each
VDOM.
At this stage, the following installation and configuration conditions are assumed:
l For WAN optimization you have already successfully installed two or more FortiGate units at various locations
across your WAN.
l You have administrative access to the GUI or CLI.
l The FortiGate units are integrated into your WAN or other networks.
l The system time, DNS settings, administrator password, and network interfaces have been configured.
l Firmware, FortiGuard Antivirus, and FortiGuard Antispam updates are completed.
l Your Fortinet products have been registered. Register your Fortinet Inc. products at the Fortinet Technical Support
website, https://support.fortinet.com.
Disk usage
Both logging and WAN optimization use hard disk space to save data. In FortiOS, you cannot use the same hard disk for
both WAN optimization and logging.
l If the FortiGate has one hard disk, then it can be used for either disk logging or WAN optimization, but not both. By
default, the hard disk is used for disk logging.
FortiOS 7.6.2 Administration Guide 3950
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,950
|
WAN optimization
Only physical FortiGate devices can switch between disk logging and WAN optimization in
the case of a single hard disk. FortiGate-VM must have two virtual disks apart from the
boot disk for WAN optimization to work.
l If the FortiGate has two hard disks, then one disk is always used for disk logging and the other disk is always used
for WAN optimization.
On the FortiGate, go to System > Settings > Disk Settings to switch between Local Log and WAN Optimization.
You can also change disk usage from the CLI using the following command:
config system storage
edit <name>
set usage {log | wanopt}
set wanopt-mode {mix | wanopt | webcache}
next
end
Option Description
wanopt-mode WAN optimization mode:
l mix: This is the default mode.
l wanopt: Recommended if only the WANopt feature is enabled.
l webcache: Recommended if only the webcache feature is enabled.
If only one of the two features is being used, using the applicable recommended
mode will give a higher cache capacity and improve performance.
Enabling WAN optimization affects more than just disk logging. The following table shows other features affected by the
FortiGate disk configuration.
Feature 1 hard disk 2 hard disks
Logging Not supported Supported
Report/Historical FortiView Not supported Supported
Firewall Packet Capture
(Policy Capture and Interface
Capture)
Not supported Supported
AV Quarantine Not supported Supported
IPS Packet Capture Not supported Supported
DLP Archive Not supported Supported
Sandbox DB & Results FortiSandbox database and results are also stored on disk, but will not be
affected by this feature.
Remote Logging Remote logging (including logging to FortiAnalyzer and Syslog servers) is not
affected by this features.
Changing the disk setting formats the disk, erases current data stored on the disk, and
disables either disk logging or WAN optimization.
FortiOS 7.6.2 Administration Guide 3951
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,951
|
WAN optimization
The following sections provide information about WAN optimization:
l Overview on page 3952
l Example topologies on page 3963
l Configuration examples on page 3965
Overview
The following topics provide an overview on WAN optimization:
l Peers and authentication groups on page 3953
l Tunnels on page 3954
l Transparent mode on page 3956
l Protocol optimization on page 3957
l Cache service and video caching on page 3958
l Manual and active-passive on page 3959
l Monitoring performance on page 3960
l System and feature operation with WAN optimization on page 3960
l Best practices on page 3963
Client/server architecture
Traffic across a WAN typically consists of clients on a client network communicating across a WAN with a remote server
network. The clients do this by starting communication sessions from the client network across a WAN to the server
network. When you have FortiGates on each end, you can optimize these sessions by adding a WAN optimization
profile.
To use WAN optimization, the FortiGate units can operate in either NAT or transparent mode. The client-side and serverside FortiGate units do not have to be operating in the same mode. The client-side FortiGate unit is located between the
client network and the WAN. The server-side FortiGate unit is located between the server network and the WAN.
WAN optimization profiles are only added to the client-side. The server-side FortiGate unit
employs the WAN optimization settings set in the WAN optimization profile on the client-side
FortiGate unit.
Profiles
Use WAN optimization profiles to apply WAN optimization techniques to traffic to be optimized. In a WAN optimization
profile you can select the protocols to be optimized and for HTTP protocol. You can also enable SSL offloading (if
supported), secure tunneling, byte caching, transparent mode, and optionally select an authentication group. You can
edit the default WAN optimization profile or create new ones. See Configuration examples on page 3965 for sample
configuration.
FortiOS 7.6.2 Administration Guide 3952
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,952
|
WAN optimization
Transparent mode Servers receiving packets after WAN optimization see different source addresses
depending on whether or not you select Transparent Mode. See Transparent
mode on page 3956 for more information.
Authentication group Select this option and select an authentication group so that the client and serverside FortiGate units must authenticate with each other before starting the WAN
optimization tunnel. See Peers and authentication groups on page 3953 for more
information.
Protocol Select CIFS, FTP, HTTP, MAPI or TCP to apply protocol optimization for the
selected protocols. See Protocol optimization on page 3957 for more information.
SSL Offloading Select to apply SSL offloading for HTTPS traffic. You can use SSL offloading to
offload SSL encryption and decryption from one or more HTTP servers to the
FortiGate unit. If you enable this option, you must also use one of the following
option to achieve SSL offloading:
l Enable ssl profile with ssl deep-inspection in the WAN optimization firewall
policy on the client-side and use the CLI command config firewall
ssl-server to add an SSL server on the server-side for each HTTP server
that you want to offload SSL encryption and decryption for.
l Enable ssl profile with ssl deep-inspection in the WAN optimization firewall
policy on client-side and WAN optimization proxy policy on server-side to
accept SSL encrypted traffic.
SSL Secure Tunneling The WAN optimization tunnel is encrypted using SSL encryption. You must also
add an authentication group to the profile. See Secure tunneling on page 3955 for
more information.
Byte Caching Select to apply WAN optimization byte caching to the sessions accepted by this
rule. See Byte caching on page 3957 for more information.
Peers and authentication groups
The client-side and server-side FortiGate units are called WAN optimization peers. The client and server roles relate to
how a session is started. Any FortiGate unit configured for WAN optimization can be a client-side and a server-side
FortiGate unit at the same time, depending on the direction of the traffic. Client-side FortiGate units initiate WAN
optimization sessions and server-side FortiGate units respond to the session requests.
During this process, the WAN optimization peers identify and optionally authenticate each other. The authentication
group is optional unless the tunnel is a secure tunnel. You need to add authentication groups to support secure tunneling
between WAN optimization peers.
Peer requirements
WAN optimization requires the following configuration on each peer:
l The peer must have a unique host ID.
l Unless authentication groups are used, peers authenticate each other using host ID values. Do not leave the local
host ID at its default value.
FortiOS 7.6.2 Administration Guide 3953
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,953
|
WAN optimization
l The peer must know the host IDs and IP addresses of all of the other peers that it can start WAN optimization
tunnels with. This does not apply if you use authentication groups that accept all peers.
l If a FortiGate unit or VDOM is operating in transparent mode, WAN optimization uses the management IP address
as the peer IP address of the FortiGate unit instead of the address of an interface.
l All peers must have the same local certificate installed on their FortiGate units if the units authenticate by local
certificate. Furthermore, system time must be enabled to ensure that SSL/TLS certificate expiry can be validated.
Similarly, if the units authenticate by pre-shared key (password), administrators must know the password. The type
of authentication is selected in the authentication group. This applies only if you use authentication groups.
Tunnel requests for peer authentication
When a client-side FortiGate unit attempts to start a WAN optimization tunnel with a peer server-side FortiGate unit, the
tunnel request includes the following information:
l The client-side host ID.
l The name of an authentication group, if included in the rule that initiates the tunnel.
l The authentication method it specifies (pre-shared key or certificate), if an authentication group is used.
l The type of tunnel (secure or not).
If the tunnel request does not include an authentication group, authentication will be based on the client-side host ID in
the tunnel request.
If the tunnel request includes an authentication group, the authentication will be based on the settings of this group as
follows:
l The server-side FortiGate unit searches its own configuration for the name of the authentication group in the tunnel
request. If no match is found, the authentication fails.
l If a match is found, the server-side FortiGate unit compares the authentication method in the client and server
authentication groups. If the methods do not match, the authentication fails.
l If the authentication methods match, the server-side FortiGate unit tests the peer acceptance settings in its copy of
the authentication group.
l If the Accept peer(s) setting is Any , the authentication is successful.
l If the Accept peer(s) setting is One, the server-side FortiGate unit compares the client-side host ID in the tunnel
request with the peer name in the server-side authentication group. If the names match, authentication is
successful. If a match is not found, authentication fails.
l If the Accept peer(s) setting is Defined Peers Only, the server-side FortiGate unit compares the client-side host
ID in the tunnel request with the server-side peer list. If a match is found, authentication is successful. If a
match is not found, authentication fails.
After a tunnel is established, multiple WAN optimization sessions can start and stop between peers without restarting the
tunnel.
Tunnels
All optimized traffic passes between the FortiGate units over a WAN optimization tunnel. Traffic in the tunnel can be sent
in plain text or encrypted. Both plain text and the encrypted tunnels use TCP destination port 7810.
FortiOS 7.6.2 Administration Guide 3954
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,954
|
WAN optimization
Secure tunneling
You can configure a WAN optimization profile to use SSL secure tunneling to encrypt the traffic in the WAN optimization
tunnel using AES-128bit-CBC SSL. WAN optimization uses FortiASIC acceleration to accelerate SSL decryption and
encryption of the secure tunnel. Secure tunneling can be enabled in both manual and active-passive WAN optimization
configuration. See Manual and active-passive on page 3959 for more information.
To use secure tunneling, you must add an authentication group and enable SSL Secure Tunneling in a WAN
optimization profile. The Accept peers(s) setting of the authentication group does not affect secure tunneling. See
Secure tunneling configuration example on page 3975 for sample configuration.
Tunnel sharing
Tunnel sharing means multiple WAN optimization sessions share the same tunnel. It can improve performance by
reducing the number of WAN optimization tunnels between FortiGate units. Having fewer tunnels means less data to
manage. Also, tunnel setup requires more than one exchange of information between the ends of the tunnel. Once the
tunnel is set up, each new session that shares the tunnel avoids tunnel setup delays.
Tunnel sharing also uses bandwidth more efficiently by reducing the chances that small packets will be sent down the
tunnel. For example, suppose a FortiGate unit is processing five WAN optimization sessions and each session has 100
bytes to send. If these sessions use a shared tunnel, WAN optimization combines the packets from all five sessions into
one 500-byte packet. If each session uses its own private tunnel, five 100-byte packets will be sent instead. Each packet
also requires a TCP ACK reply. The combined packet in the shared tunnel requires one TCP ACK packet. The separate
packets in the private tunnels require five.
Tunnel sharing is not always recommended and may not always be the best practice. For instance, aggressive and nonaggressive protocols should not share the same tunnel. An aggressive protocol can be defined as a protocol that is able
to get more bandwidth than a non-aggressive protocol, for example, HTTP and FTP. If aggressive and non-aggressive
protocols share the same tunnel, the aggressive protocols may take all of the available bandwidth. As a result, the
performance of less aggressive protocols could be reduced.
To avoid this problem, rules for HTTP and FTP traffic should have their own tunnel. To do this, set tunnel-sharing to
private for WAN optimization rules that accept HTTP or FTP traffic.
It is also useful to set tunnel-sharing to express-shared for applications, such as Telnet, that are very interactive
but not aggressive.
Set tunnel-sharing to shared for applications that are not aggressive and are not sensitive to latency or delays.
FortiOS 7.6.2 Administration Guide 3955
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.