Listing Thumbnail

    Upwind for AWS Security Hub Extended

     Info
    Upwind secures your entire cloud from deployments, configurations, and applications through a runtime fabric that transforms every layer in cloud security. When you understand what actually runs, you can cut through the noise and protect what really matters, prioritize security risks based on real usage, and detect threats in real time.
    4.8

    Overview

    Play video

    Upwind secures your entire cloud, from configurations and deployments to applications and runtime, through a runtime fabric that transforms cloud security from the inside out.

    Upwind combines agentless and sensor based scanning to secure your cloud deployments, configurations, and applications through a runtime fabric that provides real-time visibility from the inside out. You get a live map of your network and application topology, can prioritize fixes based on real usage, and detect threats as they happen across cloud configurations (CSPM), vulnerabilities,

    With Upwind, security, dev, and ops teams move faster, stay focused, and fix risks that matter most.

    Highlights

    • Upwind combines agentless scanning with real-time sensors to give you complete coverage without tradeoffs. That means CSPM, vulnerability management, container security, runtime protection, and attack surface management, across multi-cloud and on-prem, all in one platform.
    • By pairing runtime context with agentless scanning, Upwind reduces cloud risk noise by 95%. Risk prioritization improves by 10x.
    • Mean time to detect drops. Mean time to resolution drops. And every fix your team makes is grounded in what's actually running, not what might theoretically be at risk.

    Details

    Delivery method

    Deployed on AWS
    New

    Introducing multi-product solutions

    You can now purchase comprehensive solutions tailored to use cases and industries.

    Multi-product solutions

    Features and programs

    Trust center

    Trust center
    Access real-time vendor security and compliance information through their Trust Center powered by Drata or Vanta. Review certifications and security standards before purchase.

    Buyer guide

    Gain valuable insights from real users who purchased this product, powered by PeerSpot.
    Buyer guide

    Financing for AWS Marketplace purchases

    AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
    Financing for AWS Marketplace purchases

    Pricing

    Upwind for AWS Security Hub Extended

     Info
    Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time.
    Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator  to estimate your infrastructure costs.

    Usage costs (1)

     Info
    Dimension
    Description
    Cost/unit
    Units protected by Upwind
    Count of assets scanned by Upwind
    $3.75

    AI Insights

     Info

    Dimensions summary

    This listing uses a single usage-based pricing dimension. You pay based on the count of assets, called Units, that Upwind scans and protects. Your cost scales directly with how many assets you monitor. As you add cloud resources, services, or workloads to protection, your Unit count rises and your bill grows with it. There are no separate tiers or fixed packages here — pricing tracks your actual protected footprint. This structure lets your spend match the size of the environment you secure, whether that footprint expands or contracts over time.

    Top-of-mind questions for buyers

    A Unit is any asset the platform scans and protects. This includes cloud resources like compute instances, container workloads, managed databases, and cloud services. Each discovered asset counts toward your total. As the platform inventories your environment, every protected resource adds to your Unit count.
    Your bill tracks your active protected asset count. Adding cloud resources, services, or workloads raises your Unit count and increases your cost. Removing assets from protection lowers your count. There is no fixed package to exceed. Charges follow your actual protected footprint as it grows or shrinks.
    Your Unit count reflects the assets scanned and protected, not the tools you connect. The platform links to ticketing, messaging, and CI/CD systems without adding Units. Only the count of protected assets drives your bill. Integrations enrich findings but do not directly change what you pay.
    www.upwind.io+1
    Helpful?

    Vendor refund policy

    Please contact the Upwind Sales team via email at sales@upwind.io  .

    How can we make this page better?

    Tell us how we can improve this page, or report an issue with this product.
    Tell us how we can improve this page, or report an issue with this product.

    Legal

    Vendor terms and conditions

    Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .

    Content disclaimer

    Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.

    Usage information

     Info

    Delivery details

    Software as a Service (SaaS)

    SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.

    Resources

    Vendor resources

    Support

    Vendor support

    Included in your contract, Upwind provides 24/7 live chat support, onboarding, and continuous enablement. Onboarding includes integration setup, assistance configuring the platform, and guidance on utilizing it to serve you in your cloud security journey. You can also contact our support team via email at support@upwind.io  .

    AWS infrastructure support

    AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

    Similar products

    Customer reviews

    Ratings and reviews

     Info
    4.8
    4 ratings
    5 star
    4 star
    3 star
    2 star
    1 star
    100%
    0%
    0%
    0%
    0%
    4 AWS reviews
    Francisco Pulido

    Automation has transformed cloud vulnerability monitoring and has reduced response times

    Reviewed on Sep 17, 2026
    Review from a verified AWS customer

    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?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Mohammed Mudasser

    Runtime context has transformed how we prioritize exploitable cloud risks and protect workloads

    Reviewed on Aug 21, 2026
    Review from a verified AWS customer

    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.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Guy Fridman

    Gaining Confidence in Cloud Security with Improved Vulnerability Management

    Reviewed on May 09, 2025
    Review from a verified AWS customer

    What is our primary use case?

    I have several use cases for Upwind. I will start with our private cloud that is based on Kubernetes, so we're using it also for Cloud Detection and Response and also for vulnerability scanning. We're also using it on our cloud provider as a CSPM.

    For Cloud Detection and Response, one of the biggest challenges is to have detection around containers, which we were missing visibility on, and with Upwind, we get it. Related to the vulnerability, because of the strong runtime sensor Upwind developed, it helps us to reduce many of the vulnerabilities that were classified by the shift left product that we used.

    What is most valuable?

    In general, I think that Upwind as a product makes a disruption in the concept of shift left; they come with a new approach by the runtime sensor that they made, making life for the AppSec team much easier.

    It's a good question about the best features Upwind offers, but in general, they build a great product. One feature I can think about is their very strong API, allowing us to export most of the data to crunch and work with it. To me, having a wide API to interact with the data is very important.

    In general, we use the API to export the asset and then compare it with our findings to improve triage, ensuring we are not missing anything. This is one of the main use cases for the API.

    Having access to this API changes our team's efficiency dramatically; programmability makes everyone's life much easier. The operation reduces because of the time that analysts need to spend on triaging, and it also minimizes friction with developers, which is something Upwind helps us with.

    Upwind positively impacts our organization overall by helping with the CIS benchmark for Kubernetes, which is definitely one of the strongest parts. Second, by reducing the number of vulnerabilities, we automatically reduce the number of tickets opened with the dev team, which is a big win. It also helps us to tune our vulnerability program better regarding classification and priority.

    What needs improvement?

    Currently, we are working with Upwind on API security, which is something we want them to keep pushing. We also want them to be able to record SSH sessions; it's a tough request.

    For how long have I used the solution?

    We have been using Upwind for over a year now.

    What was my experience with deployment of the solution?

    The deployment of Upwind was easy peasy.

    The configuration process was pretty straightforward with no challenges.

    What do I think about the stability of the solution?

    Upwind is stable in my experience; I haven't faced any downtime or reliability issues.

    What do I think about the scalability of the solution?

    Upwind's scalability is transparent for me; I haven't faced any workload issues.

    How are customer service and support?

    From my experience, Upwind has the best support as a vendor; their response time is less than 2 minutes from the moment you slack them.

    I would rate the customer support a 10.

    Which solution did I use previously and why did I switch?

    We currently also work with customers, but I can't really disclose the names of previous solutions we used before Upwind.

    How was the initial setup?

    In terms of proof of value, we see results very fast after implementing Upwind; the deployment is quite simple and doesn't require a lot of time. We start a POC for 2 months, and then we roll out to production in 2 to 2 and a half months in our huge production environment. Related to the vulnerability feature, again, with a strong runtime sensor, you can see the value pretty fast.

    In terms of the daily day-to-day operation, Upwind has helped us a lot; even at the beginning, we needed to build a process around it because it's something new, but I would say that we feel much more confident knowing what is running in our Kubernetes environment. Related to the critical vulnerabilities, it has helped us to reduce about 70% of the critical vulnerabilities.

    What was our ROI?

    Both the licensing process and ROI were very simple, making sense overall.

    We compare the return on investment with Upwind versus other companies, but I cannot disclose the specifics.

    What's my experience with pricing, setup cost, and licensing?

    The pricing, setup cost, and licensing process were pretty reasonable.

    Which other solutions did I evaluate?

    Before choosing Upwind, I evaluated Twistlock.

    What other advice do I have?

    My company does not have a business relationship with this vendor other than being a customer.

    What I would change right now is nothing; I'm okay.

    The work with Upwind is very collaborative; analysts work closely with them to make things easier for us as a company and for other companies using Upwind. In terms of time saving, it definitely saves many hours. I struggle to quantify it in numbers.

    We did not purchase Upwind through the AWS Marketplace.

    Currently, there is no integration with other AWS services, so I cannot comment.

    The procurement process was pretty easy and straightforward.

    I haven't encountered any surprises regarding the metering and billing experience; everything is clear with our 2-year contract, so we are good to go.

    It's hard to dig into it, but I estimate that the number of tickets opened with our dev team drops by probably 30 to 40% after using Upwind.

    My advice for others looking into using Upwind is that if you are seeking a strong CNAPP with an advanced runtime and strong CDR capabilities, this is the product.

    On a scale of 1-10, I rate Upwind a 10.

    reviewer2702562

    Increased compliance and visibility boost cloud security posture

    Reviewed on May 05, 2025
    Review from a verified AWS customer

    What is our primary use case?

    We use Upwind for runtime security in our cloud environments. We also use Upwind for cloud security posture management, API security, and cloud vulnerability management.

    What is most valuable?

    Upwind has great runtime detection and response capabilities for our cloud workloads. It provides great context for vulnerability management, allowing us to see what our most important vulnerabilities are. Upwind gives us insight into API security threats and helps us identify misconfigurations in our cloud environments to align with security frameworks like CIS or NIST. With Upwind, we have greatly increased our cloud security posture. Our compliance rates have improved significantly, and they have helped us automate vulnerability management and gain insights into API endpoint security.

    What needs improvement?

    Upwind just needs to continue on the path they are on. They have some really great ideas and need to keep refining their different tool sets and add to their reporting and automation. However, they have a strong platform as it is.

    For how long have I used the solution?

    I started using Upwind a couple of years ago.

    What was my experience with deployment of the solution?

    It was very easy for us to deploy. Their deployment is much more modern and automated than others that we have seen.

    What do I think about the stability of the solution?

    Absolutely, Upwind is stable.

    What do I think about the scalability of the solution?

    Upwind scales great for us. It is deployed in such a way that whenever we build something new, it automatically deploys to those new resources, and we really don't have to touch it much. So, it scales really well.

    How are customer service and support?

    Customer support is fantastic. We have a very good relationship with the Upwind team. They are always timely in their response and provide direct integration with us via Slack. Whenever we have issues, they are right there to support us.

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    Yes, we did. We used another cloud security provider. We switched because they were a more legacy provider and their integrations were not as modern or capable. Their runtime alerting did not surface the same amount of detail or events, and we felt Upwind was cloud-first, which aligns with our company's cloud-first direction.

    How was the initial setup?

    The initial setup was fairly straightforward. Pretty much everything was done via infrastructure as code, using either Terraform or CloudFormation. It was as easy as applying those templates to our environment.

    What was our ROI?

    Upwind has definitely saved us a lot of time in reviewing the findings with the posture findings. It also saved us time in vulnerability management by significantly lowering the number of vulnerabilities we need to focus on, reducing the time required to address critical issues.

    What's my experience with pricing, setup cost, and licensing?

    Pricing, setup costs, and licensing were very fair.

    What other advice do I have?

    I would just say it's a great product. They have greatly improved our visibility. They are great to work with. They are a great overall cloud security platform and they continue innovating and adding new features. I would rate the overall solution a 10 out of 10.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    View all reviews