Telerik User Interface (UI) for Active Server Pages (ASP) .NET Asynchronous JavaScript and Extensible Markup Language (AJAX)

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Telerik User Interface (UI) for Active Server Pages (ASP) .NET Asynchronous JavaScript and Extensible Markup Language (AJAX) is an application programming interface (API) that enables users to build high-quality, professional line-of-business projects. This technology has Hypertext Markup Language-Level 5 (HTML5) and Cascading Style Sheets-Level 3 (CSS3)-based render mode, which saves HTML and CSS resources. Additionally, this software compresses data transferred between browser and server, and uses built-in Content Delivery Network (CDN) support and CSS sprites to deliver content to end-users. This technology does not store data in a database.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. 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.
Section 508 Information:	This technology has been assessed by the Section 508 Office and found non-conformant. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v22.4
Decision Date:	04/27/2022
Aliases:	UI for ASP.NET AJAX; ASP.NET AJAX UI
Introduced By:	TRM Request
Vendor Name:	Telerik

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
2011.3.1305	01/01/2012
2012.1.201	02/01/2012
2012.1.215	02/15/2012
2012.1.411	04/10/2012
2012.2.522	05/22/2012
2012.2.607	06/11/2012
2012.2.912	09/12/2012
2012.3.1016	10/17/2012
2012.3.1205	12/05/2012
2012.3.1308	01/08/2013
2013.1.130	01/30/2013
2013.1.220	02/20/2013
2013.1.403	04/03/2013
2013.1.417	04/17/2013
2013.2.522	05/22/2013
2013.2.611	06/12/2013
2013.2.717	07/17/2013
2013.3.926	08/26/2013
2013.3.1015	10/16/2013
2013.3.1114	11/14/2013
2013.3.1324	01/28/2014
2014.1.225	02/26/2014
2014.1.403	04/03/2014
2014.2.423	04/23/2014
2014.2.618	06/18/2014
2014.2.724	07/24/2014
2014.3.1002	10/02/2014
2014.3.1024	10/27/2014
2014.3.1209	12/09/2014
2015.x	11/11/2015
2016.x	01/13/2016
2017.x	01/18/2017
2018.x	01/17/2018
2019.x	01/16/2019
2020.x	01/15/2020
2021.x	01/20/2021
2022.x

Current Decision Matrix (04/18/2022)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. 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.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2022

CY2023

CY2024

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

2014.3.1209

Unapproved

2016.x

Unapproved

2017.x

Unapproved

2018.x

Unapproved

2019.x

Unapproved

2020.x

Divest
[1, 5, 6, 7]

Unapproved

2021.x

Approved w/Constraints
[1, 5, 6, 7]

Divest
[1, 5, 6, 7]

Unapproved

2022.x

Unapproved

Approved w/Constraints
[1, 5, 6, 7]

Decision Constraints


[1]	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.

[2]	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.

[3]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[4]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users should ensure Microsoft .NET Framework and Microsoft Internet Information Services (IIS) are implemented within VA-approved baselines.

[5]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[6]	Users must not utilize Active Server Pages (ASP).NET Asynchronous JavaScript And Extensible Markup Language (XML) (AJAX) as it is, at the time of writing, unapproved in the TRM. Users must not utilize Opera Desktop as it is, at the time of writing, unapproved in the TRM. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users should ensure Firefox, Google Chrome, Microsoft .NET Framework, Microsoft Internet Explorer (IE),and Microsoft Internet Information Services (IIS) are implemented within VA-approved baselines. Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.

[7]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process.

Note:

At the time of writing, version 2022.1.302 is the most current version, released 03/02/2022.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	Version History		The version history and release notes of this technology can be found here.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
No components have been identified for this entry.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Application Technology Development Tools	User Interface Design Tools

Operating Systems Supported by the Technology

Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This is a mature technology.
This is a well-documented technology
This product provides code quality and debugging functionality, which may provide efficiencies for software development teams.

Adoption Risks

Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
This technology can potentially use Active Server Pages (ASP).NET Asynchronous JavaScript And Extensible Markup Language (XML) (AJAX), an unapproved technology.
This technology can potentially use Opera Desktop, an unapproved technology.
This technology may utilize external data connections.
There are known Common Vulnerabilities and Exposures (CVEs) and VA Cyber Security Operations Center (CSOC) vulnerabilities. Please see NVD - Results (nist.gov) for more details.
This software has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.

Architectural Benefits

This technology is compatible with multiple other Technical Reference Model (TRM) technologies and standards used by the organization.

Architectural Risks

This technology is not portable as it runs only on Windows platforms.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 23.1

General Information

Vendor Release Information

Current Decision Matrix (04/18/2022)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 23.1

General Information

Vendor Release Information

Current Decision Matrix (04/18/2022)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES