IoT Security Integrations with Third-party Products
Table of Contents
Expand all | Collapse all
-
- Firewall and PAN-OS Support of IoT Security
- IoT Security Prerequisites
- Onboard IoT Security
- Onboard IoT Security on VM-Series with Software NGFW Credits
-
- DHCP Data Collection by Traffic Type
- Firewall Deployment Options for IoT Security
- Configure a Pre-PAN-OS 10.0 Firewall with a DHCP Server
- Configure a Pre-PAN-OS 10.0 Firewall for a Local DHCP Server
- Use a Tap Interface for DHCP Visibility
- Use a Virtual Wire Interface for DHCP Visibility
- Use SNMP Network Discovery to Learn about Devices from Switches
- Use ERSPAN to Send Mirrored Traffic through GRE Tunnels
- Use DHCP Server Logs to Increase Device Visibility
- Plan for Scaling when Your Firewall Serves DHCP
- Prepare Your Firewall for IoT Security
- Configure Policies for Log Forwarding
- Control Allowed Traffic for Onboarding Devices
- Support Isolated Network Segments
- IoT Security Integration with Prisma Access
- IoT Security Licenses
- Offboard IoT Security Subscriptions
-
- Introduction to IoT Security
- IoT Security Integration with Next-generation Firewalls
- IoT Security Portal
- Vertical-themed Portals
- Device-to-Site Mapping
- Sites and Site Groups
- Networks
- Reports
- IoT Security Integration Status with Firewalls
- IoT Security Integration Status with Prisma Access
- Data Quality Diagnostics
- Authorize On-demand PCAP
- IoT Security Integrations with Third-party Products
- IoT Security and FedRAMP
IoT Security Integrations with Third-party Products
IoT Security can integrate with various third-party products to expand
functionality.
After IoT Security identifies IoT devices on your network
and discovers if they pose any security threats, it works with next-generation
firewalls—and also with Prisma Access—to protect your devices and
network. In addition, you can integrate IoT Security with third-party
products to expand the use of their specific features to include
IoT. For example, when a network access control (NAC) solution integrates
with IoT Security, it can allow or deny network access to IoT devices
whose identity it would otherwise be unaware of. IoT Security users
can also send a NAC system or a wireless LAN controller commands
to quarantine IoT devices that have vulnerabilities or for which
there are security alerts. Sometimes an integration works in one
direction with IoT Security sharing its device information with
a third-party product, and sometimes it works the other way with
IoT Security learning device information from a third-party product.
Other integrations enhance IoT Security functionality, such as its
integration with third-party vulnerability scanners.
There are two options for integrating IoT Security with third-party
systems and a third option for integrating Cortex XSOAR with IoT
Security through its API:
- IoT Security public cloud with a cohosted, limited-featured Cortex XSOAR instance (requires the purchase of an IoT Security Third-party Integrations Add-on, which comes with an automatically generated, cohosted XSOAR instance at no extra charge)An IoT Security third-party integrations add-on does not require the purchase of a full Cortex XSOAR product. After you enable the add-on, IoT Security automatically generates a cloud-hosted XSOAR instance with limited functionality (in contrast to a full Cortex XSOAR product) to assist IoT Security with the integrations it supports.
- IoT Security with an on-premises, full-featured Cortex XSOAR server
- Full-featured Cortex XSOAR instance with access to the IoT Security API
For information about the third-party integrations that IoT Security
supports, see the IoT Security Integration Guide.