Data residency
Place workloads on infrastructure in Türkiye, in the Istanbul (tr-ist-01) and Ankara (tr-ank-01) regions.
Infrastructure and security
Security should remain visible across every architecture layer.
Treat data residency, isolation, access and resilience as one responsibility model.
- Regions
- Istanbul tr-ist-01 · Ankara tr-ank-01
- Certifications
- 9 ISO certifications (27001, 27017, 27701, 22301, 20000-1, 9001, 10002, 45001, 37001) — held by vMind Bilgi Teknolojileri
- Responsibility
- PortvMind Cloud layer · customer layer · joint plan
- SLA
- A service level commitment exists; its terms are defined on the SLA page and in the contract
Overview
Where are security decisions made?
On PortvMind Cloud infrastructure, security is a set of decisions across layers. Region and physical infrastructure sit with PortvMind Cloud. Network and isolation are designed together in the target architecture. Identity, access and secret storage sit with the customer. Data protection is planned with Backup. Operations and incident response scope are defined in the contract.
Control areas cover data residency, isolation, identity and resilience.
Control areas
Each control is applied together with the selected service and the target architecture.
Isolation and network
Design project, virtual network, Router, Load Balancer and access boundaries together.
Identity and access
Define least privilege, separate credentials and a secret-storage approach.
Resilience
Plan backup, retention and capacity together.
Shared responsibility
Responsibility splits into the PortvMind Cloud layer, the customer layer and controls planned together.
PortvMind Cloud layer
Infrastructure and control-plane responsibilities in the published service scope.
Customer layer
Account, access, operating system, application, data and configuration responsibilities.
Joint plan
Version, quota, network, backup, response and support scope are planned together.
Control plane
Five layers, five distinct control owners.
The diagram shows which layer a decision sits in and who owns it.
Region and physical infrastructure
Infrastructure located in Türkiye · Istanbul tr-ist-01 · Ankara tr-ank-01
ControlPortvMind CloudNetwork and isolation
Project boundary · virtual network · Router · Load Balancer · external access rules
ControlJoint designIdentity and access
Least privilege · separate credentials · secret storage approach
ControlCustomerData and resilience
Block · Object · snapshot · Backup
ControlJoint planOperations and response
Monitoring · change · capacity · incident response · support scope
ControlContract-bound
A service level commitment exists; its terms are defined in the contract.
Certifications are written together with their holder.
The certificates are issued to vMind Bilgi Teknolojileri and are read together with the relevant service scope.
Information security management system
Information security controls for cloud services
Privacy information management system
Business continuity management system
IT service management system
Quality management system
Customer satisfaction and complaints handling
Occupational health and safety management system
Anti-bribery management system
Certificate holder: vMind Bilgi Teknolojileri
Two regions, one control plane.
PortvMind Cloud is offered in two regions: Istanbul (tr-ist-01) and Ankara (tr-ank-01).
Istanbul
tr-ist-01- ComputeCPU · GPU · VKE
- StorageBlock · Object · Backup
- NetworkRouter · LB · Floating IP
Compute, storage and network resources are managed within the same project boundary.
Ankara
tr-ank-01- ComputeCPU · GPU · VKE
- StorageBlock · Object · Backup
- NetworkRouter · LB · Floating IP
The second region; included in capacity planning for resilience and rollback objectives.
Related services
The services these control areas map onto.
Router
Virtual network, routing and access rules at the project boundary.
Load Balancer
External access, health signals and traffic distribution.
Backup
Backup frequency and retention.
Object Storage
Data layer and long-term retention with full S3 API compatibility.
Related resources
Let us put the responsibility boundaries in writing.
We define isolation, access, data protection and response scope together with your target architecture.
Scope and terms
Evaluate controls alongside the scope of each service.
- Clarify the locations of primary data, backups and operational records separately.
- Review certificates alongside their holder, validity dates and relevant service scope.
- Compare access and operational responsibilities with the product documentation and your contract.