Universal Type Client 6.1.5 Download Mac Updated

Universal Type Client 6.1.5 Download Mac

VA Technical Reference Model v 22.3

Universal Type Server / Universal Type Client (Extensis)

Universal Blazon Server / Universal Type Client (Extensis)

Technologies must be operated and maintained in accordance with Federal and Section security and privacy policies and guidelines. More than data on the proper utilise of the TRM tin can exist constitute on the TRM Proper Apply Tab/Section.

Website:	Go to site
Clarification:	Universal Type Server / Universal Type Client (Extensis) is a font distribution engineering that audits user`s font drove, manage fonts centrally and command users admission. This engineering enables users to assist constitute font purchase policies, deploys font management to each user`s desktop, brand it piece of cake to keep the team on task with easy to set up and distribute. UTS (Universal Type Server) streamlines font workflow, securely manages fonts, and controls corporate typographic branding. Besides, this technology integration via automobile-activation plug-ins for professional creative software including Adobe Creative Cloud 2018 and QuarkXPress 2017. The TRM decisions in this entry merely utilise to technologies and versions endemic, operated, managed, patched, and version-controlled by VA. This includes technologies deployed every bit software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Deject services provided past the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed past an external Deject Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and deject-based products within VA, including VA private clouds, delight run across the Enterprise Deject Solutions Part (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITEPMOECSO
Applied science/Standard Usage Requirements:	Users must ensure their use of this engineering science/standard is consistent with VA policies and standards, including, but non limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Engineering (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to employ of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Data Officeholder (CIO), or local Office of Information and Applied science (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This applied science 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 Department 508 Part and advisable remedial activity required if necessary. For additional information or assist regarding Section 508, please contact the Section 508 Office at Section508@va.gov. Please see reference tab for more information apropos product versions.
Decision:	View Decisions

Determination Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v20.three
Decision Date:	03/25/2020
Introduced By:	TRM Request
Vendor Name:	Extensis

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

Version	Release Date	Vendor Finish of Life Date	Vendor Desupport Appointment
6.one.x	ten/23/2017
7.0.ten	10/18/2018

Users must ensure their utilise of this applied science/standard is consistent with VA policies and standards, including, merely not express to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Data Processing Standards (FIPS). Users must ensure sensitive information is properly protected in compliance with all VA regulations. Prior to utilise of this technology, users should bank check with their supervisor, Information Security Officer (ISO), Facility Master Data Officeholder (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all deportment are consistent with electric current VA policies and procedures prior to implementation.

The VA Determination Matrix displays the current and time to come VA IT position regarding unlike releases of a TRM entry. These decisions are based upon the best information bachelor equally of the about current date. The consumer of this information has the responsibleness to consult the organizations responsible for the desktop, testing, and/or product environments to ensure that the target version of the technology will be supported. Whatsoever 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 canonical for use.
Yellow	Approved w/Constraints: The applied science/standard tin can be used within the specified constraints located below the conclusion matrix in the footnote[1] and on the General tab.
Grayness	Unapproved: This engineering or standard can exist used simply 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 squad or organisation that wishes to apply the technology.
Orange	Divest: VA has decided to divest itself on the apply of the technology/standard. Equally a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the applied science/standard. Additional information on when the entry is projected to become unapproved may be plant on the Determination tab for the specific entry.
Blackness	Prohibited: The engineering science/standard is not (currently) permitted to exist used under whatever circumstances.
Blue	Planning/Evaluation Constraint:The catamenia of time this technology is currently existence evaluated, reviewed, and tested in controlled environments. Use of this engineering science is strictly controlled and not bachelor for utilize within the general population. If a customer would like to use this engineering, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the determination matrix. The Local or Regional OI&T office should submit an enquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes beneath.

Release/Version Information:

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

For example, a technology approved with a decision for vii.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.iv.x decision would cover any version of 7.4.(Annihilation), merely would not comprehend any version of 7.5.10 or seven.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 touch previous decimal places.

For example, a technology canonical with a decision for 12.6.4+ would encompass whatsoever version that is greater than 12.6.4, only would non exceed the .6 decimal ie: 12.6.401 is ok, 12.half-dozen.5 is ok, 12.6.nine is ok, even so 12.seven.0 or 13.0 is non.

<Past

CY2021

CY2022

CY2023

Hereafter>

Release

vi.1.10

Unapproved

7.0.ten

Approved west/Constraints
[iii, six, eight, 9]

Approved w/Constraints
[3, vi, 8, 9]

Canonical w/Constraints
[3, vi, 9, 10]

Approved w/Constraints
[3, 6, nine, 10]

Canonical due west/Constraints
[3, 6, 9, ten]

Approved westward/Constraints
[iii, 6, ix, x]

Canonical w/Constraints
[3, half dozen, 9, 10]

Approved w/Constraints
[3, 6, 9, x]

Canonical w/Constraints
[iii, half dozen, 9, 10]

Canonical w/Constraints
[iii, half-dozen, 9, 10]

Approved w/Constraints
[3, 6, 9, x]

Approved w/Constraints
[three, 6, ix, 10]

Decision Constraints


[1]	If free trialware is utilized, the software must be purchased or removed at the cease of the trial menses.

[2]	Applied science 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]	Users should check with their supervisor, Information Security Role (ISO) or local OIT representative for permission to download and employ this software. Downloaded software must always be scanned for viruses prior to installation to preclude 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 customs date. Users should note, any endeavour by the installation process to install any additional, unrelated software is not canonical and the user should take the proper steps to refuse those installations.

[4]	Due to potential information security risks, cloud based technologies may not be used without the approving of the Enterprise Cloud Solution Office (ECSO). This torso is in function responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[v]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this engineering should exist reviewed by the local ISO (Information Security Officeholder) to ensure compliance with VA Handbook 6500.

[vi]	Users must ensure that Firefox, Google Chrome, Microsoft Internet Explorer (IE), and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the 'Category' tab under 'Runtime Dependencies')

[vii]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assist on cloud products. If farther guidance is needed contact the Enterprise Deject Solution Office (ECSO), which is the body responsible for new software evolution in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational data, Personally Identifiable Data (PII), Protected Health Information (PHI), and VA sensitive data are not compromised inside the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product asking with the Project Special Forces (SPF) team, please use their online grade. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[8]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assist on deject products. If farther guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Data (PII), Protected Health Data (PHI), and VA sensitive information are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) squad, delight utilize their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[ix]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this applied science should exist reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[10]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If farther guidance is needed contact the Enterprise Deject Solution Role (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised inside the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (PSF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

Annotation:

At the fourth dimension of writing, version vii.0.5 is the nigh electric current version and was released March, 18 2020.

Notation: 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 constitute in the Decision and Decision Constraints.
Name	Clarification
No components take been identified for this entry.

macOS - Approved w/Constraints
Windows Client - Canonical w/Constraints
Windows Server - Canonical west/Constraints

Adoption Benefits

At the time of writing, no National Constitute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Network Security Operations Centre (NSOC) bulletins had been issued for the latest versions of this engineering science.
This is a well-documented technology.
This applied science may ameliorate productivity for specific staff whose responsibilities include instituting font purchase policies, deploying font management to each user`due south desktop, making it easy to keep the team on task with like shooting fish in a barrel to set up and distribute.

Adoption Risks

This technology has a free trial catamenia, which carries the potential for the disruption of service delivery and inaccurate financial planning.
At that place are other approved solutions that provide similar functionality bachelor on the TRM. The use of several similar solutions may increment organization requirements for support and maintenance.
The technology may collect, store or transmit Personally Identifiable Data (PII)/Protected Wellness data (PHI) or VA sensitive data.

Architectural Benefits

This applied science is portable equally information technology runs on multiple TRM-approved operating systems.

Architectural Risks

This applied science includes cloud-based functionality which has potential information security risks.

- The information contained on this page is accurate as of the Decision Engagement (03/25/2020).