As part of complying with internal policies, external regulation or legislative requirements, certain business documents must be securely archived for a number of years into the future.
ADSS LTANS Evidence Server is a PKI-based Archive Authority product, which provides the capability to be able to demonstrate the (time of) existence, integrity, and validity of data including signed and/or encrypted data for long or undetermined periods of time. Because cryptograph algorithms may become weak over a period of time, the ADSS LTANS Evidence Server supports the ability to refresh the evidence records using new algorithms and updated PKI certificates.
ADSS LTANS Evidence Server offers these capabilities for any document format including PDF, Office and proprietary formats. So whether the document type is legal, financial, personnel, safety, engineering drawings or project plans, they all can be evidence archived. The business application simply needs to decide which documents need to be evidenced and under which archive policy. Note the actual data object maybe stored/archived in a 3rd party DMS, ECM or Archive system, in this case ADSS LTANS Evidence Server only stores the evidence record for the data object.
As part of the archive process ADSS LTAN Evidence Server can optionally verify any pre-existing signatures (PAdES, CAdES, XAdES) prior to archiving and provide detailed OASIS DSS-X verification reports including PEPPOL signature quality ratings.
As part of the archive process ADSS LTANS Evidence Server can optionally notarise and sign the archive object to attest to the processing of the data. Long-term signatures are likely to be applied in a format that suits the ERS structure.
ADSS LTANS Evidence Server can either store Archive Data Objects and ERS Data within its own database or it can return Archive Meta Data and ERS Data to the calling business application for local storage. It can also store the archive object on a local file system or publish to an online URL.
The following diagram illustrates the internal processes and how the Evidence Record Syntax (ERS) datafile is created