| 4.x.x |
Approved w/Constraints
[5, 6, 7, 8] |
Approved w/Constraints
[5, 6, 7, 8] |
Approved w/Constraints
[5, 6, 7, 8] |
Approved w/Constraints
[5, 6, 7, 8] |
Approved w/Constraints
[6, 7, 8, 9, 10, 11] |
Approved w/Constraints
[6, 7, 8, 9, 10, 11] |
Approved w/Constraints
[6, 7, 8, 9, 10, 11] |
Approved w/Constraints
[6, 7, 8, 9, 10, 11] |
Approved w/Constraints
[6, 7, 8, 9, 10, 11] |
Approved w/Constraints
[6, 7, 8, 9, 10, 11] |
Approved w/Constraints
[6, 7, 8, 9, 10, 11] |
Approved w/Constraints
[6, 7, 8, 9, 10, 11] |
| | | | [1] | Per the Initial Product Review, users must abide by the following constraints:
Users must ensure there is no communication outside of the systems hosting WorldSpace Comply and each server has its own installation of Supervisord. The Supervisord service only manages the starting and stopping of components (services) comprising WorldSpace Comply. Data at rest must be secured by the operating system or related utilities.
Users must ensure that the supervisord configuration file cannot be read from or written to by unprivileged users and that all files installed by the supervisor package have file permission protection settings. Additionally, ensure the user`s PYTHONPATH and all Python standard library files have adequate file permission protections. The Supervisord configuration file must be secured by the operating system or related utilities.
From the noted operating systems only Red Hat Enterprise Linux and macOS have approved Secure Configuration Baselines. To use other versions of Linux, Solaris, or FreeBSD, a baseline must be developed and approved prior to deployment.
Supervisord must be monitored for vulnerabilities and care taken to ensure that known vulnerabilities mitigated expeditiously | | | [2] | 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. | | | [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] | Per the Initial Product Review, users must abide by the following constraints:
Users must ensure there is no communication outside of the systems hosting WorldSpace Comply and each server has its own installation of Supervisord. The Supervisord service only manages the starting and stopping of components (services) comprising WorldSpace Comply. Data at rest must be secured by the operating system or related utilities.
Users must ensure that the supervisord configuration file cannot be read from or written to by unprivileged users and that all files installed by the supervisor package have file permission protection settings. Additionally, ensure the user`s PYTHONPATH and all Python standard library files have adequate file permission protections. The Supervisord configuration file must be secured by the operating system or related utilities.
From the noted operating systems only Red Hat Enterprise Linux and macOS have approved Secure Configuration Baselines. To use other versions of Linux, Solaris, or FreeBSD, a baseline must be developed and approved prior to deployment.
Supervisord must be monitored for vulnerabilities and care taken to ensure that known vulnerabilities mitigated expeditiously. | | | [5] | Per the Initial Product Review, users must abide by the following constraints:
Users must ensure there is no communication outside of the systems hosting WorldSpace Comply and each server has its own installation of Supervisord. The Supervisord service only manages the starting and stopping of components (services) comprising WorldSpace Comply. Data at rest must be secured by the operating system or related utilities.
Users must ensure that the supervisord configuration file cannot be read from or written to by unprivileged users and that all files installed by the supervisor package have file permission protection settings. Additionally, ensure the user`s PYTHONPATH and all Python standard library files have adequate file permission protections. The Supervisord configuration file must be secured by the operating system or related utilities.
From the noted operating systems only Red Hat Enterprise Linux and macOS have approved Secure Configuration Baselines. To use other versions of Linux, Solaris, or FreeBSD, a baseline must be developed and approved prior to deployment. | | | [6] | 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. | | | [7] | 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. | | | [8] | 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. | | | [9] | Per the Initial Product Review, users must abide by the following constraints:
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 approved and the user should take the proper steps to decline those installations. Support for open source software can vary so, it is important to note that support services need to be maintained for this product.
Supervisor will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing Protected Health Information (PHI)/Personally Identifiable Information (PII) or VA sensitive information.
Ensure that Supervisor implements secure authentication mechanisms, such as SSL/TLS for secure communication. In addition, Supervisor should use role based access control to restrict access to specific features and functionalities.
From the noted operating systems only Red Hat Enterprise Linux and macOS have approved Secure Configuration Baselines. To use other versions of Linux, Solaris, or FreeBSD, a baseline must be developed and approved prior to deployment.
System owners must ensure they are using the most recent version of Supervisor. It is important to keep Supervisor up-to-date and follow security best practices to mitigate the risks associated with these vulnerabilities. | | | [10] | 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. | | | [11] | 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. |
|
