Cisco Cisco Identity Services Engine 1.3 백서
© 2016 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 25 of 27
APPENDIX A—Medical Device Custom Profile Checklist
If existing profiles fail to identify specific medical devices, it may be necessary to define custom profiles. This
checklist can be used to determine the primary characteristics of the endpoint that can aid in classifying and
creating custom profiles.
checklist can be used to determine the primary characteristics of the endpoint that can aid in classifying and
creating custom profiles.
The form asks a series of questions that aim to help you understand what types of information may be available
from the device and which probes should be used to collect the relevant information. This process helps focus
profiling efforts on methods that are more likely to yield useful results. It can also highlight potential gaps in profiling
or opportunities for successful classification.
from the device and which probes should be used to collect the relevant information. This process helps focus
profiling efforts on methods that are more likely to yield useful results. It can also highlight potential gaps in profiling
or opportunities for successful classification.
Once the main attributes are understood, a custom profile can be generated from the form. Each unique device
model or type will have its own record.
model or type will have its own record.
Device Characteristics
Vendor
Ex: Draeger
● Vendor contact info
● Vendor webpage
Device
Ex: Delta
Model
Device type, function, or category
Ex: Patient Monitor
Wired or wireless
Ex: Wired
Typical supported platform
Appliance or whitebox?
● NIC vendor (= OUI)
Specific vendor(s) or any?
● OS type and version
Windows? Linux? Other?
● Hardened OS?
Can authenticate: Yes/No
● 802.1X or EAP
● Protocol (PEAP, TLS, PSK)
IP addressing (DHCP)
● Static IP: Yes/No
Yes
● Static DHCP: Yes/No
No
● DHCP user class ID
configurable: Yes/No
Host/DNS Naming (DNS/DHCP)
● Hostname: static or
configurable