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). 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. 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. CodeMeter Runtime is a package that contains all the components needed to create license containers. This entry only covers CodeMeter Runtime. CodeMeter uses tokens or, in the vendor`s vernacular, license containers that could be physical hardware dongles or soft licenses.ĬodeMeter is available in three editions:ĬodeMeter Runtime, CodeMeter Embedded and CodeMeter Micro Embedded. More information on the proper use of the TRM can be found on theĬodeMeter is a product used for the protection of software through either encryption or use of an application programming interface (API).

Technologies must be operated and maintained in accordance with Federal and Department security and

Codemeter runtime service