Most security dashboards share a common problem: they show you data without telling you what to do about it. You log in, see a wall of numbers, and spend the next thirty minutes figuring out which number matters. The Safeguard.sh portal was designed to break that pattern.
This is a detailed walkthrough of every major section of the portal, what each metric actually means, and how security teams are using these views in practice.
The Overview Dashboard
When you first log in, the overview dashboard presents four primary panels. The top row shows your organization's risk posture at a glance: total active vulnerabilities, SBOM coverage percentage, policy gate pass rate, and mean time to remediation.
These are not vanity metrics. Each one links to a filtered view where you can drill into the underlying data. Click on the vulnerability count and you land on a pre-filtered list sorted by severity and exploitability. Click on the SBOM coverage percentage and you see exactly which projects are missing SBOMs and why.
The risk trend graph sits below the summary cards. It tracks your aggregate risk score over time, plotted against key events like new vulnerability disclosures, dependency updates, and policy changes. This is where you spot patterns. If your risk score spikes every Tuesday, that probably correlates with a specific team's release cycle.
The activity feed occupies the right column. It shows recent actions taken across your organization: SBOMs generated, vulnerabilities triaged, policy gates triggered, and auto-fix PRs merged. This feed is filterable by team, project, and action type.
Project Explorer
The project explorer is where most day-to-day work happens. Every project your organization tracks appears here with its current security status. The default view shows a card grid, but the table view is more practical for organizations managing hundreds of projects.
Each project card displays:
- Risk score (0-100, calculated from vulnerability severity, exploitability, and exposure)
- Dependency count with a breakdown of direct versus transitive
- Last SBOM generation timestamp
- Policy compliance status (pass, fail, or warning)
- Open vulnerability count by severity
Clicking into a project opens the project detail view, which is organized into tabs: Overview, Dependencies, Vulnerabilities, SBOM, and Policy.
Dependencies Tab
The dependencies tab shows your full dependency tree. This is not just a flat list. Safeguard resolves the complete transitive dependency graph and visualizes it as an interactive tree. You can expand any node to see what it pulls in, and hover over any package to see its version, license, known vulnerabilities, and maintenance status.
The "ghost dependencies" indicator flags packages that appear in your lock file but are not declared anywhere in your manifest files. These are often leftovers from removed features and represent unnecessary attack surface.
Vulnerabilities Tab
Vulnerabilities are displayed with contextual information that most scanners omit. For each CVE, you see:
- Severity (CVSS score and qualitative rating)
- Exploitability (whether a known exploit exists in the wild)
- Reachability (whether your code actually calls the vulnerable function)
- Fix availability (whether a patched version exists)
- Remediation path (the specific version upgrade that resolves the issue)
The reachability analysis is particularly valuable. A critical vulnerability in a transitive dependency that your code never calls is a different risk than a critical vulnerability in a function you invoke on every request. Safeguard differentiates these cases so you can prioritize effectively.
SBOM Tab
The SBOM tab displays your most recent Software Bill of Materials in a readable format. You can switch between CycloneDX and SPDX views, export in either format, and compare the current SBOM against any previous version to see what changed.
The SBOM diff view highlights added packages, removed packages, and version changes. This is useful during audits and when investigating whether a specific supply chain event affected your software.
Policy Gates
Policy gates are one of the more powerful features in the portal. You define rules, and Safeguard enforces them automatically in your CI/CD pipeline. The policy editor supports conditions based on:
- Vulnerability severity thresholds
- License compliance requirements
- Dependency age and maintenance status
- SBOM completeness requirements
- Known malware package blocklists
Policies can be set to "enforce" (block the pipeline) or "warn" (flag but allow). Most organizations start with warn mode across the board and progressively move to enforcement as their teams adjust their workflows.
The policy history view shows every gate evaluation, including what triggered a pass or fail. This audit trail is critical for compliance reporting and for debugging why a specific build was blocked.
Team Management
The team management section lets you organize projects by team and assign different access levels. The role model is straightforward: Admin, Manager, and Viewer. Admins configure policies and integrations. Managers triage vulnerabilities and manage team settings. Viewers see dashboards and reports but cannot modify configurations.
Each team gets its own dashboard that aggregates metrics across their projects. This is useful for engineering managers who need to track their team's security posture without wading through organization-wide data.
Integrations Panel
The integrations panel shows all connected systems: source control platforms (GitHub, GitLab, Bitbucket), CI/CD tools (Jenkins, GitHub Actions, GitLab CI), container registries, and notification channels (Slack, Teams, email).
Each integration has a health indicator showing whether the connection is active and when it last synced. If an integration breaks, the portal surfaces the error with troubleshooting guidance rather than silently failing.
Reporting
The reporting section generates compliance-ready documents. Pre-built templates cover common frameworks: SOC 2, ISO 27001, NIST SSDF, and PCI DSS. Each report pulls live data from your projects and formats it according to the framework's requirements.
Custom reports let you define your own metrics, time ranges, and groupings. These can be scheduled for automatic generation and delivery via email, which is useful for executive stakeholders who want a weekly or monthly summary without logging into the portal.
Keyboard Shortcuts and Power User Features
The portal includes keyboard shortcuts for common actions. Press ? on any page to see available shortcuts. The global search (/) lets you find projects, vulnerabilities, and policies by name or CVE ID. The command palette (Ctrl+K) provides quick access to any action from anywhere in the portal.
Bulk operations are available on list views. Select multiple vulnerabilities, right-click, and you can triage them all at once, mark them as accepted risk, assign them to a team member, or create Jira tickets in batch.
API Access
Everything you see in the portal is available through the REST API. The API documentation is accessible from the portal's settings page and includes interactive examples. Teams that integrate Safeguard into custom workflows typically use the API for automated reporting, custom dashboards, and integration with internal tools that the portal does not natively support.
How Safeguard.sh Helps
The Safeguard.sh portal is designed around a simple principle: security data should drive action, not just awareness. Every metric links to a workflow. Every vulnerability includes a remediation path. Every policy gate explains why it fired and what to do about it. Instead of dumping data on your screen and hoping you figure it out, the portal guides you from detection to resolution with the context you need to make informed decisions. If your current security tooling leaves you staring at dashboards wondering what to do next, the portal is worth a serious look.