Where this offering fits
Entrust PKI is relevant to certificate-based identities and the trust relationships used by devices, applications and people. The starting question is which relying systems must trust which identities. That determines certificate policy, issuing structure and enrolment, rather than simply selecting a certificate lifetime or server count.
Architecture and rollout decisions
Document identity verification, certificate profiles, trust distribution and revocation. Review signing-key protection and recovery with the customer’s cryptographic owner. A pilot should issue a test identity, use it in a representative service and demonstrate the approved revocation check. Existing trust must be migrated deliberately; changing an issuer can affect devices or applications whose trust stores are difficult to update.
An evaluation scenario for this offering
Choose a test application requiring certificate-based identity. Issue a credential under the agreed profile, validate the relying system and exercise revocation using the supported method. Include a request that fails identity proofing. Record authority roles and the custody required for recovery. The exercise should show how trust is established and withdrawn, rather than merely display a successfully generated certificate that has not been used by the intended service.
Evidence to request for this scope
- Map relying systems to supported profiles, enrolment interfaces and trust anchors.
- Agree administrative roles for authority operation and sensitive key procedures.
- Validate recovery and trust migration using a non-production authority before introducing production certificates.