Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Statistical Analysis System (SAS) Base

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:	Statistical Analysis System (SAS) Base provides a scalable, integrated software environment that is designed for data access, transformation, and reporting. This technology includes a fourth-generation programming language, programs for data manipulation, information storage and retrieval, descriptive statistics, report writing, and a macro facility. Please note that this software has many components that are listed in the components tab of this entry. There are several related SAS softwares that are included in separate entries on TRM. Common SAS add-on programs such as SAS/CONNECT, SAS Enterprise Miner, SAS/GRAPH, SAS Simulation Studio, SAS/SHARE, and SAS/STAT are included in separate entries. Please review the TRM for these entries as needed. SAS Base is a data processing engine that can read and write to/from a variety of data sources. SAS Base does not store data within the SAS system. The user has complete control over where and how data is stored (for example, locally or on a database server). The user can also choose the type of data to retrieve, analyze, and store. This technology can integrate with the following but not limited to Db2, My Structured Query Language (MySQL), Microsoft SQL, PostgreSQL, and Oracle database. SAS Base expects that the host data system (such as the operating system and database) provides the appropriate security access controls. SAS provides other utilities for these security functions, but they are not included with SAS Base. Additionally, SAS Base supports encryption. The software comes with the SAS/SECURE software which provides the security device for encryption, including Triple Data Encryption Standard (3DES) and Advanced Encryption Standard (AES), as well as additional types of encryption such as encoding and salting. SAS Base provides access to SAS Cloud Analytics Services (CAS) and SAS Viya (a cloud-enabled, in-memory analytics engine). From a SAS session with the CAS server, users can load data to the CAS server and save CAS tables, and submit SAS Viya Analytic procedures, CAS server utility procedures, and SAS Base procedures. 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 not been assessed by the Section 508 Office. 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.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.4
Decision Date:	04/08/2024 at 15:17:26 UTC
Aliases:	Base SAS
Introduced By:	TRM Request
Vendor Name:	SAS

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
6.1
8.2
9.1
9.2 Phase 1	03/17/2008
9.2 Phase 2	02/01/2009
9.3	07/12/2011
9.4	07/01/2013
9.4M3	02/01/2016
9.4x	11/30/2016

Current Decision Matrix (04/03/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

CY2023

CY2024

CY2025

Future>

Release

6.1

Unapproved

8.2

Unapproved

9.1

Unapproved

9.2 Phase 1

Unapproved

9.2 Phase 2

Unapproved

9.3

Unapproved

9.4

Unapproved

9.4M3

Unapproved

9.4x

Approved w/Constraints
[3, 13, 18, 19, 20]

Approved w/Constraints
[3, 13, 18, 19, 21]

Approved w/Constraints
[3, 13, 21, 22, 23]

Approved w/Constraints
[21, 22, 23, 24, 25, 26, 27, 28]

Decision Constraints


[1]	Due to National Institute of Standards and Technology (NIST) vulnerabilities identified for certain versions, not all versions are allowed. Please reference the Decision Tab for additional guidance.

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

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

[4]	Per the Initial Product Review, the following constraints must be followed: Developers and systems owners need to ensure that sensitive information included in the reports and output files must be encrypted using FIPS 140-2 validated cryptographic module and the system is operated in FIPS mode to protect sensitive data at rest and in transit. Reports or output files intended for general circulation must be sanitized to remove sensitive information. In addition, the Operating Unit conducts a Privacy Impact Assessments (PIA) on the information system in accordance with OMB policy and VA Directive 6508: Privacy Impact Assessments. System owners are responsible for granting appropriate level of permission to access the application and ensure that users only have the system privileges that are needed to perform their assigned duties (least privilege). Users of VA information systems or VA sensitive information sign appropriate access agreements prior to being granted access.

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

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

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

[10]	This technology must use the latest version of JDK - Oracle Java Standard Edition (SE) Development Kit.

[11]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[12]	This technology must use the latest version of JDK - Oracle Java Standard Edition (SE) Development Kit. Users must ensure that Firefox, Microsoft .NET Framework, and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines.

[13]	Users must not utilize these Operating Systems (OS) Solaris, HP-UX, OpenVMS, and AIX as it is, at the time of writing, unapproved in the TRM. Users must ensure that when using these OS Red Hat Enterprise Linux (RHEL), Windows Client, Windows Server, and z/OS that approved versions are utilized. This technology must use the latest version of JDK - Oracle Java Standard Edition (SE) Development Kit. Users must ensure that Firefox, Microsoft .NET Framework, and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines.

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

[15]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[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]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (PSF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[18]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the VA OIT Product Engineering team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

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

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

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

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

[23]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[24]	This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. Users must ensure that Firefox, Google Chrome, Microsoft Edge, Microsoft Structured Query Language (SQL) Server, MySQL, Oracle Database, and PostgreSQL are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

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

[26]	If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See MySQL Database – Commercial Edition TRM entry for more details.

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

[28]	This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details.

Note:

At the time of writing, version 9.4M8 is the most current version, released 01/15/2023.

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.

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
Computer-Generated Imagery (CGI) Utilities for the Web Server	This module applies services to the server that includes an application broker and a load manager.
Report Fonts for Clients	This application allows for interoperability of program fonts.
SAS Business Analytics Framework/ SAS Intelligence Platform	The Statistical Analysis System (SAS) Business Analytics Framework encompasses the full range of business solutions, technologies, and services from SAS. Through this framework, organizations can address business issues and then add new functionality over time to enable continuous performance improvement. The technologies that provide the foundation for the SAS Business Analytics Framework, as well as for industry and line-of-business solutions offered by SAS, are delivered through the SAS Intelligence Platform.
SAS Business Intelligence (BI) Web Services	This application provides a Web service for an interface that enables communication between distributed applications. Web services enable cross-platform integration by enabling applications written in various programming languages to communicate using a standard Web-based protocol, typically the Simple Object Access Protocol (SOAP). This functionality makes it possible for businesses to bridge the gaps between different applications and systems.
SAS Client Connection Profile Configuration	This module is the administration for connections and profiles.
SAS Deployment Tester - Client	This is a plug-in that allows users to test the SAS deployment.
SAS Deployment Tester - Server	The Deployment Tester server is installed on each server-tier machine in a SAS deployment. Before executing a Deployment Tester test suite, users must make sure that the Deployment Tester server is running on the host machine for the process that users are testing.
SAS Deployment Tester Plug-in for SAS Management Console	SAS is shipped with a plug-in that allows users to test the SAS deployment.
SAS Drivers for Java Database Connectivity (JDBC)	The SAS Drivers for JDBC allows users to leverage the advantages of Java to access SAS data (and in some cases other relational DBMS data). Using the SAS Drivers for JDBC enables developers to choose the server configuration that best fits the design of their application.
SAS Drivers for Open Database Connectivity (ODBC)	The SAS Drivers for ODBC are implementations of the ODBC interface standard that enable users to access, manipulate, and update SAS data sources from applications that are ODBC compliant. The SAS Drivers for ODBC connect from an ODBC-compliant application to SAS/SHARE servers, SAS Scalable Performance Data (SPD) Servers, or a local instance of a SAS ODBC server.
SAS Extensible Markup Language (XML) Mapper	SAS XML Mapper automatically analyzes the structure of an XML file (or XML Schema) and generates basic metadata.
SAS Formats library for Teradata	The SAS publishing macros are used to publish formats and certain SAS functions in the Teradata Enterprise Data Warehouse.
SAS Foundation	This module provides common applications and functionality that underlies many SAS technologies.
SAS Foundation Services	SAS Foundation Services is a set of infrastructure and extension services which support the development of integrated, scalable, and secure applications based on Java.
SAS Help Viewer for the Web	The SAS Help Viewer for the Web is an application that enables users to view and navigate SAS online Help and documentation.
SAS Integration Technologies Client	This package is needed for each developer who will be creating applications that run in a Windows environment and that communicates with a SAS session.
SAS Locale Setup Manager	On Windows and UNIX machines, users can use the Locale Setup Manager task in the SAS Deployment Manager to configure the language and region for SAS Foundation and certain SAS applications.
SAS Onlinedoc for the Web	All SAS web-based technologies and solutions use Webdoc to surface help and documentation.
SAS OnlineDoc for Windows	This package helps call help and documentation within SAS.
SAS Package Reader	The SAS Package Reader application enables users to retrieve the contents of a SAS package as an archive file from an archival location or e-mail without having to run SAS. Archives are most commonly delivered to users as attachments to e-mail messages. An archive is denoted by a .spk file extension, which is an abbreviation for SAS Package.
SAS Power and Sample Size	This application is used in conjunction with SAS/STAT. The SAS Power and Sample Size application (PSS) is a desktop application that provides access to power analysis and sample size determination techniques.
SAS Providers for Object Linking and Embedding Database (OLE DB)	This application allows for pulling data through multiple sources. By selecting different access components, users are able to access SAS data through a variety of mechanisms.
SAS Structured Query Language (SQL) Library for C	The SAS SQL Library for C provides an application programming interface (API) that enables applications to send SQL queries and statements through a SAS/SHARE server to data on remote hosts.
SAS Universal Viewer	The SAS Universal Viewer enables users to view, sort, and filter SAS data sets and other simple text-based files. Users cannot edit SAS data sets with the SAS Universal Viewer.
SAS Viya developer	This module allows for the FSC to Quickly build streaming projects using real-time data and machine learning to gain accurate, timely insights.
SAS Web Application Themes	SAS Web Application Themes provide a way to define a consistent look and feel across SAS Web applications.
SAS Web Infrastructure Platform	The SAS Web Infrastructure Platform is a collection of services and applications that provide common infrastructure and integration features for the SAS web applications.
SAS/ Flexible Service Processor (FSP)	SAS/FSP provides an interactive text-based facility for data entry, editing, and retrieval.
SAS/Interactive Matrix Language (IML) Studio	This module is used with SAS/STAT, SAS/IML supports large matrices on the Windows operating system.
SAS/SECURE	This module provides information about installing, configuring, and using the SAS technology SAS/SECURE. This module also discusses SAS proprietary and industry-standard encryption algorithms and third-party strategies for protecting data and credentials in a networked environment. In SAS 9.4, SAS/SECURE is included with the Base SAS software. In prior releases, SAS/SECURE was an add-on technology that was licensed separately.
Scalable Performance Data (SPD) Server Plug-in for SAS Management Console	A portion of the SAS Management Console contains a navigation tree of available management capabilities. The SPD Manager folder to access SPD Server services. The SPDS Manager folder contains the SPD Server ACL Manager, Password Manager, Server Manager, Process Profiler, and Proxy Manager.


Information Management Technologies Business Intelligence and Data Warehouse Platforms	Data Analytics (Statistical Analysis, Prediction, and Modeling)

- The information contained on this page is accurate as of the Decision Date (04/08/2024 at 15:17:26 UTC).

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 (04/03/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 (04/03/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