PSD v5.0: Permit UADs integrated into PSDs and remote controllers

Issue
PSD v4.0 already supports PSD-mediated UAD/peripheral access and requires that such a peripheral path not become a cross-domain communication path.

PSD v5.0 should clarify that a User Authentication Device (UAD), such as a CAC/smart-card reader, may be physically integrated into a PSD, secure KVM, or wired remote controller. A physically integrated implementation should not be excluded merely because it does not expose the UAD as a separate external device.
Modern secure KVMs frequently integrate the UAD into the main PSD enclosure or into a wired user-side controller. The relevant security property is not the physical location of the reader; it is that every protected-computer interface is independently mediated by the PSD and cannot transfer information to another protected computer.

Proposed clarification
Permit a UAD to be integrated into the PSD or a wired remote controller, provided that:

• The PSD continues to control the association between the selected domain and each corresponding host-facing UAD interface.
• The UAD path associated with one protected computer cannot communicate with, signal, or transfer authentication-related information to another protected computer.
• Insertion, removal, reset, selection change, reconnection, and error handling cannot cause an incorrect host association or cross-domain transfer.
• The integrated implementation does not provide an unmanaged bypass around PSD mediation.

A separately exposed UAD test port should not be required. The evaluator should use normal host-facing interfaces and other reasonable available access to verify the required security behavior. Requiring an additional external test connector would impose a product-design constraint without increasing assurance where normal interfaces enable the relevant tests.

Requested change

Add a limited clarification to the UAD requirements/use case and its Evaluation Activity permitting an integrated UAD. The clarification should retain the PSD v4.0 mediation, isolation, and selected-domain association requirements.

The Evaluation Activity should confirm that the evaluator can verify the independently mediated host-facing UAD behavior through the normal interfaces, without requiring a separately exposed UAD test port.

Locate the UAD requirements/use case and the related Evaluation Activity in the PSD v5.0 materials. Read the existing PSD v4.0 mediation, isolation, and selected-domain association requirements first; done means the text permits an integrated UAD while preserving those controls and lets evaluators verify host-facing behavior through normal interfaces without requiring a separate test port.