Depending on the use-case of the application using the Engage Engine, you can choose to implement importing of certificates from within the application, or to use the ecstool command-line utility, which uses the Engage Engine to manage certificate store files. Those files are then distributed to end-user devices, servers, etc using the customer's preferred distribution mechanism, e.g., an MDM, ActiveDirectory, LDAP, dedicated servers, clouds, file copying, shared drive access. Even public means of distribution, e.g., email, social media, public drives, may be used, because the certificate store has self-contained security accessible only to Engage Engines where the above-mentioned constraints are satisfied.