| 4.x.x |
Approved w/Constraints
[2, 3, 4] |
Approved w/Constraints
[2, 3, 5, 6] |
Approved w/Constraints
[2, 3, 5, 6] |
Approved w/Constraints
[2, 3, 5, 6] |
Approved w/Constraints
[2, 3, 5, 6] |
Approved w/Constraints
[2, 3, 5, 6] |
Approved w/Constraints
[2, 3, 5, 6] |
Approved w/Constraints
[2, 3, 5, 6] |
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] |
| | | | [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. |
|
