Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
e-Devlet is Turkey’s single sign-on gateway to thousands of public services, and its security rests on how citizens authenticate to it and how institutions behind it handle the resulting access.

What Is e-Devlet Gateway Security?
e-Devlet is the gateway through which Turkish citizens and residents reach public services: tax records, social security and employment history, vehicle and property registrations, court filings, education records, health appointments, and several thousand more, offered by hundreds of institutions behind a single login. A UK reader meets it indirectly, because Turkish employees use it to obtain the payroll and social security documents an employer asks for, and because Turkish corporate filings are frequently routed through systems that authenticate against it.
The design is interesting, and the first-registration step is unlike anything in British practice. The primary credential, a password for the gateway, is collected in person at a post office branch on presentation of an identity document. Identity proofing therefore happens face to face, once, with a physical document, which removes an entire category of remote impersonation attack at the point of enrolment.
Alternative authentication methods exist for higher-assurance use: a qualified electronic signature or mobile signature, the chip in the national identity card read through a card reader, and identity verification through internet banking with a bank that already knows the customer. Additional verification by text message can be enabled on the account.
Enrolment is strong, so attackers target everything after it.
The UK has arrived at a similar destination by a different road. GOV.UK One Login, which replaced the earlier Verify programme after it closed in April 2023, is being rolled out as the single sign-on for central government services, with identity verification performed remotely against documents and a facial likeness check, to standards published in the government’s good practice guides. Authentication supports authenticator applications and security keys alongside weaker factors.
Three differences are worth noting if you are designing anything that touches both.
First, proofing method. Turkey front-loads a physical, in-person check; the UK performs remote document and biometric verification, which scales better and introduces injection and deepfake attack surface that in-person proofing does not have.
Second, identifier design. The UK has no universal national identity number, so services rely on combinations of attributes. That is administratively messier and considerably more resistant to the problem described above.
Third, breadth. e-Devlet aggregates a wider range of services than One Login currently does, which makes a compromised account more valuable and raises the stakes on account recovery design.
For organisations with Turkish staff, the useful controls are mundane. Tell people that no institution will ask for gateway credentials by telephone or message, that documents should be obtained by navigating to the service directly rather than through a link, and that the account should carry the strongest second factor available rather than text message alone. Where your HR process asks employees to supply documents retrieved from the gateway, do not ask them to share credentials with anyone, including an accountant acting for the company; the document is what you need, not the access.
For anyone building a service that authenticates Turkish users, treat the identity number as a lookup key and never as proof of identity, and design account recovery as carefully as the login path, because recovery is where well-defended systems are usually broken. Stronger authentication options are discussed under multi-factor authentication, and at Privia Security we assess authentication and recovery flows as part of our two-factor authentication solutions work.
In person at a post office branch, on presentation of an identity document, for a small fee. That face-to-face proofing step is the foundation of the system’s assurance and is noticeably different from the UK approach, where GOV.UK One Login verifies identity remotely using document checks and a facial likeness comparison. The in-person step removes remote impersonation at enrolment but makes initial registration slower.
No, and it should never be treated as one. It is used as an identifier across public and commercial systems, appears on many documents, and large data sets containing citizen records have circulated publicly since 2016. Any system that accepts the identity number as evidence of identity, rather than as a lookup key accompanied by genuine authentication, is effectively unauthenticated.
No, and it should not try. The account belongs to the individual, and sharing credentials breaks the assurance the system depends on as well as creating obvious liability. Where an employer needs a document, such as a social security record, the correct process is for the employee to retrieve the document themselves and provide it, or for the employer to use the separate systems designed for employer access.
Phishing, by a wide margin. Fake login pages promoted through search advertising and text messages referencing payments, fines, or documents capture credentials that unlock a very broad set of personal data in one place. Fraudulent mobile applications and telephone number takeover attacks on text-message verification follow. Enrolment is strong, so attackers concentrate on everything that happens afterwards.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.