| 2023.x |
Divest
[5, 17, 20, 22, 23, 25, 26, 27] |
Divest
[5, 17, 20, 22, 23, 25, 26, 27] |
Divest
[5, 17, 20, 22, 23, 25, 26, 27] |
Divest
[5, 17, 20, 22, 23, 25, 26, 27] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| 2024.x |
Approved w/Constraints
[5, 17, 20, 22, 23, 25, 26, 27] |
Approved w/Constraints
[5, 17, 20, 22, 23, 25, 26, 27] |
Approved w/Constraints
[5, 17, 20, 22, 23, 25, 26, 27] |
Approved w/Constraints
[5, 17, 20, 22, 23, 25, 26, 27] |
Approved w/Constraints
[5, 17, 20, 22, 23, 25, 26, 27] |
Approved w/Constraints
[5, 17, 20, 22, 23, 25, 26, 27] |
Approved w/Constraints
[5, 17, 20, 22, 23, 25, 26, 27] |
Approved w/Constraints
[5, 17, 20, 22, 23, 25, 26, 27] |
Approved w/Constraints
[5, 17, 20, 22, 23, 25, 26, 27] |
Approved w/Constraints
[5, 17, 20, 22, 23, 25, 26, 27] |
Approved w/Constraints
[5, 17, 20, 22, 23, 25, 26, 27] |
Approved w/Constraints
[5, 17, 20, 22, 23, 25, 26, 27] |
| | | | [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] | Product must remain properly patched in order to mitigate known or future security vulnerabilities. | | | [3] | Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. | | | [4] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
| | | [5] | Use of this technology is limited to VA staff charged with ensuring the security of the VA network infrastructure. VA staff performing analysis with this technology need to work closely with system owners and agree on security scanning rules, such as the assets scanned, along the schedule and frequency of those scans. | | | [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] | 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. | | | [8] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [9] | This software has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [10] | 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. | | | [11] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [12] | If free trial ware is utilized, the software must be purchased or removed at the end of the trial period.
Per the Initial Product Review, users must abide by the following constraints:
NPM should be installed on servers configured to use FIPS-compliant
algorithms for encryption. Ensure `Enable FIPS 140-2` is activated by using
the SolarWinds FIPS 140-2 Manager. Supporting documentation also
indicates that SolarWinds installations on Windows server 2008 R2 and
Windows 7 require a Microsoft hotfix to realize the FIPS-compatibility features
of SolarWinds products (see http://support.microsoft.com/kb/981119).
Configure the NPM web-based management console to use SSL.
Enforce role-based access control through Active Directory for the creation of different accounts based on organizational roles. For example, network administrators can manage and monitor devices without being allowed to perform security audit functions. | | | [13] | 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. | | | [14] | If free trial ware is utilized, the software must be purchased or removed at the end of the trial period.
Per the Initial Product Review (IPR):
NPM should be installed on servers configured to use FIPS-compliantalgorithms for encryption. Ensure `Enable FIPS 140-2` is activated by usingthe SolarWinds FIPS 140-2 Manager. Supporting documentation alsoindicates that SolarWinds installations on Windows server 2008 R2 andWindows 7 require a Microsoft hotfix to realize the FIPS-compatibility featuresof SolarWinds products (see http://support.microsoft.com/kb/981119).
Configure the NPM web-based management console to use SSL.
Enforce role-based access control through Active Directory for the creation of different accounts based on organizational roles. For example, network administrators can manage and monitor devices without being allowed to perform security audit functions. | | | [15] | Users must ensure that Microsoft .NET Framework and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
If free trial ware is utilized, the software must be purchased or removed at the end of the trial period.
Per the Initial Product Review (IPR):
- NPM should be installed on servers configured to use FIPS-compliantalgorithms for encryption. Ensure `Enable FIPS 140-2` is activated by usingthe SolarWinds FIPS 140-2 Manager. Supporting documentation alsoindicates that SolarWinds installations on Windows server 2008 R2 and Windows 7 require a Microsoft hotfix to realize the FIPS-compatibility featuresof SolarWinds products (see http://support.microsoft.com/kb/981119).
- Configure the NPM web-based management console to use SSL.
- Enforce role-based access control through Active Directory for the creation of different accounts based on organizational roles. For example, network administrators can manage and monitor devices without being allowed to perform security audit functions.
| | | [16] | 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. | | | [17] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. | | | [18] | Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
If free trial ware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Per the Initial Product Review (IPR):
- NPM will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- System owners should use the latest version of this product and monitor both the CVE Details and NIST National Vulnerability Database websites for any new security vulnerabilities.
- Configure the NPM web-based management console to use SSL.
- Enforce role-based access control through Active Directory for the creation of different accounts based on organizational roles. For example, network administrators can manage and monitor devices without being allowed to perform security audit functions.
| | | [19] | 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. | | | [20] | 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. | | | [21] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [22] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process. | | | [23] | 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. | | | [24] | Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
If free trial ware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Per the Initial Product Review (IPR):
- NPM will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information.
- System owners should use the latest version of this product and monitor both the CVE Details and NIST National Vulnerability Database websites for any new security vulnerabilities.
- Configure the NPM web-based management console to use SSL.
- Enforce role-based access control through Active Directory for the creation of different accounts based on organizational roles. For example, network administrators can manage and monitor devices without being allowed to perform security audit functions.
| | | [25] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. | | | [26] | 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. | | | [27] | Users must ensure that Firefox, Google Chrome, Microsoft Edge, and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
If free trial ware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Per the Initial Product Review (IPR):
- NPM will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information.
- System owners should use the latest version of this product and monitor both the CVE Details and NIST National Vulnerability Database websites for any new security vulnerabilities.
- Configure the NPM web-based management console to use SSL.
- Enforce role-based access control through Active Directory for the creation of different accounts based on organizational roles. For example, network administrators can manage and monitor devices without being allowed to perform security audit functions.
|
|
