A customer in Germany sends you a security questionnaire. Among the questions: "Is email traffic encrypted?", "Within how many hours will you tell us about an incident?", "Where is our data stored?" At the top, a short note: "Supplier assessment under NIS2." You are a company based in Turkey. What does this have to do with you? In this article we explain how NIS2 email requirements and GDPR duties reach a business outside the EU, directly or indirectly, and how to answer such questionnaires on the email side.
We work on email infrastructure, we are not lawyers. This is a general frame; for your own situation, work with legal counsel.
Short answer: NIS2 directly binds certain EU organisations in listed sectors and above certain sizes; a Turkish company is usually affected indirectly, as a supplier, through contracts and questionnaires. GDPR can apply to Turkish companies that offer goods or services to people in the EU. In both cases customers expect provable email security and an incident-reporting process.
NIS2 and GDPR in brief
NIS2 is the EU's cybersecurity directive (Directive (EU) 2022/2555). It places security-measure and incident-reporting duties on "essential" and "important" entities above a certain size in sectors such as energy, transport, health, digital infrastructure and some ICT services. One detail matters: reporting runs in three stages. For a significant incident the directive foresees an early warning within 24 hours, a fuller notification within 72 hours and a final report within a month; for the precise rules read the directive's official text.
GDPR is the data protection regulation (Regulation (EU) 2016/679). It is about personal data rather than cybersecurity as such, but its requirement for "appropriate technical and organisational measures" covers email too. For a personal data breach the general expectation is notification to the supervisory authority within 72 hours. The official GDPR text is the reference.
Directly, or through the supply chain?
For most Turkish small and mid-sized companies the answer is "indirectly". An EU company that falls under NIS2 has to address supply-chain security among its own measures. That shows up in contracts and questionnaires: your customer asks you for particular security measures and incident-notification commitments. So even where the legal source of the duty does not bind you directly, its commercial effect does.
Being directly in scope depends on special circumstances: you have a branch or subsidiary in the EU, or you offer certain kinds of services listed in the directive (some digital infrastructure and cloud services, for instance) to the EU. This turns on sector and size. Before saying "I am in scope" or "I am not", ask a specialist.
GDPR looks a little different. If you offer goods or services to people in the EU, or monitor their behaviour, some GDPR provisions can apply to you even though you are outside the EU. Turkish e-commerce firms and software companies are typical examples.
Email questions on customer questionnaires
Reading these questionnaires, we notice that most email questions rest on a recurring core. The table lists the common ones and the evidence you can prepare.
| Question | Concern behind it | Evidence to prepare |
|---|---|---|
| Is two-factor authentication on mailboxes? | Account takeover | Screenshot of the admin policy |
| Is sender identity authenticated? | Spoofing, BEC | SPF, DKIM, DMARC records |
| Encryption in transit and at rest | Data leakage | Provider statement, settings records |
| Where is data stored? | Transfers, jurisdiction | Provider document, data location information |
| Backup and restore | Continuity | Policy, a restore-test note |
| Incident notification process | Timing and ownership | Written incident plan |
When you answer, one rule: never tick "yes" for something you do not do. Questionnaires can turn into contract terms; saying "partially" and giving an improvement date is far safer than a wrong "yes". For the order in which to put basic email controls in place, our 12-point small business email security checklist helps.
If you use a service such as Postanex, the concrete facts you can rely on are these: data is stored encrypted in data centres in Turkey, mail is backed up daily, the infrastructure is monitored around the clock, outgoing mail is DKIM-signed and the administrator can set a 2FA policy for mailboxes. Those are simply product features; they are not a certification or a compliance guarantee, and you should not present them as one.
How KVKK and GDPR relate
Many people call KVKK "Turkey's GDPR". The principles are similar: lawfulness, purpose limitation, data minimisation, data subject rights, breach notification. But these are separate laws; complying with one does not automatically satisfy the other. Deadlines, scope and procedures differ. For the Turkish side of breach reporting, see our article on KVKK breach notification.
Data location comes into this as well. An email service that keeps data in Turkey reduces cross-border transfer questions under KVKK, but for an EU customer remember that Turkey is a "third country". We discuss this in email that keeps data in Turkey and KVKK cross-border email data transfers.
Which evidence should you prepare?
A plain list is enough for a "compliance folder": an email security policy (one page), 2FA and password rules, your domain's DNS records, a backup and restore note, a written incident plan with notification times, staff training records, data processing agreements, and a retention and deletion policy. For retention, see our piece on email retention periods. Refresh the folder once a year so that you never start from zero when a questionnaire arrives.
Points that need legal counsel
Go to a specialist when: you have a branch, subsidiary or employees in the EU; you are agreeing to penalty clauses or notification deadlines in a contract with a customer covered by NIS2; or you process EU residents' data and questions about appointing a representative or choosing a transfer mechanism arise. This article is general information, not legal advice.
Frequently asked questions
Is a Turkish company directly subject to NIS2?
Mostly not; NIS2 targets organisations of certain sectors and sizes in the EU. The picture can change if you have activity in the EU or provide the services listed in the directive to it. Assess this with a specialist.
Why is my EU customer sending me a security questionnaire?
Your customer may be required to manage its own supply-chain security, so it asks suppliers about their measures. Because your answers can become contractual commitments, be honest and back them with evidence.
Does KVKK compliance mean GDPR compliance?
No. The principles are similar, but they are separate legal regimes. If you process the data of people in the EU, assess GDPR's own requirements separately.
What evidence helps most on email questions?
A 2FA policy supported by dated screenshots, SPF, DKIM and DMARC records, a backup and restore note and a written incident plan are the four that help most often.
- NIS2
- GDPR
- KVKK
- supply chain
- email security