Tier: classify the whole register by your exposure.
Every vendor is scored on six access vectors from your side of the relationship, then placed in Tier 0 to 3.
Every vendor classified by your exposure, not their scan grade.
Pricing published at launch. No qualification quiz.
| Vendor | Rating | Data | Network | Facilities | IP | People | Supply | Exposure | Tier | Assessment |
|---|---|---|---|---|---|---|---|---|---|---|
| Example Payroll Ltd | Data: yes | Network: no | Facilities: no | IP: no | People: yes | Supply: no | Data, People | Tier 0, critical | Full depth, all modules | |
| Example Software Studio | Data: no | Network: yes | Facilities: no | IP: yes | People: no | Supply: no | Network, IP | Tier 0, critical | Full depth, all modules | |
| Example Logistics | Data: no | Network: no | Facilities: yes | IP: no | People: no | Supply: yes | Facilities, Supply | Tier 1, high | Standard, plus triggered modules | |
| Example Analytics Cloud | Data: yes | Network: no | Facilities: no | IP: no | People: no | Supply: no | Data | Tier 1, high | Standard, plus triggered modules | |
| Example Facilities Services | Data: no | Network: no | Facilities: yes | IP: no | People: yes | Supply: no | Facilities, People | Tier 2, medium | Light, annual review | |
| Example Print Co. | Data: no | Network: no | Facilities: no | IP: no | People: no | Supply: no | No exposure | Tier 3, low | Signed attestation |
Example Software Studio rates A from the internet. It also holds your source code and a standing connection into your production systems, so Polestead puts it in Tier 0.
Six access vectors decide the tier, and the tier decides how deep the assessment goes. External signals are evidence, never the verdict.
It’s in the data you shared, the network paths you opened and the people you let inside. That holds for a bank and its core-banking host, a hospital and its records system, a manufacturer and its design partner. Only your side of the relationship knows, so that’s where Polestead starts.
Seven stages that usually live in seven tools. In Polestead each one reads the same vendor record.
Every vendor is scored on six access vectors from your side of the relationship, then placed in Tier 0 to 3.
Critical vendors get full depth. Low-risk vendors sign an attestation. Nobody answers questions that do not apply to them.
Full questionnaire, evidence review, penetration-test summaries, financials.
A signed attestation.
Approve, approve with conditions or reject, with the reviewer, the reason and the time logged for your auditors.
Breach news and external signals are matched to vendors and weighed by what that vendor can reach. An analyst confirms before anything is raised.
When a vendor incident reaches you, CIIC lines up every framework that binds you and drafts each notice next to its deadline.
The vendor risk register, NIS2 supply-chain evidence and board reporting come from the same record, not a spreadsheet.
Publish your security posture with NDA gates, a subprocessor list and a reusable answer library, on every plan.
Most organisations review a fraction of their suppliers. What a vendor can reach has little to do with what it costs you.
You pay for each vendor you assess, so you pick twelve. The other 68 stay unknown.
1 of 6critical vendors found. Five sit among the 68 nobody looked at.
AssessedNever looked atCritical, never looked at
Licensed for the whole register, so every vendor gets a tier. The depth of each assessment follows it.
6 of 6critical vendors found, each assessed at full depth however small the contract.
6 Tier 0, full depth12 Tier 1, standard20 Tier 2, light42 Tier 3, attestation
of large UK businesses formally review the risks posed by their immediate suppliers. 24% review their wider supply chain.
UK Government, Cyber Security Breaches Survey 2025/2026of third parties are assessed, on average, by organisations that hold 2,643 of them.
Ponemon Institute for ProcessUnity, 2026. Sponsored survey of 1,465 practitionersthe share of breaches with a third party involved, one year to the next. The count includes flaws in vendor software.
Verizon, Data Breach Investigations Report 2026The 2013 Target breach began with credentials stolen from a small heating contractor that had network access for billing.
US Senate Commerce Committee staff report, 2014In 2025 attackers used access tokens stolen from a sales chat add-on to reach its customers’ Salesforce data.
FBI alert, 12 September 2025Nobody publishes breach figures by the size of the vendor’s contract, and a large share of third-party incidents run through big, widely used providers. Both point the same way: classify by what a vendor can reach, not by what it costs.
Risk review should be a culture, not a procurement decision.
Polestead is licensed so classifying the entire register is simply what the platform does, and a misclassified vendor can’t quietly become next quarter’s incident.
CIIC already knows which regulators bind you. On an incident it hands you the plan, the clock schedule and every regulator-ready report at once.
| Framework | Clock | What is due | Then |
|---|---|---|---|
| DORA | 4h | Initial notice, from classifying the incident as major. 24h from first awareness at the latest | Intermediate report within 72h, final within one month |
| NIS2 | 24h | Early warning, from becoming aware of a significant incident | 72h incident notification, final report within one month |
| GDPR | 72h | Personal-data breach notification, from becoming aware | To the supervisory authority |
Licensable standalone. DORA and GDPR apply directly; NIS2 is set out in each national law. Deadlines checked against the legal texts in November 2026. Informational, not legal advice.
See how CIIC keeps the clocksYour trust center is built to be found. Your risk data is built to stay yours.
Public, always SaaS
Your security story, reachable by every prospect, customer and auditor, with nothing held back for a paid tier.
Private, inside your walls
Your register, assessments and incidents, deployed on your ground and inspectable by your auditors.
Can’t host it yourself?
The same platform as managed single-tenant SaaS, EU-resident. When you’re ready to bring it inside, it moves with you.
Bring a vendor-master export. Leave with your exposure mapped.
Book a demoPricing published at launch. No qualification quiz.
Ratings platforms score vendors from external scans, and context adjusts the score. In Polestead your classification is the architecture: vendors are tiered by your exposure, and the tier decides how deep the assessment goes. External signals are evidence, never the verdict.
Polestead is built around one record per vendor. Each risk domain on that record carries its own tier, cutoff and review cadence, and no domain is averaged into another, so a strong result in one area never hides a weak one. Cyber is where most teams start.
Per-vendor licensing prices each slot so high that teams ration coverage to a shortlist. Polestead is licensed so classifying the entire register is the default. You never have to justify covering a vendor.
Yes. The register, assessments, incidents and the platform itself deploy on-premises, air-gapped, or in single-tenant EU cloud. For teams that cannot host, a managed single-tenant SaaS runs the same platform. The trust center is always SaaS, because it exists to be reachable.
No, structurally. Inference runs on your own keys, with your spend caps and the model you choose. A zero-AI configuration is supported too; vendor-name resolution then falls back to deterministic matching, at lower accuracy.
No. CIIC, the Critical Incident Intelligence Center, is an operational control plane. Its regulatory dataset is checked against primary statutory sources and carries last-verified dates; national transposition should always be confirmed with counsel.