NIS2 for suppliers: what your customers will ask about your IT

NIS2 requires in-scope entities to manage the risk that comes from their suppliers. So even if the directive doesn’t apply to you directly, customers increasingly send security questionnaires. It pays to prepare – most questions come down to a handful of core measures.

NIS2 in brief

NIS2 is the EU cybersecurity directive (EU) 2022/2555. It applies to medium and large companies and organisations in many sectors – from energy, transport and health to digital services, manufacturing and food supply. In Lithuania, its requirements have been transposed into the Law on Cybersecurity.

In-scope entities must manage cyber risks, including supply-chain security, and report significant incidents: an early warning within 24 hours, a notification within 72 hours and a final report within a month.

Why it affects suppliers

Because entities are responsible for the risk their suppliers bring, they ask suppliers about security measures, add requirements to contracts and sometimes run audits. Without answers you can lose business even when your IT is actually in good shape – simply because you can’t prove it.

Common questions and what to have ready

QuestionWhat to prepare
Do you use MFA?MFA for all users, especially admins and e-mail
How do you protect data?Off-site backups and restore tests
How do you manage vulnerabilities?A patching schedule and EDR/XDR protection
Are devices encrypted?Disk encryption on computers (BitLocker / FileVault)
Who has access to systems?An access list, least privilege, access removed when people leave
Is staff trained?Regular security reminders and phishing awareness
How do you handle incidents?A documented incident handling and reporting process
How fast would you notify us?A commitment in the contract and a named contact

Steps to prepare

  1. Gap assessment

    Compare what you have with what customers usually ask.

  2. Quick wins

    MFA, patching, endpoint protection and backup restore tests.

  3. Documents

    Security policy, access list, incident process.

  4. Answer template

    Prepared answers – next time a questionnaire takes minutes, not days.

Legal note

Whether NIS2 applies to your company directly depends on your sector and size – check the competent authority’s guidance or ask a lawyer. We help implement the technical and organisational measures and prepare answers for your customers – see NIS2 implementation support.

Frequently asked questions

Does NIS2 apply if we are only a supplier?

Usually not directly, unless your company itself falls within the NIS2 sectors and size thresholds. But your customers must manage supplier risk, so they pass requirements on to you through contracts and security questionnaires.

Which measures do customers ask about most?

Multi-factor authentication (MFA), backups and restore tests, patching and vulnerability management, device encryption, access management and an incident notification process.

How long does it take to get ready?

The core technical measures (MFA, protection, restore tests) can usually be in place within a few weeks. Documents and processes take longer, so start with a gap assessment.

Do we need ISO 27001 certification?

NIS2 doesn’t require it directly. Some customers may ask for it, but usually it is enough to show that the core security measures are implemented and documented.

Be ready for the next questionnaire

CallGet a proposal

Choose which cookies you allow. You can change your choice at any time.

Strictly necessary

Needed for the site to work securely and remember your choices (e.g. cookie settings or text typed into a form). They cannot be switched off and need no consent.

Always on
Cookies (3)
  • ithink-consent · IThink (localStorage)
    Stores your cookie choice and an anonymous consent ID. Expires: 12 months.
  • ithink-form:* · IThink (sessionStorage)
    Keeps the text you type into a form so you don’t lose it while filling in a request. Expires: Until the browser tab is closed or the form is sent.
  • __cf_bm, cf_clearance · Cloudflare
    Protection against bots and attacks (set only when needed). Expires: 30 minutes.

Analytics

Help us understand how visitors use the site (Google Analytics 4) so we can improve it. Data is aggregated and IP addresses are not stored.

Cookies (3)
  • ithink-utm, ithink-landing · IThink (sessionStorage)
    Adds the campaign source and first page visited to your request. Expires: Until the browser tab is closed.
  • _ga · Google Analytics 4
    Distinguishes visitors for visit statistics. Expires: 2 years.
  • _ga_8EFLVCZYDP · Google Analytics 4
    Keeps the state of your visit (session). Expires: 2 years.

Marketing

Let us measure the effectiveness of our Google Ads advertising and show you more relevant ads.

Cookies (2)
  • _gcl_au · Google Ads
    Measures whether an ad led to a visit and a request. Expires: 90 days.
  • IDE, test_cookie · Google (doubleclick.net)
    Ad delivery and measurement on Google networks. Expires: Up to 13 months (test_cookie – 15 minutes).

Cookie policy · Privacy policy

Privacy policy

Loading…