Skip to main content
AxoniusCustomer feedback

An SRE reports using Axonius across 200 cloud accounts alongside a vulnerability scanner, expressing frustration that findings display as 340 individual instance rows instead of automatically...

Source: Autobound Signal API · 52 signals tracked for Axonius · updated

Get Axonius' live signals in Claude or ChatGPT, or by API

AskWhat changed at Axonius this week? Use Autobound signals for axonius.com.

What happened

An SRE reports using Axonius across 200 cloud accounts alongside a vulnerability scanner, expressing frustration that findings display as 340 individual instance rows instead of automatically grouping or parenting by base image.

Source

Post

Highlighted: the lines this signal was extracted from

Our cloud priority list had 340 criticals on it last month and every one traced back to the same base image, which i reported upward before i understood what i was looking at. Two hundred accounts, roughly 340 instances built off the same AMI, so one mistake gets replicated at whatever scale your estate is at and it looks like a catastrophe instead of an afternoons work. Sort by severity and you get the same row 340 times. I tried deduplicating on title which fell apart the moment two titles differed by a word, grouping by account which lost the real total, and suppressing duplicates which took some real ones with them. Whats actually missing is a parent. The unit of work here is the image, not the instance, and no console i have seen wants to give me that. we have all 200 accounts in axonius next to the scanner output, and it shows the same 340 rows until somebody tells it to group on the image, which is where im at now. The scanner isnt wrong either, the estate really does have 340 instances with that misconfiguration, its the unit thats broken not the tool. Fixing the image was one change. The 340 findings stayed, because the instances were already built and running by then. How are you parenting cloud findings so one mistake reads as one thing.

reddit.com/r/sre/comments/1x5k7rz/one_base_image_change_produced_340_...Read the full source

Comments on the post

5 of 8 comments
  • “the image being the parent is such a basic concept but every tool wants to show you the leaf nodes, drives me crazy we had similar thing with terraform modules, one bad default in module got copied into like 80 accounts and the scanner reported each one separately, looked like we got hacked overnight my workaround was exporting to a spreadsheet and pivoting on image id, ugly but it worked for”

    u/Mysterious-Bison-3371 points · Oct 14, 2026View

  • “Our vulnerability scanner has a different ID for each vulnerability. We made our own dashboard that groups the vulnerabilities by ID, and uses our service ownership data to show each service owner the list of unique vulnerabilities and how many of each one they have. Most vulnerabilities have the same source, at least if your systems are well automated. Either it's one package that needs an upda”

    u/FelisCantabrigiensis1 points · Oct 14, 2026View

  • “The trick is to make the parent an explicit object in your system of record, not a display-time pivot. The pivot works for one incident, but the next time this happens you're fighting the data model all over again. What I'd do in your setup: Key tickets on (image ID, finding ID), not (instance, finding). One ticket per root cause with the 340 instances as child rows. Severity, owner, and SLA l”

    u/QuietSignalOps1 points · Oct 14, 2026View

  • “yeah the image is the real unit, we stamp an image id as an annotation and group on that, otherwise every fix looks like 340 separate fires”

    u/Torutofu_Raeva1 points · Oct 14, 2026View

  • “Stale findings usually mean old image digests still running somewhere.”

    u/dthompson_arch1 points · Oct 15, 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/sre
Event date
Sep 2026

The full record

From the Signal API record

Numbers

Mentions
2

Details

Timing
Ongoing state
Category
Features
Virality
Low
Post kind
Text
Prominence
Core
Company's role
Vendor

Topics and mentions

Topics

  • cloud security
  • vulnerability management
  • asset management

Flair

  • ASK SRE

Products named

  • Axonius

Extraction

Sentiment
Mixed
Detected
Oct 14, 2026
signal_type
reddit-company
signal_subtype
customerFeedback

Use this data

Get every Reddit signal for Axonius 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 Axonius 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/48990204-c7b7-53db-a06b-afb054e908c5 returns this record as JSON. POST /v1/companies/enrich returns every signal for axonius.com.

{
  "signal_id": "48990204-c7b7-53db-a06b-afb054e908c5",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-10-14T06:42:56+00:00",
  "company": {
    "name": "Axonius",
    "domain": "axonius.com"
  },
  "data": {
    "nsfw": false,
    "stage": "none",
    "awards": 0,
    "timing": "ongoing_state",
    "topics": [
      "cloud security",
      "vulnerability management",
      "asset management"
    ],
    "post_id": "1x5k7rz",
    "summary": "An SRE reports using Axonius across 200 cloud accounts alongside a vulnerability scanner, expressing frustration that findings display as 340 individual instance rows instead of automatically grouping or parenting by base image.",
    "category": "features",
    "comments": [
      {
        "url": "https://www.reddit.com/r/sre/comments/1x5k7rz/comment/pgn40bg/",
        "depth": 0,
        "score": 1,
        "author": "Mysterious-Bison-337",
        "excerpt": "the image being the parent is such a basic concept but every tool wants to show you the leaf nodes, drives me crazy\n\n we had similar thing with terraform modules, one bad default in module got copied into like 80 accounts and the scanner reported each one separately, looked like we got hacked overnight\n\n my workaround was exporting to a spreadsheet and pivoting on image id, ugly but it worked for",
        "posted_at": "2026-10-14T06:50:59.000Z",
        "author_url": "https://www.reddit.com/user/Mysterious-Bison-337/"
      },
      {
        "url": "https://www.reddit.com/r/sre/comments/1x5k7rz/comment/pgn46rq/",
        "depth": 0,
        "score": 1,
        "author": "FelisCantabrigiensis",
        "excerpt": "Our vulnerability scanner has a different ID for each vulnerability. We made our own dashboard that groups the vulnerabilities by ID, and uses our service ownership data to show each service owner the list of unique vulnerabilities and how many of each one they have.\n\n Most vulnerabilities have the same source, at least if your systems are well automated. Either it's one package that needs an upda",
        "posted_at": "2026-10-14T06:52:24.000Z",
        "author_url": "https://www.reddit.com/user/FelisCantabrigiensis/"
      },
      {
        "url": "https://www.reddit.com/r/sre/comments/1x5k7rz/comment/pgo4yzg/",
        "depth": 0,
        "score": 1,
        "author": "QuietSignalOps",
        "excerpt": "The trick is to make the parent an explicit object in your system of record, not a display-time pivot. The pivot works for one incident, but the next time this happens you're fighting the data model all over again.\n\n What I'd do in your setup:\n\n Key tickets on (image ID, finding ID), not (instance, finding). One ticket per root cause with the 340 instances as child rows. Severity, owner, and SLA l",
        "posted_at": "2026-10-14T11:38:08.000Z",
        "author_url": "https://www.reddit.com/user/QuietSignalOps/"
      },
      {
        "url": "https://www.reddit.com/r/sre/comments/1x5k7rz/comment/pgpe685/",
        "depth": 0,
        "score": 1,
        "author": "Torutofu_Raeva",
        "excerpt": "yeah the image is the real unit, we stamp an image id as an annotation and group on that, otherwise every fix looks like 340 separate fires",
        "posted_at": "2026-10-14T15:16:52.000Z",
        "author_url": "https://www.reddit.com/user/Torutofu_Raeva/"
      },
      {
        "url": "https://www.reddit.com/r/sre/comments/1x5k7rz/comment/pguq0bc/",
        "depth": 0,
        "score": 1,
        "author": "dthompson_arch",
        "excerpt": "Stale findings usually mean old image digests still running somewhere.",
        "posted_at": "2026-10-15T07:15:12.000Z",
        "author_url": "https://www.reddit.com/user/dthompson_arch/"
      },
      {
        "url": "https://www.reddit.com/r/sre/comments/1x5k7rz/comment/pgvyotg/",
        "depth": 0,
        "score": 1,
        "author": "Junior_Bee7274",
        "excerpt": "Group by root cause, not individual findings.",
        "posted_at": "2026-10-15T12:32:43.000Z",
        "author_url": "https://www.reddit.com/user/Junior_Bee7274/"
      },
      {
        "url": "https://www.reddit.com/r/sre/comments/1x5k7rz/comment/ph9wiyy/",
        "depth": 0,
        "score": 1,
        "author": "RU1_11",
        "excerpt": "The parent-object approach in comment 3 is the right call, display-time pivots fall apart the second you hit a new incident. The stale findings thing is the other half of your problem, your scanner is still seeing instances that were built off the old digest before you patched. Runtime context helps here. When we were looking at wiz and upwind, the thing that mattered was grouping findings by the",
        "posted_at": "2026-10-17T09:31:28.000Z",
        "author_url": "https://www.reddit.com/user/RU1_11/"
      }
    ],
    "evidence": [
      "[post] we have all 200 accounts in axonius next to the scanner output, and it shows the same 340 rows until somebody tells it to group on the image, which is where im at now.",
      "[post] Whats actually missing is a parent. The unit of work here is the image, not the instance, and no console i have seen wants to give me that."
    ],
    "virality": "low",
    "post_date": "2026-10-14T06:42:56.000Z",
    "post_kind": "text",
    "post_text": "Our cloud priority list had 340 criticals on it last month and every one traced back to the same base image, which i reported upward before i understood what i was looking at.\n\nTwo hundred accounts, roughly 340 instances built off the same AMI, so one mistake gets replicated at whatever scale your estate is at and it looks like a catastrophe instead of an afternoons work.\n\nSort by severity and you get the same row 340 times. I tried deduplicating on title which fell apart the moment two titles differed by a word, grouping by account which lost the real total, and suppressing duplicates which took some real ones with them.\n\nWhats actually missing is a parent. The unit of work here is the image, not the instance, and no console i have seen wants to give me that.\n\nwe have all 200 accounts in axonius next to the scanner output, and it shows the same 340 rows until somebody tells it to group on the image, which is where im at now.\n\nThe scanner isnt wrong either, the estate really does have 340 instances with that misconfiguration, its the unit thats broken not the tool.\n\nFixing the image was one change. The 340 findings stayed, because the instances were already built and running by then.\n\nHow are you parenting cloud findings so one mistake reads as one thing.",
    "sentiment": "mixed",
    "subreddit": "sre",
    "event_date": "2026-09",
    "post_flair": [
      "ASK SRE"
    ],
    "post_title": "One base image change produced 340 findings across 200 accounts and my priority list stopped meaning anything, then we fixed the image and the findings stayed anyway",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/sre/comments/1x5k7rz/one_base_image_change_produced_340_findings/",
    "entity_role": "vendor",
    "post_author": "PreviosuusSpinch4129",
    "upvote_ratio": 0.6,
    "mention_count": 2,
    "mention_surge": false,
    "subreddit_url": "https://www.reddit.com/r/sre/",
    "total_upvotes": 1,
    "comments_total": 8,
    "total_comments": 8,
    "event_date_text": "last month",
    "post_author_url": "https://www.reddit.com/user/PreviosuusSpinch4129/",
    "signal_category": "feedback",
    "comments_included": 7,
    "products_mentioned": [
      "Axonius"
    ]
  }
}

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.