Cybersecurity

KVKK and Endpoint Data Leaks: Spotting Turkish ID Numbers, IBANs and Card Data on WhatsApp, USB and Cloud

Marta Teknoloji•November 4, 2026•8 min read

Personal data is rarely stolen; it is usually “sent”

When people think of a data leak, they tend to picture an outside attacker. In day-to-day reality, the most common way personal data leaves an organisation is far more ordinary: an employee forwards a customer list over WhatsApp to save time, copies a payroll file to a USB stick to work from home, drops a spreadsheet of IBANs into a personal cloud folder, or prints a list of Turkish ID numbers on a shared printer and leaves it on the tray.

Most of this involves no malice at all, but under KVKK, Türkiye's personal data protection law, the outcome is the same. Data controllers are required to take the technical and administrative measures needed to keep personal data secure. An organisation that cannot see where its data goes can neither show that those measures work nor act in time when a breach occurs.

Why DLP belongs on the endpoint

DLP (data loss prevention) aims to make visible the moments when sensitive data leaves the organisation's control. Network-level controls matter, but today many of the channels data leaves through sit directly on the user's computer:

  • Messaging apps: sharing a file through the WhatsApp, Telegram or Signal desktop apps takes a couple of clicks.
  • Removable drives: USB sticks and external disks are still the quickest way to carry data.
  • Cloud sync folders: a file dropped into a OneDrive, Dropbox, Google Drive, Box, iCloud or Yandex Disk folder can sync to an account outside the organisation without anyone noticing.
  • Printing: data on paper is the data that loses its digital trail most easily.

What these channels have in common is that the event happens on the endpoint, the user's own machine. That is where the inspection needs to happen too.

What to look for: Turkish ID numbers, IBANs, cards and confidentiality markings

Blocking every file or treating every share as an alert grinds work to a halt and soon produces a pile of alerts nobody reads. An effective DLP policy focuses on content that is genuinely sensitive for the organisation. For organisations in Türkiye, the top of that list usually looks like this:

Data typeWhy it matters
Turkish ID number (T.C. Kimlik No)Identifies a person directly; appears in almost every customer, patient and staff record.
IBANFinancial data that can be used in fraud and social engineering attempts.
Credit card numberPayment data; a leak harms both the individual and the organisation directly.
Confidentiality markingsLabels such as “GİZLİ” (confidential) or “KİŞİSEL VERİ” (personal data) show that a document has been classified and needs careful handling.
Custom patternsOrganisation-specific formats such as customer numbers or contract codes.

The privacy paradox: DLP records are personal data too

DLP carries an often overlooked risk: the records collected to catch a leak can contain a copy of the very data you are trying to protect. If a DLP console stores every captured ID number in clear text, the organisation has quietly created a new store of personal data.

The right approach is to inspect content on the endpoint and keep centrally only what is needed to understand the event: which user, which machine, which channel, which data type and a masked sample. The security team can then assess the incident without seeing the data itself. How long those records are kept should also follow the organisation's retention and disposal policy.

When a breach happens: the 72-hour process

Once DLP catches a share, the real question begins: is this a personal data breach? The Turkish Personal Data Protection Board expects the data controller to notify it within 72 hours of becoming aware of a breach, and the people affected should be informed within the shortest reasonable time. Seventy-two hours sounds generous on paper, but in practice it has to cover all of the following:

  1. Detection and recording: capturing when the event happened, through which channel and with which data.
  2. Assessment: working out the number of people and categories of data affected, and the likely consequences.
  3. Containment: taking steps to stop the leak continuing.
  4. Notification: preparing the Board's notification form completely and submitting it.
  5. Documentation: recording decisions and actions in a form that can be shown when needed.

When these steps run through email threads and scattered notes, most of the clock is spent gathering information. Because the decision to notify has to be taken together with legal and management, it is crucial that the technical team can present what it knows quickly, in order and in one place.

Common mistakes

  • Watching only network egress: USB, printing and desktop messaging apps stay in the blind spot.
  • Treating everything as an alert: the more noise, the easier a real incident is missed; policy should reflect the organisation's data inventory.
  • Storing DLP records in clear text: the security tool becomes a new source of leaks.
  • Losing track of the 72 hours: the clock runs from the moment the breach becomes known, so the countdown needs to be visible somewhere.
  • Not informing staff: privacy notices and internal policies about monitoring matter as much as the technical controls.

DLP and the KVKK breach process with Marta Security SAM

Marta Security SAM — Cyber Analysis Centre Management Software, developed by Marta Teknoloji, is a threat detection and threat notification system made up of an agent installed on Windows and Linux endpoints and a multi-tenant central web console. Its data loss prevention module watches the channels described above on the endpoint:

  • On-endpoint content inspection of files shared via WhatsApp, Telegram and Signal.
  • Sensitive files copied to USB and removable drives, recorded with device name, drive letter and serial number.
  • Monitoring of OneDrive, Dropbox, Google Drive, Box, iCloud and Yandex Disk sync folders.
  • Print monitoring: user, printer, page count and confidentiality markings in document names.
  • Detectors for Turkish ID numbers, IBANs, credit cards, confidentiality markings and custom patterns.

Raw content never leaves the endpoint; the console shows masked samples only, and records can be downloaded as a masked CSV. The DLP policy and the retention period for DLP events are set separately for each organisation. Organisations that do not want to allow devices such as USB storage at all can block them with the device restrictions in the same console.

When something happens, alerts reach the right people by email, SMS, Teams, Slack or webhook, and are grouped and tracked in case and incident management with a timeline and affected assets. A KVKK breach notification draft is prepared, a 72-hour countdown starts and a reminder alert fires at hour 48. Nothing is sent automatically; the decision always stays with you.

You can explore every module of Marta Security SAM on our product page. To review your organisation's data flows with us and arrange a demo, get in touch.

#KVKK#DLP#veri sızıntısı önleme#kişisel veri ihlali#72 saat bildirim#uç nokta güvenliği#Marta Security SAM

Want to learn more?

Contact us for information about our cybersecurity, software, and infrastructure services.

Contact Us→