Sign your scripts with a certificate your devices already trust.
An execution policy that only runs signed PowerShell, Office that only runs signed macros: both need a code signing certificate your devices trust. SCEPman issues it from the root your MDM has already deployed, and a role decides who may request one.
- Extended key usage Code Signing
- PKCS#12 or PEM
- Role-based requests
- Enterprise Edition
What you can sign
- PowerShell scripts and modules, for an AllSigned execution policy.
- Office macros, for "disable all macros except digitally signed macros".
- In-house executables and installers.
Two ways to request a certificate
By form
Enter a subject name in Certificate Master and submit. A few seconds later the browser downloads the certificate with its key as a password-protected PKCS#12 file. The password is shown once.
By CSR
Generate the key yourself, in a hardware security module, a key vault or on the build server, and upload only the certificate signing request. The key never leaves the place you created it. The certificate comes back as PEM, DER, CRT or a PKCS#7 chain.
Who may request a code signing certificate
Request.CodeSigning allows it, and its variants .Form and .Csr limit it to one method. Assign it to the two people who maintain your automation, not to the helpdesk. Every request and every revocation is recorded with the requester's Entra ID name.Trusted on every device that has your root
Questions about code signing
01Which edition do we need?
Enterprise Edition. Code signing certificates come from Certificate Master.
02How long is a code signing certificate valid?
As long as you choose when you request it, up to the maximum you configure for code signing certificates.
03What happens to signed scripts when the certificate expires?
That depends on whether the signature carries a timestamp from a timestamp service. Without one, signatures are treated as invalid once the certificate expires; plan renewals and re-signing accordingly.
04How is code signing licensed?
Per user who runs or validates the signed code. In practice that is usually everyone with the SCEPman root on a device.
Sign your next script before it ships.
Request a code signing certificate in Certificate Master and switch your execution policy to signed scripts.