Share your experience using Continuous Dynamic (formerly WhiteHat Dynamic)

My main use case for Upwind is cloud security and workload protection. I primarily use it to gain visibility into cloud assets, vulnerabilities, and runtime risks, and I mainly use it to prioritize the risks that actually matter and help the team focus remediation efforts instead of treating every finding equally.

A specific example would be using Upwind to investigate a vulnerable cloud workload and determine if it was actually exposed or active at runtime. The runtime context helped us prioritize the issue based on real traffic and workload behavior instead of treating every vulnerability as equally urgent.

I appreciate runtime context, which helps connect vulnerabilities and misconfigurations with actual workload behavior and network relationships, making it easier to prioritize remediation based on real exposure rather than simply working through a long list of security findings.

The best features that stand out to me are contextual vulnerability prioritization, cloud workload visibility, and runtime security. I especially value how Upwind connects vulnerabilities with actual runtime behavior, which helps focus on exploitable risk rather than working through a long list of findings.

It has helped us focus on actual exploitable risk instead of treating every vulnerability equally. By considering runtime activity, exposure, reachability, and sensitive data context, the team can prioritize remediation much faster and reduce unnecessary alert noise.

I also value the runtime visibility and attack path context because it connects security findings with network behavior and actual workload. This makes investigations more actionable and helps the team move from simply detecting issues to understanding their real impact.

The biggest positive impact has been the prioritization of cloud security risk and improved visibility. Instead of chasing every vulnerability, we can focus on issues that are actually exposed or active at runtime, which makes the security team more efficient and remediation more targeted.

I would appreciate more customizable dashboards and reporting for different teams, such as security operations, engineering, and leadership. The runtime context is excellent, but tailoring those views for each audience would make day-to-day use even smoother.

I would appreciate more flexibility in the filtering capabilities and reporting for different security teams. I would also appreciate customizing dashboards. As environments grow larger, making it easier to surface role-specific risk and trends would make an already strong platform even more efficient.

I have been using Upwind for around a year, approximately ten months.

Upwind's AI governance and security are strong because they combine AI posture controls with real-time runtime visibility, which gives the security team better context around data flows, identities, AI workloads, and potential threats rather than relying on static configuration checks.

I have found the AI-related security insights to be generally accurate and useful, especially when they are backed by runtime telemetry and actual workload behavior. I also appreciate that the platform provides context and evidence around findings, which makes it easier to validate whether an alert is genuinely actionable.

I would recommend Upwind to teams that need strong cloud visibility with runtime context rather than relying on static vulnerability scans. I would start with a focused set of cloud workloads, validate the risk prioritization, and then expand it across the environment as the team becomes comfortable with the workflows.

Overall, my experience is very positive with Upwind. The combination of runtime visibility, security insights, and contextual risk prioritization makes it much easier to focus on the risks that actually matter. I gave this review a rating of ten out of ten.

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.