4.x |
Unapproved |
Unapproved |
Approved w/Constraints [9, 11, 12, 13, 14, 15] |
Approved w/Constraints [9, 11, 12, 13, 14, 15] |
Authorized w/ Constraints [9, 11, 12, 13, 14, 15] |
Approved w/Constraints [9, 11, 12, 13, 14, 15] |
Approved w/Constraints [9, 11, 12, 13, 14, 15] |
Approved w/Constraints [9, 11, 12, 13, 14, 15] |
Authorized w/ Constraints [9, 11, 12, 13, 14, 15] |
Authorized w/ Constraints [9, 11, 12, 13, 14, 15] |
Authorized w/ Constraints [9, 11, 12, 13, 14, 15] |
Authorized w/ Constraints [9, 11, 12, 13, 14, 15] |
| | [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] | 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. | | [3] | 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. | | [4] | 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. | | [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 authorized 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. | | [8] | 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.
| | [9] | 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 ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | [10] | 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 VA Handbook 6500. | | [11] | 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. | | [12] | 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. | | [13] | Per the Initial Product Review, users must abide by the following constraints:
- Jekyll will require a 3rd party FIPS 140-2 certified solution for any data containing Personal Health Information (PHI) / Personally Identifiable Information (PII) or VA sensitive information.
- Users should check with their supervisor, 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.
- System owners must ensure they are using the most recent version of the Jekyll. The current version is v4.3.4.
| | [14] | 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). | | [15] | 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. |
|