Identity and access
Confirms the destination and blocks access when the identity does not match the expected one.
- Validated and pinned Host Key
- Key changes detected
- TOTP
Security from the first access
Security before any credential.
L3 Backups confirms the device identity before sending credentials and protects sensitive data through encryption, isolation, and auditing.
- Automatic validation
- Reliable history
- Failure alerts
- Connection initiated
- Host Key verified
- Credential released
- Execution audited
Protection in practice
Security applied at every stage.
From connection to storage, each layer reduces exposure and keeps actions verifiable.
Data protection
Keeps credentials and sensitive fields protected with encryption and securely managed keys.
- Credentials and secrets protected
- Sensitive fields protected
- Securely managed keys
Auditability and traceability
Records important actions and relevant events to make operations more transparent.
- Searchable auditing
- Recorded operational actions
- Relevant events for analysis
Operational principle
Protection at three moments.
- 01
Before collection
Authenticated access, protected sensitive fields, and a confirmed SSH identity before credentials are sent.
- 02
During collection
Environment-scoped execution, sanitized output, and semantic validation before the version is accepted.
- 03
After collection
History, download, comparison, and auditing keep the version available for inspection.