GlobalProtect Portals Agent HIP Data Collection Tab
Table of Contents
9.1 (EoL)
Expand all | Collapse all
-
- Objects > Addresses
- Objects > Address Groups
- Objects > Regions
- Objects > Dynamic User Groups
- Objects > Application Groups
- Objects > Application Filters
- Objects > Services
- Objects > Service Groups
- Objects > External Dynamic Lists
- Objects > Custom Objects > Spyware/Vulnerability
- Objects > Custom Objects > URL Category
- Objects > Security Profiles > Antivirus
- Objects > Security Profiles > Anti-Spyware Profile
- Objects > Security Profiles > Vulnerability Protection
- Objects > Security Profiles > File Blocking
- Objects > Security Profiles > WildFire Analysis
- Objects > Security Profiles > Data Filtering
- Objects > Security Profiles > DoS Protection
- Objects > Security Profiles > GTP Protection
- Objects > Security Profiles > SCTP Protection
- Objects > Security Profile Groups
- Objects > Log Forwarding
- Objects > Authentication
- Objects > Decryption > Forwarding Profile
- Objects > Schedules
-
-
- Firewall Interfaces Overview
- Common Building Blocks for Firewall Interfaces
- Common Building Blocks for PA-7000 Series Firewall Interfaces
- Tap Interface
- HA Interface
- Virtual Wire Interface
- Virtual Wire Subinterface
- PA-7000 Series Layer 2 Interface
- PA-7000 Series Layer 2 Subinterface
- PA-7000 Series Layer 3 Interface
- Layer 3 Interface
- Layer 3 Subinterface
- Log Card Interface
- Log Card Subinterface
- Decrypt Mirror Interface
- Aggregate Ethernet (AE) Interface Group
- Aggregate Ethernet (AE) Interface
- Network > Interfaces > VLAN
- Network > Interfaces > Loopback
- Network > Interfaces > Tunnel
- Network > Interfaces > SD-WAN
- Network > VLANs
- Network > Virtual Wires
-
- Network > Network Profiles > GlobalProtect IPSec Crypto
- Network > Network Profiles > IPSec Crypto
- Network > Network Profiles > IKE Crypto
- Network > Network Profiles > Monitor
- Network > Network Profiles > Interface Mgmt
- Network > Network Profiles > QoS
- Network > Network Profiles > LLDP Profile
- Network > Network Profiles > SD-WAN Interface Profile
-
-
- Device > Setup
- Device > Setup > Management
- Device > Setup > Interfaces
- Device > Setup > Telemetry
- Device > Setup > Content-ID
- Device > Setup > WildFire
- Device > Log Forwarding Card
- Device > Config Audit
- Device > Administrators
- Device > Admin Roles
- Device > Access Domain
- Device > Authentication Sequence
-
- Security Policy Match
- QoS Policy Match
- Authentication Policy Match
- Decryption/SSL Policy Match
- NAT Policy Match
- Policy Based Forwarding Policy Match
- DoS Policy Match
- Routing
- Test Wildfire
- Threat Vault
- Ping
- Trace Route
- Log Collector Connectivity
- External Dynamic List
- Update Server
- Test Cloud Logging Service Status
- Test Cloud GP Service Status
- Device > Virtual Systems
- Device > Shared Gateways
- Device > Certificate Management
- Device > Certificate Management > Certificate Profile
- Device > Certificate Management > OCSP Responder
- Device > Certificate Management > SSL/TLS Service Profile
- Device > Certificate Management > SCEP
- Device > Certificate Management > SSL Decryption Exclusion
- Device > Response Pages
- Device > Server Profiles
- Device > Server Profiles > SNMP Trap
- Device > Server Profiles > Syslog
- Device > Server Profiles > Email
- Device > Server Profiles > HTTP
- Device > Server Profiles > NetFlow
- Device > Server Profiles > RADIUS
- Device > Server Profiles > TACACS+
- Device > Server Profiles > LDAP
- Device > Server Profiles > Kerberos
- Device > Server Profiles > SAML Identity Provider
- Device > Server Profiles > DNS
- Device > Server Profiles > Multi Factor Authentication
- Device > Local User Database > Users
- Device > Local User Database > User Groups
- Device > Scheduled Log Export
- Device > Software
- Device > Dynamic Updates
- Device > Licenses
- Device > Support
-
- Network > GlobalProtect > MDM
- Network > GlobalProtect > Device Block List
- Network > GlobalProtect > Clientless Apps
- Network > GlobalProtect > Clientless App Groups
- Objects > GlobalProtect > HIP Profiles
-
- Use the Panorama Web Interface
- Context Switch
- Panorama Commit Operations
- Defining Policies on Panorama
- Log Storage Partitions for a Panorama Virtual Appliance in Legacy Mode
- Panorama > Setup > Interfaces
- Panorama > High Availability
- Panorama > Administrators
- Panorama > Admin Roles
- Panorama > Access Domains
- Panorama > Device Groups
- Panorama > Plugins
- Panorama > Log Ingestion Profile
- Panorama > Log Settings
- Panorama > Scheduled Config Export
End-of-Life (EoL)
GlobalProtect Portals Agent HIP Data Collection Tab
- NetworkGlobalProtectPortals<portal-config>Agent<agent-config>HIP Data Collection
Select the HIP Data Collection tab to
define the data that the app collects from the endpoint in the HIP
report:
GlobalProtect HIP
Data Collection Configuration Settings | Description |
---|---|
Collect HIP Data | Clear this option to prevent the app from
collecting and sending HIP data. Enable
GlobalProtect to collect HIP data for HIP-based policy enforcement,
so the firewall can match HIP data from endpoints against the HIP
objects and/or HIP profiles you define and then apply the appropriate
policy. |
Max Wait Time (sec) | Specify how many seconds the app should
search for HIP data before submitting the available data (range
is 10-60; default is 20). |
Certificate Profile | Select the certificate profile that the
GlobalProtect portal uses to match the machine certificate sent
by the GlobalProtect app. |
Exclude Categories | Select Exclude Categories to
specify the host information categories for which you do not want
the app to collect HIP data. Select a Category (such
as data-loss-prevention) to exclude from HIP collection. After selecting
a category, you can Add a particular Vendor and,
then, you can Add specific products from
the vendor to further refine the exclusion as needed. Click OK to
save settings in each dialog.
(Requires GlobalProtect app version 6.2.0 or later and content
release version 8699-7991) If you don't want to exclude an
entire vendor, but you do want to exclude specific patches from a
vendor, after adding the vendor you can specify the patch
name or number and optionally a date until which you want to exclude
the patch updates from the HIP report using the following format:
Exclude:[kb-article-id1: MM/DD/YYYY],
[kb-article-id2: MM/DD/YYYY]
Where kb-article-id is the name or number in the
attribute ( for example
<kb-article-id>2267602</kb-article-id>)
and the MM/DD/YYYY specifies the date up to which
the patch is excluded from the HIP report. If you do not set a date,
the patch will be excluded from the HIP report indefinitely. If you
choose to set a date, the patch will be excluded until the specified
date. |
Custom Checks | Select Custom Checks to
define custom host information you want the app to collect. For
example, if you have any required applications that are not included
in the Vendor or Product lists for creating HIP objects, you can
create a custom check to determine whether that application is installed
(it has a corresponding Windows registry or Mac plist key) or is
currently running (has a corresponding running process):
|