| 2.x |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
| | | | [1] | Users must ensure that Microsoft Internet Information Services (IIS) and Intuitive Reliable Interoperative Scalable (IRIS) for Health are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize Caché, as it, at the time of writing, requires a POA&M.
Per the Initial Product Review, users must abide by the following constraints:
- Mg_web will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing Protected Health Information (PHI) or Personally Identifiable Information (PII).
- Users should check with their supervisor, Information Security Office (ISO) 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. Furthermore, VA Web server baselines must be strictly followed. Any deviations from the VA baseline must be documented in an authorized POA&M from the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO).
- Deployment documentation recommends using Mg_web behind a proxy server. System owners should reference the VA TRM to ensure they are using a VA approved http server.
| | | [2] | 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. | | | [3] | 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. | | | [4] | 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. | | | [5] | 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. |
|
