Skip to main content
WizCustomer feedback

Engineering leadership evaluated Wiz and Upwind at AWS re:Invent, though the security lead felt Wiz's demo resembled mostly a pretty graph with unclear Lambda correlation.

Source: Autobound Signal API · 96 signals tracked for Wiz · updated

Get Wiz's live signals in Claude or ChatGPT, or by API

AskWhat changed at Wiz this week? Use Autobound signals for wiz.io.

What happened

Post: "Is guardDuty runtime monitoring enough for EKS + Lambda, or do you still need a cnapp on top?"

Source

Post

Highlighted: the lines this signal was extracted from

We're about 70 engineers, all AWS, two orgs worth of accounts (prod and everything else). Workloads are mostly EKS with a long tail of lambda and a few ECS services nobody wants to touch. Security is me plus one contractor. Right now we have guardduty runtime monitoring turned on for EKS, security hub aggregating, and inspector scanning ECR. Leadership saw a few CNAPP demos at re:Invent last year (upwind and wiz mainly; wiz's felt like mostly a pretty graph) and the question i've been handed is basically "why are we paying for guardduty AND looking at another tool". My honest problem is that the AWS-native stack gives me findings but not much context. Inspector says a container has 400 criticals, guardduty tells me a pod made a weird DNS call, and connecting those two into "this exposed service is running a vulnerable package that's actually loaded" is me in athena on a friday night. what im trying to figure out: -For people who stayed aws-native, whtat did you build to get the correlation, and was it worth it? -For people who added a cnapp, did you turn guardduty runtime off afterwards or keep both? -Where does lambda coverage actually land with the third-party tools? that's when im least sure. not looking for a vendor pitch, just what it looks like six months in..

Also quoted as evidence

  • [comment u/Comfortable-Way-6271] wiz was alright too but flagged alot of lambda "risks" that were really jst unused layers, the real difference was with eks tho thats wher

reddit.com/r/aws/comments/1xmpsbr/is_guardduty_runtime_monitoring_eno...Read the full source

Comments on the post

5 of 22 comments
  • “You want to turn on Security Hub too (not Security Hub CSPM, that’s the old one) - it will help you identify exposures which will link up this configuration makes a CVE an issue (exposure). It’s a big task and a lot of work. With 70 devs (assuming they are delivering at a rate) a team of 2 might be too small to be getting to a baseline.”

    u/BronzePainter21309 points · Nov 3, 2026View

  • “Thanks for asking about Lambda separately, because it does not follow the EKS picture. Runtime Monitoring lists EKS, ECS on Fargate and EC2, and Lambda is not on that list. On the AWS side, Lambda Protection reads network activity logs from Lambda functions in the account where you enable it, VPC or not, and raises findings on suspicious traffic. Inspector standard scanning checks function and l”

    u/rahulladumor5 points · Nov 3, 2026View

  • “You can stitch together all the native tools and sometimes in an incident you’ll have what you need and sometimes you won’t. Something like wiz generally, if set up right, means you’ll have what you need I’d be asking your incident response team to be at the table for this, not just engineers”

    u/IllThrowYourAway4 points · Nov 3, 2026View

  • “I think you have a social problem, not a tool problem, to resolve first. If you’re seeing containers with hundreds of critical CVEs, you need those 70 developers to share responsibility for routine patching so you’re working on the higher-level tasks. That kind of thing should be weekly pipelines, not you having to nag someone after reading Inspector for them. Security Hub does some of the kind”

    u/acdha3 points · Nov 3, 2026View

  • “GuardDuty alone is not enough but I think you can absolutely skip a SaaS CNAPP if you embrace the aws-native tools fully alongside some open-source tools. To get the correlations you're asking about we built a tool which I hope you'd find useful: github.com/cynative/cynative”

    u/cynative_ben2 points · Nov 3, 2026View

Extracted by Autobound

From the Signal API record
Signal
Customer feedback

What this signalsUser posts often show product pain before it reaches reviews or churn.

Subreddit
r/aws
Stage
Considering
Event date
Nov 2025

Companies

  • Amazon Web ServicesAlso named
  • Upwind SecurityAlso named

The full record

From the Signal API record

Numbers

Mentions
1

Details

Timing
Completed
Category
Features
Virality
Somewhat high
Post kind
Text
Prominence
Core
Company's role
Vendor

Topics and mentions

Topics

  • cloud security
  • evaluation
  • cnapp

Flair

  • discussion

Products named

  • Wiz

Extraction

Sentiment
Mixed
Detected
Nov 3, 2026
signal_type
reddit-company
signal_subtype
customerFeedback

Use this data

Get every Reddit signal for Wiz and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Wiz this week?”

  2. Send it to your own tools

    The Signal API returns Reddit signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full reddit-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/9e5d1508-8887-53a9-a1d3-39e62491f85a returns this record as JSON. POST /v1/companies/enrich returns every signal for wiz.io.

{
  "signal_id": "9e5d1508-8887-53a9-a1d3-39e62491f85a",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-11-03T10:46:40+00:00",
  "company": {
    "name": "Wiz",
    "domain": "wiz.io"
  },
  "data": {
    "nsfw": false,
    "stage": "considering",
    "awards": 0,
    "timing": "completed",
    "topics": [
      "cnapp",
      "cloud security",
      "evaluation"
    ],
    "post_id": "1xmpsbr",
    "summary": "Engineering leadership evaluated Wiz and Upwind at AWS re:Invent, though the security lead felt Wiz's demo resembled mostly a pretty graph with unclear Lambda correlation.",
    "category": "features",
    "comments": [
      {
        "url": "https://www.reddit.com/r/aws/comments/1xmpsbr/comment/19s2q2oirak3p/",
        "depth": 0,
        "score": 9,
        "author": "BronzePainter2130",
        "excerpt": "You want to turn on Security Hub too (not Security Hub CSPM, that’s the old one) - it will help you identify exposures which will link up this configuration makes a CVE an issue (exposure). It’s a big task and a lot of work. With 70 devs (assuming they are delivering at a rate) a team of 2 might be too small to be getting to a baseline.",
        "posted_at": "2026-11-03T11:03:41.000Z",
        "author_url": "https://www.reddit.com/user/BronzePainter2130/"
      },
      {
        "url": "https://www.reddit.com/r/aws/comments/1xmpsbr/comment/19s2qqtie4qwx/",
        "depth": 0,
        "score": 5,
        "author": "rahulladumor",
        "excerpt": "Thanks for asking about Lambda separately, because it does not follow the EKS picture. Runtime Monitoring lists EKS, ECS on Fargate and EC2, and Lambda is not on that list.\n\n On the AWS side, Lambda Protection reads network activity logs from Lambda functions in the account where you enable it, VPC or not, and raises findings on suspicious traffic. Inspector standard scanning checks function and l",
        "posted_at": "2026-11-03T11:18:43.000Z",
        "author_url": "https://www.reddit.com/user/rahulladumor/"
      },
      {
        "url": "https://www.reddit.com/r/aws/comments/1xmpsbr/comment/19s2uxi3762x0/",
        "depth": 0,
        "score": 4,
        "author": "IllThrowYourAway",
        "excerpt": "You can stitch together all the native tools and sometimes in an incident you’ll have what you need and sometimes you won’t. Something like wiz generally, if set up right, means you’ll have what you need\n\n I’d be asking your incident response team to be at the table for this, not just engineers",
        "posted_at": "2026-11-03T12:52:34.000Z",
        "author_url": "https://www.reddit.com/user/IllThrowYourAway/"
      },
      {
        "url": "https://www.reddit.com/r/aws/comments/1xmpsbr/comment/19s2xg140hf7l/",
        "depth": 0,
        "score": 3,
        "author": "acdha",
        "excerpt": "I think you have a social problem, not a tool problem, to resolve first. If you’re seeing containers with hundreds of critical CVEs, you need those 70 developers to share responsibility for routine patching so you’re working on the higher-level tasks. That kind of thing should be weekly pipelines, not you having to nag someone after reading Inspector for them.\n\n Security Hub does some of the kind",
        "posted_at": "2026-11-03T13:48:56.000Z",
        "author_url": "https://www.reddit.com/user/acdha/"
      },
      {
        "url": "https://www.reddit.com/r/aws/comments/1xmpsbr/comment/19s2un41pj70l/",
        "depth": 0,
        "score": 2,
        "author": "cynative_ben",
        "excerpt": "GuardDuty alone is not enough but I think you can absolutely skip a SaaS CNAPP if you embrace the aws-native tools fully alongside some open-source tools.\n\n To get the correlations you're asking about we built a tool which I hope you'd find useful: github.com/cynative/cynative",
        "posted_at": "2026-11-03T12:46:05.000Z",
        "author_url": "https://www.reddit.com/user/cynative_ben/"
      },
      {
        "url": "https://www.reddit.com/r/aws/comments/1xmpsbr/comment/19s2rnpk6o283/",
        "depth": 0,
        "score": 2,
        "author": "pint",
        "excerpt": "guardduty does very little on its own. first, it will never catch everything, since many malicious activities look exactly like legit ones. second, it is only an observation tool, so by the time you learn about an issue, it might be way too late.\n\n i consider guardduty as a \"why not\" option, because it is very cheap, and because it can \"cheat\" and see logs and data flows even when they are turned",
        "posted_at": "2026-11-03T11:39:12.000Z",
        "author_url": "https://www.reddit.com/user/pint/"
      },
      {
        "url": "https://www.reddit.com/r/aws/comments/1xmpsbr/comment/19s2pu68j0400/",
        "depth": 0,
        "score": 2,
        "author": "DickBrainTime",
        "excerpt": "For a two-person security team I'd run a small proof before buying another platform. Pick three cases: an internet-exposed EKS service with a reachable CVE, suspicious activity inside a pod, and a Lambda finding. Compare how quickly each setup connects exposure, runtime activity and vulnerability context, plus how much custom correlation you have to maintain.\n\n I'd keep GuardDuty enabled during th",
        "posted_at": "2026-11-03T10:58:23.000Z",
        "author_url": "https://www.reddit.com/user/DickBrainTime/"
      },
      {
        "url": "https://www.reddit.com/r/aws/comments/1xmpsbr/comment/19s2vudffhsu9/",
        "depth": 0,
        "score": 1,
        "author": "galnar",
        "excerpt": "Wiz has a new runtime sensor for Lambda, you should take a look.",
        "posted_at": "2026-11-03T13:13:02.000Z",
        "author_url": "https://www.reddit.com/user/galnar/"
      }
    ],
    "evidence": [
      "[post] Leadership saw a few CNAPP demos at re:Invent last year (upwind and wiz mainly; wiz's felt like mostly a pretty graph) and the question i've been handed is basically \"why are we paying for guardduty AND looking at another tool\".",
      "[comment u/Comfortable-Way-6271] wiz was alright too but flagged alot of lambda \"risks\" that were really jst unused layers, the real difference was with eks tho thats wher"
    ],
    "virality": "somewhat_high",
    "post_date": "2026-11-03T10:46:40.000Z",
    "post_kind": "text",
    "post_text": "We're about 70 engineers, all AWS, two orgs worth of accounts (prod and everything else). Workloads are mostly EKS with a long tail of lambda and a few ECS services nobody wants to touch. Security is me plus one contractor.\n\nRight now we have guardduty runtime monitoring turned on for EKS, security hub aggregating, and inspector scanning ECR. Leadership saw a few CNAPP demos at re:Invent last year (upwind and wiz mainly; wiz's felt like mostly a pretty graph) and the question i've been handed is basically \"why are we paying for guardduty AND looking at another tool\".\n\nMy honest problem is that the AWS-native stack gives me findings but not much context. Inspector says a container has 400 criticals, guardduty tells me a pod made a weird DNS call, and connecting those two into \"this exposed service is running a vulnerable package that's actually loaded\" is me in athena on a friday night.\n\nwhat im trying to figure out: -For people who stayed aws-native, whtat did you build to get the correlation, and was it worth it? -For people who added a cnapp, did you turn guardduty runtime off afterwards or keep both? -Where does lambda coverage actually land with the third-party tools? that's when im least sure.\n\nnot looking for a vendor pitch, just what it looks like six months in..",
    "sentiment": "mixed",
    "subreddit": "aws",
    "event_date": "2025-11",
    "post_flair": [
      "discussion"
    ],
    "post_title": "Is guardDuty runtime monitoring enough for EKS + Lambda, or do you still need a cnapp on top?",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/aws/comments/1xmpsbr/is_guardduty_runtime_monitoring_enough_for_eks/",
    "entity_role": "vendor",
    "post_author": "TotGaH",
    "upvote_ratio": 0.9375,
    "mention_count": 1,
    "mention_surge": false,
    "subreddit_url": "https://www.reddit.com/r/aws/",
    "total_upvotes": 30,
    "comments_total": 22,
    "total_comments": 22,
    "event_date_text": "last year",
    "other_companies": [
      {
        "name": "Amazon Web Services",
        "role": "incumbent",
        "domain": "amazon.com"
      },
      {
        "name": "Upwind Security",
        "role": "alternative",
        "domain": "upwind.io"
      }
    ],
    "post_author_url": "https://www.reddit.com/user/TotGaH/",
    "signal_category": "feedback",
    "comments_included": 17,
    "products_mentioned": [
      "Wiz"
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.