SolarWinds Server and Application Monitor (SAM)

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	SolarWinds Server and Application Monitor (SAM) is comprehensive application and server monitoring software for alerting, reporting, and management. The product provides built-in support for numerous applications and supports hardware from the organization`s major hardware vendor partners. This product features a single dashboard to see all application, server, and virtual infrastructure issues and metrics, calculation of thresholds from baseline data, ability to configure alerts to recognize application and server dependencies, and the ability to scale up to 15,000 servers. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g., VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e., SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has been assessed by the Section 508 Office and found non-conformant. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.2
Decision Date:	02/14/2024 at 03:26:25 UTC
Aliases:	SAM; system monitor; application monitor
Introduced By:	TRM Request
Vendor Name:	SolarWinds

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
5.5	03/06/2013
6.0	09/12/2013
6.1	04/29/2014
6.2	02/20/2015
6.3	09/25/2016
6.4	03/14/2017
6.6	03/06/2018
6.7.x	03/04/2019
6.8.x	03/12/2019
6.9.x	06/06/2019
2019.x	11/05/2019
2020.x	06/04/2020
2022.x	09/28/2022
2023.x	02/15/2023
2024.x	02/06/2024

Current Decision Matrix (02/12/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time 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. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2016

CY2017

CY2018

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

5.5

Divest
[2]

Divest
[3, 4, 5]

Unapproved

6.0

Approved w/Constraints
[2]

Approved w/Constraints
[3, 4, 5]

Divest
[3, 4, 5]

Divest
[3, 4, 6, 7, 8]

Unapproved

6.1

Approved w/Constraints
[2]

Approved w/Constraints
[3, 4, 5]

Approved w/Constraints
[3, 4, 6, 7, 8]

Divest
[3, 4, 6, 7, 8]

Divest
[3, 4, 8, 9, 10]

Divest
[3, 4, 10, 11, 12]

Divest
[5, 10, 11, 13]

Unapproved

6.2

Approved w/Constraints
[2]

Approved w/Constraints
[3, 4, 5]

Approved w/Constraints
[3, 4, 6, 7, 8]

Approved w/Constraints
[3, 4, 8, 9, 10]

Approved w/Constraints
[3, 4, 10, 11, 12]

Divest
[5, 10, 11, 13]

Divest
[5, 10, 11, 14]

6.3

Unapproved

Approved w/Constraints
[3, 4, 5]

Approved w/Constraints
[3, 4, 6, 7, 8]

Approved w/Constraints
[3, 4, 8, 9, 10]

Approved w/Constraints
[3, 4, 10, 11, 12]

Approved w/Constraints
[5, 10, 11, 13]

Approved w/Constraints
[5, 10, 11, 14]

Divest
[5, 10, 11, 14]

6.4

Unapproved

Approved w/Constraints
[3, 4, 6, 7, 8]

Approved w/Constraints
[3, 4, 8, 9, 10]

Approved w/Constraints
[3, 4, 10, 11, 12]

Approved w/Constraints
[5, 10, 11, 13]

Approved w/Constraints
[5, 10, 11, 14]

6.6

Unapproved

Approved w/Constraints
[1, 5, 10, 11, 13]

Approved w/Constraints
[1, 5, 10, 11, 14]

6.7.x

Unapproved

6.8.x

Unapproved

6.9.x

Unapproved

2019.x

Unapproved

2020.x

Unapproved

2022.x

Unapproved

2023.x

Unapproved

2024.x

Unapproved

Decision Constraints


[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]	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]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[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]	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.

[6]	Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[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]	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 ISO can advise on the ESCCB review process.

[9]	Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[11]	Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[12]	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 ISO can advise on the ESCCB review process.

[13]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. File Transfer Protocol functionality must not be leveraged.

[14]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. File Transfer Protocol functionality must not be leveraged.

Note:

At the time of writing, version 2024.1 is the most current version and released 02/06/2024.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
No components have been identified for this entry.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Systems Management Systems Management Tools	Monitoring

Operating Systems Supported by the Technology

Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Microsoft .NET Framework - (required for some configurations)
Microsoft Edge. - (required for some configurations)
Microsoft Internet Explorer (IE) - (required for some configurations)
Microsoft Internet Information Services (IIS) - (required for some configurations)
Microsoft Structured Query Language (SQL) Server - (required for some configurations)
PowerShell - (required for some configurations)
RabbitMQ - (required for some configurations)
VMware vSphere - (required for some configurations)

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology integrates with other TRM approved technologies such as SolarWinds and provides enhanced functionality.
This is a well-documented technology.
This technology supports several industry standard file formats.
This technology is Federal Information Processing (FIPS) 140-2 compliant.

Adoption Risks

This technology may utilize external data connections.
The technology requires the purchase of licenses from vendor, which could potentially lead to vendor lock-in.
This technology can integrate with and alter database technologies.
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.
Microsoft Internet Explorer, a dependency of this technology, is in End of Life status and must no longer be used.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.nist.gov/vuln/search/ for more details.
This technology can potentially use File Transfer Protocol (FTP), an unapproved protocol.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
There are other approved solutions that provide similar functionality available on the TRM. The use of several similar solutions may increase organization requirements for support and maintenance.

Architectural Benefits

This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).
This technology can use a VA-preferred database.
This technology monitors Azure and Amazon Web Services (AWS) Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS).

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.
This technology is not portable as it runs only on Windows platforms.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (02/12/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (02/12/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES