Transparency
Status Page
We continuously monitor our components: Platform Web Docs Agent Cloning Scanning Extensions Mailing Dependencies In doing so, we let all interested parties, including our developers, know the availability status of such systems. Monitoring checks are ...
Help Channel
The Help Channel serves as a communication bridge between Fluid Attacks and our clients. It is designed to address inquiries, concerns, and requests, including developer role changes and access permission modifications. This documentation outlines ...
Data Leakage Policy
In cases where Fluid Attacks detects a breach, we send emails to notify the involved parties. These emails contain information about: What data was leaked or compromised. When the data was leaked or compromised. How long the data was leaked or ...
Incident Management and Resolution Process
Definition Confirmed issues include malfunctions, performance degradation, service disruptions, or errors within Fluid Attacks products or components. These issues must have already affected or have the potential to impact a minimum of two users, ...
Continuous Hacking to Our Technology
We have projects focused on hacking our software. It is essential for us to be an example of secure software. That's why our entire technology stack goes through a process of comprehensive Continuous Hacking. All our development projects run ...
Open Source
The source code of all our applications is available on the Internet. The security advantages of having open-source code are the following: Auditability: Anyone on the Internet can audit public code. This means that to keep our business secure, we ...
Information Security Responsibility
Some of our CTO's responsibilities include defining and enforcing information security policies that fully protect our customers' data as well as our own. The person in this position works together with our engineering team to ensure we follow ...