polestead

The riskiest vendor is the one that slips through.

Every vendor classified by your exposure, not their scan grade.

Pricing published at launch. No qualification quiz.

A vendor register, classified by your exposure

Vendor registerExample Holdings exposure on this vectornone
VendorRatingDataNetworkFacilitiesIPPeopleSupplyExposureTierAssessment
Example Payroll LtdBData: yesNetwork: noFacilities: noIP: noPeople: yesSupply: noData, PeopleTier 0, criticalFull depth, all modules
Example Software StudioAData: noNetwork: yesFacilities: noIP: yesPeople: noSupply: noNetwork, IPTier 0, criticalFull depth, all modules
Example LogisticsCData: noNetwork: noFacilities: yesIP: noPeople: noSupply: yesFacilities, SupplyTier 1, highStandard, plus triggered modules
Example Analytics CloudAData: yesNetwork: noFacilities: noIP: noPeople: noSupply: noDataTier 1, highStandard, plus triggered modules
Example Facilities ServicesBData: noNetwork: noFacilities: yesIP: noPeople: yesSupply: noFacilities, PeopleTier 2, mediumLight, annual review
Example Print Co.AData: noNetwork: noFacilities: noIP: noPeople: noSupply: noNo exposureTier 3, lowSigned 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.

Scanners grade what a vendor shows the internet. Your exposure isn’t on the internet.

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.

Everyone else
Context adjusts the score.
Polestead
Your classification is the architecture.
Data
What of your data they hold, process or can reach
Network
Standing connections into your environment
Facilities
Physical access to your sites and offices
IP
Source code, designs and trade secrets in outside hands
People
Embedded personnel inside your teams
Supply
Products and services your own cannot run without

Every stage of third-party risk, on one record.

Seven stages that usually live in seven tools. In Polestead each one reads the same vendor record.

  1. TierClassify the whole register by your exposure.
  2. AskQuestionnaires sized to the tier.
  3. DecideDecisions with a record behind them.
  4. WatchSignals, read against your exposure.
  5. TellIncident notices against the clock.
  6. ProveEvidence your regulator asks for.
  7. ShareYour own trust center, free.

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.

ClassificationExample Holdings
Example Payroll LtdTier 0, critical
Example LogisticsTier 1, high
Example Print Co.Tier 3, low

Ask: questionnaires sized to the tier.

Critical vendors get full depth. Low-risk vendors sign an attestation. Nobody answers questions that do not apply to them.

Assessment scopeSet by tier
Example Payroll LtdTier 0, critical

Full questionnaire, evidence review, penetration-test summaries, financials.

Example Print Co.Tier 3, low

A signed attestation.

Decide: decisions with a record behind them.

Approve, approve with conditions or reject, with the reviewer, the reason and the time logged for your auditors.

Decision recordExample Logistics
Decision
Approved with conditions
Condition
Business-continuity test results within 90 days
Reviewed by
Example reviewer, Procurement
Logged
14 Mar 2026, 10:42

Watch: signals, read against your exposure.

Breach news and external signals are matched to vendors and weighed by what that vendor can reach. An analyst confirms before anything is raised.

SignalWaiting for review
Source
Breach report, linked
Names
Example Payroll Ltd
Your exposure
Data, People Tier 0, critical
Next
Analyst review

Tell: incident notices against the clock.

When a vendor incident reaches you, CIIC lines up every framework that binds you and drafts each notice next to its deadline.

IncidentExample Payroll Ltd
DORA initial notice
after major-incident classification
3h 41m
Frameworks
DORA and GDPR
Reports
Drafted, one per framework

Prove: evidence your regulator asks for.

The vendor risk register, NIS2 supply-chain evidence and board reporting come from the same record, not a spreadsheet.

Board packFirst quarter 2026
Vendor risk registerXLSX
Supply-chain evidence (NIS2)PDF
Tier coverage across the registerPDF

Share: your own trust center, free.

Publish your security posture with NDA gates, a subprocessor list and a reusable answer library, on every plan.

trust.example.comPublic
SOC 2 reportUnder NDA
Subprocessor listPublic
Answer libraryOn request

Risk doesn’t respect the shortlist.

Most organisations review a fraction of their suppliers. What a vendor can reach has little to do with what it costs you.

Priced per vendor

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

Polestead

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

The same sample register of 80 vendors in both pictures, largest contract first. An illustration, not customer data.

What the published numbers say

Nobody 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.

When it goes wrong, the clocks are already running.

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.

FrameworkClockWhat is dueThen
DORA4hInitial notice, from classifying the incident as major. 24h from first awareness at the latestIntermediate report within 72h, final within one month
NIS224hEarly warning, from becoming aware of a significant incident72h incident notification, final report within one month
GDPR72hPersonal-data breach notification, from becoming awareTo 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 clocks

Public where it helps you. Private where it protects you.

Your trust center is built to be found. Your risk data is built to stay yours.

Public, always SaaS

Your trust center, free at full depth

Your security story, reachable by every prospect, customer and auditor, with nothing held back for a paid tier.

  • NDA gates
  • Subprocessor lists
  • Your own domain

Private, inside your walls

Your risk data stays yours

Your register, assessments and incidents, deployed on your ground and inspectable by your auditors.

  • On-premises
  • Air-gapped
  • Single-tenant EU cloud

Can’t host it yourself?

We run it for you

The same platform as managed single-tenant SaaS, EU-resident. When you’re ready to bring it inside, it moves with you.

  • Nothing to re-buy
  • Nothing to migrate away from

Your keys, your models, or no AI at all.

Bring your own keys
Any provider, any model, under your spend caps and your billing.
Nothing to train on
Inference never touches our infrastructure, so your data cannot train our models.
Zero-AI mode
A supported configuration. Name matching becomes deterministic, at lower accuracy.

See your register classified.

Bring a vendor-master export. Leave with your exposure mapped.

Book a demo

Pricing published at launch. No qualification quiz.

Straight answers

How is Polestead different from ratings platforms?

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.

Is Polestead only for cyber risk?

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.

How is your licensing different from per-vendor pricing?

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.

Can Polestead run fully air-gapped?

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.

Does customer data train your AI models?

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.

Is CIIC legal advice?

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.