RFC 9334 Quiz

Attestation roles, evidence, results, and freshness

0 / 0

References

Q1: Which role creates Evidence about a Target Environment?

Multiple Choice
**Explanation:** A: The Attester produces Evidence containing claims about its Target Environment. B: The Verifier consumes and appraises Evidence. C: The Relying Party consumes Attestation Results for its decision.

Q2: What is the Verifier's main output?

Multiple Choice
**Explanation:** A: A role does not create the environment it is appraising. B: RATS does not define OAuth code issuance as the Verifier's output. C: The Verifier applies an Evidence appraisal policy and produces Attestation Results.

Q3: Who applies the Appraisal Policy for Attestation Results?

Multiple Choice
**Explanation:** A: The Attester creates Evidence and does not make the Relying Party's acceptance decision. B: The Relying Party evaluates Attestation Results using its result-appraisal policy. C: An Endorser supplies Endorsements used by a Verifier.

Q4: Is a positive Attestation Result automatically an authorization grant?

Multiple Choice
**Explanation:** A: The Verifier appraises Evidence while the Relying Party makes its own decision. B: Signature validity does not define the Relying Party's authorization policy. C: An Attestation Result is decision support and can still be unacceptable for a particular use.

Q5: What distinguishes the Passport Model?

Multiple Choice
**Explanation:** A: The reusable result resembles a passport carried by its holder. B: That flow describes the Background-Check Model more closely. C: Both topological patterns retain the Evidence-appraisal role of a Verifier.

Q6: What distinguishes the Background-Check Model?

Multiple Choice
**Explanation:** A: That is characteristic of the Passport Model and is not required here. B: The result returns to the Relying Party for its own appraisal and decision. C: The architecture assigns Evidence appraisal to the Verifier role.

Q7: What is the role of Reference Values?

Multiple Choice
**Explanation:** A: Nonces can support freshness but are not Reference Values. B: Reference Values are inputs to Evidence appraisal, not the final decision. C: They provide comparison material for assessing claims in Evidence.

Q8: Why does a RATS design evaluate freshness?

Multiple Choice
**Explanation:** A: Timestamps, nonces, or epoch identifiers can connect appraisal to a relevant time window. B: Freshness describes timing and cannot guarantee future state. C: Freshness and source authenticity are separate properties.

Q9: Which change addresses the disclosure risk without weakening appraisal?

Multiple Choice

An agent sends signed Evidence containing a device serial number, patch level, loaded modules, and a user identifier to any endpoint claiming to be the Verifier. The team argues that no Verifier authentication is needed because a recipient cannot alter the signature.

**Explanation:** RFC 9334 Section 7.2 notes that an Attester typically authenticates a Verifier before releasing sensitive Evidence. Section 11 explains that Evidence and Attestation Results can reveal device state and PII. A signature protects authenticity and integrity, not recipient authorization or confidentiality. C preserves appraisal while controlling disclosure; B expands the exposure, and D neither addresses the listed data nor preserves freshness analysis.

Q10: May the backend authorize the requested transfer from this result alone?

Multiple Choice

A trusted Verifier issues a fresh, authentic Attestation Result saying that an agent runs approved firmware. A gateway treats that boolean result as permission for every operation. The backend receives the result and an otherwise valid OAuth grant whose audience names a different service; the requested transfer also exceeds the grant's scope.

**Explanation:** RFC 9334 Section 8.4 defines Attestation Results as input to a Relying Party's appraisal and application-specific decision. Section 10 makes freshness relevant to whether claims still reflect recent state, but freshness does not define resource authority. C preserves the separation: the result can satisfy a device-state condition, while audience, scope, subject, and operation policy still govern access. D is too broad because authorization is an explicit Relying Party use case.