|
| [1] | Users must ensure the underlying infrastructure that supports the product`s admin tools DXmanager and DXadmind is operated in FIPS mode and CA Directory servers must adhere to VA Baseline hardening standards. |
|
| [2] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
|
|
| [3] | Users must ensure the underlying infrastructure that supports the product`s admin tools DXmanager and DXadmind is operated in FIPS mode and CA Directory servers must adhere to VA Baseline hardening standards.
Telnet should be disabled in development and in production environment. |
|
| [4] | 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. |
|
| [5] | Due to potential information security risks, cloud based versions of this product are not permitted without a waiver signed by the Deputy CIO of ASD based upon a recommendation from the Architecture and Engineering Review Board (AERB). In addition, cloud based features of this software may not be used without an Enterprise Security Change Control Board (ESCCB) approval to ensure that confidential organization and/or PII/PHI data are not compromised (ref: VA Directive 6004, VA Directive 6517 and VA Directive 6513). Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review. |
|
| [6] | Enterprise Security Solutions Services (ESSS) conducted a pre-assessment and security requirements verification of CA Directory. It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied:
- Must ensure the underlying infrastructure that supports DXmanager and DXadmind is operated in Federal Information Processing Standard (FIPS) mode.
- Extra care should be taken when accessing DXmanager using Internet Explorer 7 to ensure that the user logs out of the session and closes the browser completely rather than just closing the tab that the session was open in.
- CA Directory servers must adhere to hardening standards located in the VA Baseline Configuration Management website. System administrators who support and maintain the directory services must utilize passwords that meet the VA minimum requirements defined in control IA-5: Authenticator Management in VA Handbook 6500.
- Telnet must be disabled in development and in production environment.
- Must ensure ESE`s current Application Standards Baseline version of Java is used with CA Directory.
|
|
| [7] | Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. 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). |
|
| [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 VA Enterprise Cloud Services (ECS) Group. 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] | 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. |
|
| [11] | Security Engineering Solution Delivery Information Technology Operations and Services (ITOPS)
conducted a pre-assessment and security requirements verification of CA Directory. It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied:
- Must ensure the underlying infrastructure that supports DXmanager and DXadmind is operated in Federal Information Processing Standard (FIPS) mode.
- Extra care should be taken when accessing DXmanager using Internet Explorer 7 to ensure that the user logs out of the session and closes the browser completely rather than just closing the tab that the session was open in.
- CA Directory servers must adhere to hardening standards located in the VA Baseline Configuration Management website. System administrators who support and maintain the directory services must utilize passwords that meet the VA minimum requirements defined in control IA-5: Authenticator Management in VA Handbook 6500.
- Telnet must be disabled in development and in production environment.
- Must ensure ESE`s current Application Standards Baseline version of Java is used with CA Directory.
|
|
| [12] | 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). |
|
| [13] | Security Engineering Solution Delivery Information Technology Operations and Services (ITOPS) conducted a pre-assessment and security requirements verification of CA Directory. It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied:- Must ensure the underlying infrastructure that supports DXmanager and DXadmind is operated in Federal Information Processing Standard (FIPS) mode.
- Extra care should be taken when accessing DXmanager using Internet Explorer to ensure that the user logs out of the session and closes the browser completely rather than just closing the tab that the session was open in.
- CA Directory servers must adhere to hardening standards located in the VA Baseline Configuration Management website. System administrators who support and maintain the directory services must utilize passwords that meet the VA minimum requirements defined in control IA-5: Authenticator Management in VA Handbook 6500.
- Telnet must be disabled in development and in production environment.
- Must ensure ESE`s current Application Standards Baseline version of Java is used with CA Directory.
|
|
| [14] | 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). |
|
| [15] | Per the Initial Product Review:
Symantec Directory will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
Telnet should be disabled in development and production environments.
As of this writing, JXplorer version 3.3.1.2 is APPROVED on the VA Technical Reference Model (TRM) v21.2. Users should check the TRM before downloading and installing this software to ensure that it is still in an APPROVED status.
Symantec Directory should only be deployed on operating systems that are approved on the VA TRM. In addition, those servers must adhere to hardening standards located in the VA Baseline Configuration Management website. System administrators who support and maintain the directory services must utilize passwords that meet the VA minimum requirements defined in control IA-5: Authenticator Management in VA Handbook 6500. |
|
| [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] | 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. |
|
| [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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
| [19] | 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). |
|
| [20] | 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). |
|
| [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 VA Handbook 6500. |
|
| [22] | Per the Initial Product Review:
- Symantec Directory will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information.
- Telnet should be disabled in development and production environments. IPR – Symantec Directory
- As of this writing, JXplorer version 3.3.1.2 is APPROVED on the VA Technical Reference Model (TRM). Users should check the TRM before downloading and installing this software to ensure that it is still in an APPROVED status.
- Symantec Directory should only be deployed on operating systems that are approved on the VA TRM. In addition, those servers must adhere to hardening standards located in the VA Baseline Configuration Management website. System administrators who support and maintain the directory services must utilize passwords that meet the VA minimum requirements defined in control IA-5: Authenticator Management in VA Handbook 6500
Users must not utilize TELNET, as it is at the time of writing, unapproved in the TRM. |
|
| [23] | 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. |
|
| [24] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. |
|
| [25] | 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). |
