| Office 16.0/2016 |
Approved w/Constraints
[10, 12, 13, 14] |
Approved w/Constraints
[10, 12, 13, 14] |
Approved w/Constraints
[10, 12, 13, 14] |
Approved w/Constraints
[10, 12, 13, 14] |
Approved w/Constraints
[10, 12, 17, 18] |
Approved w/Constraints
[10, 12, 17, 18] |
Approved w/Constraints
[10, 12, 17, 18] |
Approved w/Constraints
[10, 12, 17, 18] |
Approved w/Constraints
[10, 12, 17, 18] |
Approved w/Constraints
[10, 12, 17, 18] |
Approved w/Constraints
[10, 12, 17, 18] |
Approved w/Constraints
[10, 12, 17, 18] |
| | | | [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] | Per VA Handbook 6500 (Appendix F) all systems with a Moderate or High risk assessment are required to use a FIPS 140-2 compliant DBMS solution to protect information at rest or have mitigating controls documented in an approved System Security Plan (SSP) for the system. It is the responsibility of the system owner to ensure that an appropriate DBMS technology is selected or that mitigating controls are in place and documented in the SSP.
Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Microsoft Office images which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to.
Office 15.0/2013 is under evaluation and is currently not approved for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test of this version as approved by ESE Client Services or an AERB waiver while under evaluation. | | | [3] | Configuration and deployment standards for databases and their host server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
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
Usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. Desktop DBMS technologies may not be used to support line of business operations requiring data durability/ persistence. Storage of PHI/PII/VA sensitive data in databases built on desktop DBMS platforms is Prohibited. Desktop DBMS systems are to be phased out and decommissioned by 2017 in accordance with the VA Enterprise Technology Strategic Plan. | | | [4] | 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. | | | [5] | 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). | | | [6] | 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. | | | [7] | Configuration and deployment standards for databases and their host server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
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
Usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. Desktop DBMS technologies may not be used to support line of business operations requiring data durability/ persistence. Storage of PHI/PII/VA sensitive data in databases built on desktop DBMS platforms is Prohibited.
Office 15.0/2013 is currently not approved for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test of this version as approved by ESE Client Services or an AERB waiver while under evaluation. | | | [8] | Configuration and deployment standards for databases and their host server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
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
Usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. Desktop DBMS technologies may not be used to support line of business operations requiring data durability/persistence.
Office 15.0/2013 is currently not approved for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test of this version as approved by ESE Client Services or an AERB waiver while under evaluation. | | | [9] | Configuration and deployment standards for databases and their host server images must be followed and adhered to. Information on these standards may be found at https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
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
Usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. Desktop DBMS technologies may not be used to support line of business operations requiring data durability/persistence.
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, Excel, OneNote, Outlook, PowerPoint, Publisher, Access and Word) as Enterprise System Engineering (ESE) is testing and working on a deployment plan for Office 365 ProPlus (Office 2016). As such, Windows Office 365 ProPlus (16.x) is under evaluation and is currently not approved for production.
When properly configured as a front-end client, no data at rest should be stored by Microsoft (MS) Access. MS Access 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 security configuration baselines and connected via a Federal Information Processing Standard (FIPS) 140-2 certified encrypted connection. | | | [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] | Configuration and deployment standards for databases and their host server images must be followed and adhered to. Information on these standards may be found at https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
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 security configuration baselines 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 must comply to 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 who require it to accomplished assigned tasks. All instances used for business processes OR VA sensitive data including PHI and PII, must be reviewed and approved by the local ISO and privacy officer. | | | [12] | 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 approved by the local ISO and privacy officer. | | | [13] | 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). | | | [14] | 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. | | | [15] | 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 must 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 most Office 2013 components (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 may 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 must be enforced to ensure only authorized staff have access to the data files and controls. There must be a clear delineation of duties for staff supporting and utilizing the technology. For example, access to the security controls must 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 approved by the local ISO and privacy officer. | | | [16] | 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 must 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 most Office 2013 components (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 may 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 must be enforced to ensure only authorized staff have access to the data files and controls. There must be a clear delineation of duties for staff supporting and utilizing the technology. For example, access to the security controls must 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 approved by the local ISO and privacy officer. | | | [17] | 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). | | | [18] | 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. |
|
