3.30.x |
Unapproved |
Approved w/Constraints [4, 6, 7, 8] |
Approved w/Constraints [4, 6, 7, 8] |
Approved w/Constraints [4, 6, 7, 8] |
Approved w/Constraints [4, 6, 7, 8] |
Approved w/Constraints [4, 6, 7, 8] |
Approved w/Constraints [4, 6, 7, 8] |
Approved w/Constraints [4, 6, 7, 8] |
Approved w/Constraints [4, 6, 7, 8] |
Approved w/Constraints [4, 6, 7, 8] |
Approved w/Constraints [4, 6, 7, 8] |
Approved w/Constraints [4, 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] | Per the Initial Product Review, users must abide by the following constraints:
- Azurite is meant to be used in a development environment for testing Azure blob and queue storage applications. It should not be deployed in a production environment or used for any data containing PHI/PII, sensitive information.
- Users must ensure that they are using an approved version of Node.js when installing and using this product.
- This product should be used with a VA approved container platform that has a developed and approved baseline configuration with specific hardening guidance regarding its secure implementation. Currently Kubernetes, Docker, and OpenShift are container products the VA is evaluating. Please reference the TRM for the approved solution and the Baseline Configuration Management website for more information.
- Users should disable the default devstoreaccount1 manually and/or set custom storage accounts which will automatically disable it.
| | [3] | 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. | | [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 Initial Product Review, users must abide by the following constraints:
- Azurite is meant to be used in a development environment for testing Azure blob and queue storage applications. It should not be deployed in a production environment or used for any data containing PHI/PII, sensitive information.
- Users must ensure that they are using an approved version of Node.js when installing and using this product.
- This product should be used with a VA approved container platform that has a developed and approved baseline configuration with specific hardening guidance regarding its secure implementation. Currently Kubernetes, Docker, and OpenShift are container products the VA is evaluating. Please reference the TRM for the approved solution and the Baseline Configuration Management website for more information.
- Users should disable the default devstoreaccount1 manually and/or set custom storage accounts which will automatically disable it.
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. | | [6] | 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 approved and the user should take the proper steps to decline those installations. | | [7] | Users must not utilize Microsoft Azure Storage Software Development Kit (SDK) for Node.js, as it is at the time of writing, in a divested state within the TRM.
Per the Initial Product Review, users must abide by the following constraints:
- Azurite will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information.
- Users must ensure that they are using an approved version of Node.js when installing and using this product.
- This product should be used with a VA approved container platform that has a developed and approved baseline configuration with specific hardening guidance regarding its secure implementation. Currently Kubernetes, Docker, and OpenShift are container products the VA is evaluating. Please reference the TRM for the approved solution and the Baseline Configuration Management website for more information.
- Users should disable the default devstoreaccount1 manually and/or set custom storage accounts which will automatically disable it.
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. | | [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. |
|