Visible to Intel only — GUID: GUID-982019AF-DD6F-404A-8366-E61030EB0210
For API Level 1 - Intel® ME 7.x - Sandy Bridge
For API Level 1.1 - Intel® ME 8.x lite - Sandy Bridge
For API Level 2 - Intel® ME 8.0 - Ivy Bridge
For API Level 3 - Intel® ME 8.1 - Ivy Bridge
For API Level 3 - SEC1.0, SEC1.1, SEC1.2, SEC2.0
For API Level 4 - Intel® ME 9.5, Intel ME 9.5.55 - Haswell
For API Level 4 - Intel® ME 9.1, Intel ME 9.1.35 - Haswell
For API Level 5 - Intel® ME 10.0.0 - Haswell
For API Level 6 - Intel® ME 10.0.20 - Broadwell
For API Level 7 - ME 11.0 - Skylake_LP and Skylake_H
For API Level 8 - TXE3.0 - Broxton, ME 11.5/11.8 - Kabylake_LP, Kabylake_H
For API Level 9 - Intel® ME 12.0 - Cannon Lake
Trusted Application Validation Guidelines
Validating the Manifest
Memory and Performance
Error Handling and Recovery
Functional Validation and Multi-Instance Support
Pack and DALP Generation and Validation
Host-Side Software Validation Guidelines
Trusted Application Management Flows
Error Handling and Recovery Flows
Multi-Instance and Interoperability Testing of Trusted Application Management
General and Platform-Related Events
End-to-End and Setup Validation Guidelines
Cross Trusted Application Interoperability Functional Testing
Creating a New Project
Importing an Existing Project
Converting an Existing Project
Building and Packaging Your Project and Running in Emulated Environment
Running Your Project
Running and Testing on Emulation and on Silicon
Debugging Trusted Applications
Preparing and Submitting Your Project for Signing
Signing an Applet
Signing New Versions
Visible to Intel only — GUID: GUID-982019AF-DD6F-404A-8366-E61030EB0210
Functional Validation and Multi-Instance Support
Full Functional Validation - All of the functional flows must be covered by the validation team, for both pre-production and production cases.
Note: During the signing of the trusted application, no functional tests will be executed by the team responsible for the certification flow. So it is fully under the responsibility of the business unit and application owner to verify that the trusted application is fully validated and functional in both pre-production and production.
Multi-Instance & Multi-Sessions Validation Coverage - An important aspect of this validation is to move from using a single instance of the trusted application (one trusted application session) to multiple instances. You should review and test cases in which there are several sessions running in parallel (which might be either shared on non-shared) and this is mainly based on the expected usage model of the trusted application. One of the initial questions would be whether our trusted application will be used by one specific host-side application, or whether it can/should be used by other applications as well. What will happen in that case, and how are we supporting multiple requests coming in parallel?
Note: There is a major change between the first and second generations of the VM regarding asynchronous execution of trusted applications. In Gen1 (Intel® ME 7.x), only one trusted application code could be executed at a given moment. In Gen2 (Intel ME 8.x), Intel® DAL firmware and VM can support parallel execution of different instances of trusted applications.
In addition you need to understand the difference between shared and non-shared sessions in Intel DAL Host Interface Service while opening a new session. This impacts the number of trusted application instances that will be running in the firmware.