Where this collector family fits
Container and DevOps collectors connect code and platform changes with cluster activity, runtime events, and container assets. They help teams evaluate security across the path from repository activity to running workloads.
- Repository audit review
- Container asset inventory
- Kubernetes audit activity
- Cluster and runtime-event context
Supported collectors in this family
Nova currently implements 8 collectors in this family. Each entry names the source and the customer outcome it supports.
- Container Registry Assets
- Keeps Container Registry Assets current in Nova for inventory, ownership, exposure, and security-posture review.
- GitHub Assets
- Keeps GitHub Assets current in Nova for inventory, ownership, exposure, and security-posture review.
- GitHub Audit Logs
- Brings GitHub Audit Logs activity into Nova for security monitoring, investigation, and audit review.
- GitLab Assets
- Keeps GitLab Assets current in Nova for inventory, ownership, exposure, and security-posture review.
- GitLab Audit Events
- Brings GitLab Audit Events activity into Nova for security monitoring, investigation, and audit review.
- Kubernetes Audit Logs
- Brings Kubernetes Audit Logs activity into Nova for security monitoring, investigation, and audit review.
- Kubernetes Cluster Assets
- Keeps Kubernetes Cluster Assets current in Nova for inventory, ownership, exposure, and security-posture review.
- Kubernetes Runtime Events
- Brings Kubernetes Runtime Events activity into Nova for security monitoring, investigation, and audit review.
How the evidence supports customer work
Nova keeps collected data linked to its source as it is used for asset inventory, cloud security, detection, investigation or Threat Hunting. Collecting data does not by itself prove a threat or authorize a response action.
Source coverage is not assumed to be complete. Nova keeps collection health, freshness, gaps, and partial results visible so teams can judge whether the evidence is suitable for the decision at hand.
Questions to answer during evaluation
- Which named sources are required for the use case, and which are optional context?
- What history, accounts, subscriptions, organizations, projects, or devices are available to the source product?
- What delay, volume, and missing-data conditions are acceptable for the intended decision?
- Which customer team owns source access, data interpretation, and ongoing health review?