The SAKEM implied security model is an overall organization of a security application suggested by the SAKEM procedure which, by itself, addresses only the initialization of a security relationship.
The SAKEM procedure is designed to use as little of the PKC (Public Key Cryptography) technology as possible, with the greatest relative value. Past the subscriber registration phase, the SAKEM procedure naturally leads into the traditional SKC (Secret Key cryptography) security techniques for routine automated transactions, and such traditional techniques are much less patent encumbered.
The SAKEM implied security model is this very idea to use PKC for the initial key establishment and then revert to traditional SKC for routine operations. The reader should have an idea of the correspondence between the PKC and the SKC for each type of routine security function. For instance, a PKC digital signature corresponds to a SKC MAC (Message Authentication Code). The benefits of using traditional SKC for routine operations are many, including easier computing requirements, and lesser emphasis on patented technologies.
This "implied security model" is not restricted to SAKEM as a method for initial secret key establishment (but SAKEM offers unique security features). Conversely, the SAKEM procedure can be used with other security models. Here is an example. Some VPN (Virtual Private Network) are initialized starting from secret data shared between a new node and the VPN management center. This shared secret data can be initialized with SAKEM, even though the VPN uses PKC security techniques for routine operations once the initialization procedure is complete (the routine operation in the case of a VPN is session key establishment).