Skip to content
+90 850 885 27 43 info@argeict.com

Guide · Compliance

KVKK technical measures checklist

This checklist groups the technical measures in the Personal Data Security Guide under seven headings, so that IT teams running systems that process personal data can review their current state item by item.

ARGE ICT · Published November 11, 2026 · Updated November 18, 2026

KVKK, Türkiye's Personal Data Protection Law (Law No. 6698), expects the data controller to take technical and administrative measures for the security of personal data. The law does not list which measures count as sufficient; the Personal Data Protection Authority gives examples in the Personal Data Security Guide (the Guide).

Basis and limits of the list

The list rests on Article 12 of KVKK and on the Guide. That article obliges the data controller to take the technical and administrative measures needed to ensure an appropriate level of security for personal data.

The technical measures in the Guide are grouped here under seven headings that follow the work of an IT team. The items under each heading are written so that you can answer them with yes, partly, or no.

The list is not a compliance document or a legal opinion. Meeting every item does not show that an organization complies with KVKK, because administrative measures and legal obligations fall outside the list. The Guide's recommendations on software development and application security do not have a heading of their own here either.

1. Permissions and account management

This heading covers the measures that determine who can access personal data and under which conditions.

  • Every user has an account in their own name, and shared accounts are not used.
  • Permissions are written in a permission matrix according to job descriptions and are reviewed periodically.
  • The account of an employee who leaves or changes role is closed or updated through a defined process.
  • Administrator accounts are separate from everyday accounts.
  • Administrator access and remote access to systems that hold personal data use multi-factor authentication (MFA).

2. Logging and monitoring

Logs make it possible to trace an access or a change afterward.

  • Access logs and activity logs are kept on systems that hold personal data.
  • Logs are stored in a separate environment that the administrator of the source system cannot access.
  • Logs are reviewed regularly, and an alert is defined for unusual access.
  • The retention period of logs is tied to a written rule.
  • System clocks are synchronized to a common time source.

3. Network and endpoint security

This heading covers the measures that limit access from the network and from devices to systems that hold personal data; the patching and update items also belong here.

  • A firewall stands between the internet and the internal network, and its rules are reviewed periodically.
  • Servers that hold personal data are in a separate network segment.
  • Intrusion detection and prevention is active.
  • Endpoints run up-to-date protection software.
  • Operating system and application updates are applied through a defined process, and a list of end-of-support software is kept.
  • Unused services and ports are closed.

4. Encryption and key management

Encryption makes data harder to read if it falls into unauthorized hands, but that only works when the keys are protected as well.

  • The disks of laptops and removable media are encrypted.
  • Personal data is transferred over the network with encrypted protocols.
  • Backups are encrypted.
  • Encryption keys are kept in a different place from the data.
  • Access to the keys is restricted and logged.

5. Backup

Backup is the measure that allows recovery when data is lost or corrupted.

  • All systems that hold personal data are in the backup scope.
  • One copy of the backups is kept apart from the main environment.
  • Only authorized administrators can access the backups, and they use a separate account to do so.
  • Recovery is tested, and a test record is kept; the Restore test guide can help you set the test up.

6. Data loss prevention, masking, and deletion

This heading collects the measures that limit how personal data leaves the organization and how long it stays where it is not needed.

  • Personal data leaving the organization by email, removable drives, or cloud storage is monitored or restricted (data loss prevention, DLP).
  • Masked data is used in test and development environments.
  • A method for deletion, destruction, or anonymization is defined for data whose retention period has ended, and each operation is recorded.
  • Data on disks and devices that are disposed of is erased so that it cannot be recovered.

7. Penetration testing and review

Setting up the measures is not enough; you also need to test whether they work.

  • A penetration test or vulnerability scan is carried out periodically and after major changes.
  • Findings are tracked until they are closed.
  • The operation of the measures is reviewed periodically.
  • The technical steps for a data breach are written down: preserving logs, isolating the affected system, and the people to notify.

Measure, implementation, and audit evidence

The table below takes eight of the headings above and answers three questions: how the IT team implements the measure, which document or record is shown in an audit, and which service relates to it. The evidence column gives examples; the party carrying out the audit decides which documents it asks for.

KVKK technical measures, implementation, and evidence
MeasureHow IT implements itWhich evidence is shown in an auditRelated service
Access permissions and reviewA permission matrix is built from job descriptions, every user gets their own account, and administrator tasks use a separate account. The account of an employee who leaves or changes role is closed through a process, and permissions are reviewed periodically.Permission matrix, minutes of the latest review, account closure records for departed employees, list of administrator accounts.Identity and access management; PAM
Multi-factor authentication (MFA)MFA is mandatory for administrator access and remote access, defined as a policy in the identity provider or the access layer.Screenshot of the MFA policy, list of accounts outside MFA scope, and approved exceptions.Identity and access management
LoggingAccess and activity logs of systems that hold personal data are collected in one place and stored in a separate environment that the administrator of the source system cannot access. The retention period is tied to a written rule, and an alert is defined for unusual access.Retention rule, list of log sources, a sample alert and the record of the response.SIEM and log management
EncryptionLaptop and removable media disks, network transfers, and backups are encrypted; keys are kept apart from the data, and access to them is logged.Encryption inventory, configuration output, key access logs.KVKK and ISO 27001 technical measures
Backup and restore testEvery system that holds personal data is in backup scope, one copy is kept apart from the main environment, and backups are accessed with a separate account. Recovery is tested regularly.Backup job reports, restore test record, list of backup access permissions.Backup and disaster recovery
Vulnerability scan and penetration testScans and tests run periodically and after major changes; each finding is assigned an owner and tracked until it is closed.Scan or test report, finding list, and closure records.Security assessment
Incident responseThe technical steps for a data breach are written down: preserving logs, isolating the affected system from the network, and the people to notify. The plan is prepared together with the legal team.Response plan, notes from a trial run of the plan, past incident records.SIEM; Firewall and endpoint
Data loss preventionPersonal data leaving the organization by email, removable drives, or cloud storage is monitored or restricted with rules.DLP rule list, alert and block logs, rule change history.Data loss prevention (DLP)

This page is not legal advice; the current text of the legislation prevails.

Topics that overlap with administrative measures

The IT team also contributes to some topics that the Guide places under administrative measures. These are employee training and awareness, the personal data processing inventory, policies and procedures, contracts with data processors, and confidentiality agreements. A data processor is a party that processes personal data on behalf of the data controller.

The IT team supplies technical input to this work, such as the system list, the access logs, and supplier access. These topics are owned by legal, human resources, or compliance, which is why they do not form a separate heading in the list.

How to use the list

Each item is marked yes, partly, or no, with a piece of evidence beside it: a report, a log, a screenshot, or a procedure. For missing items, an owner and a date are set, and the order follows the type and volume of the data affected.

The Personal Data Protection Board (the Board) has set additional measures for special categories of personal data, and this list does not cover them separately. A data breach must be reported within the period the Board sets, so it helps to prepare a notification plan with the legal team in advance.

Frequently asked questions

Does this table show compliance with KVKK?

No. The table collects the technical records an IT team should have. A compliance assessment also covers administrative measures and legal obligations, and for that you need the opinion of your legal team.

Which evidence is requested in an audit?

The party carrying out the audit decides, and it varies by case. The evidence in the table is a set of examples: a policy, a screenshot, a log, and a test record. It helps if each piece is dated and taken from the system itself.

How long should logs be kept?

The period is set together by Law No. 6698 on the Protection of Personal Data (KVKK), sector regulations, and contracts. Confirm the period that applies to you with your legal team from the current text of the legislation. On the IT side, what matters is that the period is written down and that the logs are preserved for that long.

Does a small company have to apply all of these measures?

The level of measures depends on the type and volume of the data processed and on the risk. Which item is mandatory for you is a legal question, and this page does not answer it. When ranking the gaps, the sensitivity of the data affected is a reasonable starting point.

Does ARGE ICT help produce this evidence?

Yes, on the technical side. We build and operate measures such as permission review, log collection, restore testing, and scanning, and the evidence comes from those systems. We do not give legal opinions or issue compliance certificates.

Sources

  • Kişisel Veri Güvenliği Rehberi (Personal Data Security Guide: Technical and Administrative Measures), Personal Data Protection Authority (kvkk.gov.tr)
  • Law No. 6698 on the Protection of Personal Data, Mevzuat Bilgi Sistemi (mevzuat.gov.tr)

Expert call for KVKK technical measures

Share the headings where you found gaps and the systems that process personal data; we respond to your request within one business day.

Speak to an expert