Our Security Principles
IOBackup Enterprise is designed with a security-first architecture. Your backup data is encrypted before it ever leaves your device, and we never have access to your encryption keys unless you explicitly choose to share them.
E Encryption at Rest
All backup data is encrypted using AES-256-GCM, the same standard used by banks and governments.
- AES-256-GCM (authenticated encryption)
- AES-256-CBC (legacy compatibility)
- ChaCha20-Poly1305 (performance optimized)
- 256-bit keys with PBKDF2 derivation
Z Zero-Knowledge
With zero-knowledge mode, your encryption keys never leave your device. We cannot access your data even if we wanted to.
- Client-side key generation
- Keys stored locally only
- No key escrow on our servers
- Optional HSM integration
W WORM Immutability
Write Once Read Many storage locks prevent ransomware from encrypting or deleting your backups.
- Object lock on cloud storage
- Compliance mode for regulations
- Legal hold support
- Tamper-evident audit logs
I Integrity Verification
Every backup is verified with SHA-256 checksums to detect corruption or tampering.
- SHA-256 file-level checksums
- Backup verification on completion
- Restore integrity validation
- Corruption detection & alerting
Secure by Design
IOBackup follows security best practices throughout the entire software development lifecycle:
- Code signing: All releases are signed with Apple Developer ID certificates
- Dependency auditing: Regular scans for known vulnerabilities in dependencies
- Minimal attack surface: No unnecessary network services or open ports
- Secure defaults: Encryption enabled by default, strong password policies
Found a security vulnerability?
We appreciate responsible disclosure. Please report security issues to security@amiplay.com.