- Overview
- Reference Guide
- Setup & Architecture
- Release Notes
- API Reference
-
Integration Guides
-
Signing Capabilities
- Supported Formats and Platforms
- Timestamping
- Windows Signing - SignTool
- Apple Signing
- AppX & MSIX Signing
- Visual Studio ClickOnce
- Jar Signing
- Sign HLK/HCK using CodeSign Secure
- NuGet Signing
- Mage Signing
- Sign OVA/OVF using Encryption Consulting’s Utility Tool
- Utility Tool for code signing
- Container Signing
- PKCS11 Wrapper
- Reproducible Build
- CI/CD Integration
-
Signing Capabilities
Security and Access Control
How CodeSign Secure controls who can sign, what needs approval, and how to run it securely.
Controls at a glance
| Control | What it protects | Where to configure it |
|---|---|---|
| HSM key custody | Private keys never leave FIPS 140-2 Level 3 hardware | Keys and Certificates |
| Roles and permissions | What each user can see and do in the portal | Roles and Permissions |
| Teams and certificate mapping | Who can sign with which certificate | App Management |
| Environment policies and MFA | Which signing requests need human approval | Designing signing policies |
| Client authentication | Which machines and users can call the signing API | Client Authentication |
| Audit Trail and logs | Evidence of who signed what, and when | Audit Trail |
| Server hardening | The server, database, network and credentials | Security hardening checklist |