Security by Disaggregation
The repository you can't reach, can't be attacked.
Sendense keeps your backup repository isolated from production networks with outbound-only connectivity, per-block encryption, and immutable storage — on-prem or in the cloud.
Why Backups Get Attacked
Most backup platforms fail the same way: they leave the repository reachable on the network.
Exposed Management Ports
Attackers scan for backup services. Open ports for "management" become entry points.
Direct Repository Access
Compromised production hosts have network paths to backup storage. Ransomware follows.
Credential Reuse
Same AD credentials for production and backup. Compromised domain = compromised backups.
The Sendense Approach
The SHA (Hub) lives in a secure zone. Remote SNAs initiate outbound tunnels — no inbound firewall rules required at remote sites.
- Single External Port (443)
Only one port exposed — the same one you use for HTTPS
- Outbound-Only Remote Sites
SNAs establish tunnels to the Hub — no inbound rules
- Repository Isolation
EBA storage not directly reachable from production networks
- Explicit Enrollment
Time-limited pairing with approval flow — no auto-join
EBA On-Prem: Local Protection
For environments that must keep data local — regulatory, air-gapped, or sovereignty requirements.
Global Deduplication
100 VMs with 80% OS overlap? Store once. Cross-VM dedup that dramatically cuts storage needs.
Per-Block Encryption
Every 4MB block individually encrypted. Steal a disk? Get nothing useful.
Immutable Storage
WORM-capable backends. Once written, data cannot be modified or deleted until retention expires.
Air-Gap Ready
Complete network isolation possible. Physically move data for ultimate protection.
Supported On-Prem Storage
Local NVMe/SSD
Direct attached
NFS
Network shares
S3-compatible
MinIO, CEPH
ZFS
Block storage
AWS S3
Object Lock supported
Azure Blob
Immutability policies
Google Cloud
Retention policies
Wasabi / Backblaze
S3-compatible
EBA Cloud: S3 Object Lock
Ransomware with admin credentials still can't delete your backups. S3 Object Lock enforces immutability at the storage layer.
- Governance Mode
Protection with override capability for authorized admins
- Compliance Mode
True WORM — nobody can delete, not even root
- Legal Holds
Preserve specific backups indefinitely for litigation
- Cost Tiers
Hot tier for recent, cold tier for archive — 80%+ savings
Ransomware Protection In Depth
Multiple layers of defense — not just one.
Network Isolation
Attackers can't reach what they can't find
Outbound-Only Tunnels
No inbound ports at remote sites
Repository Segmentation
EBA storage in isolated network zone
Separate Credentials
Not tied to production AD domain
Data Protection
Even if accessed, data is useless to attackers
Per-Block Encryption
AES-256 on every 4MB block
Client-Side Keys
Cloud provider can't read your data
Dedup-Safe Encryption
Convergent encryption preserves dedup
Delete Protection
Even with full access, deletion is blocked
S3 Object Lock
Storage-layer WORM enforcement
72-Hour Delay
Minimum wait before permanent deletion
Soft Delete + Retention
Deleted data recoverable for X days
Secure Credential Vault
vCenter passwords, S3 keys, storage credentials — all encrypted at rest with strict access controls. No cleartext secrets in config files.
- AES-256 Encryption at Rest
All credentials encrypted in the vault — never stored in plaintext
- Per-User Key Derivation
Secrets bound to user context — no shared access
- Access Logging
Every credential access logged with user, timestamp, and purpose
- Rotation Support
Rotate credentials without service interruption
Last Access: 2026-01-21 09:15 — jsmith — BACKUP_JOB — vCenter Production
Role-Based Access Control
Least-privilege by default. Users get exactly the access they need — no more.
Super Admin
Full platform control. System configuration, user management, all operations.
✓ All permissions
✓ User management
✓ System config
Backup Admin
Manage backup jobs, policies, and repositories. No system-level access.
✓ Create/edit jobs
✓ Manage policies
✗ User management
Restore Operator
Perform restores only. Cannot create jobs, modify policies, or delete backups.
✓ Initiate restores
✓ View job status
✗ Create/delete jobs
Auditor
Read-only access to logs, reports, and compliance data. Cannot perform operations.
✓ View all logs
✓ Export reports
✗ Any operations
Scope Restrictions
Limit users to specific VMs, sites, or tenants. Multi-tenant isolation built in.
- Per-VM permissions
- Site-level isolation
- Tenant boundaries
Session Management
Automatic session expiry, concurrent session limits, and forced logout capability.
- Configurable timeouts
- Single-session mode
- Force logout users
MFA Support
Optional multi-factor authentication for high-security environments.
- TOTP authenticators
- Hardware key support
- Per-role enforcement
Audit-Ready Evidence
When auditors ask "prove it" — you can. Every operation logged, every backup verifiable, every hold documented.
- Complete Audit Trail
Every create, delete, restore, and hold logged with user + timestamp
- Legal Holds
Preserve specific backups indefinitely for litigation
- Exportable Reports
Generate evidence packages for auditors and legal
- Retention Enforcement
Policies enforced automatically — no manual compliance
Type: All VMs for Customer X
Matter ID: CASE-2026-ACME-001
Custodian: Legal Department
Created: Jan 15, 2026
Status: Cannot be deleted until released
Audit Trail: 47 events logged • All actions tracked • Export available
Recent Audit Events
2026-01-21 09:15 — BACKUP_VERIFIED — prod-sql-01 — System
2026-01-21 08:30 — BACKUP_COMPLETED — prod-web-02 — Scheduler
2026-01-20 17:45 — LEGAL_HOLD_APPLIED — LH-2026-001 — jsmith
Security Summary
Security by design. Not by bolt-on.
Reduce exposure without slowing operations. Start free with 10 VMs.