Configure a File Blocking Profile (PAN-OS & Panorama)

1. Create the file blocking profile.
   1. Select ObjectsSecurity ProfilesFile Blocking and Add a profile.
   2. Enter a Name for the file blocking profile such as Block_EXE.
   3. (Optional) Enter a Description, such as Block users from downloading exe files from websites.
   4. (Optional) Specify that the profile is Shared with:
      • Every virtual system (vsys) on a multi-vsys firewall—If cleared (disabled), the profile is available only to the Virtual System selected in the Objects tab.
      • Every device group on Panorama—If cleared (disabled), the profile is available only to the Device Group selected in the Objects tab.
   5. (Optional—Panorama only) Select Disable override to prevent administrators from overriding the settings of this file blocking profile in device groups that inherit the profile. This selection is cleared by default, which means administrators can override the settings for any device group that inherits the profile.
2. Configure the file blocking options.
   1. Add and define a rule for the profile.
   2. Enter a Name for the rule, such as BlockEXE.
   3. Select Any or specify one or more specific Applications for filtering, such as web-browsing.
      Only web browsers can display the response page (continue prompt) that allows users to confirm their Choosing any other application results in blocked traffic for those applications because there is no prompt displayed to allow users to continue.
   4. Select Any or specify one or more specific File Types, such as exe.
   5. Specify the Direction, such as download.
   6. Specify the Action (alert, block, or continue).
      For example, select continue to prompt users for confirmation before they are allowed to download an executable (.exe) file. Alternatively, you could block the specified files or you could configure the firewall to simply trigger an alert when a user downloads an executable file.
      If a server sends an HTTP response header and the contents of a file in different packets, the firewall blocks the file even if the action for that file type is continue.
   7. Click OK to save the profile.
3. Apply the file blocking profile to a security rule.
   1. Select PoliciesSecurity and either select an existing security rule or Add a new rule as described in Create a Security Policy Rule.
   2. On the Actions tab, select the file blocking profile you configured in the previous step. In this example, the profile name is Block_EXE.
   3. Commit your configuration.
4. To test your file blocking configuration, access an endpoint PC in the trust zone of the firewall and attempt to download an executable file from a website in the untrust zone; a response page should display. Click Continue to confirm that you can download the file. You can also set other actions, such as alert or block, which don't provide an option for the user to continue the download. The following shows the default response page for File Blocking:

5. (Optional) Define custom file blocking response pages (DeviceResponse Pages). This allows you to provide more information to users when they see a response page. You can include information such as company policy information and contact information for a Helpdesk.
   When you create a file blocking profile with the continue action, you can choose only the web-browsing application. If you choose any other application, traffic that matches the Security policy won't flow through the firewall because users are not prompted with an option to continue. Additionally, you need to configure and enable a decryption policy for HTTPS websites.

   Check your logs to determine the application used when you test this feature. For example, if you're using Microsoft SharePoint to download files, even though you're using a web-browser to access the site, the application is actually sharepoint-base, or sharepoint-document. (It can help to set the application type to Any for testing.)