External malware block list
The external malware block list allows users to add their own malware signatures in the form of MD5, SHA1, and SHA256 hashes. The FortiGate's antivirus database retrieves an external malware hash list from a remote server and polls the hash list every n minutes for updates.
The external malware block list can be used in both proxy-based and flow-based policy inspections, but it is not supported in AV quick scan mode.
Note that using different types of hashes simultaneously may slow down the performance of malware scanning. It is recommended to use one type of hash.
To configure antivirus to use an external block list:
- Create the malware hash list.
- Configure the external malware block list source:
- Go to Security Fabric > External Connectors and click Create New.
- Click Malware Hash.
- Configure the settings as needed. The URI must point to the malware hash list on the remote server.
- Click OK.
- To view entries inside the malware block list on the External Connectors page, hover over the malware hash card and click View Entries.
The malware hash threat feed displays:
- Enable the external malware block list in the antivirus profile:
- Go to Security Profiles > AntiVirus and edit the antivirus profile.
- In the Virus Outbreak Prevention section, enable Use External Malware Block List.
- Click OK.
The malware hash list follows a strict format in order for its contents to be valid. Malware hash signature entries must be separated into each line. A valid signature needs to follow this format:
# MD5 Entry with hash description aa67243f746e5d76f68ec809355ec234 md5_sample1 # SHA1 Entry with hash description a57983cb39e25ab80d7d3dc05695dd0ee0e49766 sha1_sample2 # SHA256 Entry with hash description ae9bc0b4c5639d977d720e4271da06b50f7c60d1e2070e9c75cc59ab30e49379 sha256_sample1 # Entry without hash description 0289b0d967cb7b1fb1451339c7b9818a621903090e0020366ab415c549212521 # Invalid entries 7688499dc71b932feb126347289c0b8a_md5_sample2 7614e98badca10b5e2d08f8664c519b7a906fbd5180ea5d04a82fce9796a4b87sha256_sample3
To verify the scanunit daemon updated itself with the external hashes:
# diagnose sys scanunit malware-list list md5 'aa67243f746e5d76f68ec809355ec234' profile 'hash_list' description 'md5_sample1' sha1 'a57983cb39e25ab80d7d3dc05695dd0ee0e49766' profile 'hash_list' description 'sha1_sample2' sha256 '0289b0d967cb7b1fb1451339c7b9818a621903090e0020366ab415c549212521' profile 'hash_list' description '' sha256 'ae9bc0b4c5639d977d720e4271da06b50f7c60d1e2070e9c75cc59ab30e49379' profile 'hash_list' description 'sha256_sample1'