SecVektor — Dashboard (Mock)

Dashboard example

This example view includes: risk posture summary, jurisdictional exposure map with hotspots, dependency list and drill-down, compliance coverage, predictive signals, and action shortcuts.

Risk Posture

At-a-glance supply-chain exposure, jurisdictional risk, and compliance gaps.

Source: GitHub repos + cloud inventory

Overall Risk Score

72 / 100

↑ +8 since last audit

Click a dependency on the right to see provenance, jurisdiction, governance, and mitigation guidance.

412 External Dependencies

37 Foreign-Hosted Components

3 High-Risk Jurisdictions

12 Compliance Gaps

Jurisdictional Exposure Map

Hover hotspots to preview foreign-hosted exposure and affected services.

Foreign exposure: 13%

High risk Needs review Low risk

🇺🇸 US: 68% 🇪🇺 EU: 19% ⚠️ High risk: 13%

Live Alerts & Change Feed

“What changed since last audit?” Focused events only (no CVE spam).

Now

New foreign dependency detected

aws-sdk-js → transitive mirror hosted outside US jurisdiction. Affected: Billing API.

Dependency governance drift

Maintainer inactivity exceeded 180 days for package-x. Review alternatives.

Compliance restored

NIST-aligned evidence updated for CI pipeline integrity checks (control satisfied).

Provider relocation detected

Edge CDN node changed region for cdn-lib. Validate policy rules.

Compliance Status

Operational mapping and evidence readiness (mock view).

Tip: click a dependency to see which controls it impacts and what evidence SecVektor would generate.

Predictive Risk (Next 30 Days)

Explainable signals powering risk forecasts (mock).

Confidence: 81%

High likelihood of dependency instability

Risk is driven by governance concentration, jurisdictional volatility, and dependency monoculture in core services.

Forecast: Elevated

Maintainer inactivity Release velocity drop Jurisdiction drift Transitive dependency growth Single-point dependency concentration

Action Center

Guided operations to reduce exposure (mock).

Shortcuts

Action

—