Availability of validation data
Certificates and revocation data needed for later validation must be collected while they are available. Provider data sources may no longer be accessible years later.
← Home
TRUSTED PRESERVATION · VALIDATION AND ARCHIVING
Authenticity must remain verifiable years later.
Contracts and declarations may need to be verified years after signing. Our Trusted Archiving product supports this by validating signatures and renewing the timestamps needed for preservation. Built on EU DSS (Digital Signature Services), it uses a standard CMIS connection to work with the existing document repository.
A deployed Contum product with over eight years of preservation experience
Storing a file is not enough. Certificates, revocation information, timestamps and renewal events together create a defensible preservation chain.
EU DSSSignature validation built on the European Commission’s Digital Signature Services software.
CMISA standard interface connecting to the existing enterprise document repository.
8+ yearsExperience preserving the authenticity of electronically signed documents.
Starting point
A signed file is not automatically long-term evidence.
Long-term verifiability depends on preserving the technical evidence available at signing and periodically renewing the evidence chain.
Different signature levels
B, T and LT levels contain different sets of timestamps and validation data. Each requires the appropriate additions for long-term preservation.
Multiple formats
Unified enterprise handling of PDF, XML, CMS and container-based signatures.
Ongoing preservation monitoring
Storing documents is not enough. Validation and timestamp-renewal jobs must be monitored, alongside expiring certificates and any processing errors.
Capabilities
Automated validation, augmentation and preservation.
eIDAS-based validation
Technical validation of electronic signatures and seals using the open-source EU DSS (Digital Signature Services) software and the configured validation policy.
Evidence checks
Certificate chain, CRL, OCSP, timestamp and format checks before ingestion.
Sealing and resealing
Optional sealing at ingestion and periodic renewal of the evidence chain.
LTA augmentation
Add the validation data and archive timestamps needed for future checks. The LTA (Long-Term Archival) level supports long-term verifiability.
Administration
Notifications, exception handling, certificate management and usage tracking.
DMS integration
The capability extends an existing ECM / DMS rather than operating as an isolated repository.
Integration
Turn document management into a trusted preservation environment.
CMIS (Content Management Interoperability Services) provides a standard interface to content repositories. The preservation component uses it to work with documents in the existing repository, extending that system with Contum’s preservation functions.
Source system
Signed document from a signing platform, email, portal or external partner.
→Validation layer
Format, certificate chain, revocation data, timestamp and technically supported legal-effect result.
→Augmentation
Embed missing evidence, timestamp, create LTA and schedule renewal.
→ECM / DMS
Controlled storage of documents, metadata, validation reports and related evidence.
→Operations UI
Manage alerts, errors, certificates and resealing tasks.
Journey
From ingestion to renewed evidence.
Preservation can run automatically without business intervention while exceptions and errors stay visible.
Ingest
Receive document and metadata from the source system.
Validate
Check signature, seal, timestamp, certificate and revocation status.
Acceptance and LTA augmentation
The business system applies its acceptance rules to the validation result. The preservation component produces the report and adds the data needed for long-term validation.
Store
Hand document, evidence and validation result to the DMS.
Renew
Periodic check, new timestamp or seal and continuation of the evidence chain.
Use cases
Typical applications
Contract archive
Defensible long-term preservation of customer and partner agreements.
Incoming e-document
Technical validation of externally signed documents before acceptance.
Enterprise repository extension
Add authenticity capabilities to FileNet or another DMS.
Signing-platform output
Automatically validate and archive the result of signing journeys.
Over eight years of experience
We have supported preservation of electronically signed documents in a client environment for over eight years.
Delivery
Preservation rules aligned with enterprise operations.
We connect technical validation with business acceptance rules, document classes and operational responsibilities.
Document inventory
Formats, signature methods, retention periods and evidentiary requirements.
Rules and integration design
Acceptance, rejection, augmentation, DMS metadata and exception handling.
Implementation
Components, provider connections, migration, testing and operations readiness.
Continuous support
Standard and trusted-list changes, certificates, resealing and incidents.
Supported trust elements
EU DSSCMISPAdES · XAdES · CAdESCRL · OCSPB · T · LT · LTATimestamp renewal
PRESERVATION QUESTION
Will every required piece of evidence still be available when a document is opened ten years from now?
We assess document types, the current archive and the signature-validation chain.
Trusted Archive assessment↗