TRUST CENTER - INFRASTRUCTURE & ARCHITECTURE

Onesurance & Architecture
Last updated: December 2024

Our Platform

Onesurance on a modern, cloud-native architecture that is optimized for scalability, security, and high availability. We use Microsoft Azure's enterprise-grade infrastructure, specifically the West Europe region, to ensure that all data remains within the EU and offers low latency for our European customers.

Cloud Infrastructure

Microsoft Azure - West Europe
• Region: West Europe (Amsterdam, Netherlands)
• Availability Zones: Use of multiple availability zones for redundancy
• Data residency: 100% within the EU, no data outside Europe
• Compliance: ISO 27001, ISO 27017, ISO 27018, SOC 2, GDPR-compliant
• SLA: 99.99% uptime guarantee from Microsoft
• Physical security: Biometric access, 24/7 monitoring, multi-layer security

Why Azure?
• Enterprise-grade security and compliance
• Extensive compliance certifications
• GDPR and DORA compliance out-of-the-box
• Advanced security tools (Security Center, Sentinel)
• High availability and disaster recovery capabilities
• EU data residency guarantees
• Excellent performance and low latency for EU customers

Platform Architecture

High-Level Architecture

[Input Sources] 
    ↓
[API Gateway + WAF]
    ↓
[Application Layer]
    ├─ Risk Engine
    ├─ Defend Agent (AI)
    ├─ Churn Model
    ├─ CLV Calculator
    └─ Next Best Product
    ↓
[Data Layer]
    ├─ Azure SQL Database
    ├─ Blob Storage
    └─ Cache (Redis)
    ↓
[Output/Integration Layer]

Components

1. API Gateway Layer

• Azure API Management

• Request routing, rate limiting, authentication

• Web Application Firewall (WAF) for protection

• DDoS protection

2. Application Services

• Azure App Services / Container Instances

• Auto-scaling based on load

• Health monitoring and auto-healing

• Blue-green deployments for zero-downtime updates

3. Processing Layer

• Risk Engine: Risk analyses and calculations

• Defend Agent: AI-driven customer service

• Churn Model: Predictive analytics for customer retention

• CLV Calculator: Customer lifetime value calculations

• Next Best Product: Product recommendations

4. Data Storage

• Azure SQL Database: Primary data storage

• Azure Blob Storage: Documents, files, backups

• Azure Cache for Redis: Performance optimization

• Azure Key Vault: Secrets and encryption keys

5. Monitoring & Logging

• Azure Monitor: Application and infrastructure monitoring

• Azure Log Analytics: Centralized logging

• Azure Application Insights: Performance monitoring

• Azure Sentinel: Security information and event management (SIEM)

Network Architecture

Virtual Network (VNet)
• Isolated network within Azure
• Subnets for segregation:

• Front-end subnet (API Gateway)

• Application subnet (App Services)

• Database subnet (private, no internet access)

• Management subnet (admin access)

Network Security
• Network Security Groups (NSGs): Firewall rules per subnet
• Azure Firewall: Centralized network filtering
• Private Endpoints: Databases not exposed to the internet
• Service Endpoints: Secure connection to Azure services
• No public IP addresses for sensitive resources

Connectivity
• Internet ingress: Via Azure Front Door with WAF
• Client VPN: Available for enterprise customers
• Azure ExpressRoute: Option for dedicated private connection
• API endpoints: RESTful APIs over HTTPS only

High Availability & Redundancy

Availability Zones
• Multi-zone deployment: Resources distributed across 3 availability zones
• Failover: Automatic failover between zones in case of failure
• No single point of failure: All critical components redundant
• SLA: 99.99% uptime (52 minutes downtime per year max)

Load Balancing
• Azure Load Balancer: Traffic distribution across instances
• Health probes: Constant monitoring of instance health
• Auto-healing: Unhealthy instances are automatically replaced
• Geographic distribution: Traffic routing to the nearest healthy instance

Database Redundancy
• Azure SQL Database: Automatic geo-replication
• Read replicas: For performance and disaster recovery
• Point-in-time restore: Backup every 5 minutes
• Long-term retention: Weekly backups for up to 10 years
• Automatic failover groups: In case of database failure

Performance & Scalability

Auto-Scaling
• Horizontal scaling: More instances during high load
• Vertical scaling: Larger instance type if necessary
• Metrics-based: CPU, memory, request count triggers
• Schedule-based: Preemptive scaling for expected peaks
• Scale-in protection: Gradual scale-down to ensure stability

Performance Optimization
• Caching: Azure Cache for Redis for frequently accessed data
• CDN: Azure CDN for static assets
• Database indexing: Optimized queries and indexes
• Connection pooling: Efficient database connections
• Asynchronous processing: Non-blocking operations where possible

Capacity Planning
• Monitoring: Continuous monitoring of resource utilization
• Alerts: Proactive alerts when capacity is nearing its limit
• Regular reviews: Quarterly capacity planning sessions
• Growth projections: Forecasting based on trends
• Headroom: Maintain 30% headroom for unexpected spikes

Security (See also Template 03)

Defense in Depth

1. Perimeter: Azure Firewall, DDoS Protection, WAF

2. Network: NSGs, VNet isolation, Private Endpoints

3. Application: Secure coding, input validation, authentication/authorization

4. Data: Encryption at rest (AES-256), in transit (TLS 1.3)

5. Identity: Azure AD, MFA, RBAC, PIM

6. Monitoring: Azure Security Center, Sentinel, 24/7 SOC

Security Tools
• Azure Security Center: Security posture management
• Azure Sentinel: SIEM and threat detection
• Azure Defender: Advanced threat protection
• Azure Policy: Compliance enforcement
• Azure Blueprints: Governance at scale

Data Protection
• Encryption at rest: AES-256 on all storage
• Encryption in transit: TLS 1.3 minimum
• Key management: Azure Key Vault with HSM
• Backup encryption: Separate encryption keys
• No data export: Outside the EU without explicit consent

Backup & Disaster Recovery

Backup Strategy

Database Backups
• Frequency: Automatic backups every 5 minutes
• Retention:

• Point-in-time restore: 35 days

• Long-term backups: Weekly for 10 years
  • Geo-redundant: Replicated to paired Azure region (within EU)
  • Encryption: All backups encrypted AES-256
  • Testing: Monthly restore tests

Application & Configuration Backups
• Infrastructure as Code: Terraform/ARM templates in Git
• Configuration: Versioned and backed up
• Container images: Stored in Azure Container Registry
• Frequency: Continuous (upon change)
• Retention: Indefinite (version history)

File Storage Backups
• Blob storage: Geo-redundant replication
• Versioning: Enabled for recovery from overwrites
• Soft delete: 30 days retention
• Immutable storage: For compliance-critical data

Disaster Recovery Plan

RTO & RPO Targets
• Recovery Time Objective (RTO): 4 hours
• Recovery Point Objective (RPO): 5 minutes
• Meaning: Maximum 4 hours downtime, maximum 5 minutes data loss

DR Strategy
• Active-passive: Primarily in Western Europe, failover to Northern Europe (within the EU)
• Automated failover: For databases and critical services
• Manual failover: For complete site failover (after assessment)
• Failback: Controlled process after primary recovery

DR Testing
• Frequency: Semi-annual (twice a year)
• Scope: Full DR simulation, failover, and failback
• Documentation: Runbooks updated after each test
• Lessons learned: Improvements implemented

Disaster Scenarios

1. Availability Zone failure: Automatic failover (minutes)

2. Region failure: Manual failover to paired region (hours)

3. Data corruption: Point-in-time restore (minutes to hours)

4. Ransomware: Restore from immutable backups (hours)

5. Major Azure outage: Escalation to Microsoft, contingency plans

Monitoring & Observability

Application Monitoring
• Azure Application Insights: Performance, availability, usage
• Metrics: Response times, error rates, throughput
• Distributed tracing: End-to-end request tracking
• Dependency tracking: External service calls
• Real user monitoring: Client-side performance

Infrastructure Monitoring
• Azure Monitor: Metrics for all resources
• Log Analytics: Centralized log aggregation
• Metrics collected:

• CPU, memory, disk, network utilization

• Request rates, error rates

• Database performance metrics

• Cache hit rates
  • Retention: 90 days online, 1 year archived

Alerting
• Multi-level alerting: Info, Warning, Error, Critical
• Notification channels: Email, SMS, PagerDuty, Teams
• On-call rotation: 24/7 coverage for critical alerts
• Escalation paths: Defined escalation in case of non-response
• Alert fatigue management: Regular review and tuning

Dashboards
• Executive dashboard: High-level metrics (uptime, performance)
• Operations dashboard: Detailed system health
• Security dashboard: Security events, threats, compliance
• Custom dashboards: Per team/function
• Public status page: onesurance

Compliance & Governance

Infrastructure Compliance
• Compliance frameworks: ISO 27001, GDPR, DORA
• Azure Policy: Enforced security baselines
• Regulatory compliance dashboard: Azure Security Center
• Audit logs: All configuration changes logged
• Immutable logs: Logs cannot be modified or deleted

Change Management
• Change approval: All production changes reviewed
• Change windows: Scheduled maintenance windows
• Rollback procedures: Documented for all changes
• Post-change verification: Health checks after deployment
• Change log: Audit trail of all infrastructure changes

Asset Management
• Inventory: All resources tagged and tracked
• Classification: By criticality and data sensitivity
• Ownership: Assigned owners per resource
• Lifecycle management: Decommissioning procedures
• Cost tracking: Per resource, per team, per customer

Development & Operations

DevOps Practices
• CI/CD: Automated build, test, deploy pipelines
• Infrastructure as Code: Terraform for reproducibility
• GitOps: All config in version control
• Automated testing: Unit, integration, security tests
• Blue-green deployments: Zero-downtime updates

Environments
• Development: Isolated, feature branches
• Staging: Production-like, for final testing
• Production: Live environment
• Data: Anonymized in non-production environments
• Access: Strictly controlled per environment

Release Process

1. Code review and approval

2. Automated security scans

3. Deployment to staging

4. Automated and manual testing

5. Approval for production

6. Deployment to production (blue-green)

7. Post-deployment verification

8. Monitoring for issues

Performance & Availability SLA

Service Level Agreement
• Uptime: 99.9% monthly uptime guarantee
• Calculation: (Total minutes - downtime) / Total minutes
• Exclusions: Planned maintenance (outside business hours)
• Measurement: Automated external monitoring
• Reporting: Monthly SLA reports available

Planned Maintenance
• Frequency: Monthly maintenance windows
• Schedule: Announced minimum 7 days in advance
• Timing: Outside business hours (8:00 p.m. - 6:00 a.m. CET)
• Duration: Maximum 4 hours
• Zero-downtime: Uses blue-green deployments where possible

Incident Response (Zie Template 06)
• Detection: Automated monitoring + manual reporting
• Response: <15 minuten voor critical issues
• Communication: Status updates elk uur tijdens incident
• Post-mortem: Binnen 5 werkdagen na major incident

Technology Stack

Languages & Frameworks
• Backend: Python, Node.js
• Frontend: React, TypeScript
• Data processing: Python (pandas, scikit-learn)
• Infrastructure: Terraform, ARM templates

Databases & Storage
• Relational: Azure SQL Database
• Caching: Azure Cache for Redis
• Blob storage: Azure Blob Storage
• Search: Azure Cognitive Search

AI/ML Stack
• Training: Azure Machine Learning
• Inference: Azure Container Instances
• Models: TensorFlow, PyTorch, scikit-learn
• MLOps: Azure DevOps for model lifecycle

Third-Party Services (See Template 08)
• Cloud infrastructure: Microsoft Azure
• Development tools: GitHub, Azure DevOps
• Monitoring: Azure Monitor, Application Insights
• Security: Azure Security Center, Sentinel

Future plans

Short-term (6-12 months)
• Kubernetes migration for improved orchestration
• Enhanced observability with distributed tracing
• Additional availability zone expansions
• Improved auto-scaling algorithms
• Expanded monitoring and alerting

Long-term (1-2 years)
• Multi-region active-active setup (if customer requires)
• AI/ML model improvements
• Advanced analytics capabilities
• IoT integration possibilities
• Edge computing for ultra-low latency (if relevant)

Customer access

API Documentation
• OpenAPI (Swagger) specs available
• Interactive API docs: Try-it-out functionality
• Code samples: Python, JavaScript, cURL
• Postman collection: For easy testing
• Webhooks: Real-time notifications

Integration Support
• Dedicated integration support
• Sandbox environment for testing
• Rate limits: Clearly communicated
• SLA for API uptime: 99.9%
• Version deprecation: 12 months' notice

Contact

For technical questions and architecture:
• Technical Team: onesurance
• API Support: onesurance
• Infrastructure Incidents: onesurance (24/7)

Last updated: December 2024
Onesurance .V. | Breda, Netherlands | Chamber of Commerce: 87521997