Information security — Key management — Part 7: Cross-domain password-based authenticated key exchange
Introduction: In a security domain, two entities can authenticate each other and establish a shared session key to protect their communication. This authentication is typically based on pre-established information, such as a shared password or symmetric key or possession of each other’s public key certificates. In a cross-domain communication, two entities assigned to two distinct security domains may not have suitable pre-established authentication information. However, they can still establish a shared session key by using the authentication information that each entity shares with its own domain server and relying on the domain servers themselves to authenticate each other. Practical cross-domain communication scenarios include email communication, mobile phone communication, and instant messaging. In these cases, communications need to be protected against both passive and active attackers. In these scenarios, each entity is typically registered with a domain- specific server, such as an email exchange server (for email communications) or a home location register (for mobile phone communications). Moreover, the two communicating entities from different domains typically neither share a password or a symmetric key nor possess each other’s public key certificate. An authenticated key exchange (AKE) mechanism enables two entities to establish a shared session key based on their pre-established authentication information. A password-based AKE mechanism is based on two entities pre-sharing
Scope: This document specifies mechanisms for cross-domain password-based authenticated key exchange, all of which are four-party password-based authenticated key exchange (4PAKE) protocols. Such protocols let two communicating entities establish a shared session key using just the login passwords that they share with their respective domain authentication servers. The authentication servers, assumed to be part of a standard public key infrastructure (PKI), act as ephemeral certification authorities (CAs) that certify key materials that the users can subsequently use to exchange and agree on as a session key. This document does not specify the means to be used to establish a shared password between an entity and its corresponding domain server. This document also does not define the implementation of a PKI and the means for two distinct domain servers to exchange or verify their respective public key certificates.