Migrating to cloud computing increases organisations' IT agility, but it also brings new security challenges. The answer to the question "Are we secure in the cloud?" depends on how well you apply the shared responsibility model and cloud security best practices.
The Shared Responsibility Model
The cloud provider is responsible for the security of the physical infrastructure, the hypervisor and the core services. You are responsible for the security of your data, your access policies, your application security and your configurations. Clearly understanding this distinction is the first step of cloud security.
1. Identity and Access Management (IAM)
More than 80% of cloud security breaches stem from misconfigured IAM policies:
- Principle of least privilege: Every user and service account should have only the minimum permissions needed to do its job
- Mandatory MFA: Multi-factor authentication should be required for all console and CLI access
- Locking down root accounts: AWS root and Azure global admin accounts should not be used in day-to-day operations and should be locked down with MFA
- Service accounts: Use short-lived tokens and role-based access instead of long-lived API keys
- Regular auditing: Clean up unused accounts, over-privileged roles and old API keys every month
2. Data Security and Encryption
- Data at rest: All storage services (S3, Azure Blob, Cloud Storage) should be encrypted by default. Increase control with customer-managed keys (CMK)
- Data in transit: TLS 1.2+ is mandatory; also use mTLS for communication between internal services
- Database encryption: Enable Transparent Data Encryption (TDE) in RDS, Azure SQL and Cloud SQL
- Key management: Centralised key management with AWS KMS, Azure Key Vault or GCP Cloud KMS. Rotate keys regularly
- Data classification: Label sensitive data (PII, financial) and apply different security policies
3. Network Security
- VPC isolation: Each environment (prod, staging, dev) should run in a separate VPC, with controlled communication via VPC peering
- Security group / NSG: Whitelist approach — default deny, allowing only the necessary ports and IPs
- Minimise public access: Databases, caches and internal services should never have a public IP
- WAF: Place AWS WAF, Azure Front Door WAF or Cloudflare in front of web applications
- VPN / PrivateLink: For access from the corporate network to cloud resources, use a VPN tunnel or private endpoint rather than the internet
4. Logging and Monitoring
- CloudTrail / Activity Log: Log all API calls and back up the logs to a separate account/region (tamper-proof)
- SIEM integration: Send logs to a central SIEM (Azure Sentinel, Splunk, Elastic)
- Alert rules: Immediate notification for critical events such as root login, a new IAM policy or a security group change
- Flow logs: Monitor network traffic with VPC Flow Logs and detect abnormal patterns
5. Configuration Management
- Infrastructure as Code: Define infrastructure as code with Terraform or CloudFormation — drift detection and version control
- Config rules: Automatically detect and remediate non-compliant configurations with AWS Config, Azure Policy or GCP Organization Policy
- CIS Benchmark: Apply the CIS (Center for Internet Security) benchmarks — a detailed security checklist is available for each cloud provider
- CSPM: Continuous security scanning with Cloud Security Posture Management tools (Prisma Cloud, Wiz, Aqua)
6. KVKK and Compliance
Additional points to watch for in cloud security for Turkish organisations:
- Data location: Pay attention to region selection so that personal data is kept within Türkiye's borders (an Azure Türkiye region is available; AWS Istanbul is planned)
- Data processing agreement: A data processing agreement should be made with the cloud provider under KVKK
- Audit trails: Access logs for personal data should be retained for at least 2 years
Conclusion
Cloud security is not a one-off setup but a continuous process. At Marta Teknoloji, we offer security audits, IAM policy design, network security configuration and KVKK compliance consultancy services in AWS, Azure and GCP environments.
