Once a security system designer faces the need to provide a serious security solution encompasing client authentication (e.g. for transaction security or access control purposes), the available options are few, and any solution comes with its technology deployment guidelines.
By itself, the SAKEM procedure features featherweight technology:
In addition, if the SAKEM procedure is used with the SAKEM implied security model, the complete picture encompasses the technological lightness of secret key cryptography (SKC) mechanisms for routine operations (after the client registration).
The alternatives to the SAKEM procedure carry more extensive technological requirements. The public key infrastructure (PKI) is noteworthy because it restricts the client authentication to PKC techniques, it imposes significant interoperability requirements with certification authorities (CA) and on-line directory services. Any technology intensiveness, interoperability requirements, and discretionary recourse to PKC techniques is deemed to increase project costs. The SAKEM procedure avoids all of them.