Configure GlobalProtect to Facilitate Multi-Factor Authentication Notifications

To protect critical applications and stop attackers from using stolen credentials to conduct lateral movement throughout your network, you can configure policy-based multi-factor authentication (MFA). This ensures that each user responds to multiple authentication challenges of different types (factors) before they can access highly sensitive services and applications.
gp-multi-factor.png
If a user session matches the Authentication policy, the type of application or service determines the user experience for notifications about the authentication challenge:
  • (
    Windows or Mac endpoints only
    )
    Non-browser-based applications
    —To facilitate MFA notifications for non-HTTP applications (such as Perforce) on Windows or Mac endpoints, a GlobalProtect client is required. When a session matches an Authentication policy rule, the firewall sends a UDP notification to the GlobalProtect client with an embedded URL link to the Authentication Portal page. The GlobalProtect client then displays this message as a pop up notification to the user.
    MFA-message.png
  • Browser-based applications
    —Browser-based applications do not require GlobalProtect to display notification messages to the user. When the firewall identifies a session as web-browsing traffic (based on App-ID), the firewall automatically presents the user with Authentication Portal page (previously called the Captive Portal page) specified in the Authentication policy rule. For more information, see Configure Multi-Factor Authentication.
To configure GlobalProtect to display MFA notifications for non-browser-based applications, use the following workflow:
  1. Before you configure GlobalProtect, configure multi-factor authentication on the firewall.
    If you are using two-factor authentication with GlobalProtect to authenticate to the gateway or portal, a RADIUS server profile is required. If you are using GlobalProtect to notify the user about an authentication policy match (UDP message), a Multi Factor Authentication server profile is sufficient.
    To use multi-factor authentication for protecting sensitive resources, the easiest solution is to integrate the firewall with an MFA vendor that is already established in your network. When your MFA structure is ready, you can start configuring the components of your authentication policy. For more information, refer to Configure Multi-Factor Authentication.
    • Enable Captive Portal to record authentication timestamps and update user mappings.
    • Create server profiles that define how the firewall will connect to the services that authenticate users.
    • Assign the server profiles to an Authentication profile which specifies authentication parameters.
    • Configure a Security policy rule that allows users to access the resources that require authentication.
  2. (
    External gateways only
    ) For GlobalProtect to support multi-factor authentication on external gateways, you must Configure a response page for the ingress tunnel interface on the firewall:
    1. Select
      Device
      Response Pages
      MFA Login Page
      .
    2. Select and then
      Export
      the
      Predefined
      template to a location of your choice.
    3. On your client system, use an HTML editor to customize the downloaded response page and save it with a unique filename.
    4. Return to the
      MFA Login Page
      dialog on the firewall,
      Import
      your customized page,
      Browse
      to select the
      Import File
      , select the
      Destination
      (virtual system or shared location), click
      OK
      , and click
      Close
      .
  3. (
    External gateways only
    ) Enable
    Response Pages
    as a permitted service on the
    Interface Mgmt
    profile:
    1. Select
      Network
      Network Profiles
      Interface Mgmt
      and then select the profile.
    2. In the
      Permitted Services
      area, select
      Response Pages
      and click
      OK
      .
  4. (
    External gateways only
    ) Attach the
    Interface Mgmt
    profile to a tunnel interface:
    1. Select
      Network
      Interfaces
      Tunnel
      , and the tunnel interface on which you want to use the response page.
    2. Select
      Advanced
      , and then select the
      Interface Mgmt
      profile you configured in the previous step as the
      Management Profile
      .
  5. (
    External gateways only
    )
    Enable User Identification
    on the Zone associated with the tunnel interface (
    Network
    Zones
    <tunnel-zone
    ).
  6. Configure GlobalProtect clients to support multi-factor authentication notifications for non-browser-based applications.
    1. Select
      Network
      GlobalProtect
      Portals
      and select a portal configuration (or
      Add
      one).
    2. Select
      Agent
      and then select an existing agent configuration or
      Add
      one.
    3. In the
      App
      tab, specify the following:
      • Set
        Enable Inbound Authentication Prompts from MFA Gateways
        to
        Yes
        . To support multi-factor authentication (MFA), a GlobalProtect client must receive and acknowledge UDP prompts that are inbound from the gateway. Select
        Yes
        to enable a GlobalProtect client to receive and acknowledge the prompt. By default, the value is set to
        No
        meaning GlobalProtect will block UDP prompts from the gateway.
      • In
        Network Port for Inbound Authentication Prompts (UDP)
        , specify the port number a GlobalProtect client uses to receive inbound authentication prompts from MFA gateways. The default port is 4501. To change the port, specify a number from 1 to 65535.
      • In
        Trusted MFA Gateways
        , specify the list of authentication gateways a GlobalProtect client will trust for multi-factor authentication. When a GlobalProtect client receives a UDP message on the specified network port, GlobalProtect displays an authentication message only if the UDP prompt comes from a trusted gateway.
      • Configure the
        Default Message for Inbound Authentication Prompts
        . When users try to access a resource that requires additional authentication, GlobalProtect receives a UDP packet containing the inbound authentication prompt and displays this message. The UDP packet also contains the URL for the Authentication Portal page you specified in Configure Multi-Factor Authentication. GlobalProtect automatically appends the URL to the message. For example, to display the notification shown in the beginning of this topic enter the following message:
        You have attempted to access a protected resource that requires additional authentication. Proceed to authenticate at:
    4. Save the agent configuration (click
      OK
      twice), and then
      Commit
      your changes.

Related Documentation