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

FieldRequiredNotes
vectorStringyesCanonical CVSS-style encoding of the other identity fields. Always recomputable from the structured fields; reviewers verify by round-trip.
vuln_idyesPrimary 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.
schemenoNamespace 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).
issuernoAuthority that assigned vuln_id. For gcve, GNA-<n> matching the GNA ID in the id (e.g. GNA-110).
aliasesnoOther 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.
provideryesSpec-registered cloud provider (aws, azure, gcp, …).
serviceyesProvider-namespaced service slug (ec2, eks, kubernetes_service, …).
resource_typeyesinstance, cluster, bucket, function, etc.

Classification fields

FieldAllowed values
resource_lifecycleephemeral, stateful_managed, stateful_customer, config_only, global_control_plane
shared_responsibilityprovider_only, customer_action_required, customer_only, shared
vex_statusaffected, fixed, not_affected, under_investigation
fix_propagationautomatic, config_change, opt_in, version_update, redeploy, rebuild_and_redeploy, destroy_recreate, rolling_replace, no_fix_available
existing_deployments_remain_vulnerableboolean

Template fields

FieldNotes
templateResource locator with {slot} placeholders. Example: arn:aws:eks:{region}:{account}:cluster/{resource-id}.
template_formataws_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_date
  • provider_fix_date (required when vex_status="fixed")
  • customer_deadline_date
  • customer_deadline_source
  • service_available_date (required)

Remediation + detection

  • remediation_actions — ordered list of operator-actionable steps, each with type, 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. Empty query requires pending_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.