AM mountain monogramRISK LAB

THIRD-PARTY RISK / PUBLIC INTELLIGENCE

Know the exposure.
Document the decision.

A third-party risk workspace: tier vendors, assess them against NIST CSF, ISO 27001, and SOC 2, record risk decisions, and let public vulnerability evidence reopen the review.

Portfolio exercise. Real public vulnerability records and real framework references; fictional organization, vendor responses, ownership, and business context. This is not a rating of these vendors or evidence of a breach. Use sample notes only.

Loading the published feed snapshot…

01 / PORTFOLIO VIEW

Where third-party risk stands.

Vendors by tier and lifecycle stage, and residual risk across the register.

Residual risk heat map

Lifecycle pipeline

    Reassessment triggers

      02 / VENDOR LIFECYCLE

      Vendor watchlist

      Open a vendor to tier it, work through the questionnaire, SOC 2 review, and contract checklist, and track its stage. Northwind and Harbor are fully fictional and include a ready-made sample.

      03 / MONITOR PUBLIC SIGNALS

      High-impact threats. Clear consequences.

      Public vulnerability candidates and analyst review status
      Finding / potential impactPublic signalsApplicability / priorityOwner / target

      High / Critical focus: CISA KEV entries with CVSS ≥ 7.0, drawn from up to two recent entries per product. Product-name matching suggests candidates; it does not verify affected versions. No results does not mean no risk.

      04 / RISK REGISTER

      Decide, own, and document.

      Risks are scored likelihood × impact (1–25) before controls (inherent) and after (residual). A residual score of 10 or more is above appetite and needs an executive risk owner to accept it; accepting a Critical risk (20 or more) expires after six months.

      Third-party risk register
      RiskInherentResidualTreatment / statusOwner / targetFlag

      Optional, unencrypted browser storage. Use fictional notes only. Saves profiles and review history, not feed snapshots. No account, cross-device sync, or tamper-proof audit log.

      Saving is off.

      05 / EVIDENCE & LIMITATIONS

      Keep the reasoning visible.

      This view includes known-exploited vulnerabilities rated High or Critical (CVSS ≥ 7.0). Lower scores and missing severity are excluded from the queue and report, but counted above. This filter does not make excluded vulnerabilities safe. Potential business consequences are illustrative and depend on deployment context.

      Third-party risk method. Vendors are tiered on data sensitivity, system access, business criticality, and replaceability; regulated data or a critical function forces Tier 1. Tier sets assessment depth and reassessment cadence (12, 24, or 36 months). Questions are mapped to NIST CSF 2.0 (GV.SC and related), ISO/IEC 27001:2022 Annex A, and SOC 2 criteria. Mappings help orientation and are not a compliance determination. Control coverage reflects the answers entered in this exercise; it is not a vendor rating.

      All candidates start as Potentially affected. An analyst must check versions, configuration, exposure, and vendor advisories before confirming applicability.

      Confirmed affected KEV findings become Urgent. A low EPSS score does not override known exploitation. Accepting risk retains its priority and requires a justification, reviewer, and review date.

      CVSS describes technical severity. EPSS estimates exploitation in the wild within 30 days, not an organization's breach probability. Vulnerability counts do not constitute a vendor risk score.

      Business context is fictional. Due diligence starts unreviewed; controls cannot be inferred from public CVEs. Deadline dates are analyst-entered, not regulatory mandates.

      Enable optional browser saving to retain reviews and profiles after reload. Otherwise, edits stay in this tab only. Export an assessment for a separate copy. Feed refresh preserves reviews for matching CVEs; no continuous background monitoring is enabled.

      Feed provenance

      The initial view uses a published snapshot. Refresh requests public feeds from your browser and can take 1–3 minutes. Blocked or unavailable enrichment stays unknown. A failed CISA refresh preserves the prior snapshot. Data older than seven days is flagged for refresh.

      CISA KEV data ↗ · NVD API ↗ · FIRST EPSS ↗
      PUBLIC EVIDENCE / ANALYST REVIEW

      Review this finding

      Review history

        FICTIONAL ORGANIZATION / VENDOR PROFILE

        Entering a version does not automatically verify CVE applicability.

        Quick screening

        A first-pass screen. The tiered questionnaire, SOC 2 review, and contract checklist are in the TPRM assessment.

        THIRD-PARTY RISK MANAGEMENT / FICTIONAL EXERCISE

        RISK REGISTER ENTRY