Adapter Specs

Per-adapter operational design, runtime profile, and control mapping

Adapter Specs

Per-adapter technical specifications. Each adapter in the canonical adapter-registry.yaml gets exactly one spec in this tree; frontmatter is regenerated from canon on every sync. Adapter specs are paired 1:1 with entries in Validation Suites.

Pages in this section

Adapters currently in canon:

Slug Adapter Canon anchor
cyberark CyberArk PAM adapter-registry.yaml#cyberark
entra-id Microsoft Entra ID adapter-registry.yaml#entra-id
infoblox Infoblox DDI adapter-registry.yaml#infoblox
intune Microsoft Intune adapter-registry.yaml#intune
m365 Microsoft 365 adapter-registry.yaml#m365
mainframe Mainframe integration adapter-registry.yaml#mainframe
palo-alto Palo Alto Networks adapter-registry.yaml#palo-alto
patch-state Patch state collector adapter-registry.yaml#patch-state
pki-ca PKI certificate authority adapter-registry.yaml#pki-ca
scuba CISA SCuBA adapter-registry.yaml#scuba
scubagear SCuBAGear assessment adapter-registry.yaml#scubagear
service-now ServiceNow ITSM adapter-registry.yaml#service-now
siem SIEM ingest adapter-registry.yaml#siem
stig-compliance DISA STIG compliance adapter-registry.yaml#stig-compliance
terraform Terraform state adapter-registry.yaml#terraform
vuln-scan Vulnerability scan ingest adapter-registry.yaml#vuln-scan
Note

This list is regenerated from src/uiao/canon/adapter-registry.yaml by src/uiao/tools/sync_canon.py. Drift between this index and the registry is CI-blocking.

Back to top