Security and Disaster Recovery

Security Infrastructure

The infrastructure powering Insites has invested heavily in its Information Security Management System (ISMS) with comprehensive security policies and processes:

• Multiple network abstraction layers for isolation
• Geographically distributed data centers
• Regular third-party penetration testing
• Virus and malware scanning

Your code runs securely with redundancy and backups.

Data Backups

Your applications and databases are automatically backed up using multiple layers:

• Real-time read replicas - Database replicas across multiple availability zones provide physical disaster recovery within a data center.
• Incremental transaction logs - Captured continuously for point-in-time recovery.
• Daily and weekly backups - Automated snapshots of your data.

For developers building SaaS solutions on Insites, additional options are available for taking off-site backups and managing data removal. See Data Import/Export for tools you can use to export and back up your application data.

Related resources:

• GDPR Compliance - How the Insites infrastructure approaches GDPR and ensures your project can comply with privacy regulations.

Load Balancing and Redundancy

Insites uses application load balancers operating at the request level (Layer 7) to distribute traffic across clusters of application and database servers.

Dedicated servers are available for clients who need single-tenant hosting or additional capacity for high-traffic applications.

Behind the load balancers, both pooled and dedicated application and database servers ensure redundancy and availability.

Disaster Recovery

A comprehensive disaster recovery plan (DRP) is in place that covers:

• Guidelines for determining when to activate the plan
• Technical response flow and recovery strategy
• Recovery procedures and checklists
• Rollback procedures to return to normal operations
• References to business resumption plans and technical dependencies

Recovery Strategy

Data Center Disruption	Dependency Disruption	Network Issues
Failover to alternate data center	Reroute core functions to backup zone	Reroute to backup processing (load balancing, caching)
Reroute core processes without full failover	Participate in recovery as available	Wait for restoration, communicate with stakeholders
Operate at reduced service level	Wait for restoration, communicate as needed

Recovery Phases

• Response phase - Immediate actions after a significant event. On-call personnel are paged, recovery strategies are decided, and the full recovery team is assembled.
• Resumption phase - Recovery procedures are implemented and coordination across teams is executed.
• Restoration phase - Rollback procedures bring services back to previous levels and normal operations are restored.