Infrastead / Docs / Guides
Run the guided preview
From a vendor advisory to an executive-ready report in one sitting. This guide walks the exact six steps of the preview — what you do, and what you get at each one.
What you need
- An invite code — the preview is controlled — request access from the signup page if you do not have one
- A work email you can verify — confirmation is required before the workspace is provisioned
- Optional: your inventory CSV — or skip it — both data steps offer one-click sample data
Sign up, confirm, accept — then the run begins
- Create your account with your work email and invite code.
- Open the confirmation email and verify your address — your tenant-scoped workspace is provisioned on confirmation.
- Accept the limited-preview conditions (decision support, no automatic infrastructure changes, validate before operational action). You land on step 1 of the guided run.
Define advisory
What you do · Paste a vendor advisory URL and let Infrastead extract the structured fields, enter one manually, or click “Use the demo advisory” to load CVE-2024-3400 (PAN-OS GlobalProtect, CISA KEV).
What you get · A normalized advisory: products, version conditions, required features — something the engine can compute against.
$ advisory import CVE-2024-3400 --vendor palo-alto ✓ normalized
illustrative output · sample data
Good to know — Manual entry requires at least one affected OS or product — an advisory that would match every device of a vendor is almost never what you mean.
Scope infrastructure
What you do · Upload your inventory CSV (drag & drop; you review a diff before anything is written), or click “Load the sample estate” for 16 labeled mixed-vendor devices.
What you get · A deduplicated, workspace-scoped device set — the estate the analysis will evaluate.
$ inventory load estate.csv ✓ 16 devices · 7 vendors · 0 duplicates
illustrative output · sample data
Good to know — Required columns: hostname, vendor, model. Include os_version and os for the most precise verdicts — a blank version honestly becomes requires_validation, never a guess. Grab the CSV template or export straight from Zabbix with the open-source exporter. Preview workspaces support up to 500 devices.
Run the applicability analysis
What you do · Pick the advisory and run it. A deterministic engine crosses vendor, product, OS, version conditions, and required features against every device — no AI in the verdict.
What you get · Every device classified: affected, not affected, or requires validation, each with the reason spelled out.
$ analyze → 2 affected · 1 requires_validation · 13 not_affected
illustrative output · sample data
Good to know — requires_validation is not an error — it means the inventory data could not settle the question (missing version, unknown feature state). The next step exists to resolve exactly those devices.
Attach evidence
What you do · Record per-device facts for the devices that matter: confirmed version, workaround state, feature configuration. Clean devices never demand busywork evidence.
What you get · A versioned evidence trail — every later claim traces back to a recorded fact.
$ evidence pa-edge-fw-01 --workaround applied --hmac enabled ✓ saved
illustrative output · sample data
Validate mitigation integrity
What you do · Run the integrity check. A deterministic, versioned classifier reads the saved evidence and asks the harder question: does the mitigation actually hold?
What you get · A verdict per device: mitigated, patched, partially mitigated, requires validation, or unresolved exposure.
$ integrity run → 1 mitigated · 1 unresolved_exposure
illustrative output · sample data
Good to know — Some advisories have no supported integrity check yet. When that happens the preview says so — evidence and integrity become “not applicable”, not silently skipped, and the report stays available.
Generate the executive report
What you do · One click. The same records that produced the verdicts become the brief: scope, affected infrastructure, evidence status, integrity verdicts, unresolved actions.
What you get · An executive-ready report — plus the elapsed advisory-to-report time for your own benchmark.
$ report generate ✓ REPORT-2026-Q3-0042 ready
illustrative output · sample data
The states, and what they demand
The advisory conditions match this device. It needs attention.
Inventory data could not settle it — confirm the missing fact, never assume.
Confidently ruled out, with the reason recorded. No evidence demanded.
applicability — step 3
Workaround applied and verified against evidence.
Fixed version confirmed on-device.
Risk reduced but conditions remain (mixed HA versions, partial rollout).
Evidence insufficient to conclude either way.
The mitigation does not hold. Act on this row first.
mitigation integrity — step 5
Frequently asked
Do I need production data to try it?
Does Infrastead connect to my infrastructure?
What exactly does “requires validation” mean?
What are the preview limits?
Is the analysis AI-generated?
Ready? The clock starts at the advisory.
One advisory, an inventory, real analysis, evidence, an integrity verdict, and a report leadership can sign — in one sitting.
access · invite-gated · verified work email required