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.

This page provides a form to record a new security patch in the IT Security module. Navigate to it at /it/security/patches/new.

​
Overview

The New Patch page presents a single-step form for adding a security patch record. Required fields are Patch ID and Patch Name; all other fields (severity, release date, status, affected software, description) are optional. On successful submission the user is redirected to the Patch Tracking list at /it/security/patches.

​
Who it’s for

This route is protected by IT_PERMISSIONS.VIEW (it.view) via the module-level ITViewGuard. No additional per-route permission gate exists beyond the module guard.

​
Before you start

  • Obtain the vendor-assigned patch identifier (e.g., KB5034441).
  • Know the affected software and the applicable severity level.
  • Ensure you have access to the IT Security module.

​
Steps

  1. Navigate to IT > Security > Patch Tracking and click Add Patch, or go directly to /it/security/patches/new.
  2. Enter a Patch ID (required) — the vendor-assigned identifier.
  3. Enter a Patch Name (required) — a human-readable label.
  4. Select a Severity: Critical, High, Medium (default), or Low.
  5. Set the Release Date (defaults to today).
  6. Select a Status: Active (default), Superseded, or Deprecated.
  7. Optionally enter the Affected Software and a Description.
  8. Click Create Patch. On success you are redirected to Patch Tracking.

​
Key concepts

  • Patch ID — the vendor-supplied identifier stored as patch_id (e.g., a Microsoft KB number).
  • Severity — critical | high | medium | low from the SecuritySeverity type.
  • Status — active | superseded | deprecated from the PatchStatus type.
  • Deployment tracking — once created, patch deployment per asset is tracked separately from the patch record itself.

IT Service Management

IT Service Management overview.

Governance & parity

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/patches/NewPatchPage.tsx
  • src/cores/it/hooks/useSecurityPatchMutations.ts
  • src/cores/it/types/security.ts