Evaluating Nearshoring Partners: A 10-Point Due Diligence Checklist

Evaluating Nearshoring Partners: A 10-Point Due Diligence Checklist

As of December 6, 2025, a nearshoring partner is more than just an external provider of development capacity; it is part of a regulated supply chain.

The NIS2 Implementation Act requires contracting entities to assess this very supply chain, with fines running into the tens of millions in the event of noncompliance. A checklist with clear scoring criteria turns this assessment into a repeatable process rather than a gut decision made during a sales pitch.

Short answer

A nearshore development service provider can be evaluated based on 10 criteria across three areas: compliance and legal framework, operational maturity, and technical practices. Each criterion is scored on a scale of zero to three points. With a maximum of 30 points, a score of 24 or higher is considered defensible in terms of compliance; a score below 18 indicates that the risk outweighs the benefits, regardless of the hourly rate.

Why Choosing a Partner Becomes a Compliance Issue

Effective December 6, 2025, the revised BSI Act requires particularly important and important entities to assess the security of their supply chain, including direct service providers, as stipulated in Section 30(2)(4) of the BSIG. A software development partner with access to systems or source code falls under this definition, regardless of whether it meets the NIS2 thresholds itself. Anyone who selects a nearshoring partner is thereby also deciding who will report incidents in a timely manner in the event of an emergency and who must provide satisfactory evidence to their own regulatory authority. If a company violates its risk management obligations, it faces penalties according to According to the BSI, up to 10 million euros or 2 percent of global annual revenue, whichever amount is higher. The BSI Information on Supply Chain Security They describe this as cyber supply chain risk management, which clients use to structure this very assessment. A detailed analysis of data protection and reporting deadlines is provided in the article on GDPR and NIS2 in Nearshoring.

Evaluating Nearshoring Partners: An Overview of the 10 Criteria

Ten criteria are sufficient for an initial, reliable assessment, divided into three areas: compliance and legal basis, operational maturity, and technical practices. Each criterion is scored on a scale of zero to three points, with zero indicating “not met” and three indicating “met” and documented with supporting evidence. A score of one or two indicates a need for improvement in a single criterion; it is not automatically grounds for exclusion of the provider as a whole.

Compliance and Legal Basis (Criteria 1 through 4)

The first four criteria assess whether a provider has the legal basis for NIS2-compliant collaboration. These include current ISO 27001 certification or comparable evidence, and a documented process for data processing in accordance with Article 28 of the GDPR, incorporating EU Standard Contractual Clauses for transfers to Morocco or other third countries. In addition, there must be documented responsiveness to security incidents within the timeframes of 24 hours, 72 hours, and one month, as well as a documented approach to managing the provider’s own software supply chain, that is, subcontractors and the open-source components used. If any one of these four criteria is completely missing, further evaluation is rarely worthwhile. The service provider ascendro estimates in a Analysis from 2026, ...that an existing ISO 27001 certification already covers 70 to 80 percent of the basic NIS 2 security requirements. This shortens the audit process but does not replace the remaining nine criteria.

Operational Maturity (Criteria 5 through 7)

The middle three criteria pertain to the continuity of the partnership. A provider with stable management and a transparent corporate history can provide the audit trail required for NIS2 documentation spanning several years. Verifiable references from comparable industries indicate whether the partner is familiar with the regulatory context or needs to learn it first. Having German-speaking project management, not just German-speaking sales staff, determines whether reporting channels and internal coordination will take place in German or via a translation loop in the event of an emergency. The article on [...], describes the warning signs of a decline in quality despite good initial metrics. 5 Warning Signs That a Nearshore Partner Isn't Delivering.

Technical Practice and Quality of Delivery (Criteria 8 through 10)

The last three criteria examine what is actually in the code itself. Proper handling of intellectual property means that it is always possible to trace where source code is located, who has access to it, and how that access is logged. A security-conscious development process with automated tests in the CI/CD pipeline prevents vulnerabilities from going unnoticed until they reach production. Designated, permanent points of contact, rather than a rotating team, ensure the access control required by NIS2 for regulated entities, since otherwise it would be impossible to document who had access, when, and to what.

Analysis: When a Partner Is Vulnerable to Compliance Issues

The score is not a substitute for legal advice, but it does serve as a preliminary screening tool. A nearshoring partner with a score of 24 to 30 can be documented in a supplier evaluation under Section 30 of the BSIG with reasonable effort. A score between 18 and 23 points indicates that specific areas, usually related to certification or the reporting process, need improvement before the partner can be considered for critical systems. A score below 18 points indicates that the risk outweighs the benefits, regardless of how attractive the hourly rate may seem.

10 million euros

This is how high a fine can be for particularly important organizations if risk management measures, such as supply chain security, are lacking; alternatively, 2 percent of global annual revenue.

BSI, FAQs on NIS-2, as of 2026

An Overview of the 10 Criteria for Partner Evaluation
No. Criterion Area
1 Current ISO 27001 certification or equivalent proof Compliance
2 AVV pursuant to Article 28 of the GDPR, using EU Standard Contractual Clauses Compliance
3 Documented reporting deadlines: 24 hours, 72 hours, one month Compliance
4 Documented software supply chain, including subcontractors Compliance
5 Stable Management and Company History Operational Maturity
6 Verifiable references within the industry Operational Maturity
7 German-speaking project manager with decision-making authority Operational Maturity
8 Transparent Management of Source Code and Access Rights Technical Practice
9 Automated Tests and Security Checks in the Pipeline Technical Practice
10 Designated, permanent points of contact instead of a rotating team Technical Practice
Where this approach reaches its limits
The checklist evaluates self-reported information; it is not an independent audit. A provider may submit certificates and still operate differently in practice than what the documentation promises. For critical systems, no questionnaire can replace an independent audit or, at the very least, a review of third-party audit reports. And a high score says nothing about price or technical suitability; both are still worth evaluating on your own.

Review Existing Contracts
If you want to assess your existing contracts against the 10 criteria before your next NIS2 audit, you don't have to do it alone.

Get in touch

Frequently Asked Questions

Is my company subject to the NIS2 supply chain requirements, even if it is small?

Only “particularly important” and “important” entities as defined in Section 28 of the BSIG are directly affected, typically those with 50 or more employees in certain sectors. However, those subject to the regulation pass this requirement on to their suppliers through contracts, including small software development partners who are not themselves subject to NIS2 requirements. A provider with 20 employees may therefore effectively be required to complete NIS2 questionnaires, even though it is not itself regulated, as soon as a customer demands it.

How often should a nearshore service provider be reevaluated?

For critical suppliers, an annual review is recommended, but at a minimum, a review should be conducted after every major security incident in the industry or at the supplier itself. Certifications such as ISO 27001 have their own validity periods, which serve as natural review points. For non-critical suppliers without system access, a review cycle of two to three years is sufficient, because the risk evolves more slowly there than for a partner with direct access to source code or production systems.

Is a self-declaration from the provider sufficient as proof?

For initial classification, yes; for ongoing documentation, not on its own. A self-assessment shows whether a provider is even aware of the relevant issues and can identify them. For particularly important facilities, the regulatory authority also expects supporting documentation such as certificates, third-party audit reports, or contractual assurances with penalties for noncompliance. Anyone who relies solely on a completed form will have no proof, in the event of an emergency, that the measures claimed in the form have actually been implemented.

torck itself is a nearshoring partner with development teams in Maxhütte-Haidhof, Vienna, and Rabat; the sole contractual partner is the German company torck GmbH. This resolves the problems that traditional nearshoring structures, involving chains of subcontractors across multiple countries, actually create. A single contract, rather than multiple intermediaries, can be fully documented in a supplier evaluation pursuant to Section 30 of the BSIG; the time difference between Rabat and Central Europe is one to two hours, depending on the season, and project management communicates in German with internal compliance and reporting channels without the need for translation. More on Nearshore Software Development at torck.

Schedule a meeting

Legal note
This article refers to laws and regulations to put technical decisions in context. It is not legal advice. Whether and how a rule applies to your company is a question for your legal department or a law firm.

Questions about this post?

Just a couple of sentences about your situation will suffice. The person responding builds these kinds of systems himself.

We'll respond within one business day.torck · Code mit Drehmoment
Florian Blischke
Managing Director at torck · Over 20 years of software development experience
Florian Blischke is the managing director of torck, based in Maxhütte-Haidhof near Regensburg. He has been working in software development for over 20 years. His focus is custom software, data and AI for industry and retail, ranging from the integration of physical processes and IoT to cloud architecture and data- and AI-driven systems. torck works with its own nearshore team in Rabat. At torck, he oversees projects including the Jouvoli energy platform and the KVM Fleet fleet management product. torck develops software at its locations in Maxhütte-Haidhof, Vienna and Rabat and focuses on software that actually works in operation.

Are you facing the same question?

Since 2017, we have been building software for industry and retail from Maxhütte-Haidhof near Regensburg, with teams in Vienna and Rabat. An initial consultation takes 30 minutes and costs nothing. Afterwards you will know whether the project is worth pursuing, even if the answer is no.

More Articles