In default deployment topologies, only the responder is authenticated by the host requester. However, in zero-trust architecture or complex fabric settings, the responder needs to verify that the entity querying its internal state is authorized to do so.
We should implement Mutual Authentication capabilities, enabling the requester to serve its own cryptographic identity credentials when challenged during session establishment.
What to Add
- Mutual Auth Negotiation: Map out the capabilities bits representing mutual authentication support (
MUT_AUTH_CAP).
- Challenge Processing: Implement a responder challenge parsing mechanism.
- Identity Dispatch: Connect a secure storage abstraction interface, such as pulling a certificate reference directly from secure hardware storage or fixed memory locations, to fetch and append the requester's certificate chain to the outgoing authentication handshake.
In default deployment topologies, only the responder is authenticated by the host requester. However, in zero-trust architecture or complex fabric settings, the responder needs to verify that the entity querying its internal state is authorized to do so.
We should implement Mutual Authentication capabilities, enabling the requester to serve its own cryptographic identity credentials when challenged during session establishment.
What to Add
MUT_AUTH_CAP).