Friday, 3 August 2018

How to Setup Response Pages in VWire Mode

How to Setup Response Pages in VWire Mode

by bparker on ‎04-04-2014 05:08 AM - edited on ‎08-28-2015 12:17 PM by (9,861 Views)

Overview

This document will walkthrough the basic steps needed to setup and demonstrate Application Block Pages and URL filtering pages while the Palo Alto Networks firewall is in VWire mode.

Note: Do not use Chrome to test these pages. Chrome will force many connections to SSL even if choosing non-SSL traffic, because of this decryption will need setup due to SSL errors introduced. 

Additional information can be found in the following article:  https://live.paloaltonetworks.com/docs/DOC-3496

Steps

  1. From the WebGUI, enable the Application Block Page in Device > Response Pages > Action Enable:image1-Response Pages.png
  2. Verify the VWire in Network > Interfaces > Ethernet is being used:image2 - interfaces.png
  3. Create URL filtering profiles. For example, the following profile will look for Social-Networking URLs and present a Continue page to not only monitor, but also change user behavior. 
    This is done by going to: Object > Security Profiles > URL Filtering:image3 - URL Filtering.png
  4. Create security policies to use the URL Profile in Policies > Security.  The following example policy will match all traffic from 'inside(trust) to outside(untrust) interfaces' and match the Active Directory username. It then has the URL filter policy created above applied:

    Image 4 - Security policy.png
  5. Commit
  6. The results are as follows:
    From Firefox to http://facebook.com with URL Filtering no decryption:Image 5 - Firefox 1.png

    For https://facebook.com in Firefox with URL Filtering no decryption:Image 6 - FireFox 2 .png

    For https://facebook.com in Chrome with URL filtering no decryptionImage 7 - Chrome 1.png

For Application Blocking instead of URL Filtering Block Pages
  1. Change the security policy to the following:  
    Remove the URL Profile, add Facebook as an application, change service to application-default, and set the action to Deny:

    Image 8 - Security Application.png
  2. Commit
  3. Test
    Results:
    In Firefox to http://facebook.com with Application denied, no decryption:Image 9 - firefox 4.png

    In Chrome to http://facebook.com with Application denied, no decryption:Image 10 - Firefox 5.png

    In Firefox to https://facebook.com with Application denied, no decryption:Image 11 - Firefox 6.png

    In Chrome to https://facebook.com with Application denied, no decryption:Image 12 - Chrome 2.png

Enabling Basic Forward Proxy or Outbound Decryption, using a Self Signed Certificate
  1. From the WebGUI, go to Device > Certificate Management > Certificates > Generate. Create a new self-signed certificate that is a certificate authority. Click Generate and receive the following message: Image 13 - Cert.png
  2. Click on the certificate to open it and select Forward Trust Certificate:

    Image 14 - Cert 2.png
  3. Go to Policies > Decryption and create a new decryption policy to match the following:
    Source zone = Trust
    Source user = AD user
    Destination Zone = Untrust
    Action = Decrypt
    Type = ssl-forward-proxy

    Image 15 - Decryption.png
  4. Commit
Test Application Block PagesIn Firefox: Note the connection is untrusted, because it has not been added to the Palo Alto Networks self-signed certificate to the computer and browsers root folder. Follow the steps below to add an exception:
Image 16 - Firefox ssl 1.png

Image 17 - firefox ssl 2.png

Image 18 - Firefox ssl 3.png
In Chrome: Perform the same process as in Firefox:

Image 19 - Chrome SSL 1.png

Image 20 - Chrome SSL 2.png

Image 21 - Chrome SSL 3.png

To test URL Filtering again, switch the security rule back to the URL filtering profile used previously and Commit.
 In Firefox using https://facebook.com:Image 22 - Firefox SSL 4.png
In Chrome using https://facebook.com:Image 23 - Firefox SSL 5.png

However, please note that before testing an error was received like the one below, so Chrome depending on extensions and other security features, can have more security and can search for invalid SSL credentials to catch "Man in the Middle attacks".
Image 24 - Chrome SSL 5.png

No comments:

Post a Comment