SPECIFICATIONTCG TPM Vendor ID Registry Family 1.2 and 2.0 |TCG TPM Vendor ID Registry
Family 1.2 and 2.0
Revision 0.95
May 8, 2024
Contact: admin@trustedcomputinggroup.org
Public Review

Work in ProgressThis document is an intermediate draft
for comment only and is subject tochange without notice. Readers should
not design products based on thisdocument.

| Revision 0.95 | 5/8/2024 | Public Review© TCG 2024

TCG TPM Vendor ID Registry Family 1.2 and 2.0

DISCLAIMERS, NOTICES, AND LICENSE TERMS
THIS SPECIFICATION IS PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER, INCLUDING ANYWARRANTY OF MERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR ANY PARTICULAR PURPOSE, ORANY WARRANTY OTHERWISE ARISING OUT OF ANY PROPOSAL, SPECIFICATION OR SAMPLE.
Without limitation, TCG disclaims all liability, including liability for infringement of any proprietary rights, relating to useof information in this specification and to the implementation of this specification, and TCG disclaims all liability forcost of procurement of substitute goods or services, lost profits, loss of use, loss of data or any incidental,consequential, direct, indirect, or special damages, whether under contract, tort, warranty or otherwise, arising in any
way out of use or reliance upon this specification or any information herein.
This document is copyrighted by Trusted Computing Group (TCG), and no license, express or implied, is granted
herein other than as follows: You may not copy or reproduce the document or distribute it to others without written
permission from TCG, except that you may freely do so for the purposes of (a) examining or implementing TCG
specifications or (b) developing, testing, or promoting information technology standards and best practices, so longas you distribute the document with these disclaimers, notices, and license terms.
Contact the Trusted Computing Group at www.trustedcomputinggroup.org for information on specification licensing
through membership agreements.
Any marks and brands contained herein are the property of their respective owners.

TCG TPM Vendor ID Registry Family 1.2 and 2.0 || Revision 0.95 | 5/8/2024 | Public Review

Page 1© TCG 2024

TCG TPM Vendor ID Registry Family 1.2 and 2.0

CHANGE HISTORYREVISIONDATEDESCRIPTION

1.01/1.00

October 18, 2017•

Initial Release of Version 1.01.

•••••••

Migrate to new TCG format
Added Scope section
Moved and added explanatory text
Cleaned up tables and syntax, removed unused columns
Added Simulator and Testing TPM Capabilities Vendor ID section
Added Cisco and FlySlice
Incremented Version number only. This is because the “legacy” formatted version
1.01 was updated to 1.02 prior to this version being approved. No changes fromthis document’s 1.02. Public revision comment should be as above for 1.02 as thelegacy document has no change history so will not conflict.

1.02/1.00

April 8,2020

1.03/0.90

May 28, 2020

1.04/0.90

June 10, 2020•

Minor wording fixes

1.04/0.91

June 17, 2020•

Minor editing

1.05/0.91

April 06, 2021•

Added Huawei

1.06/0.91

April 28, 2021•

Migrate to specification template1.06/0.92

November 15, 2022•

Added vendor Ant Group

1.06/0.93

December 2, 2022•

Added vendor HP Inc.

1.06/0.94

April 25, 2022•

Added vendor Solidigm

1.06/0.95

January 10, 2024

•Added Vendor NSING, SecEdge

TCG TPM Vendor ID Registry Family 1.2 and 2.0 || Revision 0.95 | 5/8/2024 | Public ReviewPage 2© TCG 2024

TCG TPM Vendor ID Registry Family 1.2 and 2.0

CONTENTSDISCLAIMERS, NOTICES, AND LICENSE TERMS ..................................................................................................... 1
CHANGE HISTORY ....................................................................................................................................................... 21SCOPE ................................................................................................................................................................... 41.1 Key Words....................................................................................................................................................... 41.2 Statement Type............................................................................................................................................... 42

FORMAT ................................................................................................................................................................. 53

TPM Hardware Interface Vendor ID ....................................................................................................................... 64

TPM Capabilities Vendor ID ................................................................................................................................... 84.1 Product Implementations ................................................................................................................................ 84.2 Simulator and Testing Implementations ....................................................................................................... 10TCG TPM Vendor ID Registry Family 1.2 and 2.0 || Revision 0.95 | 5/8/2024 | Public Review

Page 3© TCG 2024

TCG TPM Vendor ID Registry Family 1.2 and 2.0

1 SCOPE
This document defines the values returned by a TPM implementation. This allows entries (such as OS drivers,
software stack, applications) to know the identity of the TPM implementer.
Additional values may be requested by contacting: vendor-id-request@trustedcomputinggroup.org.

1.1 Key Words
The key words “MUST,” “MUST NOT,” “REQUIRED,” “SHALL,” “SHALL NOT,” “SHOULD,” “SHOULD NOT,”“RECOMMENDED,” “MAY,” and “OPTIONAL” in this document normative statements are to be interpreted asdescribed in RFC-2119, Key words for use in RFCs to Indicate Requirement Levels.

1.2 Statement Type
Please note a very important distinction between different sections of text throughout this document. There are two
distinctive kinds of text: informative comment and normative statements. Because most of the text in this specification
will be of the kind normative statements, the authors have informally defined it as the default and, as such, havespecifically called out text of the kind informative comment. They have done this by flagging the beginning and end ofeach informative comment and highlighting its text in gray. This means that unless text is specifically marked as of
the kind informative comment, it can be considered a kind of normative statements.

EXAMPLE: Start of informative comment
This is the first paragraph of 1–n paragraphs containing text of the kind informative comment ...
This is the second paragraph of text of the kind informative comment ...
This is the nth paragraph of text of the kind informative comment ...
To understand the TCG specification the user must read the specification. (This use of MUST does not require anyaction).
End of informative comment

TCG TPM Vendor ID Registry Family 1.2 and 2.0 || Revision 0.95 | 5/8/2024 | Public ReviewPage 4© TCG 2024

TCG TPM Vendor ID Registry Family 1.2 and 2.02 FORMATThe values in this document have no implied format or endianness. How these values are presented is defined by thespecification using them such as the TPM Library and Platform Specific Specifications.

TCG TPM Vendor ID Registry Family 1.2 and 2.0 || Revision 0.95 | 5/8/2024 | Public Review

Page 5© TCG 2024

TCG TPM Vendor ID Registry Family 1.2 and 2.0

3 TPM Hardware Interface Vendor ID
These values are the TPM manufacturer-specific 16-bit VenID fields returned by the TPM interface defined in aPlatform TPM Profile.
These values are chosen by the requestor. They are often PCI-SIG ID values assigned to them by the PCI Sig
Standard Organization, however, there is no attempt by TCG to validate or coordinate these values with PCI-Sig
Standards Organization. Therefore, no attempt should be made to associate the values returned by a TPM from thissection with a particular vendor PCI-SIG value.
All values are 16-bit integers.

Table 1 TPM Hardware Interface Vendor ID

1Assigned ToValue

AMD0x1022

Ant Group

0x6688Atmel

0x1114

Broadcom

0x14E4Cisco

0xC5C0

FlySlice Technologies

0x232B

Fuzhou Rockchip

0x232A

Google0x6666HPI

0x103C

HPE

0x1590

Huawei0x8888IBM

0x1014

Infineon

0x15D1Intel

0x8086

Lenovo0x17AA

Microsoft

0x1414

National Semi

0x100B

Nationz

0x1B4E

NSING

0x9999Nuvoton Technology10x1050

Qualcomm

0x1011

Samsung

0x144D

SecEdge

0x5ECE

Sinosun0x19FA

SMSC

0x1055

Solidigm

0x025E

STMicroelectronics

0x104AThis value was formerly assigned to Winbond

TCG TPM Vendor ID Registry Family 1.2 and 2.0 || Revision 0.95 | 5/8/2024 | Public Review

Page 6© TCG 2024

TCG TPM Vendor ID Registry Family 1.2 and 2.0

Assigned ToValue

Texas Instruments

0x104CTCG TPM Vendor ID Registry Family 1.2 and 2.0 || Revision 0.95 | 5/8/2024 | Public Review

Page 7© TCG 2024

TCG TPM Vendor ID Registry Family 1.2 and 2.04 TPM Capabilities Vendor ID
This is the value that is returned by the following commands:
For TPM Family 1.2:
TPM_GetCapability with the capability TPM_CAP_PROP_MANUFACTURER
For TPM Family 2.0:
TPM2_GetCapability with the
TPM_PT_MANUFACTURER

capability

TPM_CAP_TPM_PROPERTIES

withtheProperty

Tag

These values are chosen by the requestor. They have been typically a Stock Market symbol but that is not arequirement.
In the tables in this section the column labeled “Hex” is the machine-readable definitive value. The column labeled
ASCII is a visual representation of the hexadecimal value. The bracket quote characters are added as a visualdelimiter only, they are not included in the value. A space in this column represents either 0x00 or 0x20 which is thechoice of the requestor. All values are a 32-bit array of octets.

4.1 Product Implementations
These are TPM implementations intended for use in products in end-user applications with appropriate protections forProtected Capabilities and Shielded Locations as defined by a TCG Platform TPM Profile.
Assigned to:Value(ASCII)HexAMD<AMD >0x41 0x4D 0x44 0x00Ant Group<ANT >

0x41 0x4E 0x54 0x00

Atmel

<ATML>

0x41 0x54 0x4D 0x4C

Broadcom<BRCM>

0x42 0x52 0x43 0x4D

Cisco

<CSCO>

0x43 0x53 0x43 0x4F

Flyslice
Technologies<FLYS>

0x46 0x4C 0x59 0x53

Fuzhou Rockchip<ROCC>

0x52 0x4F 0x43 0x43

Google<GOOG>

0x47 0x4F 0x4F 0x47

HPI

<HPI >

0x48 0x50 0x49 0x00

HPE

<HPE >

0x48 0x50 0x45 0x00

Huawei<HISI>

0x48 0x49 0x53 0x49

IBM

<IBM >

0x49 0x42 0x4d 0x00

Infineon<IFX >

0x49 0x46 0x58 0x00

Intel

<INTC>

0x49 0x4E 0x54 0x43

Lenovo<LEN >

0x4C 0x45 0x4E 0x00

Microsoft<MSFT>

0x4D 0x53 0x46 0x54

NationalSemiconductor<NSM >

0x4E 0x53 0x4D 0x20

TCG TPM Vendor ID Registry Family 1.2 and 2.0 || Revision 0.95 | 5/8/2024 | Public Review

Page 8© TCG 2024

TCG TPM Vendor ID Registry Family 1.2 and 2.0

Assigned to:

Value(ASCII)Hex

Nationz<NTZ >

0x4E 0x54 0x5A 0x00

NSING

<NSG >

0x4E 0x53 0x47 0x00

Nuvoton Technology<NTC >

0x4E 0x54 0x43 0x00

Qualcomm<QCOM>

0x51 0x43 0x4F 0x4D

Samsung<SMSN>

0x53 0x4D 0x53 0x4E

SecEdge<SECE>

0x53 0x45 0x43 0x45

Sinosun<SNS >

0x53 0x4E 0x53 0x00

SMSC

<SMSC>

0x53 0x4D 0x53 0x43

ST Microelectronics<STM >

0x53 0x54 0x4D 0x20

Texas Instruments<TXN >

0x54 0x58 0x4E 0x00

Winbond<WEC >

0x57 0x45 0x43 0x00

Table 2 TPM Capabilities Vendor ID

TCG TPM Vendor ID Registry Family 1.2 and 2.0 || Revision 0.95 | 5/8/2024 | Public Review

Page 9© TCG 2024

TCG TPM Vendor ID Registry Family 1.2 and 2.0

4.2 Simulator and Testing Implementations
These are TPM implementations intended for use in simulators and testing. There are no implied protections forProtected Capabilities and Shielded Locations for TPM’s providing these identifiers. These values are used to indicate
to software the nature of the TPM’s implementation.
These values are not intended for use in production Virtual or Software-based TPMs. While perhaps similar in nature,
Production Virtual or Software-based TPMs which are based on TCG defined specifications should use TCG assigned
values in section 4.1 Product Implementations and if applicable section 3 TPM Hardware Interface Vendor ID.
Use of these values is by convention only and not enforced by TCG. The values below are not assigned to any
particular vendor, however, TCG reserves the right to assign values to suppliers at a later time.
Assigned to:

ASCII

Hex

Simulator 0<SIM0>

0x53 0x49 0x4d 0x30

Simulator 1<SIM1>

0x53 0x49 0x4d 0x31

Simulator 2<SIM2>

0x53 0x49 0x4d 0x32

Simulator 3<SIM3>

0x53 0x49 0x4d 0x33

Simulator 4<SIM4>

0x53 0x49 0x4d 0x34

Simulator 5<SIM5>

0x53 0x49 0x4d 0x35

Simulator 6<SIM6>

0x53 0x49 0x4d 0x36

Simulator 7<SIM7>

0x53 0x49 0x4d 0x37

Test 0<TST0>

0x54 0x53 0x54 0x30

Test 1<TST1>

0x54 0x53 0x54 0x31

Test 2<TST2>

0x54 0x53 0x54 0x32

Test 3<TST3>

0x54 0x53 0x54 0x33

Test 4<TST4>

0x54 0x53 0x54 0x34

Test 5<TST5>

0x54 0x53 0x54 0x35

Test 6<TST6>

0x54 0x53 0x54 0x36

Test 7<TST7>0x54 0x53 0x54 0x37

Note to Editor: Before assigning new values, verify they do not conflict with
Assigned values in Table 2 TPM Capabilities Vendor ID above.

Table 3 Vendor ID for Simulators and Testing

TCG TPM Vendor ID Registry Family 1.2 and 2.0 || Revision 0.95 | 5/8/2024 | Public Review

Page 10© TCG 2024