The risk facing a small or medium-sized business in Tekirdağ should not be dismissed as “less than in a big city”. Manufacturing, logistics and trade in Çorlu, Çerkezköy, Kapaklı and Ergene; supply chains that reach Istanbul; orders that already travel over e-commerce and email — none of this requires an attacker to pick a geography. This article invents no Tekirdağ-specific breach statistics. It localises a picture that can be cited, and offers a checklist you can use today.

According to Verizon’s 2025 Data Breach Investigations Report announcement and the report’s published figures, the team reviewed 22,052 security incidents, including 12,195 confirmed breaches. Credential abuse was an initial access vector in 22% of the breaches reviewed; exploitation of vulnerabilities reached 20% and rose 34% compared with the previous year’s report. Ransomware was present in 44% of the breaches reviewed. In small organisations that figure is 88%, against 39% in larger ones. The share of breaches involving a third party has risen to 30%. These numbers are not Tekirdağ-specific, but they weaken the assumption, common in smaller firms, that “they will not pick us”.

1. Write down what you process and what you expose to the internet

If there is no list, protection cannot be planned. On one page, record which personal data (customers, staff, suppliers) sit in which software, and which domains, panels and remote-access paths are internet-facing. Article 12 of Law No. 6698 makes appropriate technical and administrative measures a duty of the data controller. The Authority’s 2025 Personal Data Security Guide also lists an inventory among administrative measures.

The inventory does not have to be an official form; it has to be current and to have a named owner.

2. Stop leaving administrator accounts on a password alone

In DBIR 2025, credential abuse is one of the leading vectors. Use separate passwords — and, where possible, a password manager — for accounting, email, the e-commerce panel and remote desktop, and turn on multi-factor authentication for administrator accounts. A shared “company password” is not a control; it is how a single leak opens everything.

Disable former staff accounts the same day. Take back temporary supplier access when the work ends.

3. Backups are the negotiating table in a disaster

The disproportionate place of ransomware in breaches at small organisations turns backup from an “IT task” into a business decision. Are your backups offline, or somewhere an attacker cannot easily encrypt? Have you ever restored them? A backup you have never restored does not count as a backup.

The report notes that the median ransom paid has fallen to 115,000 dollars and that 64% of victims did not pay. That is not an argument for paying. The goal is to be able to return to work, not to be able to pay.

4. Authenticate email for your domain

Most customer and supplier correspondence still travels by email. Without SPF, DKIM and DMARC, your domain can be used by someone else. Google and Yahoo’s sender rules expect these records, especially for bulk mail. See the article on SPF, DKIM and DMARC. The free external mini check looks at these records passively; it is not a penetration test.

5. Patch, and shrink internet-facing services

DBIR 2025 highlights the rise in vulnerability exploitation and zero-day attacks on edge devices and virtual private networks. Close unused remote access, keep VPN and firewall software current, and do not leave admin panels open to the whole internet. “We opened it as a trial during set-up” is not a reason for a port that is still open years later.

6. Treat suppliers and accounting software as part of your system

The rising share of breaches that involve a third party means that accounting, shipping and payroll tools are part of your exposure. Narrow their permissions, use separate accounts where you can, and write down the contract and the access period. The guide lists management of relationships with processors among administrative measures.

7. Do not say “we will look at it later” without logs, backups and a breach plan

Board Decision 2019/10 expects notification to the Board within 72 hours of becoming aware of a breach. If it is not written down who is called, who decides and where the logs live, you will spend that time arguing. The plan need not be perfect; it must be findable and known to more than one person.

8. If you run a shop or a customer portal, treat it as a separate risk

A shop selling from Tekirdağ to the rest of Turkey is as exposed to authorisation and payment flaws as a shop in Istanbul. The article on e-commerce security testing sets out where to look, in the frame of OWASP Top 10:2025. How a test sits under KVKK is summarised in the KVKK penetration-testing guide.

9. Do not stop at “we had a scan”

An automated scan is a useful start, not the whole of an audit. The official guide lists penetration testing among technical measures; that does not mean every SME must commission a full test every quarter. If you have an internet-facing system that processes personal data, though, an authorised, scoped, verified test gives substance to the audit duty in Article 12. The report is not a compliance certificate or a guarantee of security.

10. Use being local as an advantage, not as an excuse

Working in the same city makes scope and communication easier; it does not take you off the target list. Serving Istanbul, writing to a supplier in Germany, or only keeping customers inside the province does not change the basic controls: inventory, identity, backup, email authentication, narrowed access, logging and a plan.

This list is not an audit form. Marking each item “yes / no / whose job / date” is, for most SMEs, the first real progress. You do not need to buy a service you do not need; shrink the visible risk first, then widen the scope.

External network testing, vulnerability assessment or KVKK readiness can come later if you need them. The first step is usually an honest look at the surface you already expose.

Where to start this week

A new budget or a long project is not required. In one afternoon you can: list internet-facing panels, close unused remote access, turn on multi-factor authentication for administrators, restore a backup once to see that it works, check SPF, DKIM and DMARC on the domain, and write down two people to call if something goes wrong.

A manufacturer in an organised industrial zone and a shop closer to the centre will order these items differently; most of the items themselves do not change. If you bring in help, start with a written authorisation and the surface you actually need, without inflating the scope. ILREDO Sentinel is based in Tekirdağ. That is not a claim about local statistics; it means scope and communication can be settled in person.

Sources