Question 840
Original unofficial Palo Alto Networks NetSec-Architect scenario: An IoT asset appears with low-confidence classification, but the automated workflow treats it as a fully verified trusted controller. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: An IoT asset appears with low-confidence classification, but the automated workflow treats it as a fully verified trusted controller. Governing principle: Probabilistic discovery must not automatically yield high-trust authorization. The most defensible design response is: Require a confidence threshold and manual verification for high-risk device identity decisions. Validation: A simulated ambiguous sensor remains in restricted posture until evidence resolves its type. Sustained assurance: Monitor misclassification rates and reassess low-confidence devices
Incorrect Answers
“Audit transitions from onboarding state to privileged production state.” concerns the separate design topic: design device-id policies and identity-based device segmentation. It would not fix the described weakness: an IoT asset appears with low-confidence classification, but the automated workflow treats it as a fully verified trusted controller. Probabilistic discovery must not automatically yield high-trust authorization.
This alternative is linked to the architecture category: design device visibility through ngfw, metadata collectors and sd-wan. The actual problem is that an IoT asset appears with low-confidence classification, but the automated workflow treats it as a fully verified trusted controller; the controlling distinction is: probabilistic discovery must not automatically yield high-trust authorization.
The proposed design “Reconcile Device Security findings with biomedical engineering inventories.” addresses this related architecture topic: architect iot and ot device security visibility, risk and enforcement. The actual security gap is that an IoT asset appears with low-confidence classification, but the automated workflow treats it as a fully verified trusted controller. Probabilistic discovery must not automatically yield high-trust authorization.