Lists the connection capabilities that must be considered in security management: whether the device has hardware connectivity at all, with the installed or optional hardware and operating-system capabilities listed and whether each is a purchase option or can be disabled (CONN-1); wireless support (1.1): Wi-Fi with its authentication protocols such as WPA2 EAP-TLS (1.1.1), Bluetooth with its security modes and whether they can be enforced (1.1.2), other wireless networks such as LTE, Zigbee or proprietary (1.1.3), and other wireless links such as custom RF controls or wireless detectors (1.1.4); physical connections (1.2): RJ45 Ethernet (1.2.1), usable USB ports with their use and protection (1.2.2), removable memory devices required, used or supported (1.2.3), and other physical connections (1.2.4). Then: a list of the network ports and protocols used or usable, including transport (IPv4, IPv6), application (DICOM, IEEE 11073, HL7), service (DHCP, SMB, RDP) and custom protocols with versions (CONN-2); communication with other systems inside the customer environment (CONN-3) and outside it, such as a service host (CONN-4); making or receiving API calls (CONN-5); needing internet access to perform its intended use (CONN-6); TLS support with the versions supported or unusable (CONN-7) and whether TLS is configurable (7.1); and operator control of the device from another device, such as in telehealth (CONN-8).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.