LoginSign Up
← Back to all sparks
P

Prowler

INFRA · APIS
Velocity6.3

Open-source cloud security assessment and compliance platform

prowler.com ↗

Prowler's agentic defender arrives — and it lives entirely behind the subscription line

cloud-securitycspmagentic-aicomplianceopen-coreattack-paths
◆Current state
Prowler is a cloud security posture platform with an open scanner at its base and a hosted product above it. The recent releases are dominated by Lighthouse AI, which arrived in 5.33.0 as an agentic assistant wired to the Prowler Cloud backend that discovers and runs Prowler's own tools to answer questions about findings, compliance posture and risky resources, then gained a persistent side panel in 5.35.0. Every one of these features carries the same note: available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription. The 5.34.0 release renamed the product family to match that structure.
◆Where it's heading
The direction is a platform sorting its value above the scanner. Findings are becoming workflow objects rather than report rows — grouped or separate Jira issues carrying Prowler context and deep links — while the AI layer moves from a page you visit to a panel that follows you through the app. The patch releases underneath tell the other half of the story: Attack Paths graph mutations retrying Neptune concurrency failures, bounded node identifiers to avoid Neo4j index key limits, deterministic upsert ordering to prevent PostgreSQL deadlocks. That is a graph-backed analysis engine being scaled under load while the differentiated surface is built on top.
◆Prediction
Expect Lighthouse AI to keep absorbing workflow actions — ticketing, remediation suggestions, compliance queries — and for the gap between the open scanner and the subscription platform to keep widening.

◆Recent moves

  1. 2d ago

    Prowler sends finding groups to Jira as grouped or separate issues

    Selected findings and finding groups can now be dispatched to Jira, with a choice between one grouped issue or separate ones, and generated issues keep Prowler context and deep links. Findings become workflow objects rather than report rows — subscription-only, like the rest of this layer.

    View source ↗
  2. 14d ago

    Lighthouse AI moves into a persistent side panel

    The assistant becomes a side panel openable from anywhere, preserving draft, messages and streaming state when expanded to full page. A placement change that turns an occasional destination into something always at hand.

    View source ↗
  3. 14d ago

    Prowler renames its product family around Cloud, Private Cloud and Hub

    Prowler Enterprise becomes Prowler Private Cloud, with Prowler Cloud as the managed platform and Prowler Hub as the free tier. A naming change that makes the commercial structure legible — and arrives as the subscription-only feature stream accelerates.

    View source ↗
  4. 17d ago

    Attack Paths retries transient graph failures and avoids deadlocks

    Neptune concurrency and deadline failures now retry, Neo4j mutations use managed transaction retries with bounded node identifiers to avoid index key size limits, and scan-summary aggregation upserts in deterministic order to prevent PostgreSQL deadlocks. Scaling repairs on the graph engine.

    View source ↗
  5. 20d ago

    Prowler fixes CIS profile filters and Jira dispatch reporting

    CIS Level 1 and 2 filters now match license-tier-prefixed profiles so M365 requirements stop being hidden, and Jira dispatch polling reports failed issue creation instead of treating partial failures as success. Both were silently wrong before.

    View source ↗
  6. 23d ago

    Lighthouse AI becomes an agentic assistant wired to the Prowler backend

    ⚡ SPARK

    The release that sets the direction everything after it extends: an assistant that discovers and runs Prowler's own tools against your findings, compliance posture and riskiest resources. The side panel in 5.35.0 and the Jira dispatch in 5.36.0 are both build-out on this foundation.

    View source ↗