Extensive logs
Last updated: Nov 3, 2026
Logs are essential for a successful non-repudiation policy. At this time, Fluid Attacks keeps logs for these systems:
- Platform logging system: The Fluid Attacks platform keeps the historical status of projects, findings, vulnerabilities, and other critical components. Each change to these components is always related to a user and a date. The historical status does not expire. No one can change these logs.
- Platform error tracking system: The Fluid Attacks platform gives real-time logs of the errors in its production environments. These logs are very useful to quickly find new errors and hacking attempts. Fluid Attacks keeps these logs for 15 days, and no one can change them.
- Redundant data centers: Data centers keep full logs of all the infrastructure components of Fluid Attacks. Fluid Attacks keeps the audit trail logs of the write actions on its cloud accounts in object storage with log file validation, and these logs do not expire. Fluid Attacks can detect changes to the audit trail logs. Fluid Attacks keeps the log group of the Fluid Attacks platform for two years (731 days). It keeps most other log groups for 90 days, for example the search, ingestion, data-processing, job, and cluster log groups. It keeps the log group of one workflow for 30 days. Fluid Attacks sends the security logs of its cloud accounts, firewall, IAM, and collaboration systems to its observability platform. This platform keeps them for 450 days, and no one can change these logs on the platform.
- CI Gate execution: When the CI pipeline of a client runs the CI Gate, the CI Gate uploads logs to the data centers of Fluid Attacks. These logs contain information such as who ran it, vulnerability status, and other relevant data. Thus, Fluid Attacks always knows the current status of the CI Gate service of the client. These logs do not expire, and no one can change them.
- IAM authentication: The IAM of Fluid Attacks keeps logs of user login attempts, accessed applications, and possible threats. These logs expire after seven days, and no one can change them.
- Collaboration systems activity: The collaboration systems of Fluid Attacks, such as email and calendar, keep full activity logs of the talent. They also keep logs of spam, phishing, and malware emails, suspicious login attempts, and other potential threats. The activity logs of the talent do not expire. Other security logs expire after 30 days. No one can change these logs.
- CI job logs: All the CI pipelines of Fluid Attacks give a full record of who started them, when, and the console output. These logs are in GitLab, not in the cloud log groups above. They do not expire, and no one can change them.
Requirements
These Fluid Attacks requirements apply to the controls on this page: