Spec Overview
A CRIT record is a JSON object that ties a single CVE to a single cloud resource template, with the lifecycle and remediation metadata an operator needs to act on it.
Identity fields
| Field | Required | Notes |
|---|---|---|
vectorString | yes | Canonical CVSS-style encoding of the other identity fields. Always recomputable from the structured fields; reviewers verify by round-trip. |
vuln_id | yes | Primary identifier in any namespace: CVE-2024-6387, GCVE-110-CLOUD-2022-0025, a GHSA id, or a vendor-issued id. MUST use only A-Z a-z 0-9 - _ ., because it is carried in the vector string, which has no escaping. |
scheme | no | Namespace of vuln_id. Open token (^[a-z][a-z0-9_-]*$); well-known values cve, gcve, ghsa, osv. For cve and gcve the id syntax is enforced (GCVE: GCVE-BCP-04 pattern). |
issuer | no | Authority that assigned vuln_id. For gcve, GNA-<n> matching the GNA ID in the id (e.g. GNA-110). |
aliases | no | Other ids for the same vulnerability as { "scheme", "id" } objects. JSON only, never in the vector, so ids may contain : / # etc. MUST NOT repeat vuln_id. |
provider | yes | Spec-registered cloud provider (aws, azure, gcp, …). |
service | yes | Provider-namespaced service slug (ec2, eks, kubernetes_service, …). |
resource_type | yes | instance, cluster, bucket, function, etc. |
Classification fields
| Field | Allowed values |
|---|---|
resource_lifecycle | ephemeral, stateful_managed, stateful_customer, config_only, global_control_plane |
shared_responsibility | provider_only, customer_action_required, customer_only, shared |
vex_status | affected, fixed, not_affected, under_investigation |
fix_propagation | automatic, config_change, opt_in, version_update, redeploy, rebuild_and_redeploy, destroy_recreate, rolling_replace, no_fix_available |
existing_deployments_remain_vulnerable | boolean |
Template fields
| Field | Notes |
|---|---|
template | Resource locator with {slot} placeholders. Example: arn:aws:eks:{region}:{account}:cluster/{resource-id}. |
template_format | aws_arn, azure_resource_id, gcp_resource_name, cloudflare_locator, oracle_ocid, plus per-provider extended formats. |
Temporal fields
temporal carries lifecycle dates as YYYY-MM-DD strings:
vuln_published_date(required)provider_acknowledged_dateprovider_fix_date(required whenvex_status="fixed")customer_deadline_datecustomer_deadline_sourceservice_available_date(required)
Remediation + detection
remediation_actions— ordered list of operator-actionable steps, each withtype,title,description,auto_remediable,requires_downtime,stateful_impact,compensating_control.detections— phase-tagged queries (pre_fix,misconfiguration,post_fix) that consumers run to find affected resources. Emptyqueryrequirespending_reason.
Schema
Every CRIT record validates against
crit-record-v0.3.0.schema.json.
The reference implementation embeds it; the
in-browser validator loads it client-side via fetch.