| 2016 |
Approved w/Constraints
[4, 6, 7, 10] |
Approved w/Constraints
[4, 6, 7, 10] |
Approved w/Constraints
[4, 6, 7, 10] |
Approved w/Constraints
[4, 6, 7, 10] |
Approved w/Constraints
[4, 10, 11, 12] |
Approved w/Constraints
[4, 10, 11, 12] |
Approved w/Constraints
[4, 10, 11, 12] |
Approved w/Constraints
[4, 10, 11, 12] |
Approved w/Constraints
[4, 10, 11, 12] |
Approved w/Constraints
[4, 10, 11, 12] |
Approved w/Constraints
[4, 10, 11, 12] |
Approved w/Constraints
[4, 10, 11, 12] |
| | | | [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] | 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.
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.
Access 2016 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 Architecture and Engineering Review Board (AERB) waiver while under evaluation. | | | [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] | 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. | | | [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] | 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. | | | [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] | Users must adhere to configuration and deployment standards for databases and their host server images. Information on these standards may be found at https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
Usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. This technology may not be used to support line of business operations requiring data durability/persistence.
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 may be stored by Microsoft (MS) Access. MS Access must 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. | | | [9] | Users must adhere to configuration and deployment standards for databases and their host server images. Information on these standards may be found at https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
Usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. This technology may not be used to support line of business operations requiring data durability/persistence.
When properly configured as a front-end client, no data at rest may be stored by Microsoft (MS) Access. MS Access must 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 Structured Query Language (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] | Usage is limited to databases supporting individual user`s personal productivity and/or training as database administrators. This technology may not be used to support line of business operations requiring data durability/persistence.
When properly configured as a front-end client, no data at rest may be stored by Microsoft (MS) Access. MS Access must 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 Structured Query Language (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. | | | [11] | 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. | | | [12] | 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). |
|
| Note: |
At the time of writing, version 2016 is the most current version, released 12/04/2015. At the time of writing, the VA will not be deploying or approving the use of Office 2013 or its components (InfoPath, Excel, OneNote, Outlook, PowerPoint, Publisher and Word) as the Solution Delivery (SD) has approved the use of Office 365 ProPlus (Office 2016). |
