feat(spec): Specify Agent Authorization Verifiable Credential profile#149
Merged
feat(spec): Specify Agent Authorization Verifiable Credential profile#149
Conversation
… (Section 5.4.2) Define the Agent Authorization VC Profile (AAVC) for interoperable cross-domain agent authorization: Required Claims: - id: Globally unique agent identifier (dereferenceable URI) - agentType: Classification (tool, orchestrator, workflow, system, ephemeral) - authorizedScopes: Array of permitted authorization scopes - issuerDomain: Administrative domain for trust policy application Recommended Claims: - agentName, agentVersion, tenantId - dataSensitivityClearance (public → regulated) - complianceAttestations (ISO-27001, SOC2, GDPR, etc.) - operationalConstraints (rate limits, time windows, geofence) - trustSignals (scores, risk indicators, audit timestamps) Optional Claims: - modelInfo: AI model details and approved/prohibited use cases - delegation: Delegation permissions (per Section 5.4.1) - provenance: SLSA build provenance and deployment info - policyBindings: References to governing policies Extension Mechanism: - JSON-LD context-based extensions for organization-specific claims - Graceful handling of unrecognized claims Includes complete example VC for XDR Triage Assistant and interoperability requirements matrix (MUST/SHOULD/MAY). Section 5.4.2 of the DCR v1 Draft proposal. Signed-off-by: Nik Kale <nikkal@cisco.com>
nikkal12
requested review from
beryder,
copasseron,
hmuyal,
jadiaconu,
mayannuz,
mkedjour and
rafaelsilva29
as code owners
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
jadiaconu
approved these changes
Jan 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This contribution specifies the Agent Authorization Verifiable Credential Profile
(AAVC) - Section 5.4.2 - providing a standardized credential schema for interoperable
cross-domain agent authorization.
The profile enables Authorization Servers across different administrative domains to
make informed, consistent authorization decisions while preserving organizational
flexibility through a structured extension mechanism.
Required Claims (MUST)
Core identity and authorization claims for interoperability:
Recommended Claims (SHOULD)
Production deployment guidance for security and compliance:
Optional Claims (MAY)
Extended capabilities for specific use cases:
Extension Mechanism
JSON-LD context-based extensions allow organizations to add domain-specific claims
while maintaining baseline interoperability. Implementations gracefully handle
unrecognized claims following the robustness principle.
Complete Reference Implementation
Includes a fully-specified example credential for an XDR Triage Assistant workflow
agent, demonstrating practical application of all claim categories.
Interoperability Requirements
Defines normative conformance matrix (MUST/SHOULD/MAY) for:
This profile enables the vision of cross-organizational agent ecosystems with
verifiable, privacy-preserving, and policy-compliant authorization.
Related: Part of the DCR v1 Draft proposal series for the AGNTCY Identity Working Group.
Builds on: Threat model (PR #146), Security considerations (PR #147), Delegation
semantics (PR #148)
References: W3C Verifiable Credentials Data Model, SD-JWT (Selective Disclosure
for JWTs), JSON-LD, SLSA Provenance
Type of Change
Checklist