| 1.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (PLANNING/EVALUATION)
[1, 2, 3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints (PLANNING/EVALUATION)
[1, 2, 3, 4, 5, 6, 7, 8] |
Unauthorized, Conditions Required[c]
[1, 2, 3, 4, 5, 6, 7, 8] |
Unauthorized, Conditions Required[c]
[1, 2, 3, 4, 5, 6, 7, 8] |
Unauthorized, Conditions Required[c]
[1, 2, 3, 4, 5, 6, 7, 8] |
Unauthorized, Conditions Required[c]
[1, 2, 3, 4, 5, 6, 7, 8] |
Unauthorized, Conditions Required[c]
[1, 2, 3, 4, 5, 6, 7, 8] |
Unauthorized, Conditions Required[c]
[1, 2, 3, 4, 5, 6, 7, 8] |
Unauthorized, Conditions Required[c]
[1, 2, 3, 4, 5, 6, 7, 8] |
Unauthorized, Conditions Required[c]
[1, 2, 3, 4, 5, 6, 7, 8] |
| | | | [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] | Users must not utilize the Secure Sockets Layer (SSL) protocol, as it requires a POA&M.
This technology can be deployed with Kubernetes. At the time of writing, the baseline for Kubernetes dictates that it can only be used in on-premises in Amazon Web Services (AWS) VA Enterprise Cloud (VAEC) implementations.
Users must ensure that Kubernetes and PostrgresSQL are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review (IPR) users must abide by the following constraints:
- Skylar Analytics will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information.
- 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.
- 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. The system user or administrator initiating the Skylar
Analytics process should have robust authentication credentials that prevent unauthorized or casual access.
- OMB Memorandum M-22-18,” Enhancing the Security of the Software Supply Chain through Secure Software Development Practices,” and OMB
Memorandum M-23-16, “Update to Memorandum M-22-18,” limit agencies’ ability to use software that is not developed using secure practices. The
attestation form will allow software producers to confirm that they follow those practices.
A Supply Chain Risk Management (SR) Policy and VA Handbook 6500.6,
Contract Security, Appendix C states that the contractor (including producers
and resellers) shall comply with Office of Management and Budget (OMB) M-22-18 and M-23-16 when using third-party software on VA information
systems or otherwise affecting the VA information. This includes new software
purchases and software renewals for software developed or modified by
major version change after the issuance date of M-22-18 (September 14,
2022).
| | | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 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] | 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. | | | [6] | 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. Contact your local CIO office if more information is needed in regards to the use of this technology. | | | [7] | This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL 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 PostgreSQL Database TRM entry for more details. | | | [8] | 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. |
|
