Assets

Isolation playbook

Catalog entries with no vendor fix to apply: CISA's required action is to stop using the product or take it off the network. Each is shown with CISA's own words and one status per affected organization.

CISA catalog …Updated …Deadlines last recomputed …

Not an official CISA service. BOD 26-04 binds US federal civilian agencies; for everyone else its timelines are a benchmark. A match means an asset may be affected: check CISA's catalog and the vendor's advisory before you act.

When there is no fix

  1. Confirm it. The catalog names products, not versions: check the entry's links for the versions and models it covers.
  2. Discontinue where you can: take the product out of service and replace it. An end-of-life product gets no further fixes.
  3. Isolate what has to stay for now: remove its exposure to the internet, restrict it to the systems that need it (a separate segment, an allow list or an access gateway), and watch it.
  4. Record the decision below, per organization, and come back to anything still isolated.

These steps are general practice, not CISA's text. CISA's required action for each entry is quoted with it. Listed here: entries whose required action is to stop using, disconnect or remove the product, and entries you marked on the dashboard as having no fix for you.

Your organizations

One press sets an organization's status. These entries count for an asset whenever they were added.

Loading…

Every entry with no vendor fix

Loading…

DashboardOrganizations and assetsWork listIsolation playbookDecision treeHow deadlines are worked outC4.vet patch and security trackers