Question 360
A Cisco ISE operations team investigates this site issue: A company wants printers classified separately from PCs but creates one broad profiler rule based only on a common network-card manufacturer identifier. Which architectural fact determines the appropriate fix?
Explanation
Correct Answer
A shared MAC OUI can identify network hardware vendor but not reliably distinguish an endpoint's functional device type. This behavior directly governs the stated requirement. The recommended action is: Use multiple discriminating profiler attributes and a suitably precise printer profile rather than a vendor-only classifier. The acceptance result is: The intended printers match the specialized profile and a workstation using the same NIC vendor does not.
Incorrect Answers
Keep profiler-derived device categories separate from strong user authentication and use combined identity and device conditions for privileged access. The repeat risk here is different: Regression-test profiler rules with representative phones and non-phone devices. A directly relevant preventive control is: A shared MAC OUI can identify network hardware vendor but not reliably distinguish an endpoint's functional device type.
Reassess profiling data freshness after moving or replacing physical devices. The repeat risk here is different: Regression-test profiler rules with representative phones and non-phone devices. A directly relevant preventive control is: A shared MAC OUI can identify network hardware vendor but not reliably distinguish an endpoint's functional device type.
A profiler classification and a manually administered identity-group membership are distinct attributes used in policy conditions. The repeat risk here is different: Regression-test profiler rules with representative phones and non-phone devices. A directly relevant preventive control is: A shared MAC OUI can identify network hardware vendor but not reliably distinguish an endpoint's functional device type.