Features & Benefits
Sign PDF, XML, web-forms, transactions, emails and any other e-document types
Sign full documents or just document hash values (for high performance and confidentiality). Create enveloped, enveloping or detached signatures
Utilise the full power of PDF signatures: visible/invisible signatures, certify signatures (locked against change), PDF/A compliant signatures, Adobe CDS and AATL certificates, watermarking, add blank signature fields according to pre-defined templates. Also includes server-side PDF creator and PDF viewer in pure HTML for secure document viewing on any platform
A built-in document viewer displays PDF documents to users as a flattened image within an HTML page (documents in other format are converted to PDF on the fly by ADSS Server). The viewer is optimised for viewing even large documents efficiently by streaming the page images when required. Supports the conversion of following document formats to PDF before signing: .doc, .docx, .xls, .xlsx, .ppt, .pptx, .odt, .sxw, .rtf, .txt, .ods, .csv and .tsv. Developers have complete control over the look and feel of the user interface. Ascertia provides sample source code web pages to show how a solution can quickly be deployed. Supports both local and server side signing along with WACOM STU-500 and SignoTec ST-ME105-2-FT-100 tablets
Embed secure timestamps into digital signatures as proof of signing date and time
Embed signer’s certificate validation data into digital signatures for long-term validation using ETSI CAdES, XAdES and PAdES Part 1, 2, 3 or 4 signature formats
Access user signing keys held centrally on ADSS Server or locally by the user on smart card/tokens (via PKCS#11, Windows CAPI or Mac Keychain keystore) or on mobile devices (in software app or on secure micro-SD Cards or SIM). Also support specific eID card implementations licensed separately e.g. the Emirates eID card, Belgian eID card via IntoIT middleware)
Capture user’s biometric hand-signature from popular hardware signature tablets like Wacom, Signotec and others
Create automated corporate signatures on bulk documents (e.g. e-invoices) using one or more centrally held signing keys e.g. in a secure Hardware Security Module (HSM)
Authorise the use of corporate signatures via signed requests from pre-defined a list of approved staff (e.g. business managers) following an M of N scheme
Configure all aspects of the signature process within one or more Signing Profiles, making business applications integration very simple by just referencing these signing profiles in API request calls
Use built in ADSS Server PKI components (RA, CA, OCSP and TSA) or optionally integrate with any existing trust scheme for key generation and certification including handling the registration process for new users
Programmatically verify digitally signed PDF, XML, and other document types
Perform historic verification of long-term signatures: CAdES, XAdES & PAdES using embedded validation info and trusted timestamps
Verify and enhance basic signatures for long-term preservation
Verify old basic signatures with expired certificates using archive of historic CRLs
Provide detailed verification evidence reports using OASIS DSS-X Verification Reports specifications
Configure multiple signature verification profiles with unique trust anchors and validation parameters for easy integration with business applications
Support dynamic certificate path discovery across complex PKI hierarchies, bridge CAs, cross-certificates and mesh architectures
Support complete certificate validation using IETF RFC5280 validation algorithm including certificate validation using OCSP and/or CRLs, plus certificate quality checking using PEPPOL specifications
Validate signature polices in addition to certificate policy checking
Connect to multiple CAs, their CRLs, OCSPs, and LDAPs, ensuring that ADSS Server can bridge interoperability between disparate PKI “islands” without need for cross-certificates or bridge CAs
Easy integration within existing applications for automated signing and verification using on-demand web services or HTTP Post via high-level ADSS Client SDK (available in Java and .NET). Alternatively integrate using our Auto File Processor (uses one or more watched folders) or the Secure Email Server (automatic signing/verification of emails and/or attachments)
Accessibility from anywhere, using HTTP or HTTPS
ADSS Server is built using Java EE architectures to provide high performance and scalability. Supports virtualised environment, simply increase CPU and memory to increase performance
Multiple ADSS Servers can be used in load-balanced mode to maximise availability across one or more live sites (also use DB replication/clustering and HSM replication for complete infrastructure resilience)
FIPS and Common Criteria certified HSMs from SafeNet, Thales and Utimaco can be used to store and protect all cryptographic keys. Support for other PKCS#11 compliant HSMs can also be provided if required. HSMs can be network, PCIe or USB connected. One or more HSMs, smart cards or USB tokens can be connected to ADSS Server. Another key feature of ADSS Server is the sophisticated auto-reconnect feature that prevents a network issue requiring operator intervention to reconnect a network HSM
Support for the common cryptographic algorithms is provided including SHA1, SHA-2 (SHA-256, SHA-384, SHA-512), RSA keys up to 4096 bits and ECDSA up to 521 bits.
ADSS Server operators are authenticated using certificates over mutually authenticated TLS/SSL sessions. The operator’s private key and certificates can be on a hardware token for strong multi-factor authentication. ADSS Server performs full certificate validation, including revocation checking, before allowing operators to login to the console.
ADSS Server enables multiple operator roles to be defined. Each operator registered within the system is assigned a role. The role-based access control system enables very fine control over specific service modules that an operator can see and whether they have read, write, edit or delete capability for specific areas of functionality.
ADSS Server implements dual control in a flexible and practical way, i.e. dual control can be applied selectively to the important aspects of functionality that are considered most sensitive (such as key generation, policy change etc). When used, an operator’s actions are queued for a Security Officer role-holder to review and then approve or reject the action.
Business applications are authenticated using TLS/SSL client certificates that are pre-registered in ADSS Server. The application’s access to specific profiles and/or keys is checked as part of the ADSS Server authorisation process when service requests are received.
Cryptographic tamper-resistant logs are provided for all service transaction logs that contain details of requests and responses, all operator activity logs and all system event logs. Advanced reporting, reviewing including searching and filtering of log records is provided. All database log records are cryptographically protected to prevent record modification, deletions or additions.
All ADSS Server configurations and settings held in the database are cryptographically protected to prevent record modification, deletion or addition. The system automatically checks these records at pre-defined intervals or on demand to ensure system integrity. A detailed report is produced for any issues that are found.
Selected system operators can be alerted when certain event conditions occur using email or SMS messages. Management systems can be alerted using SNMP messages or via Syslog (log4j) messages.
ADSS Server is feature rich to increase IT efficiency. The simple installation wizard, the automatic checking of system integrity and auto-archiving and alerting ensure the system runs without daily operator involvement. The detailed transaction logs and detailed request/response viewers reduce support desk time in resolving operational issues. ADSS CA Server is also able to run an automatic upgrade process for its settings and data to run the latest version of software.
To prevent database bloating ADSS Server can be configured to automatically archive database log records. As the archive log files are created and written to disk, they are digitally signed to provide authentication and integrity. The archived files can later be imported, verified and viewed within the transaction log viewer.
ADSS Server features an optional NTP Time Monitor service that regularly checks the operating system time and compares this with one or more configured NTP time servers to detect unacceptable time drift or IT operational errors. Configured time thresholds allow ADSS Server operators to be alerted to time issues and ultimately all trust services can also be stopped automatically.