Question 820
Original unofficial Palo Alto Networks NetSec-Architect scenario: A hospital uses static IPs to identify infusion pumps, but DHCP maintenance changes an approved device’s address. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A hospital uses static IPs to identify infusion pumps, but DHCP maintenance changes an approved device’s address. Governing principle: Network addresses are mutable and do not uniquely prove embedded device role. The most defensible design response is: Design stable supported Device-ID conditions with narrowly restricted medical application policy instead of relying solely on address. Validation: The identified pump retains only its approved telemetry path after an authorized address change. Sustained assurance: Test identity binding after DHCP or network readdressing changes
Incorrect Answers
“Reconcile Device-ID records with approved asset ownership.” concerns the separate design topic: design device-id policies and identity-based device segmentation. It would not fix the described weakness: a hospital uses static IPs to identify infusion pumps, but DHCP maintenance changes an approved device’s address. Network addresses are mutable and do not uniquely prove embedded device role.
This alternative is linked to the architecture category: validate device security architectures and risk-response capabilities. The actual problem is that a hospital uses static IPs to identify infusion pumps, but DHCP maintenance changes an approved device’s address; the controlling distinction is: network addresses are mutable and do not uniquely prove embedded device role.
The proposed design “Require risk and change-owner signoff on high-impact medical rules.” addresses this related architecture topic: validate device security architectures and risk-response capabilities. The actual security gap is that a hospital uses static IPs to identify infusion pumps, but DHCP maintenance changes an approved device’s address. Network addresses are mutable and do not uniquely prove embedded device role.