Turkish Personal Data Protection Law No. 6698 does not draw a line between a small firm and a large group: if you process personal data, you are a data controller and you have a security duty. The statute does not, however, contain a sentence that says “commission a penetration test every year”. This article sets out how SMEs should read that gap, based on official texts. It is not legal advice; you should consult a lawyer about your own situation.

What does the law actually require?

Article 12(1) of Law No. 6698 requires the data controller to take “all necessary technical and administrative measures to provide an appropriate level of security” for three purposes: preventing unlawful processing of personal data, preventing unlawful access, and ensuring that the data are retained.

Article 12(3) requires the controller to carry out, or have carried out, the audits needed to ensure that the Law is applied in their organisation. Article 12(5) requires the controller to notify the data subject and the Board “as soon as possible” if personal data are obtained by others through unlawful means.

In that frame, a penetration test is not the single, named, mandatory tool in the statute. It is still relevant in two ways. First, it gives substance to the ideas of “necessary measures” and “audits” in Article 12: with written authorisation and a defined scope, it shows how your systems actually stand from the outside or the inside. Second, the Board’s official guide lists penetration testing among example technical measures.

Where does the official guide mention penetration testing?

To provide practical clarity, the Board has published the Personal Data Security Guide (Technical and Administrative Measures). In the current text (KVKK Publications No. 72, April 2025), the summary table of technical measures (Table 4.1) includes “Sızma Testi” (penetration testing) alongside access control, network and application security, encryption, backups and intrusion detection.

The guide is not a regulation, and it does not say that every item must be applied in the same way in every business. Measures should follow the nature of the data and the environment in which they are kept. Even so, the table weakens the claim that “penetration testing is outside KVKK”: the Authority treats it as one of the technical measures that may be taken.

The same guide lists inventory, policies, contracts, risk analysis, training and VERBİS notification among administrative measures. A technical test does not replace that administrative foundation. Conversely, a test without a clear inventory and scope is a weak one.

Does a penetration test “prove” KVKK compliance?

It does not. A penetration test shows what was exploitable in a defined scope, under defined rules, at a point in time. It does not:

  • Certify that your firm complies with KVKK, ISO/IEC 27001 or any other framework.
  • Give any assurance about systems that were out of scope, vulnerabilities published later, or changes made after the test.
  • Replace duties on breach notification, privacy notices, retention or deletion.

Do not treat the report as a “compliance certificate”. Keep it as a record of an audit you commissioned to strengthen the measures in Article 12 and to prioritise fixes. Written authorisation, a clear scope, evidence-led findings and a retest of fixes all make that record more useful. Compliance readiness work and a web application penetration test or external network test complement each other; one does not replace the other.

What does the notification deadline mean if a breach happens?

In Decision 2019/10 of 24 January 2019, the Board interprets “as soon as possible” in Article 12(5) as 72 hours. The controller must notify the Board without delay and within 72 hours of becoming aware of the breach. If notification cannot be made within 72 hours, the reasons for the delay must also be explained. Data subjects should be notified, once those affected have been identified, within a reasonable shortest time — directly if possible, otherwise by another appropriate method.

The same decision asks controllers to prepare a breach-response plan and to review it at intervals. A penetration test can sit inside that plan: a critical finding during a test may or may not trigger a notification duty, depending on whether personal data were obtained by others through unlawful means and on the facts of the case. Make that assessment with the testing team and, where needed, with legal support. The contract should say how and how quickly critical findings will be reported.

How should an SME actually proceed?

Even at a small scale, start with an inventory: which personal data, in which systems, for whom, and for how long? An internet-facing shop, a customer portal, ordinary business email and an accounting package often share the same exposure in an SME.

Second, look at the publicly visible surface with a written, narrow scope. Domain, email authentication, TLS and security headers can already be reviewed passively with the free external mini check. That is not a penetration test and does not include unauthorised offensive attempts.

Third, for applications that really matter, commission an authorised penetration test: web or API, and the external network if needed. Scope, testing window and contact rules are agreed in writing. Fourth, fix the findings, retest them, and review the breach plan and access management.

A TSE TS 13638 authorisation or any certification claim is not part of this process. ILREDO Sentinel does not hold that authorisation and does not present test results as a certificate.

For a more practical list, see the SME cybersecurity checklist. If email spoofing is a weak point, the article on SPF, DKIM and DMARC is the next step.

What should you look for in a delivery?

When you buy a test, look at the method, not at promises of a “KVKK compliance pack”. A sound engagement at least includes written authorisation and scope, a testing window, urgent contact, early reporting of critical findings, a split between an executive summary and a technical report, a chance to retest fixes, and deletion of test data at the end. Passwords and real customer data should not be shared in a first message or over an uncontrolled channel.

Over-scoping is as unhelpful as under-scoping. Buying a “full compliance test” of an unused internal network does not discharge the audit duty in Article 12. A raw automated scan does not match the spirit of the guide’s penetration-testing example either; findings need to be verified and explained in terms of business impact. Our methodology sets out why we draw that distinction.

If you have a VERBİS registration duty, treat it as a separate administrative task. The registry entry does not replace a penetration test, and a test does not complete a registry filing. Privacy notices, lawful bases and retention-deletion processes should not be confused with a technical test.

Sources