slug: aserto
provider: Aserto
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 3
edges:
- tag: Authorizer
  spec_file: aserto-authorizer-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.88
  evidence: POST /api/v2/authz/is  authorizer.is  Is (authorized)
  reason: Operations evaluate whether an identity is authorized against a policy context (decision tree,
    compile, query), i.e. runtime access control — Identity & Access Management.
- tag: Auth ZEN
  spec_file: aserto-auth-zen-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.85
  evidence: POST /access/v1/evaluation  Access Evaluation API; schemas v1Subject, v1Resource, v1Action
  reason: AuthZen subject/action/resource evaluation and search endpoints make real-time access-control
    decisions, which is squarely identity and access management rather than any subscription-entitlement
    or product capability.
- tag: Directory
  spec_file: aserto-directory-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.8
  evidence: POST /api/v3/directory/check/permission  Check permission; POST /api/v3/directory/object  Set
    object
  reason: A Zanzibar-style relationship directory storing objects/relations and answering permission and
    relation checks. Although it is object/relation CRUD, its purpose stated by the vendor and the check
    endpoints is access control, so IAM is the honest mapping; it is not customer or master data management.