Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • Administration Guide

    Home FortiSandbox 3.1.0 Administration Guide
    3.1.0
    5.0.0
    4.4.6
    4.4.5
    4.4.4
    4.4.3
    4.4.2
    4.4.1
    4.4.0
    4.2.7
    4.2.6
    4.2.5
    4.2.4
    4.2.3
    4.2.2
    4.2.1
    4.2.0
    4.0.5
    4.0.4
    4.0.3
    4.0.2
    4.0.1
    4.0.0
    3.2.4
    3.2.3
    3.2.2
    3.2.1
    3.2.0
    3.1.5
    3.1.4
    3.1.3
    3.1.2
    3.1.1
    3.1.0
    3.0.7
    3.0.6

    Scan Profile Job Queue Tab

    Scan Profile Job Queue Tab

    The Job Queue tab is to define file types and URLs that are allowed to enter the job queue if they are from a sniffer, device, adapter and/or network share.

    If files or URLs are submitted through On-Demand or RPC JSON API, they will always be put into the job queue, even if their file types are not set to enter the job queue.
    To allow a file type to enter the job queue:

    Click its toggle button on the right side to enable it. If the button is greyed out, files of that type will be dropped.

    URL Detection

    When URL detection is enabled, it means FortiSandbox will scan URLs (WEBLinks). The user can also define Default Depth setting (from 0 to 5) FortiSandbox should visit the URL and the Default Timeout value that FortiSandbox should stop even when not all depths have been scanned.

    If the FortiSandbox unit has a long queue of pending jobs, users should consider turning off certain file types to job queue. For example, in most network environments, static web files (JavaScript, html, aspx files, etc...) and Adobe Flash files comprise a large portion of all files. When performance issue are met, users can consider turning them off.

    If a file type is turned off, files of this type already in the job queue will still be processed. Users can use the pending-jobs CLI command or Scan Input > Job Queue page to purge them if required.

    To determine the number of each file type and its input source, users can use CLI command pending-jobs or Scan Input > Job Queue page.
    Previous
    Next

    Scan Profile Job Queue Tab

    Scan Profile Job Queue Tab

    The Job Queue tab is to define file types and URLs that are allowed to enter the job queue if they are from a sniffer, device, adapter and/or network share.

    If files or URLs are submitted through On-Demand or RPC JSON API, they will always be put into the job queue, even if their file types are not set to enter the job queue.
    To allow a file type to enter the job queue:

    Click its toggle button on the right side to enable it. If the button is greyed out, files of that type will be dropped.

    URL Detection

    When URL detection is enabled, it means FortiSandbox will scan URLs (WEBLinks). The user can also define Default Depth setting (from 0 to 5) FortiSandbox should visit the URL and the Default Timeout value that FortiSandbox should stop even when not all depths have been scanned.

    If the FortiSandbox unit has a long queue of pending jobs, users should consider turning off certain file types to job queue. For example, in most network environments, static web files (JavaScript, html, aspx files, etc...) and Adobe Flash files comprise a large portion of all files. When performance issue are met, users can consider turning them off.

    If a file type is turned off, files of this type already in the job queue will still be processed. Users can use the pending-jobs CLI command or Scan Input > Job Queue page to purge them if required.

    To determine the number of each file type and its input source, users can use CLI command pending-jobs or Scan Input > Job Queue page.
    Previous
    Next