Fresh
Usefulgood for triage, still validate source and assetsData Freshness
Read freshness as decision context, not as a guarantee.
Freshness labels tell you when the current site or feed snapshot was seen. They do not prove that upstream sources, local assets, scanners, or vendor pages have nothing newer.
Stale
Cautioncheck original sources before reporting or actingDegraded
Partialcounts and queues may be incompleteUnknown
Validatemissing timestamps should slow decisions downInterpretation
What freshness labels should change
Fresh data can guide the next step
Use fresh queues for triage order, owner questions, and source review. Still confirm affected version, exposure, patch path, and business impact.
Stale data needs source checks
If a source or page looks stale, open vendor, NVD, CISA, distro, or product-owner evidence before creating deadlines or public summaries.
Degraded state makes counts partial
When a feed is degraded, avoid interpreting low counts, empty cards, or missing records as absence of risk.
Cached data is orientation
Cached snapshots preserve workflow continuity, but they may not include new exploit notes, fixed versions, rejected records, or superseding guidance.
Record freshness differs from page freshness
A page can be newly rendered while one record is old. Check published, first seen, last seen, and source update dates separately.
Local freshness is separate
Saved notes, compare queues, and exported briefings reflect your browser state. They do not update automatically with asset inventory or ticket status.
Decision Rules
When freshness should block action
Block urgent claims
Do not report an empty urgent queue as low risk when Status shows degraded, stale, unavailable, or unknown source state.
Block closure
Do not close a finding from a stale scanner, stale portal record, missing vendor update, or old owner response alone.
Block leadership certainty
Use language like "current portal view shows" until source freshness and local evidence support stronger statements.
Best next move: when freshness is unclear, open Status and Source Analytics, then validate original source links before turning the view into tickets or reports.