Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Scripts and other non-Portable Executable (non-PE) files usually lack version resources that identify an executable's original file name, product, and version. The absence of that data is particularly concerning for organizations using App Control for Business to control what code runs on the organization's endpoints. SignTool can add this information as authenticated metadata in the file's embedded signature. Changing the signed metadata or the file data covered by its Subject Interface Package (SIP) invalidates that signature.
This procedure signs a PowerShell script, but the same metadata options apply to other file types for which Windows has a registered SIP that supports embedded signatures.
Prerequisites
- SignTool from the Windows 11, version 24H2 SDK (build 10.0.26100.0; SDK build tools package version 10.0.26100.1) or later for the signed file metadata workflow, including when you use
/d. - A code-signing certificate and access to its private key.
- An RFC 3161 time stamp service.
- A registered SIP that supports an embedded signature for the target file type.
Choose authenticated metadata
Use stable values that remain consistent across releases. Consistent metadata lets application-control policies identify a product while allowing expected version changes.
Assign an internal name and original file name that uniquely identify the script within the product.
Assign file and product versions that follow the version scheme used by the release pipeline.
Assign a product name and description that distinguish the script from other components published by the same signer.
The following table lists the friendly SignTool options:
| Option | Purpose | Example |
|---|---|---|
/InternalName |
Stable internal identity for the file | Contoso.Deploy |
/FileVersion |
4-part version of the individual file | 2.1.0 |
/FileDescription |
Human-readable description of the file | Contoso deployment script |
/Product |
Product or application name | Contoso Tools |
/ProductVersion |
4-part version of the product | 2.1.0.0 |
/OriginalFilename |
Original file name | Deploy.ps1 |
/Language |
Language identifier or name used by the publisher | en-US |
/Author |
Author or publishing organization | Contoso Software |
/PublishTime |
Publishing time value used by the publisher | 2026-10-28T12:00:00Z |
/SourceURL |
Authoritative source location for the file | https://www.example.com/downloads/Deploy.ps1 |
/FileDescription adds a signed metadata attribute. It differs from /d, which sets the Authenticode description in the program name field of the signed OPUS information attribute (SPC_SP_OPUS_INFO_OBJID, 1.3.6.1.4.1.311.2.1.12). Prefer /d when you want to reference the description in an App Control for Business (ACfB) policy by using a CertOemID signer condition, which previously applied only to kernel drivers. For policy XML and signing examples, see Use CertOemID to match the signed description. Although /d is a longstanding option, older SignTool versions don't provide the signed file metadata support described here. Use the SDK version listed in the prerequisites.
Sign a PowerShell script
Open a command prompt where
signtool.exeis available.Sign and time stamp the script:
signtool sign /a /fd SHA256 /tr http://timestamp.digicert.com /td SHA256 /InternalName "Contoso.Deploy" /FileVersion "2.1.0" /FileDescription "Contoso deployment script" /Product "Contoso Tools" /ProductVersion "2.1" /OriginalFilename "Deploy.ps1" /Language "en-US" /Author "Contoso Software" /PublishTime "2026-10-28T12:00:00Z" /SourceURL "https://www.example.com/downloads/Deploy.ps1" Deploy.ps1Verify the embedded signature:
signtool verify /pa /v Deploy.ps1
The verification result confirms the cryptographic signature and certificate policy. It doesn't confirm that a specific application-control product uses every authenticated metadata field.
Add metadata by OID
Use /sa when automation stores metadata as OID-value pairs or when a friendly option isn't appropriate. SignTool encodes each value as an ASN.1 UTF-8 string. Repeat /sa to add multiple attributes.
Map each value to its OID:
Metadata OID Internal name 1.3.6.1.4.1.311.2.7.1File version 1.3.6.1.4.1.311.2.7.2File description 1.3.6.1.4.1.311.2.7.3Product 1.3.6.1.4.1.311.2.7.4Product version 1.3.6.1.4.1.311.2.7.5Original file name 1.3.6.1.4.1.311.2.7.6Language 1.3.6.1.4.1.311.2.7.7Author 1.3.6.1.4.1.311.2.7.8Publish time 1.3.6.1.4.1.311.2.7.9Source URL 1.3.6.1.4.1.311.2.7.10Sign the script and repeat
/safor each attribute:signtool sign /a /fd SHA256 /tr http://timestamp.digicert.com /td SHA256 /sa 1.3.6.1.4.1.311.2.7.1 "Contoso.Deploy" /sa 1.3.6.1.4.1.311.2.7.2 "2.1.0" /sa 1.3.6.1.4.1.311.2.7.4 "Contoso Tools" /sa 1.3.6.1.4.1.311.2.7.6 "Deploy.ps1" Deploy.ps1Verify the signature:
signtool verify /pa /v Deploy.ps1
Sign another non-PE file
Confirm that a SIP is registered for the file type.
Run the same signing command and specify the target file:
signtool sign /a /fd SHA256 /tr http://timestamp.digicert.com /td SHA256 /InternalName "Contoso.Startup" /FileVersion "2.1.0" /Product "Contoso Tools" /ProductVersion "2.1" /OriginalFilename "Startup.js" Startup.jsVerify the signature:
signtool verify /pa /v Startup.js
If the file type doesn't support an embedded signature, create and sign a catalog that contains the file hash. For the catalog procedure, see Use SignTool to sign a file.