Supply Chain Defense · Reporting
The whole supplier base on one page, and every supplier in detail
The point of reporting here is not a quarterly PDF. It is being able to answer, on any given day, three questions management actually asks: which suppliers are above the risk we accept, what is being done about it, and is it getting better.
The portfolio dashboard
Suppliers above your threshold, over time
The line that should go down.
Escalated findings by status
Open, with the supplier, resolved.
Risk distribution
Now compared with 30 days ago, and by portfolio.
High Volume Monitoring
How many long-tail suppliers are monitored, how many sit at each risk level, and a click-through to the individual companies.
Each supplier in detail
Score and categories
The supplier’s overall score and its five category scores.
Findings and suggested actions
Every finding, its severity, the evidence grouped by IP address or domain, and the recommended action.
Action plan
The summarised list of recommended actions for that supplier, with the status of each.
Analyst messages
The conversation between the analysts and the supplier about each escalated finding.
Dependencies you did not know you had
Geographic dependencies
Where your suppliers’ infrastructure actually sits, on a map, and how much of your supply chain depends on a single country or region.
Technology dependencies
Which products and services your suppliers run, so that when one product has a problem you can see how many suppliers it touches.
These views answer a question that per-supplier scores cannot: what a single failure somewhere else would take down at once.
Reports and the API
On-demand reports
For any supplier: all findings, escalated findings only, insights, or the analyst messages.
API access
To the same data, for your ticketing system, your governance, risk and compliance (GRC) tool or your SIEM.
For management
A management view needs three numbers, and the dashboard holds all three: how many critical suppliers sit above the accepted risk, how many escalated findings were resolved this period, and whether the overall distribution moved. Your Spirity contact can walk management through it in Hungarian or German.
Where you run a security program with us, the same figures feed the supplier-risk part of it.
Where this stops
The portal and the analysts’ findings are in English. What is localised is the layer around them: your Spirity contact, the walkthroughs, and the correspondence with your suppliers.
A dashboard reports; it does not decide. Whether to keep, replace or renegotiate with a supplier that stays above threshold is a business decision. The reports give you the evidence for it.
Frequently asked questions
The questions we hear most often from security and IT leaders.
Something not covered here? Ask us directly
Yes. The API exposes the data you see in the portal, for integration with ticketing systems, GRC tools and SIEMs.
No. Each supplier sees only its own findings, in its own portal.
On-demand reports per supplier show the findings, the escalations and the analyst messages, which together document what was found, what was asked of the supplier and what was done. For NIS2 supply chain obligations, that record can support your evidence; what an auditor accepts depends on your requirements and the scope of the audit.
The rest of the program
Remediation
Findings above your threshold validated by an analyst, with a recommended fix and, in the directed tier, supplier outreach.
Zero-day response
Affected suppliers identified and warned within hours of a critical disclosure.
How it works
Six stages, who does what, how long it takes to start, and where the limits are.
Ready to get started?
Partner with Spirity Enterprise to implement the right security and IT solutions for your organization.