RFC 5280 Quiz (EN)

**Judgment point:** Separate the role of X.509 certificate profile from nearby security functions and policy decisions. **Related keywords:** - **path validation**: Building and checking a certificate chain - **SAN**: Subject Alternative Name identity data - **CRL**: Certificate revocation list data **Options:** - A: proving that a service is authorized for every business action is not the central purpose of RFC 5280. It can be nearby work, but it is not the decision this RFC primarily supports. - B: reviewing certificate contents, certification paths, revocation data, and Internet name forms is the reason this RFC belongs in the review path. It drives checks on inputs, validation, and boundaries. - C: replacing the TLS handshake with a standalone certificate parser is outside the RFC boundary. Higher-layer policy and adjacent protocol responsibilities still need separate text.

**Judgment point:** X.509 certificate profile is a building block. Acceptance conditions, authorization, and deployment exceptions must still be explicit. **Related keywords:** - **path validation**: Building and checking a certificate chain - **SAN**: Subject Alternative Name identity data - **CRL**: Certificate revocation list data **Options:** - A: which trust anchors, names, EKUs, and revocation freshness are acceptable for this application is not decided by the RFC alone. The relying application must say what success means. - B: Skipping local acceptance policy can accept a valid object in the wrong context. That crosses the RFC boundary. - C: verify chain building, trust anchor, validity time, name constraints, key usage, and revocation inputs as required by the relying context is a boundary the implementation review must preserve. Source and scope mistakes cause false acceptance. - D: An RFC citation can be necessary, but deployment configuration, keys, trust, and failure handling are not automatic.

**Judgment point:** A profile is the contract that makes use of X.509 certificate profile consistent across implementations. **Related keywords:** - **path validation**: Building and checking a certificate chain - **SAN**: Subject Alternative Name identity data - **CRL**: Certificate revocation list data **Options:** - A: If input bytes and context are free-form, implementations verify different values. - B: Human-readable text is useful for explanation, but it is unstable as a validation input. Locale and wording changes break it. - C: put service identities in the correct name form and mark CA, key usage, and policy extensions consistently is required. Clear producer rules let verifiers evaluate the same object under the same assumptions.

**Judgment point:** Interoperability failures appear when the same wire data receives different processing meanings. **Related keywords:** - **path validation**: Building and checking a certificate chain - **SAN**: Subject Alternative Name identity data - **CRL**: Certificate revocation list data **Options:** - A: checking only the signature chain while ignoring name constraints, key usage, or revocation policy shifts the validation target or meaning. Implementations can then disagree about success. - B: Limiting BCP 14 words to real requirements reduces ambiguity rather than creating it. - C: Documenting unsupported-extension behavior reduces implementation divergence.

**Judgment point:** X.509 certificate profile needs validation against its defined inputs and scope, not just its delivery path. **Related keywords:** - **path validation**: Building and checking a certificate chain - **SAN**: Subject Alternative Name identity data - **CRL**: Certificate revocation list data **Options:** - A: HTTPS protects transport, but it does not replace validation of X.509 certificate profile. - B: verify chain building, trust anchor, validity time, name constraints, key usage, and revocation inputs as required by the relying context is the central step. It separates well-formed input from acceptable input. - C: A filename or path can be a routing hint, but it is not enough as identity or security proof.

**Judgment point:** A specification can define processing rules while still leaving acceptance policy outside the mechanism. **Related keywords:** - **path validation**: Building and checking a certificate chain - **SAN**: Subject Alternative Name identity data - **CRL**: Certificate revocation list data **Options:** - A: certificate fields, extensions, path validation, and CRL processing is part of the mechanism RFC 5280 addresses directly. It is not the policy layer. - B: which trust anchors, names, EKUs, and revocation freshness are acceptable for this application is an application or deployment acceptance condition. - C: Well-formed syntax and algorithm processing belong to the RFC-defined side. The meaning of success still needs policy. - D: what to do when revocation status is unavailable is local policy. It should be written for the deployment and threat model.

**Judgment point:** A security review looks for false-acceptance paths, not just whether the mechanism is present. **Related keywords:** - **path validation**: Building and checking a certificate chain - **SAN**: Subject Alternative Name identity data - **CRL**: Certificate revocation list data **Options:** - A: Performance can matter, but caching does not replace a security property. - B: A recent library helps, but local policy, inputs, and threat model still need review. - C: accepting a certificate only because it parses or chains to some unrelated trust anchor is the central failure mode. Attackers exploit this kind of context or trust shift.

**Judgment point:** Adjacent specifications are usually safer to read as layered responsibilities, not automatic replacements. **Related keywords:** - **path validation**: Building and checking a certificate chain - **SAN**: Subject Alternative Name identity data - **CRL**: Certificate revocation list data **Options:** - A: TLS uses certificates during authentication, but RFC 5280 defines the Internet certificate and CRL profile underneath preserves the responsibility split. - B: Obsoletion is explicit in RFC metadata and text. Nearby concepts do not automatically replace one another. - C: X.509 certificate profile matters in protocol composition reviews. Treating it as unrelated hides boundaries.

**Judgment point:** Review questions should show whether implementers can reproduce the same success and failure boundary. **Related keywords:** - **path validation**: Building and checking a certificate chain - **SAN**: Subject Alternative Name identity data - **CRL**: Certificate revocation list data **Options:** - A: Naming inputs, context, validation rules, and rejection behavior directly reduces implementation differences. - B: An RFC number does not define local semantics by itself. A profile or policy must fill the gap. - C: Treating unknown values as success can accept extensions or attacker input incorrectly. - D: when a service certificate, client certificate, or verifier certificate must be accepted or rejected is a real review setting. Fixing success conditions there reduces misuse.

**Judgment point:** Validation failure is a signal to stop using that input as evidence for the decision. **Related keywords:** - **path validation**: Building and checking a certificate chain - **SAN**: Subject Alternative Name identity data - **CRL**: Certificate revocation list data **Options:** - A: Downgrading to a warning creates fail-open behavior. Attacker-controlled input can enter the success path. - B: Treating the result as unusable for that decision is safe. If fallback exists, it needs explicit policy. - C: Authorization is important, but it does not automatically repair broken validation input.