A working guide to cloud code signing for CI/CD: where the key has to live under today's rules, a signing step you can run unattended, and how to plan for certificates that now last about fifteen months.
For release engineers, DevOps leads and security teams who ship signed Windows software or Java code from a build pipeline.
CodeSignTool sign \ -username=$ESIGNER_USER \ -password=$ESIGNER_PASSWORD \ -credential_id=$CREDENTIAL_ID \ -totp_secret=$ESIGNER_TOTP_SECRET \ -input_file_path=build/app.exe \ -output_dir_path=signed
Since June 1, 2023, a code signing key has to be held in certified hardware, a compliant cloud key solution or a signing service. Certificates issued from March 1, 2026 are capped at 460 days. The guide reads both from the CA/Browser Forum requirements and says what each one means for a build.
Commands you can copy for CodeSignTool: listing credentials, signing one file or a folder of up to 100, the one-time password, the output folder, and what to do about the clock on the runner.
A table sized for 10 certificates shows about 3 issuances a year at the old 39-month limit and about 8 at 458 days, and lists what each reissue involves.
Who should hold signing roles, what to rotate first, and when a certificate authority has to revoke.
The guide follows the CA/Browser Forum Code Signing Baseline Requirements, edition 3.11.0, published June 16, 2026.
Read the source: Code Signing Baseline Requirements 3.11.0. SSL is listed among the Certification Authorities on the Forum's members page.
SSL was founded in 2002.
Free with your work email. The guide opens on the next page.
Take our survey and let us know your thoughts on your recent purchase.