K-Shield API Reference
K-Shield exposes REST APIs for security scanning, SCAP compliance, threat intelligence, audit-stream, nmap/rkhunter monitoring, VM eligibility and scanning, remediation, and administration.
Raw OpenAPI spec
The K-Shield OpenAPI (Swagger 2.0) spec is served alongside the karios-core spec for use by IaC tools, SDK generators, and AI assistants:
karios-security-service.yaml (146 operations across 140 paths)
karios-core.yaml (734 operations across 686 paths)
Base URL and authentication
All K-Shield endpoints require a Bearer token:
curl -H "Authorization: Bearer $KARIOS_TOKEN" \
https://<your-karios-cluster>/api/v1/security/health
Endpoint groups
K-Shield endpoints are organised primarily under two top-level URL prefixes:
/api/v1/security/*- security scanning + monitoring + compliance/api/v1/system/*- system information + inventory
A small number of root-level utility endpoints (/metrics,
/security/health, /api/v1/users) exist for operational purposes and
sit outside those two prefixes.
Common categories:
URL prefix |
Coverage |
|---|---|
|
Datacenter-wide aggregation (compliance trend, risk distribution, score histogram, top vulnerabilities, node status, nmap and rkhunter summaries) |
|
Nmap scan history, port details, risk timelines (per-node and flat) |
|
Rkhunter scan execution, results, historical reports |
|
Audit stream configuration, activity, metrics, raw lines, status |
|
Threat intelligence inventory, sources, precheck, refresh |
|
SCAP compliance results (Day-0 and ongoing) |
|
VM security scans (single and multi-VM), scheduling, cancellation |
|
Multi-VM scan orchestration, history, scheduling |
|
Node-level scan execution, cancellation, active-scan tracking |
|
Vulnerability and internal finding remediation triggers |
|
Resource policy read + update ( |
|
Custom SCAP profile upload and management |
|
System info, findings, stats, recent scans, summary |
Programmatic consumption
For IaC tools (OpenAPI Generator, kiota, autorest, Terraform provider generators) fetch the raw YAML directly:
curl -O https://docs.karios.com/_static/api-specs/karios-security-service.yaml
Note on schemas
Path and method information for every endpoint is verified from the live
router registrations in karios-security-service main. Full request and
response schemas are being progressively added via swaggo annotations in
the source; a rolling docs refresh will pick those up.