| 6.x |
Approved w/Constraints
[4, 10, 11, 12] |
Approved w/Constraints
[4, 10, 11, 12] |
Approved w/Constraints
[4, 10, 11, 12] |
Approved w/Constraints
[4, 10, 11, 12] |
Approved w/Constraints
[4, 10, 13, 14] |
Approved w/Constraints
[4, 10, 13, 14] |
Approved w/Constraints
[4, 10, 13, 14] |
Approved w/Constraints
[4, 10, 14, 15] |
Approved w/Constraints
[4, 10, 15, 16] |
Divest
[4, 15, 16, 17, 18, 19] |
Divest
[4, 15, 16, 17, 18, 19] |
Divest
[4, 15, 16, 17, 18, 19] |
| 7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[4, 15, 16, 17, 18, 19] |
Approved w/Constraints
[4, 15, 16, 17, 18, 19] |
Approved w/Constraints
[4, 15, 16, 17, 18, 19] |
| | | | [1] | This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. | | | [2] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
| | | [3] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [4] | Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities. | | | [5] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [6] | 1. The system user or administrator initiating Deque WorldSpace Comply must have robust authentication credentials, which includes Personal Identification Verification PIV-compliant two-factor authentication (2FA), to prevent unauthorized or casual execution of the application.
2. The user must ensure that provisions specified in VA Handbook 6500 SC-8: `Transmission Integrity` are met. Verify that if the hashing function option for creating and editing a scan is used, the hashing function is a Federal Information Processing Standards (FIPS) 140-2 compliant hashing algorithm, such as Secure Hash Algorithm (SHA)-512. Refer to VA Handbook 6500 SC-13: `Use of Cryptography` for guidance.
3. The user must ensure that provisions specified in VA Handbook 6500 IA-5: `Authenticator Management` are enforced regarding password management.
4. Provisions Requirements of VA Handbook 6500 AC-20: `Use of External Information Systems`, VA Handbook 6500 AC-17: `Remote Access` and VA Directive 6513: `Secure External Connections` must be met.
5. Use of WorldSpace Comply entails installing the Mozilla Firefox browser. If Firefox is utilized, users MUST use the official enterprise version that Solution Delivery (SD) Desktop Technologies has packaged to sustain patching and management of the application. Users are prohibited from downloading and installing any other version. Strict version control/compliance is imperative in to maintain the Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIG) settings ` as such, only use what the VA provides. The product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. It is a requirement that VA sensitive data be properly protected in accordance with VA Handbook 6500, Federal Information Security Management Act (FISMA), and Federal Information Processing Standards (FIPS) 140-2. In accordance with National Institute of Standards and Technology (NIST) SP 800-53 and SP 800-70, Information Security is an important business process that should be considered in all phases of the acquisition process to ensure data and information technology (IT) systems are adequately protected against risk of loss, misuse, and unauthorized access. In accordance with FISMA, government information or government IT systems require compliance with the agency IT Security Policy. All information technology acquisitions must meet the requirements outlined in the Federal Acquisition Regulation (FAR) Part 39.101 (d) policy ensuring the use of common security configuration checklists in the management of risk. Therefore, SD always advises further evaluation prior to any new technology or product considered for use within the VA infrastructure. If applicable, SD will test and monitor the technology within the lab environment to analyze security functionality and compliance with VA requirements. Then, if the new technology satisfies a need, a controlled pilot may be conducted to determine if organizational requirements of the VA are satisfied. Furthermore, systems that are in development (pilot, proof-of-concept, or prototype) should not be attached to VA networks without first being assessed and authorized. Should the pilot meet the security requirements of the VA, management may decide to approve the new technology for use within the VA Enterprise. | | | [7] | This technology`s older versions had a dependency on Redis open-source, only versions that do not use Redis open-source are approved for use. | | | [8] | This technology`s older versions had a dependency on Redis open-source, only versions that do not use Redis open-source are approved for use.
Users must ensure that Microsoft .NET Framework and Microsoft Internet Explorer are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- The system user or administrator initiating Deque WorldSpace Comply must have robust authentication credentials, which includes PIV-compliant two-factor authentication (2FA), to prevent unauthorized or casual execution of the application.
- Ensure that provisions specified in VA Handbook 6500 SC-8: “Transmission Integrity” are met. Verify that if the hashing function option for creating and editing a scan is used, the hashing function is a FIPS 140-2 compliant hashing algorithm, such as SHA-512. Refer to VA Handbook 6500 SC-13: `Use of Cryptography` for guidance.
- Ensure that provisions specified in VA Handbook 6500 IA-5: “Authenticator Management” are enforced regarding password management.
- Provisions Requirements of VA Handbook 6500 AC-20: “Use of External Information Systems”, VA Handbook 6500 AC-17: “Remote Access” and VA Directive 6513: “Secure External Connections” must be met.
- Use of WorldSpace Comply entails installing the Mozilla Firefox browser. If Firefox is utilized, users MUST use the official enterprise version that Solution Delivery, Desktop and Device Engineering (SDDDE) has packaged to sustain patching and management of the application. Users are prohibited from downloading and installing any other version. Strict version control/compliance is imperative in to maintain the DISA STIG settings – as such, only use what the VA provides.
| | | [9] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [10] | This technology`s older versions had a dependency on Redis open-source, only versions that do not use Redis open-source are approved for use.
This product can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors should be considered especially when an instance of this product will be considered a Moderate or High Risk system. See the MySQL Database TRM entry for more details.
Users must ensure that Microsoft .NET Framework, Firefox and Microsoft Internet Explorer are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- The system user or administrator initiating Deque axe Monitor must have robust authentication credentials, which includes PIV-compliant two-factor authentication (2FA), to prevent unauthorized or casual execution of the application.
- Ensure that provisions specified in VA Handbook 6500 SC-8: “Transmission Integrity” are met. Verify that if the hashing function option for creating and editing a scan is used, the hashing function is a FIPS 140-2 compliant hashing algorithm, such as SHA-512. Refer to VA Handbook 6500 SC-13: `Use of Cryptography` for guidance.
- The products password protection must be configurable to meet VA standards for complexity, as defined in VA Handbook 6500 (IA-5). Ensure that all VA password requirements are met with regard to length and complexity. VA Knowledge Service Control IA-5: Authenticator Management requires a case sensitive 14-character password comprised of upper-case letters, lower case letters, numbers and special characters, including at least one of each category. VA defines and enforces at least 50% of characters in the password must be changed when new passwords are created.
- Users should check with their supervisor, Information System Security Office (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.
| | | [11] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [12] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [13] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | | [14] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [15] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | | [16] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. | | | [17] | Users must ensure that Microsoft Structured Query Language (SQL) Server, My Structured Query Language (SQL) Database - Commercial Editions, Firefox, Google Chrome, and Microsoft Edge are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- The system user or administrator initiating Deque axe Monitor must have robust authentication credentials, which includes PIV-compliant two-factor authentication (2FA), to prevent unauthorized or casual execution of the application.
- Ensure that provisions specified in VA Handbook 6500 SC-8: “Transmission Integrity” are met. Verify that if the hashing function option for creating and editing a scan is used, the hashing function is a FIPS 140-2 compliant hashing algorithm, such as SHA-512. Refer to VA Handbook 6500 SC-13: `Use of Cryptography` for guidance.
- The products password protection must be configurable to meet VA standards for complexity, as defined in VA Handbook 6500 (IA-5). Ensure that all VA password requirements are met with regard to length and complexity. VA Knowledge Service Control IA-5: Authenticator Management requires a case sensitive 14-character password comprised of upper-case letters, lower case letters, numbers and special characters, including at least one of each category. VA defines and enforces at least 50% of characters in the password must be changed when new passwords are created.
- Users should check with their supervisor, Information System Security Office (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.
| | | [18] | If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See MySQL Database – Commercial Edition TRM entry for more details. | | | [19] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. |
|
