The Axway Validation Authority (VA) Suite provides a comprehensive, scalable, and reliable framework for real-time validation of digital certifications for the Public Key Infrastructure (PKI). The Axway VA Suite provides a variety of PKI and certificate management functionality to prevent revoked credentials from being used for secure email, smart card login, network access (including wireless), or other sensitive electronic transactions. The Axway VA Suite provides the following functionality:
\r\n· Maintains and processes a store of digital certificate revocation data by obtaining the digital Certificate Revocation List (CRL) from multiple CA or VA sources and performing end-to-end certificate validation if one or more intermediate CAs are used and the validation policy requires a complete certificate chain validation.
\r\n· Generates and signs OCSP/SCVP responses.[1] Maintains a cache loaded with OCSP responses that are pre-computed or dynamically built up by proxy client requests to a responder.
\r\n· Allows caching of CRLs and delta CRLs to support non-OCSP clients or clients that want to maintain their own revocation data caches for backup and in low-bandwidth and non real-time environments.
\r\n· Supports SSL-based communications with clients, digitally signed client requests/responses, and digitally signed XML logs and CRL archives, as well as SSL-based server administration.
\r\n· Supports software PKCS #11 or CAPI token based hardware signing and encryption products, including hardware security modules from leading vendors that comply with FIPS 140-2 Level 2 or above.[2]
\r\nFor purposes of this evaluation, the Axway VA Suite is a software application that offers CAVP certified cryptographic functions (key generation, hashing, signing, random bit generation), secure remote administration, secure storage of credentials, X.509 certificate validation and authentication, trusted update, anti-exploitation capabilities and restricted network communications.
\r\n[1] The generation and signing of OCSP/SCVP has not been tested in the evaluated configuration.
\r\n[2] The use of a Hardware Security Module (HSM) is not included in the evaluated configuration.
\r\n\r\n
The TOE is composed of three software-only applications which execute on a Microsoft Windows or RHEL operating system platform. The underlying platform is considered part of the operating environment but provides some of the security functionality required by the ASPP12.
\r\nSpecifically, the evaluated configuration includes the following:
\r\n· Axway Validation Authority Server v5.0 - a software server application running on the following two platforms:
\r\no Microsoft Windows 2012 (64 bit) on a 64 bit Intel Xeon processor
\r\no RHEL 7 (64 bit) on a 64 bit Intel Xeon processor
\r\no Microsoft Windows 2012 (64 bit) on a 64 bit Intel Xeon processor
\r\no Microsoft Windows 2012 (64 bit) on a 64 bit Intel Xeon processor
\r\no RHEL 7 (64 bit) on a 64 bit Intel Xeon processor
\r\nServer Validator provides revocation checking for the following web servers in the operational environment: Apache 2.4 and Oracle HTTP Server (OHS) 12c.
","security_evaluation_summary":"\r\n\r\nThe evaluation was carried out in accordance to the Common Criteria Evaluation and Validation Scheme (CCEVS) requirements and guidance. The criteria against which the TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1, Revision 5, April 2017. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Evaluation Methodology, Version 3.1, Revision 5, April 2017. The product, when delivered and configured as identified in the Axway Axway Validatio Authority Version 5.0 Common Criteria Guide, 19 July 2019 document, satisfies all of the security functional requirements stated in the Axway Validation Authority Suite (ASPP12) Security Target, Version 0.10, 07/16/2019. The project underwent CCEVS Validator review. The evaluation was completed in August 2019. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.
","environmental_strengths":"\r\n\r\nThe logical boundaries of the TOE are realized in the security functions that it implements. Each of these security functions is summarized below.
\r\nCryptographic support:
\r\nThe TOE uses CAVP-validated cryptographic algorithm implementations, provided by the Axway Security Kernel, a cryptographic module built upon a custom version of OpenSSL 1.0.2k, to support asymmetric key generation, encryption/decryption, signature generation and verification and establishment of trusted channels to protect data in transit. The TOE provides a web server for TLS/HTTPS to facilitate trusted remote communications and implements functionality to securely store key data related to secure communications. The TOE also relies on the underlying platform to generate entropy that is used as input data for the TOE’s deterministic random bit generator (DRBG).
\r\nUser data protection:
\r\nThe TOE does not access any hardware resources or sensitive information repositories and no sensitive data is stored in non-volatile memory. Inbound and outbound network communications are restricted to those that are user-initiated.
\r\nIdentification and authentication:
\r\nThe TOE implements X509 certificate validation to validate the revocation status of certificates using CRL. The TOE uses X509 certificates to support HTTPS/TLS authentication.
\r\nSecurity management:
\r\nThe TOE provides a Web-based Graphical User Interface (Web GUI) to access and manage the TOE security functions. When configured with default credentials or no credentials, the TOE restricts its functionality and only allows the ability to set new credentials. By default, the TOE is configured with file permissions to protect itself and its data from unauthorized access.
\r\nPrivacy
\r\nThe TOE does not transmit personally identifiable information (PII) over any network interfaces.
\r\nProtection of the TSF:
\r\nThe TOE protects itself against exploitation by implementing address space layout randomization (ASLR) and by not allocating any memory region for both write and execute permission. The TOE is compiled for both Windows and Linux with stack-based buffer overflow protection and does not allow user-modifiable files to be written to directories that contain executable files. The TOE uses standard platform APIs and includes a number of third party libraries used to perform its functions.
\r\nThe TOE includes mechanisms to check for updates and to query the current version of the application software. TOE software is digitally signed and distributed using the platform-supported package manager (Windows or Linux). The TOE does not update its own binary code in any way and when removed, all traces of the TOE application software are deleted.
\r\nTrusted path/channels:
\r\nThe TOE protects communications between itself and remote administrators using HTTPS/TLS.
","features":[]}