VAULT-ASSOCIATE-002 · Question #79
Vault supports which type of configuration for source limited token?
The correct answer is C. CIDR-bound tokens. Vault supports CIDR-bound tokens, allowing tokens to be restricted for use only from specified IP address ranges, enhancing security.
Question
Options
- ACloud-bound tokens
- BDomain-bound tokens
- CCIDR-bound tokens
- DCertificate-bound tokens
How the community answered
(45 responses)- A7% (3)
- B2% (1)
- C89% (40)
- D2% (1)
Why each option
Vault supports CIDR-bound tokens, allowing tokens to be restricted for use only from specified IP address ranges, enhancing security.
"Cloud-bound tokens" is not a standard Vault token binding type; Vault might integrate with cloud identity, but tokens aren't bound to generic "clouds."
"Domain-bound tokens" is not a standard Vault token binding type; while policies might restrict access based on attributes, a direct domain binding for tokens is not a feature.
Vault tokens can be configured with a `cidr_list` parameter, which restricts their usage to clients originating from specific IP CIDR blocks. This feature is known as CIDR-bound tokens, enhancing security by limiting the network locations from which a token can be used.
While Vault can issue certificates (e.g., via PKI engine) and authentication methods can use certificates, the term "certificate-bound tokens" as a direct token configuration for source limiting is not a standard feature like `cidr_list`.
Concept tested: Vault token CIDR binding
Source: https://developer.hashicorp.com/vault/docs/concepts/tokens#cidr-list
Topics
Community Discussion
No community discussion yet for this question.