Question 300
After correcting this architecture issue: New manufacturing printers are not recognized by Device-ID and match a fallback any-device rule. Which ongoing control belongs in the runbook?
Explanation
Correct Answer
Review Device-ID unknown counts after firmware and model updates. This lowers the risk linked to: Unclassified devices need explicit default handling rather than borrowed trusted categories. Verification should show: A new recognized printer matches the printer rule; unknown peers remain restricted.
Incorrect Answers
Update conditional access after firmware remediation or risk reclassification. This safeguard addresses another situation: Two physically identical medical devices have different firmware and risk scores but use the same broad access template. It is less directly relevant than the control for: Unclassified devices need explicit default handling rather than borrowed trusted categories.
Maintain clinical asset ownership and purpose-specific policy groups. This safeguard addresses another situation: A shared device class includes both sterilization equipment and ordinary office printers. It is less directly relevant than the control for: Unclassified devices need explicit default handling rather than borrowed trusted categories.
Compare expected network paths with telemetry coverage after topology changes. This safeguard addresses another situation: A large plant has few firewall choke points and cannot inspect all machine-to-machine traffic from its perimeter. It is less directly relevant than the control for: Unclassified devices need explicit default handling rather than borrowed trusted categories.