Everything backed up
Last updated: Nov 4, 2026
Data is probably the most valuable asset of Fluid Attacks. Thus, Fluid Attacks protects its data in these ways:
- The S3 buckets that keep the client repositories have versioning. Versioning is different from a backup. It only lets Fluid Attacks return a file in these buckets to a version from the last 60 days.
- Fluid Attacks stores all its backups in decentralized data centers. Thus, problems such as the lifespan of hard drives are not a concern. The backups exist for as long as Fluid Attacks wants, with full traceability and recoverability.
- The database of the Fluid Attacks platform has point-in-time recovery. Fluid Attacks can recover the database to its state at a specific date and time (hours, minutes, and seconds) in the last 35 days. The most recent point is usually about 5 minutes before the current time.
- All the exploits are versioned.
- The backups that Fluid Attacks creates in its AWS environment do not include client repositories. The backup routines are only for the operational data of the platform, for example, the DynamoDB database, which supports point-in-time recovery. The source code of clients is never part of the backup schedule of Fluid Attacks.
Backup policies
This is the DynamoDB backup policy of Fluid Attacks.
Fluid Attacks does not use AWS Backup for its S3 buckets.
Backup protection
Fluid Attacks uses the data protection controls and procedures that AWS applies to its storage systems:
Distributed firewall
Fluid Attacks protects its domain with a distributed firewall that includes DDoS protection, rate limiting, anti-bot challenges, and OWASP Core Rule Set.
Multiple zones
Fluid Attacks ensures high availability by running its AWS infrastructure across multiple Availability Zones of the Northern Virginia region, with global edge delivery and monitoring.