Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

The Edit Vulnerability screen allows updating an existing vulnerability record and is accessible at /it/security/vulnerabilities/:id/edit.

​
Overview

The Edit Vulnerability page loads the existing record via useVulnerability. The form fields include: CVE ID (optional), vulnerability name, severity (default medium), discovery date, remediation status (default open), description, remediation notes, and optional remediation date. On save, updateVulnerability is called. A loading skeleton is shown while data loads and an error/not-found state is displayed when appropriate. A back-navigation button is provided.

​
Who it’s for

Requires IT_PERMISSIONS.VIEW (outer ITViewGuard). No additional per-route permission gate.

​
Before you start

  • You must hold IT_PERMISSIONS.VIEW to access this screen.
  • The vulnerability record must exist.

​
Steps

1

Open the edit form

Navigate to /it/security/vulnerabilities/:id/edit from the vulnerability detail or list page.
2

Update vulnerability details

Modify CVE ID, name, severity, discovery date, remediation status, description, and notes.
3

Record remediation

If remediation is complete, set the remediation status accordingly and enter the remediation date and notes.
4

Save changes

Submit the form to save updates and navigate back.

​
Key concepts

  • cve_id — Optional CVE identifier (e.g., CVE-2024-12345); stored as a free-text field.
  • severity — SecuritySeverity type; default medium.
  • remediation_status — RemediationStatus type; default open.
  • remediation_date — Optional date when the vulnerability was remediated.

IT Service Management

IT Service Management overview.

Governance & parity

Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/it.tsx
  • src/cores/it/pages/security/vulnerabilities/EditVulnerabilityPage.tsx