Upwind Cloud Security Platform
Real-Time Threat Stories That Shine on the Dashboard
Powerful Threat Intel, Automated Workflows, and Excellent Customer Service
Automation has transformed cloud vulnerability monitoring and has reduced response times
What is our primary use case?
My main use case for Upwind is vulnerability management program automation, CSPM, Cloud Security Posture Management, and overall monitoring of security vulnerabilities across the company. For example, I have my cloud provider connected to Upwind, and it scans every resource existing inside and alerts me if there is any vulnerability, such as an instance with port 22 open to the world.
How has it helped my organization?
Upwind has positively impacted my organization by reducing time to action and time to response by half. I save time because any change that is non-compliant is automatically triggered in the form of an alert, so I do not have to wait for any other scans from any other tools. Instead of having many alerts at the beginning of the day, I have an alert at the moment it happens.
What is most valuable?
The best features Upwind offers are the ability to see everything globally across many different cloud accounts, which I appreciate the most, and its ability to reduce noise is also very helpful.
Upwind helps reduce noise for me by not only firing findings but also using context to ensure that those findings are truly as critical as they claim to be. For example, a critical finding on a resource that does not have internet reachability is not as critical, but another one with high criticality that is exposed to the internet may have a raised criticality.
The accuracy and reliability of Upwind's AI output are really useful. It provides great summaries upon findings, is able to generate full investigations upon findings as well, and the ability to talk to the AI myself to get any more context or any other summaries or related information from a finding is really useful.
What needs improvement?
Upwind can be improved because its UI is a bit difficult to navigate. I find myself getting lost many times, not being able to find the option, and sometimes completely forgetting where some of the functionality is.
For how long have I used the solution?
I have been using Upwind for six months.
What do I think about the stability of the solution?
Upwind is stable.
What do I think about the scalability of the solution?
The scalability of Upwind is great so far.
How are customer service and support?
The customer support is amazing, with a sub-two-minute response time. I rate the customer support a ten on a scale of one to ten.
How was the initial setup?
My experience with pricing, setup cost, and licensing was really easy to figure out. I received a request from the support team or the sales team asking for what my needs were, and right from that email, I automatically received a quote.
What was our ROI?
I have seen a return on investment because I am basically saving costs on some monitoring tools offered on AWS, since they are now taken care of by Upwind. The amount of people needed to check all of the alerts has drastically lowered, and now I can take care of it myself. The response times are two times faster.
What other advice do I have?
My advice to others looking into using Upwind is that it is a great tool to use and can take care of many things across many areas of security, and it will save you a lot of headaches. I gave this review a rating of nine out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Automated cloud vulnerability management has reduced manual work and now frees hours every week
What is our primary use case?
My main use case for Upwind is to automate the vulnerability management program and monitor cloud security posture.
I track every change performed in the cloud environment and contrast those changes against security frameworks that I am obliged to follow. For the vulnerability management program, I track every change made to every code repository that I own and run rules against it to find vulnerabilities before they reach production.
How has it helped my organization?
We now have clear visibility of everything we own in the cloud and get notified automatically if anything deviates from normality.
What is most valuable?
The best features Upwind offers are that it is really easy to set up and the customer support team is really helpful.
Before using Upwind, I managed an in-house vulnerability management program workflow that demanded a lot of time invested to make it work, fix issues, and ensure everything was in place. Now, thanks to Upwind, everything is automated.
I am saving around six hours per week since switching to Upwind.
What needs improvement?
I believe the user interface can use improvement because some features are quite tricky to find since they are not where you would expect them to be, but with enough time, you are able to find them.
I gave it an eight because even though it is very easy to set up, the onboarding is a bit rough still, as some of the scripts that you are supposed to launch are not really well defined and can fail. With the help of customer support, you are able to keep going. The UI is another area for improvement.
These are all the improvements I have identified for Upwind.
For how long have I used the solution?
I have been using Upwind for six months.
What do I think about the stability of the solution?
Upwind is stable.
What do I think about the scalability of the solution?
Upwind's scalability is very good because they manage the infrastructure themselves.
How are customer service and support?
Customer support is very useful, helpful, and they respond really fast.
I would rate customer support a 10.
Which solution did I use previously and why did I switch?
No
How was the initial setup?
The setup process was smooth for me because it was conducted during a call with the sales representative and customer support who helped me at every step of the way. There is an onboarding process where you follow a few clicks and run a command, and basically you are ready to start monitoring the cloud. For the code, it is basically just installing a GitHub application.
What about the implementation team?
It was very easy to integrate Upwind with my existing tools and workflows because it comes very prepared to be automatically integrated with both AWS and GitHub, which are my two pillars.
The learning curve for new users on my team is quite easy because Upwind has several scoped versions of the UI. If you are just working only on development, you can set your UI to focus on code findings. The only tricky part is the UI improvements that it needs, so apart from that, the learning curve is quite low.
What was our ROI?
I have seen a return on investment because I could remove all infrastructure use for the VMP, which saved approximately one hundred dollars per month. The time needed and the team needed to manage all of the issues is quite smaller now.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that the pricing part is through a contact sales button, so it is not very transparent. However, their team made their pricing model very clear once I had a meeting with them.
Which other solutions did I evaluate?
None
What other advice do I have?
Regarding Upwind's AI capabilities, I do not know its governance and security.
Upwind's accuracy and reliability of output are really nice because it helps reduce the noise from the findings by a lot.
Upwind helps my team stay compliant with industry standards or regulations by standing up findings that violate those security frameworks, so I can filter by framework and see what is going on.
I handle alerts and notifications generated by Upwind immediately, and I usually handle them through both Slack and email.
The quality and clarity of the documentation provided by Upwind are very good and on point because it is very easy to navigate.
Upwind helps me with incident response or remediation because since I have clear visibility of the issues, they are really easy to pinpoint, allowing me to quickly find out where this change comes from and who made it, so anything that stands out is very fast and its actionability is really fast.
Upwind's reporting and dashboard capabilities meet my needs because the reports are really useful for both my technicians and my senior management team.
My advice to others looking into using Upwind is to invest some time at the beginning and not rush into having everything. Instead, spend your time in each of the functionalities, learn how it works and where the options are.
I gave this review a rating of eight.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Runtime context has transformed how we prioritize exploitable cloud risks and protect workloads
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Upwind for around a year, approximately ten months.
What other advice do I have?
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.