slug: sandboxaq
provider: SandboxAQ
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Electrical Components & Equipment
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: 2
edges:
- tag: assets
  spec_file: sandboxaq-assets-api-openapi.yml
  capability_id: BC-620
  capability_id_l1: BC-620
  capability_name: Cybersecurity Management
  confidence: 0.72
  evidence: GetAssetEdges  Get all cryptographic objects associated with a Asset
  reason: Asset inventory linked to cryptographic objects — the cryptographic posture management core
    of AQtive Guard. Clearly cybersecurity at L1; the crypto-inventory activity does not map cleanly onto
    any listed L2.
- tag: issues
  spec_file: sandboxaq-issues-api-openapi.yml
  capability_id: BC-620
  capability_id_l1: BC-620
  capability_name: Cybersecurity Management
  confidence: 0.72
  evidence: GetIssuesIndex  List issues; GetIssueObjectDetails  List details (instances) for an issue
    object
  reason: Security findings ('issues') and their affected objects/instances from posture scans — cybersecurity
    finding management. Plausibly Vulnerability Management but the operations do not name remediation
    or scanning, so L1 only.