> Chapter 17 - Logging and Reporting > Logging and reporting for small networks

Logging and reporting for small networks

This section explains how to configure the FortiGate unit for logging and reporting in a small office or SOHO/SMB network. To properly configure this type of network, you will be modifying the default log settings, as well as the default FortiOS report.

The following procedures are examples and can be used to help you when configuring your own network’s log topology. Since some of these settings must be modified or enabled or disabled in the CLI, it is recommended to review the FortiGate CLI Reference for any additional information about the commands used herein, as well as any that you would need to use in your own network’s log topology.

Modifying default log device settings

The default log device settings must be modified so that system performance is not compromised. The FortiGate unit, by default, has all logging of FortiGate features enabled, except for traffic logging. The default logging location will be either the FortiGate unit’s system memory or hard disk, depending on the model. Units with a flash disk are not recommended for disk logging.

Modifying the FortiGate unit’s system memory default settings

When the FortiGate unit’s default log device is its system memory, the following is modified for a small network topology. The following is an example of how to modify these default settings.

To modify the default system memory settings

Log in to the CLI.
Enter the following command syntax to modify the logging settings:

config log memory setting

set status enable

end

The following example command syntax modifies which FortiGate features that are enabled for logging:

config log memory filter

set forward-traffic enable

set local-traffic enable

set sniffer-traffic enable

set anomaly enable

set voip disable

set multicast-traffic enable

set dns enable

end

Modifying the FortiGate unit’s hard disk default settings

When the FortiGate unit’s default log device is its hard disk, you need to modify those settings to your network’s logging needs so that you can effectively log what you want logged. The following is an example of how to modify these default settings.

To modify the default hard disk settings

Log in to the CLI.
Enter the following command syntax to modify the logging settings:

config log disk setting

set ips-archive disable

set status enable

set max-log-file-size 1000

set storage FLASH

set log-quota 100

set report-quota 100

end

In the CLI, enter the following to disable certain event log messages that you do not want logged:

config log disk filter

set sniffer-traffic disable

set local-traffic enable

end

Testing sending logs to the log device

After modifying both the settings and the FortiGate features for logging, you can test that the modified settings are working properly. This test is done in the CLI.

To test sending logs to the log device

In the CLI, enter the following command syntax:

diag log test

When you enter the command, the following appears:

generating a system event message with level - warning

generating an infected virus message with level - warning

generating a blocked virus message with level - warning

generating a URL block message with level - warning

generating a DLP message with level - warning

generating an IPS log message

generating an anomaly log message

generating an application control IM message with level - information

generating an IPv6 application control IM message with level - information

generating deep application control logs with level - information

generating an antispam message with level - notification

generating an allowed traffic message with level - notice

generating a multicast traffic message with level - notice

generating a ipv6 traffic message with level - notice

generating a wanopt traffic log message with level - notification

generating a HA event message with level - warning

generating netscan log messages with level - notice

generating a VOIP event message with level - information

generating a DNS event message with level - information

generating authentication event messages

generating a Forticlient message with level - information

generating a NAC QUARANTINE message with level - notification

generating a URL block message with level - warning

In the web-based interface, go to Log & Report > Event Log > User, and view the logs to see some of the recently generated test log messages.
You will be able to tell the test log messages from real log messages because they do not have “real” information; for example, the test log messages for the vulnerability scan contain the destination IP address of 1.1.1.1 or 2.2.2.2.

Configuring the backup solution

A backup solution provides a way to ensure logs are not lost. The following backup solution explains logging to a FortiCloud server and uploading logs to a FortiAnalyzer unit. With this backup solution, there can be three simultaneous storage locations for logs, the first being the FortiGate unit itself, the FortiAnalyzer unit and then the FortiCloud server.

Configuring logging to a FortiCloud server

The FortiCloud server can be used as a redundant backup, or your primary logging solution. The following assumes that this service has already been registered, and a subscription has been purchased for expanded space. The following is an example of how to these settings are configured for a network’s log configuration. You need to have access to both the CLI and the web-based manager when configuring uploading of logs. The upload time and interval settings can be configured in the web-based interface.

To configure logging to the FortiCloud server

Go to System > Dashboard > Status and click Login next to FortiCloud in the License Information widget.
Enter your username and password, and click OK. (Or register, if you have not yet done so.)
Logs will automatically be uploaded to FortiCloud as long as your FortiGate is linked to your FortiCloud account.
To configure the upload time and interval, go to Log & Report > Log Config > Log Settings.
Under the Logging and Archiving header, you can select your desired upload time.

With FortiCloud you can easily store and access FortiGate logs that can give you valuable insight into the health and security of your network.

Configuring uploading logs to the FortiAnalyzer unit

The logs will be uploaded to the FortiAnalyzer unit at a scheduled time. The following is an example of how to upload logs to a FortiAnalyzer unit.

To upload logs to a FortiAnalyzer unit

Go to Log & Report > Log Config > Log Settings.
In the Logging and Archiving section, select the check box beside Send Logs to FortiAnalyzer/FortiManager.
Select FortiAnalyzer (Daily at 00:00).
Enter the FortiAnalyzer unit’s IP address in the IP Address field.
To configure the daily upload time, open the CLI.
Enter the following to configure when the upload occurs, and the time when the unit uploads the logs:

config log fortianalyzer setting

set upload-interval {daily | weekly | monthly}

set upload-time <hh:mm>

end

To change the upload time, in the web-based manager, select Change beside the upload time period, and then make the changes in the Upload Schedule window. Select OK.

Testing uploading logs to a FortiAnalyzer unit

You should test that the FortiGate unit can upload logs to the FortiAnalyzer unit, so that the settings are configured properly.

To test the FortiAnalyzer upload settings

Go to Log & Report > Log Config > Log Settings.
In the Logging and Archiving section, under Send Logs to FortiAnalyzer/FortiManager, change the time to the current time by selecting Change.
For example, the current time is 11:10 am, so Change now has the time 11:10.
Select OK.

The logs will be immediately sent to the FortiAnalyzer unit, and will be available to view from within the FortiAnalyzer’s interface.

Modifying the default FortiOS report

The default FortiOS report is provided to help you quickly and easily configure and generate a report. The following is an example of how to modify the default FortiOS report.

To modify the default FortiOS report

In the web-based manager, go to Log & Report > Report > Local.
Select Customize to open the Report Editor.
Change the default Fortinet image to the new image: select the Fortinet image and right-click so that Delete icon appears, and then select Delete; drag the Image icon to the box where the Fortinet image was previous; choose or upload a new image and then select OK.
Return to Log & Report > Report > Local.
Under Report Options, set the Generate report schedule to Daily and set a Time for the report to be compiled every day.
Enable Email Generated Reports. You may have to configure an SMTP server to send the reports before this option can be enabled. The SMTP configuration can be found in System > Config > Messaging Servers.
Select Apply to save the changes.
Select Run Now to generate a new On Demand report based on your changes.
Select the report from the Historical Reports list to view it.

Running On Demand reports can be a good way to compare report modifications as you configure.