Skip to main content

Vulnerabilities

Overview

Vulnerabilities are known weaknesses in software, infrastructure, or configuration that could be exploited if left unresolved. These records often come from scanning tools, cloud security platforms, and security integrations, and may include references like CVE IDs and severity scores.

In Openlane, vulnerability records help you keep source data, status, and remediation timelines organized in one place. They are most useful when linked to the affected asset and the remediation work needed to resolve them.

Compliance Significance

  • SOC 2: CC7 and CC8 security operations
  • ISO 27001: technical vulnerability management expectations

Practical Examples

  • A security engineer imports scanner output and tracks remediation SLA compliance by severity.
  • A compliance manager links open vulnerabilities to in-scope assets to show active governance during audit.

Examples

OperationAPI
CreatecreateBulkCSVVulnerability
UpdateupdateVulnerability
# Create
ExternalID,CveID,DisplayName,Severity,Score,Status,RemediationSLA,Source
scanner-8842,CVE-2025-12345,OpenSSL out-of-date,HIGH,8.1,OPEN,30,scanner
scanner-8843,CVE-2024-77890,Container privilege escalation,CRITICAL,9.6,OPEN,7,scanner
# Update
ID,Severity,Status,RemediationSLA,Validated
VUL01J9VULN11111111111111,MEDIUM,IN_PROGRESS,21,true
VUL01J9VULN22222222222222,LOW,CLOSED,7,true