Study guide

4.4 Device Security (IoT), Device-ID & IoMT Visibility

Palo Alto Networks Certified Network Security Professional Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: PAN-OS Architecture, Interfaces & Routing

1.1 Security Zones, Virtual Routers & Interface Types 1.2 Advanced Routing Engine, Logical Routers & Dynamic Routing 1.3 High Availability Architecture, Links & Failover Mechanics

2 Chapter 2: PAN-OS Core Policy, App-ID & NAT

2.1 App-ID Classification Engine & Application Management 2.2 User-ID Architecture, Identity Mapping & Group Enforcement 2.3 Security Policy Enforcement & NAT Architecture

3 Chapter 3: SSL/TLS Decryption Architecture & Policy

3.1 SSL Forward Proxy Architecture & Enterprise PKI 3.2 SSL Inbound Inspection, Server Certificates & TLS 1.3 3.3 Decryption Policy, Decryption Profiles & Decryption Broker 3.4 SSH Proxy, No-Decrypt Policy & Decryption Exclusions

4 Chapter 4: Cloud-Delivered Security Services (CDSS) & Threat Prevention

4.1 Advanced Threat Prevention & Security Profiles 4.2 Advanced WildFire & Inline Machine Learning Models 4.3 Advanced URL Filtering & DNS Security 4.4 Device Security (IoT), Device-ID & IoMT Visibility 4.5 Enterprise SaaS Security: Discovered Apps, Data Security & SSPM

5 Chapter 5: Prisma Access Infrastructure & Network Onboarding

5.1 Prisma Access Cloud Architecture & Multi-Tenant Fabric 5.2 Remote Networks (RN) Onboarding & Branch Routing 5.3 Mobile Users (MU) Architecture, Locations & Dedicated IPs

6 Chapter 6: ZTNA 2.0, Cloud Identity & Digital Experience

6.1 ZTNA Connector Architecture & Private Application Publishing 6.2 Cloud Identity Engine (CIE) & Modern Authentication 6.3 Autonomous Digital Experience Management (ADEM) & Enterprise DLP

7 Chapter 7: Strata Cloud Manager (SCM) & AI-Driven Management

7.1 Strata Cloud Manager (SCM) Architecture & Cloud Control Plane 7.2 Unified Policy Hierarchy, Folders & Snippets 7.3 Configuration Push Preview, Validation & Migration Pathways 7.4 Strata Copilot & AIOps for NGFW

8 Chapter 8: Prisma SD-WAN & Branch Edge Architecture

8.1 Prisma SD-WAN ION Devices & Branch Topologies 8.2 Application-Defined Fabric (AppFabric) & Path Policies 8.3 Prisma SD-WAN & Prisma Access CloudBlade Integration 8.4 PAN-OS SD-WAN Subscription, Link Tags & Path Quality

9 Chapter 9: GlobalProtect, Cloud NGFW & AI Runtime Security

9.1 GlobalProtect Remote Access Architecture & Gateways 9.2 Host Information Profile (HIP) & Dynamic Split Tunneling 9.3 Cloud NGFW & Virtual Firewall Architecture (AWS, Azure & Containers) 9.4 AI Runtime Security & Generative AI Protection 9.5 Explicit Proxy, Prisma Access Browser & Remote Browser Isolation

10 Chapter 10: Packet Processing Architecture & System Troubleshooting

10.1 PAN-OS Single-Pass Parallel Processing (SP3) Architecture & Packet Flow 10.2 Operational Troubleshooting CLI Commands & Packet Diagnostics 10.3 High Availability Troubleshooting, System Maintenance & Log Forwarding

11 Chapter 11: Panorama, Subscriptions, Digital Trust & Quantum Readiness

11.1 Panorama Architecture, Device Groups & Template Stacks 11.2 CDSS Subscriptions, Premium GlobalProtect & License Lifecycle 11.3 Next-Generation Trust Security (NGTS) & Certificate Lifecycle 11.4 Quantum Security Risks & Post-Quantum Readiness

4.4 Device Security (IoT), Device-ID & IoMT Visibility

Key Takeaways Explain This Topic AI

Palo Alto Networks IoT Security is now Device Security managed by Strata Cloud Manager, entitled by a Device Security subscription, a Precision AI bundle subscription, or a Device Security X subscription.

The next-generation firewall is the sensor and the cloud application is the analysis engine: Enhanced Application Logs, firewall-hosted DHCP, the Network Discovery Policy, and optional SPAN/ERSPAN via a Tap interface feed metadata to the Strata Logging Service.

Device-ID imports IP-to-device mappings so device objects can be used as source or destination match criteria in Security, Decryption, Authentication, and QoS policy, with the device dictionary delivered as Device-ID content under Device > Dynamic Updates.

Policy rule recommendations are generated from observed inbound and outbound device behaviour but must be imported at Device > Policy Recommendation > IoT, positioned in the rulebase, and committed by an administrator — nothing is applied automatically.

Some firewall platforms support IoT device visibility and manual application of policy recommendations but not Device-ID enforcement, so visibility and enforcement are separately gated capabilities.

Last updated: September 2026

  • 4.4 Device Security (IoT), Device-ID & IoMT Visibility
  • Why This Sits in Two Blueprint Domains

IoT security appears twice on the NetSec-Pro blueprint: task 3.2.1 lists it as a Cloud-Delivered Security Service component you must be able to explain, and task 5.2 asks specifically about "the function of Security policies, Device-IDs , and monitoring and logging in the configuration and maintenance of IoT security." Device-ID is also one of the five hardening methods named in task 1.4. That triple listing makes this one of the highest-yield topics in the whole blueprint relative to how little airtime it gets in most study material.

Naming: IoT Security Is Now Device Security

Palo Alto Networks rebranded the product. Documentation now describes Device Security (Managed by Strata Cloud Manager) with the older IoT Security (standalone portal) marked as legacy. Both names refer to the same machine-learning device-identification service. Exam items may use either label, and the blueprint itself still says "IoT security."

Entitlement is by subscription, and the documented options are a Device Security subscription , a Precision AI bundle subscription , or a Device Security X subscription .

The Problem: Unmanaged Devices Cannot Run an Agent

A hospital infusion pump, a building-management HVAC controller, a badge reader, a PLC on a plant floor, and a networked ultrasound machine share three properties: they carry high business or safety impact, they run firmware you cannot patch on your schedule, and none of them can host an endpoint agent . Traditional inventory tooling is agent-based, so these devices are systematically invisible to it.

The firewall, however, already sees every packet they send. Device Security turns that traffic into an identity.

  • Architecture: The Firewall Is the Sensor, the Cloud Is the Brain IoT / IoMT / OT devices
  • |
  • v
  • +--------------------+ Enhanced Application Logs (EALs),
  • | NGFW (sensor) |-- DHCP, traffic + threat metadata --> Strata Logging Service
  • | or Prisma Access | (Cortex Data Lake)
  • +--------------------+ |
  • ^ v
  • | +------------------------------+
  • | IP-to-device mappings <-------------------| Device Security cloud app |
  • | Policy rule recommendations <--------------| three-tier machine learning |
  • | +------------------------------+
  • v
  • Device-ID usable as match criteria in
  • Security / Decryption / Authentication / QoS policy

There is no separate on-premises sensor appliance to deploy. The next-generation firewall — physical, VM-Series, CN-Series, Cloud NGFW, or Prisma Access — is the sensor, and the analysis happens in the cloud application.

The Data Sources That Make Identification Work

Source What it contributes Where it is enabled

Enhanced Application Logs (EALs) Extra Layer 7 metadata (DHCP option strings, DNS queries, HTTP headers, protocol attributes) that ordinary traffic logs omit Log Forwarding profile, "Enhanced Application Logging"

DHCP server or DHCP relay on the firewall Authoritative IP-to-MAC binding, which is what anchors an IP address to a physical device Network > DHCP

Network Discovery Policy Tells the firewall which subnets and traffic to profile and send for analysis Device Security configuration

Tap interface fed by SPAN/ERSPAN Visibility into segments the firewall does not route, such as an intra-VLAN clinical network Network > Interfaces (Tap)

Exam Trap Alert: Device Security depends on logs reaching the Strata Logging Service . A design that keeps all logs on the local firewall disk, or forwards only to a third-party SIEM, will produce an empty device inventory no matter how many subscriptions are licensed. If an exam scenario says "devices are not appearing in the inventory," check logging service connectivity and Enhanced Application Logging before anything else.

Device-ID: Turning Identity Into Enforcement

Device-ID is the PAN-OS mechanism that consumes the cloud's device identification and makes it usable in policy, exactly as User-ID does for people.

  • Mechanism Answers the question Mapping imported Usable as
  • App-ID What is this traffic? Content updates Application match criteria
  • User-ID Who is sending it? Agent, CIE, syslog, XFF, portal Source/destination user

Device-ID What device is sending it? IP-to-device mappings from Device Security Source/destination device object

Device-ID mappings and policy rule recommendations are imported from Device Security to the firewall or Panorama. Once imported, a device object can be used as source or destination match criteria in Security, Decryption, Authentication, and QoS policy rules. The device dictionary that defines the available attributes is itself delivered as a dynamic content package — you can check its version under Device > Dynamic Updates > Device-ID Content .

Device attributes available for matching typically include category, profile, vendor, model, and OS family, which is what allows a rule to say "any device whose profile is Infusion Pump " instead of enumerating a hundred IP addresses that DHCP will change next week.

Exam Trap Alert: All Palo Alto Networks next-generation firewalls support Device Security, but there are documented exceptions where a platform supports IoT device visibility and the manual application of policy recommendations but not Device-ID . Visibility and enforcement are separately gated capabilities. Do not assume that seeing a device in the inventory means you can match on it in policy.

Policy Rule Recommendations

This is the workflow the blueprint means by "Security policies … in the configuration and maintenance of IoT security."

Device Security observes each device profile long enough to learn its normal network behaviour — which destinations, applications, and protocols a given class of device legitimately uses, both outbound and inbound.

It generates a policy set : an automatically generated set of rules describing permitted behaviours for that device profile.

The administrator reviews and imports the recommendation at Device > Policy Recommendation > IoT (or the Panorama equivalent).

The administrator places the imported rule in the rulebase and commits. Creating recommendations from both outbound and inbound profile behaviours is what helps prevent vulnerability exploitation and lateral movement.

As devices gain new capabilities, Device Security updates its recommendations . You must periodically re-check recommendations for profiles you have already imported and pull the newer version.

Exam Trap Alert: Policy rule recommendations are not auto-applied . Import, placement, and commit are administrator actions. An answer stating that Device Security automatically writes and commits Security rules to production firewalls is wrong.

IoMT, OT, and the Risk Model

The datasheet audience explicitly names internet of things (IoT), internet of medical things (IoMT), and operational technology as device classes you must be able to secure.

Class Representative devices Dominant concern

IoT Cameras, badge readers, printers, smart TVs, HVAC and BMS controllers Default credentials, botnet recruitment, lateral movement into IT

IoMT Infusion pumps, patient monitors, imaging and ultrasound systems Patient safety plus protected health information; devices are often certified against a fixed OS and cannot be patched

OT PLCs, HMIs, SCADA gateways, industrial robots Availability and physical safety; scanning the device can itself cause an outage

Because IoMT and OT devices frequently cannot tolerate active scanning, Device Security's passive, traffic-derived identification is not a convenience — it is often the only safe discovery method available.

Risk Scoring and Vulnerability Context

Device Security assigns each discovered device a risk score derived from observed behaviour, known vulnerabilities associated with the identified make, model, and firmware, and the sensitivity of what it communicates with. That score is the input to segmentation decisions: a high-risk, unpatchable imaging device gets a tight allow-list rule set, while a low-risk networked printer is handled by a broader profile rule.

Segmentation Design Pattern

A defensible zero-trust design for unmanaged devices combines everything above: 1. Discover -> DHCP on firewall + EALs + Network Discovery Policy (+ ERSPAN for

  • segments the firewall does not route)
  • 2. Classify -> Device Security profiles devices and assigns risk
  • 3. Segment -> Dedicated zones/VLANs per device class; no flat clinical VLAN
  • 4. Enforce -> Security rules matching device objects (Device-ID), not IP ranges
  • 5. Inspect -> Attach Security profiles; decrypt only where the device tolerates it
  • 6. Monitor -> Device Security alerts + firewall threat logs; re-import updated
  • policy recommendations as device behaviour changes

The reason Device-ID matters more than IP-based segmentation here is churn: unmanaged devices are moved, re-imaged, and re-addressed constantly, and a rulebase keyed on IP subnets silently drifts out of alignment with reality. A rulebase keyed on device identity does not.