Identity
Confirm the certificate subject, issuer, validity period and intended use.
CERTIFICATE GUIDE
Sign with your own certificate: what to verify first.
A certificate must be assessed in context: who issued it, who controls the key, what signature format is produced and how a verifier can validate the result later.
Use the control that matches the real need. Keep the result understandable and exportable.
Signature, Identity and Mail remain separate products and connect when the workflow requires it.
WHAT YOU CAN DO
Check the complete certificate chain
Choose the capabilities that match your workflow and keep every step easy to understand.
Key custody
Document where the private key is held and who can authorise its use.
Verification
Preserve the signature format, certificate chain, timestamps and validation information needed later.
FROM ACTION TO EVIDENCE
A clear result for every step.
Compare the product used, the control applied and the result returned at each step.
| Need | Availability or product | Control | Output |
|---|---|---|---|
| Certificate | Issuer and subject | Before integration | Identity basis |
| Private key | Controlled custody | During signing | Authorisation evidence |
| Signature format | Interoperable output | At signing | Verifiable document |
| Validation | Chain and revocation data | After signing | Long-term verification context |
Need a precise scope? We map the expected result, controls and evidence before deployment.Talk to SignCloud →
READY FOR A REAL WORKFLOW
Start with the outcome you need.
We will identify the right SignCloud product, recipient journey and evidence level for your use case.