Aikido Security

My main use case for Aikido Security is a centralized place where I can manage all of my security posture across my company.

For that main use case, I use mainly Aikido Security to check that my cloud accounts are safe, that there are no critical vulnerabilities around, and that all of the best practices are applied across the board.

Regarding my main use case for Aikido Security, it helps me a lot in my day-to-day life because it has automated built-in reports for Jira and Slack, so having this kind of information instantly alleviates a lot of pressure.

In my opinion, the best features Aikido Security offers include how easy it is to implement and how fast you can have it running on day one.

When I say it is easy to implement, basically, I just had to run a template in my AWS account and give it access to GitHub; with those two steps, 80% of the implementation was already done.

Aikido Security has positively impacted my organization by reducing the time spent chasing vulnerabilities and increasing the visibility of our issues internally, making them easier to track down and pinpoint an origin for them, while also alleviating a lot of pain we had when reaching out to developers about security issues.

Aikido Security can be improved; its Jira implementation is great, but it is lacking a few departments, such as having the ability to inject HTML within Jira, which would be really nice to have.

I have been using Aikido Security for over a year.

Aikido Security is stable.

Aikido Security's scalability is wonderful.

The customer support for Aikido Security is unbeatable; they are really easy to talk to, very friendly, and their response time is ridiculously low.

I would rate the customer support a 10 out of 10.

I did not previously use a different solution.

My experience with Aikido Security's pricing, setup cost, and licensing is that pricing is very straightforward, its information is publicly available on the website, setup cost was none basically, and the licensing is included within the price.

I have seen a return on investment; I already shared earlier that our biggest ROI is the time needed in chasing vulnerabilities, which has been reduced by roughly 70%.

Before choosing Aikido Security, I did not evaluate other options.

I find myself checking Aikido Security for these issues daily.

I use Aikido Security daily since I received daily reports of usage and compliance across the board, which means I need to check it daily and even several times a day.

I think Aikido Security's AI capabilities are scoped correctly; it only affects a few parts of the applications, so not everything is governed by AI, just a few features.

Regarding Aikido Security's AI accuracy and reliability of output, I think its AI capabilities are all right, but it can miss the point sometimes; it is good to have a fast and cheap overview, but I would not rely 100% on it.

My advice to others looking into using Aikido Security is to get it as soon as possible; right now, it is a very good tool for a very good price, and you will see a return on investment in less than six months. I have given Aikido Security an overall rating of 10 out of 10.

My main use case for Aikido Security is to scan our code base for vulnerabilities, threats, CVEs, code practices, approved patterns, and general code scanning from the developer end. Aikido Security helps to check both the code and is integrated with our CI tool.

A quick specific example of how I have used Aikido Security in my work is when it helped me catch credentials that people may have directly hardcoded in the code. Using Aikido Security, I am able to get that removed and sorted out.

Aikido Security handles bypasses or advanced threats by providing a unified environment for both code and Trivy scanning. In general, when we want to use any tool for our CI codebase, we need to have separate tools for coding and one for the container. Aikido Security unifies this by allowing code and image or container registries, so we can have it all in one.

In my opinion, the best feature Aikido Security offers is checking CVEs. Some CVEs are being bypassed by multiple tools, but here, Aikido Security scans it at a granular level, which is a valuable utility it provides.

Aikido Security has positively impacted my organization by helping to save time in terms of redeployment. Post-deployment, it is very difficult for folks to quickly check each and every test case, but when I use this tool, it helps me remediate all the bottlenecks of security and vulnerabilities over a single UI.

Aikido Security can be improved by addressing the lags in the UI and ensuring that updates can be given very quickly and rapidly.

I have been using Aikido Security for the last six to eight months.

Aikido Security is stable, and I find that any stability issues are totally based on our codebase. It remains stable even when generating a large amount of code.

Aikido Security's scalability is impressive, as it can handle growth or increased workloads easily. It can scale spontaneously to adopt newer code changes.

My experience with customer support has been good. We had some issues, and they responded very quickly. Their solutions and suggestions have been acceptable based on standard practices.

Before Aikido Security, we used SonarQube and Trivy scanning. However, we realized that those solutions incurred more resource costs, took more time to scan, and functioned within our day-to-day CI/CD flows less efficiently. Switching to Aikido Security helped us achieve a single straightforward approach, reducing the scanning time.

I can tell that I have seen a return on investment from the QA end, where they save time monitoring and checking the vulnerabilities at the code level, which also helps them to follow everything in line with our organization restrictions.

My experience with pricing, setup cost, and licensing is that the pricing is reasonable and based on the repository; they charge accordingly.

We did not evaluate other options before choosing Aikido Security.

I would add that Aikido Security will be integrated into a platform where we can check both the coding and image scan, which is very beneficial.

I would add that the integration done with other tools such as Git and CI/CD Jenkins pipeline is seamless.

I can share that we can deploy an additional two more deployments with Aikido Security. Usually, it takes four deployments per day, but now we can have two more, which makes it six deployments per day, allowing QA to navigate the security threats easily within the window.

Regarding Aikido Security's AI capabilities, I think its governance and security are quite secure. We get to use our cloud-native tool, which is seamless. Aikido Security's database is well managed by us rather than relying on SaaS.

Regarding Aikido Security's AI capabilities, I find it very reliable. Aikido Security's output is as expected.

My advice for others looking into using Aikido Security is that if the codebase and everything need to be audited and recorded in a single forum, and if they want a unified solution to scan both the code and the image, they can definitely use it. I would rate my overall experience with Aikido Security a ten out of ten.