API / Venafi Interview questions
Explain the lifecycle of a certificate in Venafi from request to retirement?
Every certificate Venafi manages moves through the same broad stages, whether it's a TLS certificate on a web server or a code-signing certificate for a build pipeline.
A request enters as a CSR generated by the requester or by TPP itself, gets checked against the owning policy folder's rules (key size, SAN entries, validity period), and if the folder requires it, waits for a human approval step before it's forwarded to the CA. Once the CA signs it, TPP either hands the certificate back for manual installation or pushes it directly onto the target endpoint through an orchestration connector.
From there the certificate sits in monitoring, tracked against its expiration date, until either a renewal cycle brings it back through issuance and installation again, or it's revoked early (a key compromise, a decommissioned server) or simply allowed to retire at natural expiration once the system it protected is gone.
More Related questions...