CCSI Officer course · Module 03 of 10
Remote attestation and verifiers
The IETF RATS architecture (RFC 9334): roles, evidence, endorsements, reference values, appraisal policy, freshness, and the passport and background-check models.
Learning objectives
- Name the RATS roles and the artifacts that flow between them
- Explain how a verifier appraises evidence and what an attestation result is
- Choose between the passport and background-check conveyance models
- Recognise common verifier mistakes such as missing freshness or debug checks
Lessons
Lesson 3.1 · 15 min
RATS roles and artifacts (RFC 9334)
Attester, Verifier, Relying Party, Endorser and Reference Value Provider, and what each one produces.
Lesson 3.2 · 15 min
Appraisal, freshness and binding
What a verifier must check, why nonces matter, and how to bind a key to evidence.
Lesson 3.3 · 12 min
Passport and background-check models
Two ways to move evidence and results between parties, and when to use each.
Check your understanding
Module 3 quiz
6 questions · pass mark 80%
1.In RFC 9334, which role appraises Evidence and produces Attestation Results?
2.Known-good measurements published by your build pipeline are, in RATS terms:
3.What is the main purpose of including a verifier-supplied nonce in evidence?
4.Why bind a public key into the evidence's caller-data field?
5.AWS KMS checking a Nitro Enclave attestation document attached to a Decrypt request is an example of:
6.Which finding should cause a verifier to reject evidence even if all measurements match?
Glossary
- Evidence
- Claims about an Attester's state, signed by the Attester's hardware-rooted key.
- Attestation Result
- The Verifier's output after appraising Evidence, consumed by Relying Parties.
- Endorsement
- A statement from a vendor vouching for an Attester's signing capability or configuration.
- Reference Value
- A known-good value, such as an expected measurement, used during appraisal.
- Nonce
- A single-use random value that proves freshness.