Additional information on when the entry is projected to become unapproved may beįound on the Decision tab for the specific entry. Has been granted to the project team or organization that wishes to use the technology.ĭivest: VA has decided to divest itself on the use of the technology/standard.Īs a result, all projects currently utilizing the technology/standard must plan to eliminate their use of The Authorizing Official Designated Representative ( AODR) as designated by the Authorizing Official ( AO) or designeeĪnd based upon a recommendation from the POA&M Compliance Enforcement, Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by In the VA Decision Matrix is considered unapproved for use.Īpproved: The technology/standard has been approved for use.Īpproved w/Constraints: The technology/standard can be used within the specified constraints locatedīelow the decision matrix in the footnote and on the General tab. Any major.minor version that is not listed To ensure that the target version of the technology will be supported. Responsibility to consult the organizations responsible for the desktop, testing, and/or production environments These decisions areīased upon the best information available as of the most current date.
The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. TRM Technology, obtained from the vendor (or from the release source). The Vendor Release table provides the known releases for the For additional information or assistance regarding Section 508, please contact the Section 508 Office at Decisions Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. This technology has not been assessed by the Section 508 Office. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), 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. Users must ensure sensitive data is properly protected in compliance with all VA regulations. Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 61 VA Directives 6004, 6513, and 6517 and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: This entry covers the Desktop Edition of this technology and not any mobile versions.
For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at:
Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e.
#Wolfram player 12 software
This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This technology is available in two editions: CDF Player and CDF Player Pro. The user will have the ability to engage with live, interactive Wolfram Language examples, reports and files that are powered by real-time computation. It allows the user to view and interact with Wolfram Notebooks and CDF files.
Wolfram Player is Wolfram Computable Document Format (CDF) Player. More information on the proper use of the TRM can be found on the Technologies must be operated and maintained in accordance with Federal and Department security and
0 kommentar(er)
