|
<Past |
Future> |
| 7.2.x |
Approved w/Constraints
[1, 3, 5, 6] |
Approved w/Constraints
[1, 3, 5, 6] |
Divest
[3, 5, 6, 7, 8, 9] |
Divest
[3, 5, 6, 7, 8, 9] |
Divest
[3, 7, 8, 9, 10, 11] |
Divest
[3, 7, 8, 9, 10, 11] |
Divest
[3, 7, 8, 9, 10, 11] |
Divest
[3, 7, 8, 9, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| 8.x |
Unapproved |
Unapproved |
Approved w/Constraints
[3, 5, 6, 7, 8, 9] |
Approved w/Constraints
[3, 5, 6, 7, 8, 9] |
Approved w/Constraints
[3, 7, 8, 9, 10, 11] |
Approved w/Constraints
[3, 7, 8, 9, 10, 11] |
Approved w/Constraints
[3, 7, 8, 9, 10, 11] |
Approved w/Constraints
[3, 7, 8, 9, 11, 12] |
Approved w/Constraints
[3, 7, 8, 9, 11, 12] |
Approved w/Constraints
[3, 7, 8, 9, 11, 12] |
Approved w/Constraints
[3, 7, 8, 9, 11, 12] |
Approved w/Constraints
[3, 7, 8, 9, 11, 12] |
| | | | [1] | All installations of this technology must complete a Wide Area Network (WAN) impact review (contact VA e-mail:[OIT ITOPS SD Engagement Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements.
This technology must not be configured using Maria Database (MariaDB) Server.
This technology can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors should be considered especially when an instance of this product will be considered a Moderate or High Risk system. See the MySQL Database TRM entry for more details.
Per the Initial Product Review, users must abide by the following constraints:
- Central Control meets VA requirements for the Security Control Family IA - Identification and Authentication, Control Number IA-5(1). However, Central Control does not enforce this Security Control. System Administrators must enforce VA complexity, length, change requirements, auditing, etc. related to the IA-5(1) Security Control. The Authorizing Official must accept this risk when authorizing this system with a Plan of Action and Milestones that is tracked for compliance with this Security Control.
- Central Control is an on-premise application with limited communication with other video production software that uses standard Transmission Control Protocol ports. If VA sensitive information is exchanged, Central Control must employ third-party FIPS 140-2 encryption to protect data at rest and data in transit.
- Per VAIQ 7615193 FTP must be disabled by system administrators.
| | | [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 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). | | | [5] | 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. | | | [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] | The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)
This technology must not be configured using Maria Database (MariaDB) Server.
Per the Initial Product Review, users must abide by the following constraints:
- Central Control meets VA requirements for the Security Control Family IA - Identification and Authentication, Control Number IA-5(1). However, Central Control does not enforce this Security Control. System Administrators must enforce VA complexity, length, change requirements, auditing, etc. related to the IA-5(1) Security Control. The Authorizing Official must accept this risk when authorizing this system with a Plan of Action and Milestones that is tracked for compliance with this Security Control.
- Central Control is an on-premise application with limited communication with other video production software that uses standard Transmission Control Protocol ports. If VA sensitive information is exchanged, Central Control must employ third-party FIPS 140-2 encryption to protect data at rest and data in transit.
- Per VAIQ 7615193 FTP must be disabled by system administrators.
| | | [8] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | | [9] | 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. | | | [10] | 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. | | | [11] | 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). | | | [12] | 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. |
|
| Note: |
At the time of writing, version 8.3.119.1 is the most current version and was released 3/29/2022. |
