Cloud Ctrl

# Platform Security & Data Protection

Cloud Ctrl is designed as a secure, cloud-native platform for collecting, processing, and analysing cloud usage, billing, and metadata across multiple cloud providers.

Security is embedded across platform architecture, data handling, identity management, and operational practices.

This page provides a high-level overview of how Cloud Ctrl protects customer data and supports enterprise security requirements.

# Security-First Architecture

Cloud Ctrl is built on Microsoft Azure using a PaaS-first architecture aligned to Azure security best practices.

Core principles include:

  • Cloud-native, PaaS-based services
  • Strong tenant isolation
  • Least-privilege access using managed identities
  • Encryption in transit and at rest
  • Centralised monitoring and auditability

The platform has evolved across multiple architectural iterations to improve security, scalability, and extensibility.

# Data Protection Overview

Cloud Ctrl processes usage, billing, and configuration metadata only.

# Data Types Processed

  • Cloud usage and consumption data
  • Billing and pricing metadata
  • Tenant configuration and non-sensitive metadata
  • Events, alerts, and aggregated statistics

Cloud Ctrl does not:

  • Access customer workload data
  • Store customer application content
  • Require privileged access beyond billing and usage scopes

# Encryption & Secure Transport

# Data in Transit

  • All communications use SSL/TLS encryption
  • APIs, ingestion pipelines, and portals are encrypted end-to-end
  • Azure Front Door provides secure ingress with Web Application Firewall (WAF) protection

# Data at Rest

All stored data is encrypted at rest using Azure-managed encryption:

  • Azure Data Explorer (usage, events, metrics)
  • Azure SQL (metadata and non-sensitive configuration)
  • Azure Storage (blobs, tables, queues)
  • Backups and platform logs

Usage data is held in memory only during processing before being securely persisted.

# Identity, Authentication & Access Control

# User Authentication

  • User access is managed via Auth0
  • Modern authentication standards (OIDC / OAuth)
  • Role-based access control within the application

# Platform & Service Authentication

  • Azure AD Managed Identities are used for service-to-service authentication
  • No secrets are stored in application code
  • Azure AD security groups enforce least-privilege access

This ensures:

  • Strong identity boundaries
  • Revocable and auditable permissions
  • Reduced credential exposure

# Secrets & Credential Management

Sensitive credentials are securely managed using Azure Key Vault.

Stored securely:

  • Cloud provider API credentials
  • Connection secrets
  • Platform configuration secrets

Access controls:

  • Secrets are never exposed to end users
  • Applications access secrets via managed identities only
  • Key Vault access is restricted using Azure RBAC

# Tenant Isolation & Data Segregation

Cloud Ctrl is a multi-tenant platform with logical data segregation.

Controls include:

  • Tenant-scoped metadata and usage datasets
  • Access enforcement at API and query layers
  • No shared credentials between tenants
  • Tenant identifiers applied throughout ingestion and analysis pipelines

Customers can only access their own data.

# Monitoring, Logging & Auditability

Cloud Ctrl includes comprehensive operational visibility:

  • Centralised application logging
  • Platform telemetry and diagnostics
  • Usage ingestion and processing statistics
  • System events and audit trails

Monitoring and observability tools support:

  • Incident response
  • Root-cause analysis
  • Compliance evidence and reporting

# Platform Reliability & Resilience

Security is reinforced by resilient platform design:

  • Built-in retry policies for external APIs
  • Durable, queue-based ingestion pipelines
  • Health checks and heartbeat monitoring
  • Automatic handling of processing spikes

Cloud Ctrl operates:

  • In Azure Australia
  • In a separate standalone Azure China environment for regional partners

# Secure Development & Operations

Cloud Ctrl follows DevSecOps best practices:

  • Source control, CI/CD, and deployments via Azure DevOps
  • Automated deployments to reduce configuration drift
  • Centralised configuration management
  • Auditable change management processes

# Shared Responsibility Model

Cloud Ctrl operates under a shared responsibility model.

Area Cloud Ctrl Customer
Platform infrastructure Yes No
Data encryption Yes No
Platform access controls Yes No
User account management No Yes
Cloud account permissions No Yes

Customers retain full control over:

  • Permissions granted to Cloud Ctrl
  • Connected cloud providers
  • User access within their tenant

# Security Transparency

Cloud Ctrl is designed to support:

  • Customer security reviews
  • Partner audits
  • Enterprise procurement requirements

Additional security documentation and architecture details are available on request.

←