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 Firewalls 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
- IoT Security Integrations with Third-party Products
- IoT Security and FedRAMP
MDS2
Upload MDS2 files that IoT Security can use to detect
vulnerabilities and security alerts in medical IoT
Note: The page only appears when
the portal theme is
Medical IoT Security.
Administration
MDS2
Medical device vendors often release Manufacturer Disclosure
Statement for Medical Device Safety (MDS2) forms. These list the
security-related features of their products. Vendors issue MDS2
documents for each version of a medical device and include information
such as whether a device processes PHI (personal health information); if
it stores PHI and, if so, if it's encrypted; and if antivirus software
is installed on the device.
On ,
you can upload MDS2 files to IoT Security so it will consider the information
they contain together with environmental factors when assessing
device risk. On this page, you can view uploaded files, download
them, and remove them. You can also download a complete list of
all uploaded MDS files or a list of one or more selected files.
Administration
MDS2

To upload a file, click the
), navigate to an MDS2 file in
PDF format, and then select and upload it.
Upload
icon
(

IoT Security matches the uploaded MDS2 file with devices that
share the same model, vendor, and profile as those specified in
the file. Although you can upload an MDS2 file on the Device Details
page, IoT Security only applies the MDS2 file to that individual
device. On the other hand, if you upload an MDS file on the MDS2
page, IoT Security searches its inventory for all devices with the
same model, vendor, and profile attributes and applies the MDS2
file to all matched devices. Furthermore, if new devices are added
to the inventory later, IoT Security will apply the MDS2 file to
those devices as well.
Clicking a number in the Matched Device column opens the Devices
page with a filter applied to show just those devices that match
the MDS2 file.

The number in the Matched Device column on the MDS2 page
is the total for all sites. If you have administrative access to
device data for a subset of sites, the number of matched devices
on the Devices page might be smaller than the number on the MDS2
page.
To view some details about an MDS2 file, click the entry in the
File Name column. An information panel slides open on the right
side of the main window listing the three attributes that IoT Security
uses to map the MDS2 file to devices. Below this, it lists several
key points about the device, the document, and security.

If you notice any inaccuracies among the device mapping rule
values, it’s possible that text alignment issues in the PDF caused
the characters to be parsed incorrectly. As a result, IoT Security
wouldn’t be able to match the MDS2 file with any devices. In such
cases, click
Edit
to the right of Device
Mapping Rule, modify the text as necessary, and then click Update
.
In addition to the values in the Device Mapping Rule, you can
edit other attributes in the MDS2 file if they were parsed incorrectly
as well. Whenever you click
Update
—either
for changes to Device Mapping Rule or Data from MDS2 File—IoT Security
immediately removes any previous matches for the MDS2 document and
runs the matching process again.
To view an entire MDS2 file in PDF format, click
Show
PDF
in the information panel.
To download the PDF, click the
) at the top of the PDF viewer.
Download
icon
(

To close the information panel (and PDF viewer if it’s also open),
either click the X in the upper right corner or click the file name
again.
To download a list of all uploaded MDS2 files in a .csv file,
click the
) above the MDS2
table. To download a list of one or more MDS2 files in a .csv file,
select check boxes of the ones you want to download and then click
Download
icon (

Download
.
To delete one or more previously uploaded MDS2 files, select
the check boxes of the files to delete and then click
Remove
.