The local use case means that key owners accessing the Trident HSM locally through the provided API calls use their own electronic signatures or seals. In this case, instead of the Signature Activation Module (SAM) only the cryptographic module (CM) capability of the HSM is in use, performing the cryptographic operations and the related key management locally. Clients can use these capabilities to create qualified and unqualified electronic signatures and electronic seals for local keyholders who can be natural or legal persons.

This can be useful for several customers including service providers who use their own seals or signatures on e-invoices or registered emails, as well as enterprises that want to place qualified electronic signatures and seals on their documents in bulk, with automated systems. In these use cases, the local key holder is responsible for the security of the environment in which Trident v2.1.3 is running in use and managed. In this case, Trident v2.1.3 only generates, stores and uses keys that belong to the local end user, besides the infrastructure keys that are essential for internal protection mechanisms.