Home / AuraLink with ProtectionGrid / Immutable Backup

A backup your own domain admin can't delete.

Immutable backup on the 2U AuraLink appliance, locked in the storage controller.

Attackers delete the backup first. Then they encrypt. AuraLink locks every snapshot inside the storage controller. Until retention expires, the controller rejects every delete and every change, including an administrator's.

An immutable backup is a copy that can't be altered or deleted for a fixed retention period once it has been written. Identiqa anchors that lock in the 2U AuraLink appliance with ProtectionGrid: in the storage controller rather than in the backup software, in your own rack, and mirrored to the Identiqa Cloud.

94%
of ransomware victims say attackers went after their backups
The attackers tried to destroy the backups or make them unusable.
57%
of those attempts succeeded
Attackers succeeded in more than half of their attempts.
8×
the recovery cost when the backup was hit
Median recovery cost: $3 million instead of $375,000.

Sophos, The Impact of Compromised Backups on Ransomware Outcomes, March 2024, survey of 2,974 organizations hit by ransomware. Source

Where a software lock gives way.

Both are sold as immutable. The difference shows only when an attacker is working with a real administrator account.

Lock in the backup software

  1. Admin account stolen
  2. Backup console opened
  3. Retention shortened
  4. Backup deleted

The lock held only as long as the console was in the right hands.

Lock in the AuraLink storage controller

  1. Admin account stolen
  2. Delete command sent
  3. Storage controller rejects it
  4. Backup stays

The command arrives and is rejected until the retention period has run out.

Simplified.

What a lost backup costs.

Sophos surveyed organizations after a ransomware attack and compared two groups: those whose backup the attacker reached, and those whose backup stayed intact.

What changes when the attacker reaches the backup

Data was encrypted

  1. Backup compromised85%
  2. Backup intact52%

Ransom was paid

  1. Backup compromised67%
  2. Backup intact36%

Source: Sophos 2024, as above.

Four ways to protect a backup
MethodDeletable with an admin account?Recovery
Network share or NASUsually, through normal administrationFast, if it survives the attack
Lock in the backup softwarePossible once the console or the hypervisor is taken over or the system clock is manipulatedFast
Tape stored off siteNo, the tape is offlineHours to days, depending on volume and transport
AuraLink with ProtectionGridNo, the storage controller rejects the commandFast, from your own rack

The backup sits in your rack.

AuraLink is a 2U appliance with two Aura processors of our own. It works alongside your firewall and holds the backup copy that ransomware can't delete.

AuraLink 2U rack appliance by Identiqa
AURALINK 2U · DUAL AURA PROCESSORS · IMMUTABLE STORAGE

The backup sits in your rack, locked in the appliance's storage controller.

2UYour own hardware in your own rack
In the controllerThe lock lives in storage, not in software
Second copyMirrored to the Identiqa Cloud
No shellSigned commands from a closed list only

What you can rely on in an incident.

No account lifts the lock

Once a snapshot is written, the storage controller rejects every change and every delete until retention has expired. That includes commands sent with administrator rights.

LOCKED IN STORAGE

A clean recovery

Before systems go back into production, AuraCore checks servers, virtual machines, Kubernetes clusters, and Docker hosts for backdoors an attacker may have left behind.

AURACORE

Evidence instead of assurances

The lock record from AuraLink shows auditors and your cyber insurer that your backup was out of reach of an administrator account.

LOCK RECORD

Someone picks up

Our 24/7 incident response team guides the recovery from the locked snapshots and preserves the evidence for investigators and insurers.

24/7 INCIDENT RESPONSE
Why the lock in storage holds where software gives way

In many environments the backup software shares its operating system, its time source, or its directory service with production. An attacker who gains domain admin there, or takes over the backup server, moves the system clock forward or lifts the retention period in the console.

AuraLink anchors immutability in the storage itself. Once a snapshot is written, the storage controller rejects every change or delete command until the defined retention period has expired. A copy is mirrored to the Identiqa Cloud.

The appliance has no open shell. AuraLink accepts only signed commands from a closed command list.

Common questions

Isn't the immutability setting in my backup software enough?

It helps for as long as nobody takes over the software's management plane. When the lock lives in the same console an administrator uses, an attacker with that account can shorten retention or move the system clock forward. On AuraLink the lock sits in the appliance's storage controller, outside your domain. No account from your network can lift it.

What's the difference between an immutable backup and an air-gapped backup?

An immutable backup can't be changed or deleted until its retention period ends. An air-gapped backup is separated from the production network, so an attacker can't reach it from there. AuraLink combines an immutable backup with a logical air gap in a single 2U appliance.

Does NIST CSF 2.0 call for immutable backups?

Not by name. Subcategory PR.DS-11 asks that backups of data are created, protected, maintained, and tested, and RC.RP-03 asks that the integrity of backups is verified before they are used for restoration. The framework names outcomes, not technologies. A backup that a stolen administrator account can delete is hard to describe as protected.

In your rack. On the cloud contract you already have.

We size Identiqa to your infrastructure and sites. Buy directly through Identiqa or on your existing agreement with Amazon Web Services, Google Cloud, or Microsoft Azure.

Architecture briefing & advisory