Tableau Server

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:	Tableau Server is a business analytics platform that is part of the Tableau workflow. This technology enables browser-based users to view and edit Tableau workbooks and dashboards published to the server from Tableau Desktop. Tableau Server is hosted on VA premises and has the ability to access and pull data from multiple VA-supported data sources. This technology does not manipulate data within the data source. Views published to Tableau Server are interactive and may have a live connection to a database. As users interact with the views in a web browser, the data that is queried gets stored in a cache. Subsequent visits will pull the data from this cache if it is available, and caching can be configured to query the database as frequently or infrequently as needed. For most data connections, a server name and authentication information are required; some data connections support specifying an initial Structured Query Language (SQL) command to configure custom data environments and temporary tables to use during the session. Additionally, Tableau Server is available as a mobile application and can be optionally deployed in cloud environments including Amazon Web Services (AWS), Microsoft Azure, or Google Cloud. 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 This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: https://dvagov.sharepoint.com/sites/OITMT/SitePages/MTHome.aspx
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.7
Decision Date:	07/12/2024 at 02:56:02 UTC
Introduced By:	TRM Request
Vendor Name:	Tableau Software

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
7.0	01/17/2012
8.0	03/20/2013
8.1	11/20/2013
8.2	06/18/2014
8.3	12/01/2014
9.0	04/06/2015
9.1	09/14/2015
9.2.x	12/07/2015
9.3	03/23/2016
10.0.x	08/15/2016
10.1.x	11/06/2016
10.2.x	02/28/2017
10.x	06/12/2017
2018.x	04/24/2018
2019.x	02/14/2019
2020.x	05/06/2020
2022.x	03/30/2022
2023.x	03/14/2023
2024.x	07/01/2024

Current Decision Matrix (07/08/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

CY2017

CY2018

CY2019

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

7.0

Unapproved

8.0

Unapproved

8.1

Unapproved

8.2

Unapproved

8.3

Unapproved

9.0

Divest
[2, 3, 5, 6]

Divest
[2, 5, 7, 8]

Unapproved

9.1

Unapproved

9.2.x

Approved w/Constraints
[2, 3, 5, 6]

Divest
[2, 3, 5, 6]

Divest
[2, 5, 7, 8]

Divest
[2, 5, 8, 9]

Unapproved

9.3

Approved w/Constraints
[2, 3, 5, 6]

Divest
[2, 3, 5, 6]

Divest
[2, 5, 7, 8]

Divest
[2, 5, 8, 9]

Divest
[1, 8, 9]

Unapproved

10.0.x

Approved w/Constraints
[2, 3, 5, 6]

Approved w/Constraints
[2, 5, 7, 8]

Approved w/Constraints
[2, 5, 8, 9]

Approved w/Constraints
[1, 8, 9]

Divest
[2, 5, 8, 9]

10.1.x

Approved w/Constraints
[2, 3, 5, 6]

Approved w/Constraints
[2, 5, 7, 8]

Approved w/Constraints
[2, 5, 8, 9]

Approved w/Constraints
[1, 8, 9]

Divest
[2, 5, 8, 9]

10.2.x

Approved w/Constraints
[2, 3, 5, 6]

Approved w/Constraints
[2, 5, 7, 8]

Approved w/Constraints
[2, 5, 8, 9]

Approved w/Constraints
[1, 8, 9]

Divest
[2, 5, 8, 9]

10.x

Unapproved

Approved w/Constraints
[2, 3, 5, 6]

Approved w/Constraints
[2, 5, 7, 8]

Approved w/Constraints
[2, 5, 8, 9]

Approved w/Constraints
[1, 8, 9]

Divest
[2, 5, 8, 9]

2018.x

Unapproved

Approved w/Constraints
[1, 8, 9]

Divest
[2, 5, 8, 9]

2019.x

Unapproved

Approved w/Constraints
[2, 5, 8, 9]

2020.x

Unapproved

2022.x

Unapproved

2023.x

Unapproved

2024.x

Unapproved

Decision Constraints


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

[2]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

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

[4]	Due to potential information security risks, cloud based versions of this product are not permitted without a waiver signed by the Deputy CIO of ASD based upon a recommendation from the Architecture and Engineering Review Board (AERB). In addition, cloud based features of this software may not be used without an Enterprise Security Change Control Board (ESCCB) approval to ensure that confidential organization and/or PII/PHI data are not compromised (ref: VA Directive 6004, VA Directive 6517 and VA Directive 6513). Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review.

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

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

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

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

Note:

At the time of writing, version 2024.2 is the most current version, released 07/01/2024.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description

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
Application Server	The Application Server handles the web application, which supports browsing and searching functions in Tableau Server.
Backgrounder	Backgrounder executes server tasks, including extract refreshes, "Run Now" tasks, and tasks initiated from tabcmd.
Data Engine	The Data Engine stores data and extracts, and answers queries.
Data Server	The Data Server manages connections to Tableau Server data sources.
VizQL Server	The VizQL Server process handles loading and rendering views for Tableau Server users. If a user is trying to optimize its deployment for a high number of users and a lot of view interaction, this is the process the users should focus on.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Information Management Technologies Business Intelligence and Data Warehouse Platforms	Business Intelligence Platforms

Operating Systems Supported by the Technology

Amazon Linux - Approved w/Constraints
Oracle Linux - Approved w/Constraints
Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Citrix Virtual Apps and Desktops (CVAD) - (required for some configurations)
Microsoft Edge.
Safari
VMware vSphere - (required for some configurations)

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology utilizes built-in Authentication and Authorization (A&A) capabilities.
This technology may improve productivity for specific staff whose responsibilities include viewing and editing Tableau workbooks and dashboards.
This technology allows users to create workbooks, views, dashboards, and data sources in Tableau Desktop, and then publish this content to the server.
This technology has a comprehensive set of documentation.

Adoption Risks

This technology can integrate with and alter database technologies.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.
This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
There is no indication based on either the vendor documentation or the Cryptographic Module Validation Program (CMVP) that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
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.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.nist.gov/vuln/search for more details.

Architectural Benefits

This technology is portable as it runs on multiple TRM-approved operating systems.
This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012). (Add Virtualization and Consolidation of Servers (Server Virtualize First) to Supported Standards)

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

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 (07/08/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 (07/08/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