Device-ID Overview
Table of Contents
Expand All
|
Collapse All
Next-Generation Firewall Docs
-
PAN-OS 11.1 & Later
- PAN-OS 11.1 & Later
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
- PAN-OS 10.0 (EoL)
- PAN-OS 9.1 (EoL)
- Cloud Management of NGFWs
-
- Management Interfaces
-
- Launch the Web Interface
- Use the Administrator Login Activity Indicators to Detect Account Misuse
- Manage and Monitor Administrative Tasks
- Commit, Validate, and Preview Firewall Configuration Changes
- Commit Selective Configuration Changes
- Export Configuration Table Data
- Use Global Find to Search the Firewall or Panorama Management Server
- Manage Locks for Restricting Configuration Changes
-
-
- Define Access to the Web Interface Tabs
- Provide Granular Access to the Monitor Tab
- Provide Granular Access to the Policy Tab
- Provide Granular Access to the Objects Tab
- Provide Granular Access to the Network Tab
- Provide Granular Access to the Device Tab
- Define User Privacy Settings in the Admin Role Profile
- Restrict Administrator Access to Commit and Validate Functions
- Provide Granular Access to Global Settings
- Provide Granular Access to the Panorama Tab
- Provide Granular Access to Operations Settings
- Panorama Web Interface Access Privileges
-
- Reset the Firewall to Factory Default Settings
-
- Plan Your Authentication Deployment
- Pre-Logon for SAML Authentication
- Configure SAML Authentication
- Configure Kerberos Single Sign-On
- Configure Kerberos Server Authentication
- Configure TACACS+ Authentication
- Configure TACACS Accounting
- Configure RADIUS Authentication
- Configure LDAP Authentication
- Configure Local Database Authentication
- Configure an Authentication Profile and Sequence
- Test Authentication Server Connectivity
- Troubleshoot Authentication Issues
-
- Keys and Certificates
- Default Trusted Certificate Authorities (CAs)
- Certificate Deployment
- Configure the Master Key
- Export a Certificate and Private Key
- Configure a Certificate Profile
- Configure an SSL/TLS Service Profile
- Configure an SSH Service Profile
- Replace the Certificate for Inbound Management Traffic
- Configure the Key Size for SSL Forward Proxy Server Certificates
-
- HA Overview
-
- Prerequisites for Active/Active HA
- Configure Active/Active HA
-
- Use Case: Configure Active/Active HA with Route-Based Redundancy
- Use Case: Configure Active/Active HA with Floating IP Addresses
- Use Case: Configure Active/Active HA with ARP Load-Sharing
- Use Case: Configure Active/Active HA with Floating IP Address Bound to Active-Primary Firewall
- Use Case: Configure Active/Active HA with Source DIPP NAT Using Floating IP Addresses
- Use Case: Configure Separate Source NAT IP Address Pools for Active/Active HA Firewalls
- Use Case: Configure Active/Active HA for ARP Load-Sharing with Destination NAT
- Use Case: Configure Active/Active HA for ARP Load-Sharing with Destination NAT in Layer 3
- HA Clustering Overview
- HA Clustering Best Practices and Provisioning
- Configure HA Clustering
- Refresh HA1 SSH Keys and Configure Key Options
- HA Firewall States
- Reference: HA Synchronization
-
- Use the Dashboard
- Monitor Applications and Threats
- Monitor Block List
-
- Report Types
- View Reports
- Configure the Expiration Period and Run Time for Reports
- Disable Predefined Reports
- Custom Reports
- Generate Custom Reports
- Generate the SaaS Application Usage Report
- Manage PDF Summary Reports
- Generate User/Group Activity Reports
- Manage Report Groups
- Schedule Reports for Email Delivery
- Manage Report Storage Capacity
- View Policy Rule Usage
- Use External Services for Monitoring
- Configure Log Forwarding
- Configure Email Alerts
-
- Configure Syslog Monitoring
-
- Traffic Log Fields
- Threat Log Fields
- URL Filtering Log Fields
- Data Filtering Log Fields
- HIP Match Log Fields
- GlobalProtect Log Fields
- IP-Tag Log Fields
- User-ID Log Fields
- Decryption Log Fields
- Tunnel Inspection Log Fields
- SCTP Log Fields
- Authentication Log Fields
- Config Log Fields
- System Log Fields
- Correlated Events Log Fields
- GTP Log Fields
- Audit Log Fields
- Syslog Severity
- Custom Log/Event Format
- Escape Sequences
- Forward Logs to an HTTP/S Destination
- Firewall Interface Identifiers in SNMP Managers and NetFlow Collectors
- Monitor Transceivers
-
- User-ID Overview
- Enable User-ID
- Map Users to Groups
- Enable User- and Group-Based Policy
- Enable Policy for Users with Multiple Accounts
- Verify the User-ID Configuration
-
- App-ID Overview
- App-ID and HTTP/2 Inspection
- Manage Custom or Unknown Applications
- Safely Enable Applications on Default Ports
- Applications with Implicit Support
-
- Prepare to Deploy App-ID Cloud Engine
- Enable or Disable the App-ID Cloud Engine
- App-ID Cloud Engine Processing and Policy Usage
- New App Viewer (Policy Optimizer)
- Add Apps to an Application Filter with Policy Optimizer
- Add Apps to an Application Group with Policy Optimizer
- Add Apps Directly to a Rule with Policy Optimizer
- Replace an RMA Firewall (ACE)
- Impact of License Expiration or Disabling ACE
- Commit Failure Due to Cloud Content Rollback
- Troubleshoot App-ID Cloud Engine
- Application Level Gateways
- Disable the SIP Application-level Gateway (ALG)
- Maintain Custom Timeouts for Data Center Applications
-
- Decryption Overview
-
- Keys and Certificates for Decryption Policies
- SSL Forward Proxy
- SSL Forward Proxy Decryption Profile
- SSL Inbound Inspection
- SSL Inbound Inspection Decryption Profile
- SSL Protocol Settings Decryption Profile
- SSH Proxy
- SSH Proxy Decryption Profile
- Profile for No Decryption
- SSL Decryption for Elliptical Curve Cryptography (ECC) Certificates
- Perfect Forward Secrecy (PFS) Support for SSL Decryption
- SSL Decryption and Subject Alternative Names (SANs)
- TLSv1.3 Decryption
- High Availability Not Supported for Decrypted Sessions
- Decryption Mirroring
- Configure SSL Forward Proxy
- Configure SSL Inbound Inspection
- Configure SSH Proxy
- Configure Server Certificate Verification for Undecrypted Traffic
- Post-Quantum Cryptography Detection and Control
- Enable Users to Opt Out of SSL Decryption
- Temporarily Disable SSL Decryption
- Configure Decryption Port Mirroring
- Verify Decryption
- Activate Free Licenses for Decryption Features
-
- Policy Types
- Policy Objects
- Track Rules Within a Rulebase
- Enforce Policy Rule Description, Tag, and Audit Comment
- Move or Clone a Policy Rule or Object to a Different Virtual System
-
- External Dynamic List
- Built-in External Dynamic Lists
- Configure the Firewall to Access an External Dynamic List
- Retrieve an External Dynamic List from the Web Server
- View External Dynamic List Entries
- Exclude Entries from an External Dynamic List
- Enforce Policy on an External Dynamic List
- Find External Dynamic Lists That Failed Authentication
- Disable Authentication for an External Dynamic List
- Register IP Addresses and Tags Dynamically
- Use Dynamic User Groups in Policy
- Use Auto-Tagging to Automate Security Actions
- CLI Commands for Dynamic IP Addresses and Tags
- Application Override Policy
- Test Policy Rules
-
- Network Segmentation Using Zones
- How Do Zones Protect the Network?
-
PAN-OS 11.1 & Later
- PAN-OS 11.1 & Later
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure a PPPoE Client on a Subinterface
- Configure an IPv6 PPPoE Client
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
-
- DHCP Overview
- Firewall as a DHCP Server and Client
- Firewall as a DHCPv6 Client
- DHCP Messages
- Dynamic IPv6 Addressing on the Management Interface
- Configure an Interface as a DHCP Server
- Configure an Interface as a DHCPv4 Client
- Configure an Interface as a DHCPv6 Client with Prefix Delegation
- Configure the Management Interface as a DHCP Client
- Configure the Management Interface for Dynamic IPv6 Address Assignment
- Configure an Interface as a DHCP Relay Agent
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Create a Source NAT Rule with Persistent DIPP
- PAN-OS
- Strata Cloud Manager
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
- Network Packet Broker Overview
- How Network Packet Broker Works
- Prepare to Deploy Network Packet Broker
- Configure Transparent Bridge Security Chains
- Configure Routed Layer 3 Security Chains
- Network Packet Broker HA Support
- User Interface Changes for Network Packet Broker
- Limitations of Network Packet Broker
- Troubleshoot Network Packet Broker
-
- Enable Advanced Routing
- Logical Router Overview
- Configure a Logical Router
- Create a Static Route
- Configure BGP on an Advanced Routing Engine
- Create BGP Routing Profiles
- Create Filters for the Advanced Routing Engine
- Configure OSPFv2 on an Advanced Routing Engine
- Create OSPF Routing Profiles
- Configure OSPFv3 on an Advanced Routing Engine
- Create OSPFv3 Routing Profiles
- Configure RIPv2 on an Advanced Routing Engine
- Create RIPv2 Routing Profiles
- Create BFD Profiles
- Configure IPv4 Multicast
- Configure MSDP
- Create Multicast Routing Profiles
- Create an IPv4 MRoute
-
-
PAN-OS 11.2
- PAN-OS 11.2
- PAN-OS 11.1
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
- PAN-OS 10.0 (EoL)
- PAN-OS 9.1 (EoL)
- PAN-OS 9.0 (EoL)
- PAN-OS 8.1 (EoL)
- Cloud Management and AIOps for NGFW
Device-ID Overview
Learn about Device-ID.
According to the 2020 Unit 42 IoT Threat Report,
30% of all network-connected devices in an average enterprise are
IoT. This presents a constantly growing area of risk with many possibilities
for exploitation by malicious users. Additionally, once you identify
these devices, how do you secure them from vulnerabilities such
as outdated operating software? Using Device-ID™ on your firewalls,
you can get device context for events on your network, obtain policy
rule recommendations for those devices, write policy rules based
on devices, and enforce Security policy based on the recommendations.
Similar to how User-ID provides user-based policy rules and App-ID
provides app-based policy rules, Device-ID provides policy rules
that are based on a device, regardless of changes to its IP address
or location. By providing traceability for devices and associating
network events with specific devices, Device-ID lets you gain context
for how events relate to devices and adds policy rules that are
associated with devices, instead of users, locations, or IP addresses,
which can change over time. You can use Device-ID in Security, Decryption, Quality
of Service (QoS), and Authentication policies.
For Device-ID features to be available on a firewall, you must
purchase an IoT Security subscription and select the firewall during
the IoT Security onboarding process. There
are two types of IoT Security subscriptions:
- IoT Security Subscription
- IoT Security – Doesn’t Require Data Lake (DRDL) Subscription
With the first subscription, firewalls send data logs to the logging service, which streams them
to IoT Security for analysis and to a Strata Logging Service instance
for storage. The data lake instance can either be a new or existing one. With the second
subscription, firewalls send data logs to the logging service, which streams them to IoT
Security for analysis but not to a Strata Logging Service instance for storage.
It’s important to note that both IoT Security and IoT Security (DRDL) subscriptions
provide the same functionality in terms of IoT Security and Device-ID.
To permit connections to IoT Security, a firewall needs a device
license; and to permit connections to the logging service, it needs
a logging service license. A firewall also requires a device certificate to
authenticate itself when connecting to IoT Security and the logging
service.
If you use PAN-OS version 8.1.0 through PAN-OS 9.1.x on a firewall,
the IoT Security license provides device classification, behavior
analysis, and threat analysis for your devices. If you use PAN-OS
10.0 or later, you can use Device-ID to obtain IP address-to-device
mappings to view device context for network events, use IoT Security
to obtain policy rule recommendations for these devices, and gain
visibility for devices in reports and the ACC.
You can create a device-based Security policy on any Panorama
or firewall that uses PAN-OS version 10.0 or later. To enforce the
Security policy, the device must have a valid IoT Security license.
To identify and classify devices, the IoT Security app uses
metadata from logs, network protocols, and sessions on the firewall.
This does not include private or sensitive information or data that
is not relevant for device identification. Metadata also forms the
basis of the expected behavior for the device, which then establishes
the criteria for the policy rule recommendation that defines what
traffic and protocols to allow for that device.
When a firewall imports Security policy rule recommendations
and IP address-to-device mappings from IoT Security, the firewall
sends its device certificate to
an edge server to authenticate itself. The edge server authenticates
itself to the firewall by sending its own certificate. The firewall
uses Online Certificate Status Protocol (OCSP) to validate the server’s
certificate by checking it against the following sites using HTTP
on TCP port 80:
- *.o.lencr.org
- x1.c.lencr.org
Panorama performs the same check to validate the edge server’s
certificate when Panorama imports policy rule recommendations from
IoT Security.
After IoT Security identifies and classifies the devices in your
network using the Palo Alto Networks firewalls already there—so
you don’t have to implement new devices or third-party solutions—Device-ID
can leverage this data to match devices with policy rules and provide
device context for network events. Through the visibility that the
firewall or Panorama provides for traffic, apps, users, devices,
and threats, you can instantly trace network events back to individual
devices and obtain Security policy rule recommendations for securing
those devices.
All firewall platforms that support PAN-OS 10.0 also support
Device-ID and IoT Security with the exception of the VM-50 series,
VM-200, and the CN series.
There are six levels of classification (also known as attributes)
for devices:
Attribute | Example |
---|---|
Category | Printer |
Profile | Sharp Printer |
Model | MX-6070N |
OS Version | ThreadX 5 |
OS Family | ThreadX RTOS |
Vendor | SHARP Corporation |
To obtain policy rule recommendations for devices in your network, the firewall observes traffic
to generate Enhanced Application logs (EALs). The firewall then forwards the EALs to the
logging service. IoT Security receives logs from the logging service for analysis,
provides IP address-to-device mappings, and generates the latest Security
policy rule recommendations for the device profiles of your devices. You can
then import the rule recommendations to the Security policy rulebase on a firewall or,
through Panorama, to the rulebase on multiple firewalls and commit your Security
policy.
To identify devices with dynamically assigned network settings,
the firewall must be able to observe DHCP broadcast and unicast
traffic on your network. IoT Security also supports static IP devices.
The more traffic the firewall can observe, the more accurate the
policy rule recommendations are for the device and the more rapid
and accurate the IP address-to-device mappings are for the device.
When a device sends DHCP traffic to obtain its network settings,
the firewall observes this type of request and generates EALs to
send to the logging service, where IoT Security accesses them for
analysis.
To observe traffic on an L2 interface, you must configure
a VLAN for that interface. By allowing the firewall to treat the
interface as an L3 interface for a DHCP relay, it can observe the
DHCP broadcast traffic without impacting traffic or performance.
Because the firewall needs to both detect the devices based on
their traffic and then enforce Security policy for those devices,
the firewall acts as both a sensor to collect metadata
from devices and an enforcer by enforcing your Security
policy for the devices. IoT Security automatically detects new devices
as soon as they send DHCP traffic and can identify 95% of devices
within the first week.
In addition to the traffic that traverses firewalls, there are options to obtain
traffic metadata from other areas of your network where device traffic doesn't reach
the firewall. You can mirror traffic from network switches through GRE
tunnels, forward server logs from DHCP servers,
use SNMP to query switches, and integrate with third-party products.
IoT Security automatically creates a policy rule recommendation for each application used by
devices in the same profile and pushes all its latest rule recommendations for a profile
when you choose a profile in the PAN-OS web interface (Device or Panorama Policy RecommendationIoT). After you import a policy rule recommendation into the Security policy
rulebase, the firewall or Panorama creates a source device object that identifies the
device profile where traffic originates.
If any of the device objects already exist on the firewall or
Panorama, the firewall or Panorama updates the device object instead
of creating a new one. You can use these device objects in Security,
authentication, decryption, and Quality of Service (QoS) policy
rules.
Additionally, the firewall assigns two tags to each rule:
- One that identifies the source device, including the category (such as Amazon Device).
- One that indicates that the rule is an IoT policy rule recommendation (IoTSecurityProfileBehavior).
For optimal deployment and operation of Device-ID, we recommend
the following best practices:
- Deploy Device-ID on firewalls that are centrally located in your network. For example, if you have a large environment, deploy Device-ID on a firewall that is upstream from the IP address management (IPAM) device. If you have a small environment, deploy Device-ID on a firewall that is acting as a DHCP server. For more deployment suggestions, see IoT Security Deployment Design Guide.
- During initial deployment, allow Device-ID to collect metadata from your network for at least fourteen days. If devices are not active daily, the identification process might take longer.
- Create device-based policy rules in order from your most to
least critical devices. Use the following considerations to prioritize
them:
- Class (secure networked devices first)
- Critical devices (such as servers or MRI machines)
- Environment-specific devices (such as fire alarms and badge readers)
- Consumer-facing IoT devices (such as a smart watch or smart speaker)
- Enable Device-ID on a per-zone basis for internal zones only.