MATLAB Compiler Runtime (MCR)

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:	MATLAB Compiler Runtime (MCR) is used to run compiled MATLAB programs and executables on any user machine that does not have MATLAB installed. MATLAB is a high-level language and interactive environment for numerical computation, visualization, and programming. The technology is used to analyze data, develop algorithms, and create models and applications. This entry specifically covers MATLAB Compiler Runtime (MCR) and not MATLAB.
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 v24.7
Decision Date:	07/19/2024 at 16:33:48 UTC
Aliases:	Compiler; MATLAB Compiler
Introduced By:	TRM Request
Vendor Name:	MathWorks

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
R2013a (8.1)	03/07/2013
R2013b (8.2)	09/06/2013
R2014a (8.3)	03/07/2014
R2014b (8.4)	11/20/2014
R2015a (8.5)	03/05/2015
R2015b (8.6)	09/03/2015
R2016a (9.0.1)	03/03/2016
R2016b (9.1)	09/15/2016
R2017a (9.2)
R2017b (9.3)
R2018a (9.4)
R2018b (9.5)
R2019a (9.6)
R2019b (9.7)	09/17/2019
R2020a (9.8)	04/22/2020
R2021a (9.10)	03/26/2021
R2021b	09/28/2021
R2022a	03/26/2022
R2023a	03/21/2023
R2023b	01/16/2024
R2024a	03/20/2024

Current Decision Matrix (07/12/2024)

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

CY2017

CY2018

CY2019

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

R2013a (8.1)

Unapproved

R2013b (8.2)

Unapproved

R2014a (8.3)

Divest
[2, 3, 4]

Unapproved

R2014b (8.4)

Divest
[2, 3, 4]

Unapproved

R2015a (8.5)

Approved w/Constraints
[2, 3, 4]

Divest
[2, 3, 4]

Divest
[2, 3, 5]

Unapproved

R2015b (8.6)

Approved w/Constraints
[2, 3, 4]

Approved w/Constraints
[2, 3, 5]

Divest
[2, 3, 5]

Divest
[3, 6]

Unapproved

Divest
[2, 3]

Unapproved

R2016a (9.0.1)

Approved w/Constraints
[2, 3, 4]

Approved w/Constraints
[2, 3, 5]

Divest
[3, 6]

Unapproved

R2016b (9.1)

Approved w/Constraints
[2, 3, 4]

Approved w/Constraints
[2, 3, 5]

Divest
[3, 6]

Unapproved

Approved w/Constraints
[2, 3]

R2017a (9.2)

Unapproved

Approved w/Constraints
[3, 6]

Approved w/Constraints
[2, 3]

R2017b (9.3)

Unapproved

Approved w/Constraints
[3, 6]

Approved w/Constraints
[2, 3]

R2018a (9.4)

Unapproved

Approved w/Constraints
[2, 3]

R2018b (9.5)

Unapproved

Approved w/Constraints
[2, 3]

R2019a (9.6)

Unapproved

R2019b (9.7)

Unapproved

R2020a (9.8)

Unapproved

R2021a (9.10)

Unapproved

R2021b

Unapproved

R2022a

Unapproved

R2023a

Unapproved

R2023b

Unapproved

R2024a

Unapproved

Decision Constraints


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

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

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

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

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

[6]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that they are only downloading this technology from the vendor`s website.

Note:

At the time of writing, version R2024a is the most current version, released 03/20/2024.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*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
Information Management Technologies Business Intelligence and Data Warehouse Platforms	Data Analytics (Statistical Analysis, Prediction, and Modeling)

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

MATLAB

Comparable Technologies:

Companion Technologies/Supported Standards:

C++ Programming Language

General Analysis

Adoption Benefits

This is a well-documented technology.
There are minimal other TRM-approved technologies that provide the same functionality.
This technology extends the functionality of MATLAB software.
This technology may improve productivity for specific staff whose responsibilities include running MATLAB programs and executables.
At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Cyber Security Operations Center (CSOC) bulletins had been issued for the latest versions of this technology.

Adoption Risks

The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
There is no indication based on either the vendor documentation or the Cryptographic Module Validation Program (CMVP) that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
This technology is available as freeware. As such this technology may be without clearly defined support options which may result in suboptimal enterprise level support.

Architectural Benefits

This technology is portable as it runs on multiple TRM-approved operating systems.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (07/12/2024)

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

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (07/12/2024)

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

EMAIL UPDATES