Supply-Chain Security · SC-Q01

Question: Is there a formal third-party risk management (TPRM) program defining scope, ownership, and lifecycle (onboarding → monitoring → offboarding)?

Why This Matters

Vendors extend your attack surface. A structured TPRM program prevents silent risk creep and ensures controls exist across the entire supplier lifecycle.

Maturity

0 — Unaware
No TPRM policy or inventory of vendors.
1 — Ad Hoc
Security reviews happen informally for some critical deals.
2 — Defined
TPRM policy approved; risk tiers and basic questionnaires.
3 — Managed
Lifecycle in place: due diligence, contracts, monitoring, exit.
4 — Integrated
TPRM linked to risk register, incidents, and procurement systems.
5 — Optimized
Continuous assurance and automated control evidence ingestion.

How to Level Up

From → To Actions
0 → 1 Create vendor inventory and designate a TPRM owner.
1 → 2 Approve TPRM policy with risk tiering (critical/high/standard).
2 → 3 Embed security review in procurement and renewal steps.
3 → 4 Integrate TPRM with risk, incident, and CAPA workflows.
4 → 5 Automate evidence collection and reminders across the lifecycle.

Enablers

Evidence

KPIs

Low-Cost / Open-Source Options (MSME)

Purpose Tool Notes
Inventory & workflow Airtable / Odoo Community Tiering, dates, owners
Questionnaires Google Forms Lightweight due diligence
Tracking Metabase TPRM dashboards

Common Pitfalls

Compliance Mapping

Standard Clauses / Notes
ISO/IEC 27001 A.5.19 (Supplier relationships)
NIST CSF 2.0 ID.SC (Supply chain)
DPDP Act 2023 Processor obligations via contracts
NIRMATA Mapping SC-Q01 establishes the program backbone for supply-chain assurance.