|
<Past |
Future> |
| 3.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 4.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 2019.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 2020.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 2022.1.x |
Authorized w/ Constraints (DIVEST) [11, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [11, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [11, 15, 17, 18, 19, 21] |
Authorized w/ Constraints (DIVEST) [11, 15, 17, 18, 19, 21] |
Unauthorized, Conditions Required (POA&M Required) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 2023.1.x |
Authorized w/ Constraints [11, 15, 17, 18, 19, 20] |
Authorized w/ Constraints [11, 15, 17, 18, 19, 20] |
Authorized w/ Constraints [11, 15, 17, 18, 19, 21] |
Authorized w/ Constraints [11, 15, 17, 18, 19, 21] |
Authorized w/ Constraints [11, 15, 17, 18, 19, 21] |
Authorized w/ Constraints [11, 15, 17, 18, 19, 21] |
Authorized w/ Constraints [11, 15, 17, 18, 19, 21] |
Authorized w/ Constraints [11, 15, 17, 18, 19, 21] |
Authorized w/ Constraints [11, 15, 17, 18, 19, 21] |
Authorized w/ Constraints [11, 15, 17, 18, 19, 21] |
Authorized w/ Constraints [11, 15, 17, 18, 19, 21] |
Authorized w/ Constraints [11, 15, 17, 18, 19, 21] |
| Note: |
At the time of writing, version 2023.1.00 is the most current version, released 09/26/2023. |
| | | | [11] | 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. | | | [15] | Users should check with their supervisor, Information System Security Officer (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 authorized and the user should take the proper steps to decline those installations. | | | [17] | 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. | | | [18] | 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. | | | [19] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [20] | Users must ensure that Microsoft Internet Information Services (IIS), Microsoft Structured Query Language (SQL) Server, Apache Hypertext Transfer Protocol (HTTP) Server, Google Chrome, Firefox, Microsoft Edge, and Oracle Database are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Maria Database (MariaDB) Server should not be used with this technology, it is unapproved for use at this time. There are other authorized databases available. See Category Tab for more details.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle. | | | [21] | Users must ensure that Microsoft Internet Information Services (IIS), Microsoft Structured Query Language (SQL) Server, Apache Hypertext Transfer Protocol (HTTP) Server, Google Chrome, Firefox, Microsoft Edge, and Oracle Database are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize Maria Database (MariaDB) Server, as it, at the time of writing, requires a POA&M.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle.
Per the Initial Product Review/Security Assessment Review, users must abide by the following constraints:
- Tungsten Transact is not Federal Information Processing Standards (FIPS) 140-2 (or its successor) certified. Tungsten Transact will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- Tungsten Transact supports Maria Database (MariaDB) database technology that is unauthorized for use on the VA TRM. Users must ensure that only VA TRM authorized databases are implemented with VA-authorized baselines.
- Tungsten Transact utilizes AI, specifically for intelligent document processing (IDP) functions like data extraction, classification, and validation from various document types. The use of AI is increasing, and guidance is still developing. Users must check the most recent VA guidance before using AI technologies and solutions. Consideration should be given to the source of any initial data for the AI tool,
if any VA data will be collected and ingested into the data set, where that data will be stored, and what rights the VA has to that data. “No web-based, publicly available generative AI service has been approved for use with VA-sensitive data. Examples of these include OpenAI’s ChatGPT and GPT4, Google’s Bard, Anthropic’ s Claude, and Microsoft’s new Bing. VA follows existing federal requirements and processes to ensure VA data is protected. When users enter information into an unapproved web-based tool, VA loses control of the data. Tungsten Transact’s AI-powered document processing capabilities introduce AI-specific security risks like model tampering, adversarial input vulnerabilities, and privacy concerns. The ATO package should require documentation, testing evidence, and contractual commitments addressing these AI risks.
- Tungsten Automation Transact is available as a cloud-based solution, but is not FedRAMP authorized. Due to potential information security risks, SaaS/PaaS solutions must complete the Business Integration and Outcomes Service (BIOS) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Digital
Transformation Center (DTC), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS or Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by DTC.
|
|