Question 1

How does Aikido know which alerts are relevant?

Accepted Answer

We’ve built a rule engine that takes the context of your environment into account. This allows us to easily adapt the criticality score for your environment & filter out false positives. If we’re not sure, the algorithm always reverts to the safest option...

Question 2

What happens to my data?

Accepted Answer

We clone the repositories inside of temporary environments (such as docker containers unique to you). Those containers are disposed of, after analysis. The duration of the test and scans themselves take about 1-5 mins. All the clones and containers are then auto-removed after that, always, every time, for every customer.

Question 3

Does Aikido make changes to my codebase?

Accepted Answer

We can’t & won’t, this is guaranteed by read-only access.

Question 4

I don’t want to connect my repository. Can I try it with a test account?

Accepted Answer

Of course! When you sign up with your git, don’t give access to any repo & select the demo repo instead!

Question 5

How is Aikido different?

Accepted Answer

Aikido combines features from lots of different platforms in one. By bringing together multiple tools in one platform, we’re able to contextualize vulnerabilities, filter out false positives and reduce noise by 95%.

Question 6

How can I trust Aikido?

Accepted Answer

We’re doing everything we can to be fully secure & compliant. Aikido has been examined to attest that its system and the suitability of the design of controls meets the AICPA’s SOC 2 Type II & ISO 27001:2022 requirements.