Aria AI — Cybersecurity
Collection
Evidence-linked cybersecurity review demos. Analyst workstations, not automatic enforcement. • 27 items • Updated
Dataset Viewer
The dataset could not be loaded because the splits use different data file formats, which is not supported. Read more about the splits configuration. Click for more details.
Couldn't infer the same data file format for all splits. Got {NamedSplit('validation'): (None, {}), NamedSplit('test'): ('json', {})}
Error code: FileFormatMismatchBetweenSplitsError
Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
AriaKube Kubernetes manifest lab
Synthetic Kubernetes 1.29 manifests for the AriaKube configuration-review demo: a privileged shop Deployment, a Restricted lookalike, wildcard RBAC, an unrendered Helm image with missing namespace context, and a world-open NetworkPolicy plus hostPort.
Organization dataset and collection are public. Live Gradio is alirezaaminzadeh/aria-kube and the organization card is AriaAICompany/aria-kube. Runnable Space source is stored in demo/. Collection: Aria AI — Cybersecurity.
Generated data, seed 17. Namespaces, images, and ServiceAccounts are laboratory placeholders. The control catalog is pss-restricted-k8s-1.29-v1 (2026-09-20). Checkov is not executed on this dataset. A NetworkPolicy object is not proof of isolation.
Files
- data/scenarios.jsonl
- data/expected.json
- data/schema.json
- data/splits.json
- data/controls.json
- data/evaluation.json
- data/sample_preview.json
- data/stacks/ — five scenario folders of
.yamlfiles - demo/ — runnable Gradio Space source
- showcase/ — organization static card
Split
Development vs test is by scenario family: PSS exposure and RBAC vs lookalike, unknown context, and network ambiguity. Renaming one object of the same finding is not placed across the split.
License
CC-BY-4.0. Keep the synthetic-data and laboratory-manifest labels.
- Downloads last month
- 45