Techbanq

Cybersecurity · vendor risk

Every vendor with access is part of your attack surface

The payroll processor holds your employees' data, the maintenance contractor holds a VPN account, the SaaS tool holds your customer list — and a breach at any of them is a breach of you. A third-party risk programme makes that exposure visible, tiers it by what each vendor could actually damage, and applies scrutiny where it is owed rather than evenly and thinly everywhere.

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

Tiering

Vendors are tiered by what you give them, not by contract value

Procurement instinctively ranks vendors by spend, but the stationery supplier on a large contract can do you less harm than a small SaaS tool holding your customer data. Tiering by exposure puts the scrutiny where the damage potential is.

Critical — they can become your incident

Sensitive or personal data at scale, privileged or network access into your estate, or an operational dependency your business stops without.

The scrutiny it earns: Full assessment with evidence, not just answers; contract clauses with teeth; review on a schedule and at every material change.

Significant — bounded but real exposure

Limited data sets, access to a single system, or a service whose failure hurts a department rather than the business.

The scrutiny it earns: A proportionate questionnaire, key clauses in the contract, and reassessment when the relationship changes shape.

Low — no data, no access

Suppliers who touch neither your systems nor your data. Most of the vendor list, once you actually check.

The scrutiny it earns: Standard contract terms and nothing else — the effort saved here funds the scrutiny above.

The questionnaire problem

A vendor security questionnaire people actually answer

The three-hundred-question spreadsheet sent identically to every supplier is the ritual that discredits third-party risk programmes. Big vendors answer it from a pre-written library without reading your questions; small vendors either abandon the deal or answer optimistically; and the completed sheets pile up unread because nobody has time to review three hundred answers per vendor. Everyone involved knows it is theatre, and the exposure the programme exists to manage is untouched by it.

A questionnaire that works is short, tiered and specific to what the vendor holds. A supplier with your personal data gets questions about encryption, residency, subprocessors and breach notification; one with VPN access gets questions about their own access control and endpoint hygiene; neither answers questions about physical security at data centres they do not run. For critical vendors, key answers are verified — an independent audit report, a certificate checked against the issuer, a call with their security lead — because at that tier an attestation alone is not evidence. The measure of a good questionnaire is that every answer changes a decision; a question whose answer you would not act on should not be asked.

The cadence decision

Annual vendor review or continuous monitoring — what each one catches

The honest answer is a blend set by tier, because the two approaches catch different failures and cost very different amounts of attention.

OptionWhat it detectsWhat it missesWhat it costs to runBest for
Point-in-time reviewStructural facts that change slowly — governance, architecture, certifications, subprocessor chains — examined properly once a cycle.Everything that happens between reviews: the vendor breached in March looks fine in the January assessment and the next one.A concentrated effort per vendor per cycle — heavy at critical tier, light below it.The structural baseline for every tiered vendor, and the whole answer for lower tiers.
Continuous monitoringChanges as they happen: an exposed service, a leaked credential, a public breach report, an expired certificate on something of theirs you depend on.The internal reality: monitoring sees a vendor's outside surface, not their controls, processes or discipline.A stream of signals that must be triaged, or it becomes a second unread mailbox — which is why it is reserved for the vendors that matter.Critical-tier vendors, layered on top of the periodic review rather than replacing it.

Our role

What we build into a third-party risk programme and what procurement owns

  1. 01

    The tiering model and the first pass

    We build the tiering criteria on data, access and dependency, and run your existing vendor list through it — which always reclassifies a few quiet suppliers as critical and retires scrutiny wasted on harmless ones.

  2. 02

    Clauses that survive negotiation

    We draft the security schedule with your legal team — breach notification with a deadline, audit and evidence rights, subprocessor approval, data return and deletion at exit, residency where PDPL or a regulator requires it — tiered too, because demanding everything of everyone is how clauses get traded away.

  3. 03

    A process procurement can run without us

    The onboarding gate, the questionnaires, the review calendar and the monitoring triage are handed over as an operating process with owners — because a vendor risk programme that lives in a consultant's inbox is itself a third-party dependency.

Which vendors the business cannot walk away from, and how much residual risk each relationship is allowed to carry, are commercial decisions for you; we make sure they are taken with the exposure in plain view.

Common questions

What buyers ask

Which vendors deserve a full security assessment rather than a short questionnaire?+

The ones whose compromise would be an incident of yours: vendors holding sensitive or personal data at scale, vendors with privileged or network access into your estate, and vendors your operation stops without. That set is usually far smaller than the vendor list — and almost never the same as the highest-spend list, which is why tiering by exposure rather than by contract value is the foundation. For that small set, answers are verified against evidence; for the middle tier, a proportionate questionnaire is enough; for suppliers with no data and no access, standard contract terms and no questionnaire at all.

What security clauses actually belong in a vendor contract?+

The ones you would need on a bad day, written specifically enough to invoke. Breach notification with a defined clock, because "promptly" is unenforceable when it matters. The right to evidence — an audit report, a summary of testing, answers to follow-up questions — scaled to the tier. Subprocessor transparency and approval, so your data cannot be quietly passed to a fourth party. Data return and verified deletion at contract end, negotiated while your bargaining position is still strong. And residency commitments where PDPL or your regulator requires them. What we advise against is pasting a maximal clause set into every contract: it gets negotiated away wholesale, and the clauses that mattered go with it.

Is continuous vendor monitoring worth adding on top of annual reviews?+

For the critical tier, yes; for everyone else, usually not. The failure the annual review cannot catch is the one that happens in between — the vendor breached in March who looked fine in January — and for a supplier whose compromise becomes your incident, eleven months of blindness is a real gap. Continuous signals close it for exposed services, leaked credentials and public breach reports. But monitoring only sees a vendor's outside surface, produces a stream that someone must triage, and adds little for suppliers who could not hurt you much anyway. So the cadence follows the tier: periodic review as the structural baseline everywhere, continuous signals layered on the vendors that could genuinely become your bad quarter.

Tier your vendor list with us

A working session that tiers your current vendor list by data and access, and flags the small set whose compromise would be an incident of yours.

What happens next

  1. 1We reply within one business day.
  2. 2A 30-minute scoping call with a senior consultant.
  3. 3A written proposal with scope, team, and timeline.

Or reach us directly

By submitting this form you agree to our Terms of Use and Privacy Policy.