What else is card scheme and network called?

card network, payment rail, clearing house.

How critical is a card scheme and network vendor by default?

Critical when the paste gives no rating: There is no substitute for a scheme the customers pay on; the relationship is governed by the rulebook, not a negotiated contract.

Which obligations attach to a card scheme and network vendor?

NIS2: NIS2 Art. 21(2)(d), NIS2 Art. 21(3); SP 800-161: SP 800-161 SR-6, SP 800-161 SR-8, SP 800-161 SA-4, SP 800-161 SR-13, SP 800-161 SA-9, SP 800-161 CP-2, SP 800-161 CP-4; ISO 27001: ISO 27001 5.19, ISO 27001 5.20, ISO 27001 5.22.

Which contract clauses does the register look for on a card scheme and network contract?

Rulebook obligations and change notice, settlement and collateral, incident reporting, membership conditions, beside the clauses each ticked regime expects on every vendor agreement.

Every vendor category · Payments and financial

Card scheme and network

The rails and schemes the processors settle through; membership is a licence with its own rulebook.

How the register reads it

Also called	card network, payment rail, clearing house
Family	Payments and financial
Default criticality	Critical when the paste gives none. There is no substitute for a scheme the customers pay on; the relationship is governed by the rulebook, not a negotiated contract.
DORA scope	Not an ICT service in itself: recorded in the register of information only where a service element (support, maintenance, hosting) sits in the contract.
Contract focus	Rulebook obligations and change notice, settlement and collateral, incident reporting, membership conditions.

What each regime attaches

12 clauses across 3 regimes

Shown on a register for the regimes you tick; with none ticked, the ISO 27001 rows are the default. Requirement text drawn from a human-verified compliance corpus under licence: the corpus statement of each clause, not the instrument verbatim.

The NIS2 Directive

Attaches to every direct supplier and service provider of the entity, whatever it supplies; the depth of the assessment follows the access and the criticality.

NIS2 Art. 21(2)(d) Supply chain security, covering the relationship with each direct supplier and service provider

The Directive scopes this deliberately at direct suppliers and service providers, which makes the first artefact an inventory of who those parties are and which of them touch the network and information systems behind the service. From there the entity has to manage the security-related aspects of each relationship: what the supplier may access, what securit...

Evidence an auditor accepts: Inventory of direct suppliers and service providers, flagged for access to in-scope systems; Risk assessment per supplier proportionate to the access and criticality involved; Contractual security clauses, including incident notification obligations and audit or assurance rights
Common gap: Inventory built from the procurement system, so shadow and free-tier services are missing
Source framework: NIS2 Directive

NIS2 Art. 21(3) Take account of supplier-specific vulnerabilities and of Union coordinated supply chain risk assessments

Deciding what supply chain measures are appropriate is not left to general judgement. The entity has to take into account the vulnerabilities specific to each direct supplier and service provider, and the overall quality of those parties' products and cybersecurity practices including their secure development procedures. Separately, it must take into account...

Evidence an auditor accepts: Per-supplier assessment records that address that supplier's own vulnerabilities and secure development practice; A watch process for Union coordinated supply chain risk assessments and the outputs it has captured; Decision records showing how each relevant coordinated assessment was reflected in supplier measures
Common gap: Supplier assessment reduced to a questionnaire score with no view of that supplier's actual weaknesses
Source framework: NIS2 Directive

NIST SP 800-161 Rev 1

Attaches to every supplier, developer, integrator and service provider of a federal system, with the hardest controls on components and on privileged access.

SP 800-161 SR-6 Supplier Assessments and Reviews

Assesses and reviews suppliers, at a depth matched to what they supply and the access they hold.

Evidence an auditor accepts: assessment methodology and tiering by criticality; assessment records per supplier; review cycle evidence
Common gap: all suppliers assessed with the same questionnaire
Source framework: NIST SP 800-161 Rev 1

SP 800-161 SR-8 Notification Agreements

Establishes agreements requiring suppliers to notify the organization of compromise, vulnerability and relevant change.

Evidence an auditor accepts: notification clauses with defined triggers and timeframes; evidence of notifications received; escalation route when notification fails
Common gap: notification obligation absent or without a timeframe
Source framework: NIST SP 800-161 Rev 1

SP 800-161 SA-4 Acquisition Process

Puts security and supply chain requirements into the contract, including the evidence the supplier must provide.

Evidence an auditor accepts: contract templates carrying security and C-SCRM requirements; evidence of requirements in executed contracts; acceptance criteria tied to those requirements
Common gap: requirements in the template but absent from signed contracts
Source framework: NIST SP 800-161 Rev 1

SP 800-161 SR-13 Supplier Inventory

A control new in this publication: maintains an inventory of suppliers so that exposure to any one of them can actually be answered.

Evidence an auditor accepts: supplier inventory with the systems and components each supports; criticality attached to each supplier; update procedure on supplier change
Common gap: supplier list held by procurement with no link to systems
Source framework: NIST SP 800-161 Rev 1

SP 800-161 SA-9 External System Services

Governs external service providers across their life cycle, including the security roles each party holds.

Evidence an auditor accepts: inventory of external services; agreements defining security roles and responsibilities; monitoring and assessment evidence
Common gap: responsibilities assumed rather than defined
Source framework: NIST SP 800-161 Rev 1

SP 800-161 CP-2 Contingency Plan

Plans for continued operation when a critical supplier, integrator or component source becomes unavailable.

Evidence an auditor accepts: contingency plan with supplier failure scenarios; identification of critical suppliers and single points of failure; alternate sourcing arrangements
Common gap: plan lists systems but not the suppliers that keep them running
Source framework: NIST SP 800-161 Rev 1

SP 800-161 CP-4 Contingency Plan Testing

Tests the supply chain elements of the contingency plan, including whether alternate sources can actually deliver.

Evidence an auditor accepts: test plan including supplier failure scenarios; test results and lessons; evidence alternate sources were contacted or validated
Common gap: alternate supplier named but never approached
Source framework: NIST SP 800-161 Rev 1

ISO/IEC 27001:2022

Attaches to every supplier relationship through controls 5.19 to 5.23, and to outsourced development through 8.30. With no regime ticked, these rows render as the default.

ISO 27001 5.19 Information security in supplier relationships

Define and apply processes to manage the security risk suppliers introduce.

Evidence an auditor accepts: supplier_risk_assessment; contractual_security_requirements; supplier_security_monitoring
Common gap: Treating all suppliers as low risk
Source framework: ISO/IEC 27001:2022

ISO 27001 5.20 Addressing information security within supplier agreements

Establish and agree the relevant security requirements in each supplier contract.

Evidence an auditor accepts: contract_security_clauses; supplier_risk_assessment; security_incident_reporting
Common gap: missing explicit security clauses
Source framework: ISO/IEC 27001:2022

ISO 27001 5.22 Monitoring, review and change management of supplier services

Regularly monitor, review and manage change in supplier security practice and service delivery.

Evidence an auditor accepts: supplier_security_monitoring_reports; supplier_service_review_meetings; supplier_change_management_records
Common gap: relying on informal verbal updates
Source framework: ISO/IEC 27001:2022

Findings this category can raise

Single-source vendors with no fallback named
The paste marks these vendors as the only source and names no fallback. Every regime treats that as the concentration it exists to surface: the question is what happens on the day the vendor is unavailable, and who has written the answer down.
Concentration at or above the threshold
One vendor carrying a quarter or more of the spend, the top three carrying sixty percent or more, or one country carrying half or more: the register names the share so the dependence is a recorded one. Concentration is often the right commercial choice; the regimes ask that it be assessed, not avoided.
Contracts ending inside 90 days with no re-tender noted
A contract end inside ninety days of the as-at date, with no re-tender, renewal or extension recorded in the paste. Ninety days is shorter than most exit plans and most procurement cycles; the finding lists the days left beside each vendor.
Critical vendors with no contract end recorded
A vendor rated critical, by the paste or by derivation, with no contract end date. A register with no end date cannot schedule the exit, the renewal or the re-assessment; the date belongs in the register even when the contract rolls.
NIS2 supplier assessment not evidenced
The Directive asks an essential or important entity to manage the security of each direct supplier relationship and to take account of each supplier's own vulnerabilities and practices. These vendors touch in-scope systems and the paste carries no assessment date for them: the assessment may exist, but the register cannot show it.
Sub-outsourcing chains longer than one hop
The paste names a chain of two or more parties beneath a vendor. Each hop is a relationship the buyer has no contract with; DORA asks for the chain in the register, NIS2 asks that the supplier's own suppliers be considered, and the notification duty has to run the whole length of it.

Do this for every vendor on your list

Paste the list and get this classification for every vendor at once, with the share of spend and systems, the country it lands in, the criticality, the findings and the obligation rows per regime. Eight vendors free, no account.

Build my vendor register

Banking and treasury · Insurer and broker