3.8.5 |
Unapproved |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [2, 4, 5, 6] |
Approved w/Constraints [2, 4, 5, 6] |
Approved w/Constraints [2, 4, 5, 6] |
Approved w/Constraints [4, 5, 6, 7] |
Approved w/Constraints [4, 5, 6, 7] |
Approved w/Constraints [4, 5, 6, 7] |
Approved w/Constraints [4, 5, 6, 7] |
| | [1] | When using Jekyll to process, store, and transmit VA sensitive information, it should be installed on machines configured to use FIPS-compliant algorithms for encryption. If it is not technically possible to employ FIPS 140-2 encryption, then other third-party encryption solutions must be used.
Administrators must stay informed about the Jekyll development activities to ensure software updates and patches are tested and installed in a timely manner.
Administrators must ensure that the most current verision of Jekyll is being used, and that it is included on the list of constantly monitored products. | | [2] | 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. | | [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] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities. | | [5] | IPR Additional Constraints:
Per the Initial Product Review, users must abide by the following constraints:
- When using Jekyll to process, store, and transmit VA sensitive information, it should be installed on machines configured to use FIPS-compliant algorithms for encryption. If it is not technically possible to employ FIPS 140-2 encryption, then other third-party encryption solutions must be used.
- Administrators must stay informed about the Jekyll development activities to ensure software updates and patches are tested and installed in a timely manner.
- Administrators must ensure that the most current verision of Jekyll is being used, and that it is included on the list of constantly monitored products.
| | [6] | 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. | | [7] | 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. |
|