Security and compliance

Security is the first design decision, not an add-on

The security and continuity of critical systems are managed on every project with written targets and clear responsibilities.

Security by design

Network segmentation, least privilege and firewall policies are part of the first architecture draft; they are not treated as a layer added later.

Data residency and KVKK

Where data will be kept, who can access it and how long it is retained are put in writing at the start of the project, taking KVKK and sector regulations into account.

Access and audit

Authorization, authentication and activity logs are designed to fit your audit requirements.

Continuity

Backup, immutable copy and disaster recovery targets (RTO/RPO) are set in writing and tested regularly.

Application and network protection

Applications are protected at the edge with CDN, WAF and DDoS protection; rules are tuned in monitoring mode and enforced gradually.

AI security

With an AI Gateway, AI DLP and an AI security framework, AI use is governed rather than banned; sensitive data is checked before it reaches AI services.

KVKK compliance

On every project that processes personal data, KVKK obligations are part of the design, and responsibilities are written into the contract.

Roles and responsibilities

Data controller and data processor roles, the data categories processed and the purposes are put in writing at the start; a data processing agreement is prepared for work carried out as a data processor.

Data minimization and access

Only the data the service requires is accessed, on a least-privilege basis and with logging.

Retention and disposal

Retention periods and how data is returned or destroyed when the service ends are set in advance.

Transfers and data subject rights

If a transfer abroad is needed, the conditions of KVKK Art. 9 are addressed in writing at the start of the project. Data subject requests are answered through the channels stated in the KVKK Notice.

ISO 27001 and information security management

Information security is run through the systematic management model required by ISO/IEC 27001: risks are identified, controls are applied and results are measured.

Risk-based approach

Assets, threats and risks are assessed regularly; controls are selected by risk level and documented.

Controls and policies

Written policies and procedures apply to areas such as access control, cryptography, physical security, incident management, supplier relationships and business continuity.

Internal audit and review

The management system is tested through internal audits and management review; findings are closed with corrective actions.

Continual improvement

Lessons from incidents and audits are used to improve the management system and the services.

Data center in Istanbul, disaster recovery in Ankara

Services are delivered from data centers located in Türkiye: the primary data center is in Istanbul and the disaster recovery (DR) site is in Ankara.

Data residency

Infrastructure located in Türkiye makes it easier to meet KVKK and sector rules that require data to be kept within the country.

Low latency

A short network path for users and systems in Türkiye; domestic and international access are designed together with a CDN.

Two cities, two sites

The primary data center is in Istanbul and the disaster recovery site is in Ankara. Because the sites are in different cities, a single regional event cannot stop the service; data stays within the country.

Continuity

Backup, immutable copies and the disaster recovery plan in Ankara are designed and tested as part of the service.

SLA: 99.95% availability

Our SLA rate is 99.95%. A service level is an obligation that is measured and reported, not just promised; the SLA is attached to the contract in writing.

99.95% availability

The SLA rate is 99.95%; which services it covers and how it is measured are defined in writing in the contract.

Response and resolution times

Initial response and resolution times by incident priority, support hours and escalation steps are defined.

Maintenance and change

Planned maintenance windows and change management are announced in advance.

Reporting and remedies

Service levels are reported regularly; remedies (service credits) for missed targets are included in the SLA.

Frequently asked about KVKK, data center and SLA

Is my data kept in Türkiye?

Yes. Our primary data center is in Istanbul and our disaster recovery site is in Ankara. Where your data will be kept is put in writing at the start of the project.

What does Nanda Teknoloji offer around ISO 27001?

Information security is managed under an ISO/IEC 27001 information security management system: risk assessment, controls, internal audit and continual improvement. Certificate and scope details are shared on request.

What role does Nanda Teknoloji have under KVKK?

It depends on the service. When we process customer data as part of a service we act as a data processor, and we put the responsibilities in writing in a data processing agreement.

What does the SLA include?

The 99.95% SLA rate and how it is measured, response and resolution times by incident priority, support hours, planned maintenance rules, reporting, and remedies when a target is missed.

How do I request the SLA document?

Send it through the contact form or together with your quote request; the service-specific SLA and related policies are discussed during the quotation process.

Your document and evidence requests

We discuss the security and compliance documents, policies and division of responsibilities you need for your vendor evaluation during the quotation process. You can send your request through the contact form.

Let's plan your critical systems together

Tell us what you need; our team will work out the right architecture and migration path with you.