Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First Draft of Caliptra Trademark Audit #175

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
72 changes: 72 additions & 0 deletions doc/CaliptraTrademarkAudit.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,72 @@

# Caliptra Trademark Auditing Process

This document will describe the specific requirements to be reviewed by a 3rd party and attest to Caliptra TAC that the requirements have been met.

The goal of a Caliptra Trademark Audit would be to be compliant with OCP Safe Level 2 requirements using an OCP Safe approved auditor.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An additional goal of a ....

s/would/is/

s/Safe/S.A.F.E./


Currently, this is a list of Topics to review for Trademark Compliance. Specific testable requirements will need to be spelled out subsequently.

* Each of these topics will have to be reviewed for an integration to get approval of Trademark Usage
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "approval for TM usage" but English is my second language


## Caliptra IP

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Preface sentence.

"A compliant integration must show:"

  • bullet points

* Show how the RTL was integrated into the device environment
* Show a Run of the tool to verify the RTL Release Hash (in development)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO here? Replace to link for source code of tool when ready

* Show the ROM hash from a release ROM hash
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the ROM hash maps to a verifiable build of a tagged ROM release

* Show the internal Caliptra FW signing process used to sign Caliptra FW
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

redundant, remove the first "Caliptra FW"

* Show what options were used to synthesize the RTL
* Show input wires to RTL
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have an integration guide. Can we reference the sections in said guide?

Same for options used to synthesize

* Clock
* Reset
* Power Good, Ready for fuses, Ready for FW, etc.
* Show how the Generic input/output wires are addressed

## Caliptra Wrapper

* Show how the Obfuscation key is provided and ensure that it is not available to any FW.
* Describe the noise source for the RNG (indicating if Internal RNG or external RNG)
* External RNG description should be shown
* Show error handling integration
* Show how debugging will be enabled/disabled in production
* Show SRAM zeroization
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

process for SRAM zeroization


## HSM Support

* Show how the FW signing key is created and protected
* If applicable, show LMS sign keys derivations and how HSM protects them
* If applicable, prove LMS verify.

## Fusing

* Show how the fuses are loaded into the Caliptra IP
* Show how the Security State is provided to Caliptra IP
* Show the fuse recipe that is expected to used for Caliptra
* Ensure the Public Key Hash is fused
* Ensure that the security state is fused

## Manufacturing

* Indicate how the manufacturing process will flow.
* Show the UDS Seed creation
* Show the CSR extraction and signing

## Cert Chain Verify

* Show that a part can have IDevID Signed Cert.
* Create a valid Caliptra cert chain with IDevID, LDevID, FMC Alias and R-TAlias cert. Prove that the cert chain verifies.

## SOC Root of Trust

* Show that SOC RoT is sending SOC FMC measurements to Caliptra before running FMC.
* Show the design for the SOC ROT Storage and fetching of Caliptra FW
* Describe how Caliptra PA_USER management will be used.

## SOC Run-Time

* Show how SVNs fuses will be incremented.
* Show how keys revoke bits can be revoked.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo, key revoke bits

* Show how Run-Time Entropy will be fused.
* Show how owner key hash will be fused.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

capitalization

* Show how the IDevID Cert gets recreated on part.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on part? Is this sentence incomplete?

* Show how external entities would interact with Calitpra (path through Security processor, direct access, etc.)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need a specific PAUSER requirement. Show those are not spoofed and correctly bound to callers