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 System Security Officer (ISSO), 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 VAIT
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.
|
|
Legend: |
White |
Authorized: The technology/standard has been authorized for use.
|
Yellow |
Authorized 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 |
Authorized w/ Constraints (POA&M): 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 |
Authorized w/ Constraints (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 unauthorized may be
found on the Decision tab for the specific entry.
|
Black |
Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
|
Blue |
Authorized w/ Constraints (PLANNING/EVALUATION): 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 authorized 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 authorized 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.
|
Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M). |
<Past |
Future> |
Office 11.0/2003 |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Office 12.0/2007 |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Office 14.0/2010 |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Office 15.0/2013 |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Office 16.0/2016 |
Approved w/Constraints [20, 22, 23, 25, 26, 27] |
Approved w/Constraints [20, 22, 23, 25, 26, 27] |
Approved w/Constraints [20, 22, 23, 25, 26, 27] |
Authorized w/ Constraints [20, 22, 23, 25, 26, 27] |
Authorized w/ Constraints [20, 22, 23, 25, 26, 27] |
Authorized w/ Constraints [20, 22, 23, 25, 26, 27] |
Authorized w/ Constraints [20, 22, 23, 25, 26, 27] |
Authorized w/ Constraints [20, 22, 23, 25, 26, 27] |
Authorized w/ Constraints [20, 22, 23, 25, 26, 27] |
Authorized w/ Constraints [20, 22, 23, 25, 26, 27] |
Authorized w/ Constraints [20, 22, 23, 25, 26, 27] |
Authorized w/ Constraints [20, 22, 23, 25, 26, 27] |
Office 19.0/2018 |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Note: |
The use of Office 2013 components require a POA&M as Solution Delivery (SD) has moved to baseline the use of Office 365 ProPlus (Office 2016). Office 2019 requires a POA&M as a baseline configuration of the version has not yet been developed.
Note: the 16.0 scheme does not limit the patches and updates the vendor releases that remedy bugs and security issues. At the time of writing, the current standard versions of this technology are 16.0.17928.20512 (2408) and 16.0.18526.20264 (2502). |
| | [20] | 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. | | [22] | 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 authorized and the user should take the proper steps to decline those installations. | | [23] | 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. | | [25] | 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. | | [26] | Configuration and deployment standards for Microsoft Office products (including Microsoft Access) are defined and managed at the enterprise level by ITOPS Solution Delivery Client Services (email: OIT ITOPS SD EE Desktop and Device Engineering) and must be followed.
VA has ELAs in place for preferred RDBMS technologies (Microsoft SQL Server and Oracle DB). Customers should get their licenses through these channels, not via independent, uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
The VA will not being deploying or approving the use of Office 2013 or its components (InfoPath, Access, Excel, OneNote, Outlook, PowerPoint, Publisher, Access and Word) as Solution Delivery (SD) is deploying Office 365 ProPlus (Office 2016).
For Microsoft Access 2010 and prior versions, usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. For Microsoft Access 2010 and prior versions, Microsoft Access may not be used to support line of business operations requiring data durability/persistence. Further, when properly configured as a front-end client, no data at rest should be stored by Microsoft (MS) Access 2010 and prior. These older versions may only be used with sensitive data as part of a secured system when Access is configured as a client front-end to an appropriately secured MS SQL Server or MS SharePoint Server following VA SQL Server security configuration baselines (located at: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx) and connected via a Federal Information Processing Standard (FIPS) 140-2 certified encrypted connection.
For Microsoft Access 2016 and subsequent versions, the security configuration baseline defined and managed at the enterprise level by ITOPS Solution Delivery Client Services (email: OIT ITOPS SD EE Desktop and Device Engineering) must comply with the DISA STIG for Microsoft Access 2016 or subsequent version. When Microsoft Access 2016 and subsequent versions are used for business processes OR used with VA sensitive data including PHI and PII, the data files must be stored in storage location encrypted by FIPS 140-2 certified encryption. Further, the files must be securely backed up on a regular basis for recovery purposes, and access controls to that encrypted storage location must be restricted to only those individuals that are allowed access to the data. Users must not solely rely on Microsoft Access application passwords to protect sensitive data from unauthorized access. Appropriate authorization and role-based access control should be enforced to ensure only authorized staff have access to the data files and controls. There should be a clear delineation of duties for staff supporting and utilizing the tool. For example, access to the security controls should be restricted to certain staff that requires it to accomplished assigned tasks. All instances used for business processes OR VA sensitive data including PHI and PII, must be reviewed and authorized by the local ISO and privacy officer. | | [27] | 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. |
|