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 been assessed by the Section 508 Office and found non-conformant. 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 and those controlled and managed by an external Cloud Service Provider (i.e.
This includes technologies deployed as software 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. 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. In addition to rendering forms, this product supports XML data and schema bindings and the capability to enhance document security with secure template designs for digital signatures.
More information on the proper use of the TRM can be found on theĪdobe LiveCycle Designer is a forms authoring software intended to render Extensible Markup Language (XML) forms as Portable Document Format (PDF) or HyperText Markup Language (HTML) files, mirroring the paper forms they will replace. Technologies must be operated and maintained in accordance with Federal and Department security and