PlungeAI · Trust Center

App security

Coming soon

How we find and fix weaknesses in our code.
6 in place · 1 written as policy

Responsible disclosure

In place

Report a vulnerability to legal@plungeai.com. Good-faith research under our rules has a safe harbor.

Write to legal@plungeai.com with what you found, where, and how to reproduce it. The same contact is in our security.txt.

Research that follows the disclosure rules in our Acceptable Use Policy (Sections 7.4 and 7.5) is treated as authorized. We do not run a paid bug bounty.

Source: Security, Report a vulnerability

Application penetration testing

Policy

A written testing plan covers external penetration tests. We publish no penetration test report yet.

A written testing plan describes external penetration tests of the public APIs and sign-in flows.

We do not publish a penetration test report yet. When we do, it will be listed here. This is a written internal policy. It has not been independently audited.

Source: DORA ICT Resilience Testing Plan (on request)

Secure code review

In place

Production code is kept under version control and reviewed before it is deployed.

Changes to production code are kept under version control and reviewed by PlungeAI before they are committed and deployed.

Source: Security, Code and fixes

Dependency and vulnerability management

In place

We apply security fixes to our code and its dependencies according to how severe the risk is.

We apply security fixes to our code and its dependencies according to the severity of the risk.

Source: Security, Code and fixes

Rate limiting

In place

Rate limits protect the services.

We set rate limits to protect the services. Circumventing them is prohibited by the Acceptable Use Policy.

Source: Security, Code and fixes

Secret redaction

In place

When our systems find a secret in an execution trace, they replace it with a marker before the trace is stored.

When our systems find a secret, such as a password or a key, in an execution trace, they replace it with a marker before the trace is stored.

Source: Security, Keys and credentials