PAGES
← all tools
◆ CNAPP

Plerion

CDR findings, easier to find and easier to read: commercial

Plerion is a cloud security platform that detects and responds to infrastructure vulnerabilities and misconfigurations across multi-cloud environments.

Summary

Plerion is a commercial cloud-native application protection platform (CNAPPCNAPPA cloud-native application protection platform that combines checks across cloud configuration, workloads and development. It helps teams connect risks that separate tools might report apart.) run as a SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. service that scans AWS, Azure, GCP, and Kubernetes environments for misconfigurations, compliance gaps, and risky access. Onboarding is built for cloud and platform security teams rather than individual developers: GCP organizations can be connected with a single generated command using keyless Workload Identity Federation, or provisioned via Terraform, and it then discovers projects, scans organization-level resources, builds SBOMsSBOMsA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. and scans for secrets in container images across Kubernetes workloads. It maps findings to compliance frameworks like PCI DSSPCI DSSThe Payment Card Industry Data Security Standard, security requirements for protecting payment account data. It covers organizations that store, process or transmit that data and relevant service providers. 4.0.1, NIST SP 800-53, and CISCISA nonprofit that publishes consensus-based configuration benchmarks and controls for hardening operating systems, cloud environments, and software; cyber tools use it as a ready-made compliance baseline. benchmarks, and includes an access-review workflow that inventories external grants across AWS sharing mechanisms and tracks remediation decisions with audit history. Its release history shows 18 updates in the tracked window, indicating active, ongoing development.

Plerion is a cloud security platform that detects and responds to infrastructure vulnerabilities and misconfigurations across multi-cloud environments.

How Plerion helps

Which of my cloud accounts have configurations that fail PCI DSS, NIST, or CIS benchmarks?

maps every scanned resource across AWS, Azure, GCP, and Kubernetes against the current detection catalog for each framework and reports a control-by-control pass or fail, with posture percentages that shift as mappings are rebuilt

Which external parties have standing access into my AWS accounts?

inventories every resource policy, role trust policy, Resource Access Manager share, and directly-attached cross-account permission across 97 resource types and flags any grant to a principal not marked trusted

Which container images in my Kubernetes workloads are carrying secrets or vulnerable packages?

builds a software bill of materials for every image across Deployments, DaemonSets, StatefulSets, Pods, Jobs, and CronJobs, and separately scans each for exposed API keys, tokens, and passwords with a severity rating

Are there GCP projects or resources nobody has reviewed for security posture?

discovers every project in the organization automatically, including ones created after onboarding, and scans organization-level IAM policy, folders, org policies, and VPC Service Controls perimeters

Is a given external access grant still justified, or has it drifted past when someone meant to check it?

tracks a keep, remove, review-later, or trust-until-review decision per grant with notes and a future review date, and surfaces any grant whose review date has passed

Which of my AI and machine learning services in GCP are misconfigured?

runs posture checks against Vertex AI, Vertex AI Workbench, Colab Enterprise, Agent Engine, Model Armor, Dialogflow CX, Cloud TPU, and related services, including org-policy guardrails on Workbench access and Model Garden use

all 39 features, with the evidence for each →

Languages

Not documented

Features

39 capabilities across 5 capability groups

Built from Plerion's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • Plerion covers 2 of the 8 data discovery and protection capabilities we track.
  • Plerion covers 3 of the 8 vulnerability assessment methods capabilities we track.

What Plerion offers you

  • Command-line interface2
  • Web management console2
  • CI/CD pipeline integration1
  • CSV data export1
  • Python scripting support1
  • REST API1
  • Role-based access control1
  • Scheduled jobs1
  • Scripting language support1
  • SIEM forwarding1
  • Ticketing integration1
  • User-defined detection rules1
Data access governance 2 features Data discovery and protection since 2026
Bedrock agent configuration posture checks shipped Raises findings for risky agent configurations, such as a gateway reachable without credentials or a memory store open to any AWS account. 6 releases · first seen Oct 2026

Shared capability: Data access governance

release

  • Adds PLERION-AWS-1202: AgentCore browser runs with an IAM execution role (new, Low) — flags browsers where a forged request or malicious page could expose the role's credentials; AWS-provided browser is skipped. changelog · Oct 2026 · source · release history
  • Adds PLERION-AWS-1201: AgentCore code interpreter runs with an IAM execution role (new, Low) — flags custom interpreters where code injection could expose AWS credentials; AWS-provided interpreter is skipped. changelog · Oct 2026 · source · release history
  • Raises findings for risky agent configuration, such as a gateway reachable without credentials or a memory store open to any AWS account. Seventeen SageMaker privilege escalation checks are removed: · Oct 2026 · source · release history
  • Updates AgentCore memory finding logic for publicly accessible resources using [PLERION-AWS-1195], rating High/Medium/Low based on required access identifiers 2026-10-04 · Oct 2026 · source · release history
  • Ratings apply to findings where anyone can read stored text with just the memory's ARN Know which vulnerabilities are likely to be exploited: · Oct 2026 · source · release history
  • Adds AgentCore memory access risk ratings (High, Medium, Low) based on open policy permissions Know which vulnerabilities are likely to be exploited: · Oct 2026 · source · release history
Public cloud storage exposure detection shipped Raises a top risk when Azure blob containers or Google Cloud Storage buckets are publicly readable on the internet, extending the coverage previously limited to S3 buckets. 1 release · first seen Nov 2026

Shared capability: Data access governance

release

  • Plerion now raises a top risk when an Azure blob container or a Google Cloud Storage bucket is publicly readable on the internet, extending coverage that previously applied only to S3 buckets.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Top risks now cover Azure and GCP storage: · Nov 2026 · source · release history
Sensitive data discovery 1 feature Data discovery and protection since 2026
GCP Compute Engine startup script secret detection shipped Reads Compute Engine instance startup scripts from metadata keys and fails the instance at Medium severity when a hard-coded credential is found, naming the metadata key in the finding. 1 release · first seen Nov 2026

Shared capability: Sensitive data discovery

release

  • Plerion adds a new GCP check (PLERION-GCP-340) that reads Compute Engine instance startup scripts from metadata keys startup-script, user-data, and the Windows startup and sysprep script keys, and fails the instance at Medium severity when a script holds a hard-coded credential — the finding names the metadata… Say hello to a new Compute Engine secret check: · Nov 2026 · source · release history
Static application security testing 1 feature Vulnerability assessment methods since 2026
SAST scanning for source code repositories shipped Enables static application security testing on Bitbucket, GitLab, and Azure DevOps integrations to scan Java, Kotlin, TypeScript, Python, Go, and other source files on default-branch and pull/merge request scans, reporting injection flaws and weak cryptography as findings and inline comments. 1 release · 2 other sources · first seen Oct 2026

Shared capability: Static application security testing

Also counts toward: CI/CD pipeline integration, Python scripting support, Scripting language support

release

  • Enable static application security testing for GitLab and Azure DevOps integrations to scan Java, Kotlin, TypeScript, Python, Go and other source files on default branch and merge or pull request scans, reporting injection flaws and weak cryptography as findings and inline comments; off by… IAM role fact check says Unknown when it cannot test the trust: · Oct 2026 · source · release history

example

  • Turn on SAST scanning for an existing GitLab or Azure DevOps integration so that every merge request automatically gets injection and weak-cryptography findings posted as inline comments. In the Plerion console, go to your GitLab or Azure DevOps integration page and enable 'SAST scanning'. IAM role fact check says Unknown when it cannot test the trust: · Oct 2026 · source
  • Enable SAST scanning on a Bitbucket integration so default-branch and pull-request scans surface injection flaws and weak cryptography in source code. In the Plerion console, go to Integrations > Bitbucket > [your integration] and turn on 'SAST scanning'. Custom checks, now in Terraform: · Oct 2026 · source
Container image vulnerability scanning 1 feature Vulnerability assessment methods since 2026
Amazon Bedrock AgentCore runtime scanning shipped Scans Amazon Bedrock AgentCore runtimes running container images or code-zip configurations for vulnerabilities, sensitive data, and SBOMs, with dedicated checks covering vulnerability severity, secret exposure, exploitability, and memory accessibility. 10 releases · 3 other sources · first seen Oct 2026

Shared capability: Container image vulnerability scanning

release 10 total

  • Scans container images and code inside AgentCore runtimes for exploitable vulnerabilities and secrets left in the image. Seventeen SageMaker privilege escalation checks are removed: · Oct 2026 · source · release history
  • Expands [PLERION-AWS-1195] AgentCore memory accessibility check to evaluate every read action an open policy allows, with findings rated High (ARN alone), Medium (ARN plus record or session ID), or Low (user and session IDs only). Know which vulnerabilities are likely to be exploited: · Oct 2026 · source · release history
  • Existing [PLERION-AWS-1195] AgentCore memory findings previously rated High may be downgraded to Medium or Low on the next scan under the revised severity logic. Know which vulnerabilities are likely to be exploited: · Oct 2026 · source · release history
  • Adds the PLERION-AWS-1195 check to detect publicly accessible Bedrock AgentCore memories via live cross-account verification. Say hello to a new AgentCore check: · Oct 2026 · source · release history
  • Enables code-zip AgentCore runtimes to be scanned like Lambda functions by turning on Bucket ABAC for the S3 bucket holding the zip and tagging it PlerionAccess: Granted. AgentCore runtimes get workload scanning: · Oct 2026 · source · release history
  • Adds ten new AWS checks (PLERION-AWS-1185 through PLERION-AWS-1194) covering low/medium/high/critical image vulnerabilities, low/medium/high/critical secret exposure, exploitable vulnerabilities, and known-exploited vulnerabilities for AgentCore runtime images. AgentCore runtimes get workload scanning: · Oct 2026 · source · release history

example

  • Audit an Amazon Bedrock AgentCore runtime end-to-end — from its IAM role to secrets in its container image — to understand the full blast radius if the agent is compromised. In Plerion, go to Agent Security > AgentCore Runtimes, select a runtime, then click through to Gateways, Tools, Memory, Guardrails, and IAM Role to trace the attack surface. Seventeen SageMaker privilege escalation checks are removed: · Oct 2026 · source
  • Scan an AgentCore container image runtime for vulnerabilities and secrets by ensuring Lambda scanning is enabled. Ensure 'Lambda scanning' is on for the Plerion integration containing the AgentCore runtime. AgentCore runtimes get workload scanning: · Oct 2026 · source
  • Enable scanning for an AgentCore runtime deployed from a code zip by sharing the bucket with Plerion. Turn on Bucket ABAC for the code zip bucket and tag it 'PlerionAccess: Granted'. AgentCore runtimes get workload scanning: · Oct 2026 · source
Infrastructure-as-code security scanning 1 feature Vulnerability assessment methods since 2026
IaC finding exemptions shipped Allows users to exempt infrastructure-as-code findings from Code Security checks (covering Terraform, CloudFormation, and other templates) by exempting individual findings or adding name exemptions scoped to a repository or a single file, so exempted findings are suppressed on all future scans. 1 release · 1 other source · first seen Oct 2026

Shared capability: Infrastructure-as-code security scanning

release

  • Exempt infrastructure-as-code findings from all 426 Code Security checks (Terraform, CloudFormation, and other template checks) by choosing Exempt on a finding or adding a name exemption to the code integration's profile — name exemptions scoped to a full repository (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ my-org/infra) or a… Exempt findings from your infrastructure as code: · Oct 2026 · source · release history

example

  • Permanently exempt a false-positive IaC finding scoped to a single Terraform file so it stays out of open findings on every future scan. In the Plerion console, open the finding (e.g. [PLERION-AWS-630] S3 bucket objects not encrypted with a KMS key), choose Exempt, then in the code integration's profile add a name exemption for… Exempt findings from your infrastructure as code: · Oct 2026 · source
Other / not yet classified 33 features Features we have not matched to a capability yet. A suggested match is marked.
AWS Well-Architected Reliability pillar checks shipped Evaluates live AWS resources against the Well-Architected Reliability pillar, covering backup configurations, Multi-AZ, replication, failover, redundancy, dead-letter queues, and deletion/termination protection across RDS, Aurora, DocumentDB, Neptune, ElastiCache, OpenSearch, Redshift, DynamoDB, CloudFront, VPN, SQS, EC2, and load balancers, with AutoFill integration that updates pillar answers on each daily run. 14 releases · first seen Oct 2026

Also counts toward: Scheduled jobs

release 14 total

  • Adds PLERION-AWS-1199: Auto Scaling group uses a single Availability Zone (new) — scanning appliance groups are skipped. changelog · Oct 2026 · source · release history
  • Adds PLERION-AWS-1197: RDS DB instance does not have deletion protection enabled (new) — instances inside a cluster are covered by the cluster check and skipped. changelog · Oct 2026 · source · release history
  • Adds PLERION-AWS-1200: VPC routes a subnet through a NAT gateway in another Availability Zone (new) — regional NAT gateways and VPCs without a NAT gateway are skipped. changelog · Oct 2026 · source · release history
  • Adds PLERION-AWS-1245: OpenSearch domain does not have zone awareness enabled (new, Low) — flags domains where a single AZ outage takes out every node. changelog · Oct 2026 · source · release history
  • Adds PLERION-AWS-1242: Route 53 hosted zone has a failover record without a health check (new, Medium) — finds hosted zones whose failover records lack a health check, causing Route 53 to treat the primary as always healthy.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ changelog · Oct 2026 · source · release history
  • Adds PLERION-AWS-1243: AWS service quota usage is at or above 80% (new, Medium) — covers EC2 On-Demand Standard vCPUs, Elastic IPs, VPCs per Region, and Lambda concurrent executions using 24-hour peak CloudWatch usage metrics. changelog · Oct 2026 · source · release history
Azure workload scanning shipped suggested Scans Azure App Service web apps, Virtual Machine Scale Sets, Container Apps, Container Instances, Batch pools, virtual machines, and functions for vulnerabilities, sensitive data, and SBOMs, with per-workload-type enablement, ACR image pull support, and attack path findings for publicly exposed workloads with high or critical vulnerabilities. 9 releases · 1 other source · first seen Sep 2026

Suggested capability: Credentialed vulnerability scanning. This is our guess, not confirmed.

release 9 total

  • Adds 8 new Azure checks for exploitable and known-exploited vulnerabilities in Container App, Container Instance, Batch pool images and Batch application packages. Azure workload scanning covers every workload family: · Sep 2026 · source · release history
  • Adds support for scanning Virtual Machine Scale Sets, Container Apps, Container Instances, Batch pools and App Service web apps in addition to existing virtual machines and functions coverage. Azure workload scanning covers every workload family: · Sep 2026 · source · release history
  • Extends vulnerability, sensitive data, and SBOM scanning to Azure App Service web apps, Virtual Machine Scale Sets, Container Apps, Container Instances, and Batch pools — in addition to the virtual machines and functions already covered.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Azure workload scanning covers every workload family: · seen Sep 2026 · source · release history
  • Grants AcrPull to the appliance identity via the install script so container images in Azure Container Registries can be pulled for scanning. Azure workload scanning covers every workload family: · seen Sep 2026 · source · release history
  • Enables each workload type individually under the subscription's workload scanning settings. Azure workload scanning covers every workload family: · seen Sep 2026 · source · release history
  • Generates attack path findings for publicly exposed workloads with high or critical vulnerabilities (PLERION-AZURE-446). Azure workload scanning covers every workload family: · seen Sep 2026 · source · release history

example

  • Enable scanning for newly supported workload types on an Azure subscription so Container Apps and Batch pools are included in vulnerability and SBOM assessments. In the Plerion console, go to the subscription's Workload Scanning Settings and toggle on 'App Service web apps', 'Container Apps', 'Container Instances', and 'Batch pools'. Azure workload scanning covers every workload family: · seen Sep 2026 · source
GCP posture and compliance checks shipped suggested Evaluates Google Cloud posture against CIS Google Cloud Platform Foundation Benchmark v5.0.0 and scans organization-level resources including IAM policies, folders, organization policies, and VPC Service Controls perimeters. 8 releases · first seen Oct 2026

Suggested capability: Data access governance. This is our guess, not confirmed.

release 8 total

  • The fact-check tab for PLERION-AWS-553 (IAM role publicly accessible) now shows Unknown instead of Non-factual when a role trusts GitHub Actions, Amazon Cognito, or an AWS account under a condition that blocked the assume-role test. IAM role fact check says Unknown when it cannot test the trust: · Oct 2026 · source · release history
  • The fact check for PLERION-AWS-244 (EBS snapshot publicly accessible) now batches snapshot visibility queries, retries longer, and runs only on failed findings, reducing the error rate caused by AWS rate limits. IAM role fact check says Unknown when it cannot test the trust: · Oct 2026 · source · release history
  • Fourteen fact checks retired — PLERION-AWS-568, PLERION-AWS-119, PLERION-AWS-570, PLERION-AWS-159, PLERION-AZURE-447, PLERION-AZURE-448, PLERION-GCP-94, PLERION-GCP-182, PLERION-GCP-196, PLERION-GCP-215, PLERION-GCP-240, PLERION-GCP-216, PLERION-GCP-213, and PLERION-GCP-311 — now derive… IAM role fact check says Unknown when it cannot test the trust: · Oct 2026 · source · release history
  • The fact check for PLERION-AWS-194 (EC2 instance publicly accessible) now sends an HTTP request through each listener that forwards to the instance's target group, promoting Unknown results to Factual or Non-factual based on actual reachability. IAM role fact check says Unknown when it cannot test the trust: · Oct 2026 · source · release history
  • Expands the Access logging filter on the Assets page and the matching custom-report field to cover API Gateway (PLERION-AWS-494, PLERION-AWS-799, PLERION-AWS-801), load balancers (PLERION-AWS-791, PLERION-AWS-792, PLERION-AWS-795), VPCs (PLERION-AWS-37) and EKS clusters (PLERION-AWS-107). Catch leaked AWS keys before someone runs up your Bedrock bill: · Oct 2026 · source · release history
  • Adds five new GCP IAM checks: PLERION-GCP-335 (external or public principal holds a folder-level or organization-level role), PLERION-GCP-336 (user, group, or domain holds an administrative role at folder or organization level), PLERION-GCP-337 (principal holds a basic role at folder or organization level),… More GCP IAM in your inventory: · Oct 2026 · source · release history
Sumo Logic integration shipped Sends workflow-selected findings (as they open, change, and resolve, with a weekly resend of all open findings) and tenant audit logs in real time to a Sumo Logic HTTP Source, with an on-demand Sync now action to push changes immediately. 6 releases · 2 other sources · first seen Oct 2026

Also counts toward: SIEM forwarding

release

  • The Send tenant audit logs checkbox on the Sumo Logic action is replaced by the Add audit log condition workflow condition; existing workflows that had the box ticked continue sending audit logs automatically. changelog · Oct 2026 · source · release history
  • Adds Add audit log condition as a workflow condition for Sumo Logic actions, allowing tenant audit logs to be sent independently or alongside finding conditions; replaces the former Send tenant audit logs checkbox on the Sumo Logic action. changelog · Oct 2026 · source · release history
  • Adds a Sumo Logic workflow integration that posts findings as they open, change, and resolve (with a weekly full resend), supports Send tenant audit logs to stream audit events in real time, and provides a Sync now option for immediate delivery. changelog · Oct 2026 · source · release history
  • Provides a Sync now action on the Sumo Logic integration to push changes immediately on demand. Global CBPR mapping refreshed: · Oct 2026 · source · release history
  • Adds a new Sumo Logic integration that posts to a Sumo Logic HTTP Source, sending workflow-selected findings as they open, change, and resolve, with every open finding resent weekly.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Global CBPR mapping refreshed: · Oct 2026 · source · release history
  • Enables sending tenant audit logs to Sumo Logic in real time via the Send tenant audit logs option on the integration. Global CBPR mapping refreshed: · Oct 2026 · source · release history

example

  • Stream tenant audit logs to Sumo Logic in real time alongside findings, using the new workflow condition instead of the retired checkbox. In the Plerion console, open Workflows, select or create a workflow with a Sumo Logic action, click 'Add audit log condition', then save — audit events will post to your Sumo Logic HTTP Source as… changelog · Oct 2026 · source
  • Route nightly workflow findings and real-time audit logs to Sumo Logic for centralised SIEM correlation. In the platform, go to Integrations > Add Integration > Sumo Logic, enter your Sumo Logic HTTP Source URL, attach the integration as an action on a workflow, and tick 'Send tenant audit logs' to… Global CBPR mapping refreshed: · Oct 2026 · source
EPSS scoring for vulnerabilities shipped Attaches an EPSS (Exploit Prediction Scoring System) score to every vulnerability, showing the 30-day exploitation probability as a percentage across the Vulnerabilities dashboard, alerts, tickets, CSV exports, the API, and the CLI, with support for filtering, sorting, and use as a condition in workflow and exemption rules. 8 releases · first seen Oct 2026

Also counts toward: Command-line interface, CSV data export, REST API, Ticketing integration, Web management console

release 8 total

  • Introduces EPSS score support in workflow conditions, exemption rule conditions, alerts, tickets, CSV exports, and the customer API Know which vulnerabilities are likely to be exploited: · Oct 2026 · source · release history
  • Supports EPSS score as a condition in workflow and exemption rule configurations. Know which vulnerabilities are likely to be exploited: · Oct 2026 · source · release history
  • Adds EPSS (Exploit Prediction Scoring System) score to every vulnerability, showing the probability of exploitation in the next 30 days as a percentage on the Vulnerabilities dashboard and code security issues.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Know which vulnerabilities are likely to be exploited: · Oct 2026 · source · release history
  • Enables filtering and sorting by EPSS score on the Vulnerabilities dashboard, CLI, and customer API Know which vulnerabilities are likely to be exploited: · Oct 2026 · source · release history
  • Enables filtering and sorting of vulnerabilities by EPSS score in the Vulnerabilities dashboard. Know which vulnerabilities are likely to be exploited: · Oct 2026 · source · release history
  • Surfaces EPSS scores in alerts, tickets, CSV downloads, the customer API, and the CLI. Know which vulnerabilities are likely to be exploited: · Oct 2026 · source · release history
Dashboard and navigation customization shipped Allows setting a home dashboard and sidebar navigation per user or user group, configuring a tenant-wide default home dashboard, and listing custom dashboards. 7 releases · first seen Oct 2026

release 7 total

  • Adds ability to set a user’s or user group’s sidebar navigation via API. Preferences and dashboards over the API: · Oct 2026 · source · release history
  • Adds ability to set the tenant default home dashboard via API. Preferences and dashboards over the API: · Oct 2026 · source · release history
  • GET /dashboards/custom endpoint lists all custom dashboards for authenticated users. 2026-10-05 · Oct 2026 · source · release history
  • Adds API key-authenticated endpoints to set a user's or user group's home dashboard and sidebar navigation, set the tenant default home dashboard, and list custom dashboards.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Preferences and dashboards over the API: · Oct 2026 · source · release history
  • Adds ability to list custom dashboards using an API key. Preferences and dashboards over the API: · Oct 2026 · source · release history
  • Adds ability to set a user’s or user group’s home dashboard via API. Preferences and dashboards over the API: · Oct 2026 · source · release history
Find assets by package shipped Adds a 'Find by package' search on the Assets page to identify every asset running a specific library, filterable by version range, showing the exact version each asset holds, with direct links from each package entry on an asset's SBOM tab. 4 releases · 1 other source · first seen Oct 2026

release

  • Adds Find by package search on the Assets page to locate every asset running a given package, with version range filtering (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ >= 2.0, < 2.15.0) and results showing exact version, environment, owner, and exposure per asset. Find every asset that runs a package: · Oct 2026 · source · release history
  • Every package on an asset's SBOM tab now links directly to the Find by package view for that package. Find every asset that runs a package: · Oct 2026 · source · release history
  • Adds Find by package search on the Assets page to identify every asset running a specific library, filterable by version range (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ >= 2.0, < 2.15.0), showing the exact version each asset holds. Find every asset that holds a package: · Oct 2026 · source · release history
  • Every package entry on an asset's SBOM tab links directly to the Find by package view for that package. Find every asset that holds a package: · Oct 2026 · source · release history

example

  • When a package release is reported as compromised, quickly find every asset in your inventory running a vulnerable version range. In the Plerion platform, go to Assets > Find by package, enter the compromised package name (or paste a list), then enter a version range such as `>= 2.0, < 2.15.0` to see each affected asset with… Find every asset that runs a package: · Oct 2026 · source
APEC CBPR compliance framework shipped Maps cloud posture against the APEC Cross-Border Privacy Rules framework, available as an opt-in framework enabled from Compliance under Manage frameworks. 3 releases · 2 other sources · first seen Oct 2026

release

  • Adds APEC Cross-Border Privacy Rules (CBPR) System Program Requirements (November 2019) as a new compliance framework, mapping 6 of 73 requirements covering security safeguards, attack detection/response, and safeguard testing across AWS, Azure, GCP, and Kubernetes; enable it from Compliance under Manage frameworks. changelog · Oct 2026 · source · release history
  • Refreshes the Global Cross-Border Privacy Rules (CBPR) System Program Requirements (September 2025 edition) mapping, expanding coverage across AWS, Azure, GCP, and Kubernetes for checks including backups, encryption, public/external exposure, audit logging, vulnerabilities, secrets, and alerting. Global CBPR mapping refreshed: · Oct 2026 · source · release history
  • The APEC CBPR framework is off by default and must be enabled from Compliance under Manage frameworks.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ APEC Cross-Border Privacy Rules requirements are now available: · Oct 2026 · source · release history

example

  • Enable the APEC CBPR compliance framework to start mapping your cloud posture against its security safeguard requirements across AWS, Azure, GCP, and Kubernetes. In the Plerion console, go to Manage > Compliance > Manage frameworks, locate 'APEC Cross-Border Privacy Rules (CBPR) System Program Requirements', and toggle it on. changelog · Oct 2026 · source
  • Enable the APEC CBPR framework to start mapping your cloud posture against its requirements. In Plerion, go to Manage frameworks under Compliance, locate 'APEC Cross-Border Privacy Rules (CBPR) System Program Requirements', and toggle it on. APEC Cross-Border Privacy Rules requirements are now available: · Oct 2026 · source
Threat detection rules shipped Runs detection rules against cloud activity to surface threats such as compromised AWS access keys reported by AWS Health, deletion of Bedrock model invocation logging as a sign of LLMjacking cover-tracking, and secrets in GCP Cloud Function environment variables. 4 releases · first seen Oct 2026

release

  • Plerion's findings list now has two views next to Group by: Configuration findings (opens by default, showing cloud, workload, and code configuration checks) and Event findings (showing CDR findings, newest first).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ CDR findings, easier to find and easier to read: · Nov 2026 · source · release history
  • Update your CDR StackSet to the latest template to enable four new AWS Security Incident Response detections (PLERION-CLOUDTRAIL-86 through PLERION-CLOUDTRAIL-89) that fire when a case is created or updated, or when a comment is added or edited — detections are Medium severity and off by default, so turn them on… Say hello to a new Compute Engine secret check: · Nov 2026 · source · release history
  • Adds PLERION-CLOUDTRAIL-84 (Critical) to detect compromised AWS keys via AWS Health exposed/compromised access key reports, naming the key and IAM user (requires us-east-1 in your CDR regions); PLERION-CLOUDTRAIL-85 (High) to detect deletion of Amazon Bedrock model invocation logging, a LLMjacking cover-track… Catch leaked AWS keys before someone runs up your Bedrock bill: · Oct 2026 · source · release history
  • Promotes PLERION-GCP-18 (Medium) from a manual recommendation to an active finding: scans Cloud Function runtime and build environment variables for credentials (API keys, access tokens, private keys), naming the variable but never its value. Catch leaked AWS keys before someone runs up your Bedrock bill: · Oct 2026 · source · release history
Continuous scanning for AWS accounts shipped Re-scans AWS resources triggered by CloudTrail management events, covering 166 resource types across more than 50 services, so findings reflect configuration changes within minutes; each scan that detects a change costs 3 Plerion units while no-change re-scans are free. 3 releases · 1 other source · first seen Nov 2026

release

  • Existing CDR StackSet deployments must be updated to the latest template to send AWS Security Incident Response events to Plerion; without this update, PLERION-CLOUDTRAIL-86 through PLERION-CLOUDTRAIL-89 will not fire. Every asset, an owner: · Nov 2026 · source · release history
  • Turn on continuous scanning for an AWS account on the account integration's page (requires CDR to be set up first); it is off by default, re-scans on CloudTrail management events, covers 166 resource types across more than 50 AWS services, and updates findings within minutes of each event.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Continuous scanning for AWS accounts: · Nov 2026 · source · release history
  • Each continuous asset scan that finds a change costs 3 Plerion units; re-scans that detect no change are free; continuous scanning appears as its own type on the subscription usage chart. Continuous scanning for AWS accounts: · Nov 2026 · source · release history

example

  • Enable continuous scanning on an account where CDR is already configured, so a newly opened security group or unencrypted bucket surfaces in findings within minutes rather than waiting for the next scheduled scan. In the Plerion console, go to the AWS account integration's page, confirm CDR is set up for that account, then toggle 'Continuous scanning' on. Continuous scanning for AWS accounts: · Nov 2026 · source
AWS Agent Registry integration shipped Reads registries from the new AWS Agent Registry service and runs posture checks against them, replacing the deprecated Bedrock AgentCore registry API, with legacy AgentCore registry findings automatically resolved on upgrade. 4 releases · first seen Oct 2026

release

  • Migrates check PLERION-AWS-1110 ('Agent registry publishes new records without review') to the new standalone Agent Registry service, collecting registries via agent-registry read permissions added in the latest Plerion stack; flags registries whose auto-approval rules include APPROVE_ALL. changelog · Oct 2026 · source · release history
  • Registries created in AgentCore before 6 August are no longer checked and their open findings resolve — any findings from those legacy AgentCore registries will be automatically closed on upgrade. Agent Registry check follows Agent Registry to its new home: · Oct 2026 · source · release history
  • Updates check PLERION-AWS-1110 ('Agent registry publishes new records without review') to run against registries in the new AWS Agent Registry service instead of the deprecated Bedrock AgentCore registry API.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Agent Registry check follows Agent Registry to its new home: · Oct 2026 · source · release history
  • Reads new Agent Registry registries once the Plerion stack is updated to the latest version, which adds agent-registry read permissions. Agent Registry check follows Agent Registry to its new home: · Oct 2026 · source · release history
GCP AI services posture checks shipped Discovers resources across 16 new GCP AI service types and runs 46 posture checks covering Vertex AI, Workbench, Colab Enterprise, Agent Engine, Model Armor, Dialogflow CX, Cloud TPU, and related services, including org-policy guardrails for Workbench access and Model Garden use. 4 releases · first seen Oct 2026

release

  • Seventeen SageMaker privilege escalation checks (PLERION-AWS-996 through PLERION-AWS-1012) are removed and no longer produce findings; these checks are also removed from the AWS Generative AI Lens, ISO/IEC 42001, NIST AI RMF, OWASP LLM and Agentic Top 10, and AWS MSP Validation Checklist framework mappings. Seventeen SageMaker privilege escalation checks are removed: · Oct 2026 · source · release history
  • Extends asset discovery to 16 new GCP resource types behind the newly supported AI services. GCP AI coverage widens further: · seen Aug 2026 · source · release history
  • Adds 46 new posture checks spanning Vertex AI, Vertex AI Workbench, Colab Enterprise, Agent Engine, Vertex AI Search, Gemini Enterprise, Model Armor, Dialogflow CX, Cloud TPU, and Gemini Code Assist. GCP AI coverage widens further: · seen Aug 2026 · source · release history
  • Adds project-level org-policy guardrails covering Vertex AI Workbench access and Model Garden model use. GCP AI coverage widens further: · seen Aug 2026 · source · release history
Google Cloud organization onboarding shipped Connects an entire GCP organization to the tool via a single generated command using keyless Workload Identity Federation, with options for Terraform-based onboarding, automatic project discovery, and single-resource revocation of access. 4 releases

Also counts toward: Command-line interface

release

  • Onboards an entire Google Cloud organization from a single generated command using keyless access via Workload Identity Federation — no service account keys required. Connect your entire GCP organization at once: · seen Aug 2026 · source · release history
  • Provides an equivalent Terraform template for organizations preferring infrastructure-as-code onboarding. Connect your entire GCP organization at once: · seen Aug 2026 · source · release history
  • Automatically discovers every project in the organization, including projects created after initial onboarding, with the option to include all automatically or select individually. Connect your entire GCP organization at once: · seen Aug 2026 · source · release history
  • Revoke all Plerion access to the GCP organization by deleting a single resource. Connect your entire GCP organization at once: · seen Aug 2026 · source · release history
AWS Lambda web function workload scanning shipped suggested Scans every revision of a Lambda web function that receives endpoint traffic for vulnerabilities, secrets (including environment variables), and SBOMs, activating automatically when the existing Lambda toggle is enabled, and surfaces the S3 bucket name for any revision that cannot yet be scanned. 3 releases · first seen Oct 2026

Suggested capability: Static application security testing. This is our guess, not confirmed.

release

  • Extends Lambda workload scanning to cover every Lambda web function revision that an endpoint sends traffic to, scanning for vulnerabilities, secrets (including environment variables), and generating an SBOM.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Workload scanning covers Lambda web functions: · Oct 2026 · source · release history
  • Raises Lambda workload checks on web functions automatically when the existing Lambda toggle is enabled — no new setting required. Workload scanning covers Lambda web functions: · Oct 2026 · source · release history
  • Surfaces the S3 bucket name on any web function that cannot yet be scanned, guiding operators to share that bucket with Plerion the same way as for an AgentCore runtime deployed from a code zip. Workload scanning covers Lambda web functions: · Oct 2026 · source · release history
KMS-blocked resource visibility shipped suggested Identifies Bedrock and AgentCore resources that cannot be fully inspected due to a customer-managed KMS key blocking read access, and names the key on the asset page so the user can decide whether to grant access. 2 releases · 1 other source · first seen Oct 2026

Suggested capability: Data access governance. This is our guess, not confirmed.

release

  • When a customer-managed KMS key blocks Plerion from reading part of an Amazon Bedrock or AgentCore resource, the asset page now names the key and lets you decide whether to grant access. Seventeen SageMaker privilege escalation checks are removed: · Oct 2026 · source · release history
  • Ratings apply to findings where anyone can read stored text with just the memory's ARN Know which vulnerabilities are likely to be exploited: · Oct 2026 · source · release history

example

  • Identify Bedrock or AgentCore resources that Plerion cannot fully inspect because a customer-managed KMS key is blocking read access. In Plerion, open any Amazon Bedrock or AgentCore asset page — if a customer-managed KMS key is restricting access, the page names the key so you can decide whether to grant Plerion read permission. Seventeen SageMaker privilege escalation checks are removed: · Oct 2026 · source
Kubernetes workload scanning shipped Scans container images across Kubernetes workload types to build an SBOM and detect secrets such as API keys and tokens, with scan types selectable at cluster-connect time or changed later from integration settings. 3 releases

release

  • Secret scanning detects API keys, tokens, and passwords inside container images and reports them with severity on the asset's Sensitive data tab, so practitioners know what to rotate first. Onboard AWS accounts with Terraform: · seen Aug 2026 · source · release history
  • Scan types (SBOM, secret scanning) can be selected at cluster-connect time or changed at any point from the integration's workload scan settings. Onboard AWS accounts with Terraform: · seen Aug 2026 · source · release history
  • Workload scanning now builds a software bill of materials (SBOM) for every container image across Kubernetes Deployments, DaemonSets, StatefulSets, Pods, Jobs, and CronJobs, surfaced on each asset's SBOM tab. Onboard AWS accounts with Terraform: · seen Aug 2026 · source · release history
CDR finding event details shipped Shows a plain-language summary of who did what, where, and when on each CDR finding's Event tab, covering CloudTrail, GuardDuty, Macie, IAM Access Analyzer, and AWS Security Incident Response events, with a toggle to view or copy the raw JSON event payload. 1 release · 1 other source · first seen Nov 2026

Also counts toward: Web management console

release

  • The Event tab on a CDR finding now shows a plain-language summary of who did what, where, and when, covering CloudTrail, GuardDuty, Macie, IAM Access Analyzer, and AWS Security Incident Response events, with a JSON toggle to view or copy the raw event. CDR findings, easier to find and easier to read: · Nov 2026 · source · release history

example

  • Navigate to CDR findings sorted newest-first, then switch to raw JSON to copy the full event payload for an incident under investigation. In the Findings list, select 'Event findings' next to 'Group by' to see CDR findings newest first. CDR findings, easier to find and easier to read: · Nov 2026 · source
Asset ownership management shipped Automatically discovers asset owners from existing tags, allows manual ownership rules scoped by tag, integration, resource type, region, or name, merges duplicate owners, and surfaces assets with no owner assigned. 2 releases · first seen Nov 2026

Also counts toward: User-defined detection rules

release

  • Add ownership rules for assets your tags miss, by tag, integration, resource type, region or name, and see which assets nobody owns yet. Every asset, an owner: · Nov 2026 · source · release history
  • Discover owners automatically from existing tags, merge owners that are clearly the same, and keep them current as tags change. Every asset, an owner: · Nov 2026 · source · release history
AWS Security Incident Response case detection shipped Detects when an AWS Security Incident Response case is opened or a comment is added, surfacing these as CDR findings after updating the CDR StackSet to the latest template. 1 release · 1 other source · first seen Nov 2026

release

  • Existing CDR StackSet deployments must be updated to the latest template to send AWS Security Incident Response events to Plerion; without this update, PLERION-CLOUDTRAIL-86 through PLERION-CLOUDTRAIL-89 will not fire. Every asset, an owner: · Nov 2026 · source · release history

example

  • Turn on AWS Security Incident Response case detections after updating your CDR StackSet, so your team is alerted whenever a case is opened or a comment is added. In Plerion, go to your profile settings and enable PLERION-CLOUDTRAIL-86, PLERION-CLOUDTRAIL-87, PLERION-CLOUDTRAIL-88, and PLERION-CLOUDTRAIL-89 (all are off by default). Every asset, an owner: · Nov 2026 · source
AWS Well-Architected Security (SHIP) lens shipped Adds the AWS Security Health Improvement Program lens to the Well-Architected page, grouping Security pillar best practices under SHIP's 11 security use cases with answers pre-populated from existing Plerion findings. 1 release · 1 other source · first seen Oct 2026

release

  • Plerion's Well-Architected page now includes the AWS Security Health Improvement Program (SHIP) lens, grouping AWS Well-Architected Security best practices under SHIP's 11 security use cases with answers populated from Plerion findings. IAM role fact check says Unknown when it cannot test the trust: · Oct 2026 · source · release history

example

  • Review your AWS security posture against SHIP's 11 use cases — including threat detection, permissions analysis and credentials protection — with answers pre-populated from your existing Plerion findings. In the Plerion console, go to the Well-Architected page and select the AWS Security Health Improvement Program (SHIP) lens. IAM role fact check says Unknown when it cannot test the trust: · Oct 2026 · source
AWS Lambda Web Functions inventory shipped Provides an inventory of AWS Lambda Web Functions, showing each function's HTTPS endpoints with authentication type and domain name, the revisions receiving traffic, the execution role per revision, resource policies, and tags. 2 releases · first seen Oct 2026

release

  • Adds Lambda Web Functions to asset inventory, showing each function's endpoints with authentication type and domain, revisions, execution roles, resource policy, and tags. changelog · Oct 2026 · source · release history
  • Adds inventory support for AWS Lambda Web Functions, displaying each function's HTTPS endpoints with authentication type and domain name, the revisions receiving traffic, the execution role per revision, resource policies, and tags.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Lambda Web Functions are now in your inventory: · Oct 2026 · source · release history
Global CBPR compliance framework shipped Maps cloud posture against the Global Cross-Border Privacy Rules framework across 7 requirements, with posture scores updated on each scan run. 2 releases · first seen Oct 2026

release

  • Refreshes Global CBPR (September 2025 edition) mapping, expanding coverage across AWS, Azure, GCP, and Kubernetes for its 7 mapped requirements with checks for backups, encryption, exposure, audit logging, vulnerabilities, secrets, and alerting. changelog · Oct 2026 · source · release history
  • If the Global CBPR framework has been enabled, posture scores for its 7 mapped requirements will change on the next scan due to the refreshed mapping. Global CBPR mapping refreshed: · Oct 2026 · source · release history
MITRE ATLAS threat mapping shipped Adds the MITRE ATLAS AI Framework matrix to the threat mapping view on asset pages, allowing users to review AI-specific threat coverage alongside existing MITRE ATT&CK matrices. 1 release · 1 other source · first seen Oct 2026

release

  • Renames the Mitre attack tab on asset views to Threat mapping and adds the matrix picker there.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Threat mapping covers AI: · Oct 2026 · source · release history

example

  • Select the MITRE ATLAS AI Framework matrix to review AI-specific threat coverage for a cloud asset. In the Plerion console, navigate to an asset > Threat mapping tab > use the matrix picker to select 'MITRE ATLAS AI Framework'. Threat mapping covers AI: · Oct 2026 · source
GCP Compute Engine end-of-life OS detection shipped Reads the public image license on a Compute Engine instance's boot disk and fails the instance at Medium severity when the OS is past end-of-life, covering Debian, Ubuntu, CentOS, RHEL, Rocky Linux, AlmaLinux, Oracle Linux, SUSE, and Windows Server. 1 release · first seen Nov 2026

release

  • Plerion adds a new GCP check (PLERION-GCP-341) that reads the public image license on a Compute Engine instance's boot disk and fails the instance at Medium severity when the OS is past end-of-life, covering Debian, Ubuntu, CentOS, RHEL, Rocky Linux, AlmaLinux, Oracle Linux, SUSE, and Windows Server images. Say hello to a new Compute Engine secret check: · Nov 2026 · source · release history
CWPP service account template drift detection shipped Raises a Medium-severity finding when a customer-managed CWPP service account's permissions stack or any enabled region stack does not match the latest Plerion-provided template, listing the deployed and latest versions. 1 release · first seen Nov 2026

release

  • New check [PLERION-PLN-5] ('Ensure the CWPP service account is using the latest Plerion provided templates') fails at Medium severity when a customer-managed CWPP service account's permissions stack or any enabled region stack does not match the latest Plerion template, listing deployed and latest versions and each… Continuous scanning for AWS accounts: · Nov 2026 · source · release history
CVE file and package path attribution shipped suggested Names the specific file or package path carrying a CVE on each affected asset. 1 release · first seen Oct 2026

Suggested capability: Vulnerability database matching. This is our guess, not confirmed.

release

  • Pleri (AI assistant) now names the specific file or package path carrying a CVE on each affected asset. Catch leaked AWS keys before someone runs up your Bedrock bill: · Oct 2026 · source · release history
Amazon ECS cluster inventory shipped suggested Collects ECS cluster configuration into the asset inventory, including KMS keys for managed and Fargate ephemeral storage, ECS Exec settings, and associated logging, so custom checks can query these fields after each scan. 1 release · first seen Oct 2026

Suggested capability: Encryption at rest. This is our guess, not confirmed.

release

  • Collects Amazon ECS cluster configuration in inventory, including KMS keys for managed storage and Fargate ephemeral storage, ECS Exec settings, and its associated KMS key and logging, surfaced as fields on each cluster asset after the next scan so custom checks can query them.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ ECS cluster settings in your inventory: · Oct 2026 · source · release history
GCP IAM and identity asset inventory shipped suggested Collects and surfaces GCP folder and organization IAM policy members, service account IAM policy members, custom roles at project and organization level, and Workload Identity pools for organization integrations in the asset inventory. 1 release · first seen Oct 2026

Suggested capability: Data access governance. This is our guess, not confirmed.

release

  • Collects GCP folder and organization IAM policy members, service account IAM policy members, custom roles at project and organization level, and Workload Identity pools for organization integrations — all visible in asset inventory.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ More GCP IAM in your inventory: · Oct 2026 · source · release history
Lambda web function posture checks shipped Runs posture checks against Lambda web functions, including detection of unauthenticated internet-accessible endpoints with ApplicationManaged authentication, with failing functions surfaced in exposure views and attack paths. 1 release · first seen Oct 2026

release

  • Adds four new Lambda web function checks: PLERION-AWS-1246 (High) detects ApplicationManaged authentication-type Lambda web function endpoints that accept unauthenticated internet requests, naming the endpoints and domains, with failing web functions appearing in exposure views and attack paths; PLERION-AWS-1247… changelog · Oct 2026 · source · release history
Amazon Bedrock agent inventory shipped Provides an inventory of Amazon Bedrock AgentCore runtimes and harnesses and Bedrock Agents Classic agents, with navigation from each agent to its gateways, tools, memory stores, guardrails, and IAM role. 1 release · first seen Oct 2026

release

  • Adds Agent Security inventory covering Amazon Bedrock AgentCore runtimes and harnesses and Amazon Bedrock Agents Classic agents, letting you navigate from an agent to its gateways, tools, memory, guardrails, and IAM role.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Seventeen SageMaker privilege escalation checks are removed: · Oct 2026 · source · release history
AWS integration via Terraform shipped Provisions the required IAM role and policies as native Terraform resources and registers the AWS integration automatically, with a choice of running workload scanning in the customer's own account or through a Plerion-managed service account. 1 release

Also counts toward: Role-based access control

release

  • New Terraform template provisions the IAM role and policies as native Terraform resources and registers the AWS integration automatically — no CloudFormation stack, no manual console step — with a choice of running workload scanning inside your own account or through a Plerion-managed service account. Onboard AWS accounts with Terraform: · seen Aug 2026 · source · release history
Azure DevOps pull request management shipped Allows the tool's AI assistant to check pull request status, request reviews, or abandon pull requests with a reason inside Azure DevOps. 1 release

release

  • Pleri can check pull request status, request a review, or abandon a pull request with a reason inside Azure DevOps. Pleri now raises pull requests in Azure DevOps: · seen Aug 2026 · source · release history
Azure inventory expansion shipped Adds OpenShift, Service Fabric, and Batch resources to the Azure asset inventory. 1 release

release

  • Adds OpenShift, Service Fabric, and Batch resources to the inventory. Azure workload scanning covers every workload family: · seen Sep 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Command line

2 commands for Plerion, each with where it came from. This tool has no source analysis yet, so there is no option reference and no captured run beside them.

Source

Screenshots

From the release notes, newest first. Click one to see it full size.

api-docs-2981f275f2f9 Sep 26, 2026

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface

Five scores for Plerion, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Plerion puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Coverage

Missing something? Tell us

What Plerion connects to, runs on and detects, read from its release notes and docs. So far: 5 updated vulnerability checks, 3 new vulnerability checks, 3 updated detections, 2 updated integrations, 2 new supported platforms, 2 new detections, 1 retired vulnerability check, 1 new compliance framework, 1 new integration.

Show
When

20 changes, tracked since Oct 3, 2026.

  • Nov 42026

    updated CDR Event tab summaries for AWS services

    With CloudTrail, GuardDuty, Macie, IAM Access Analyzer, AWS Security Incident Response

    It has a summary for CloudTrail, GuardDuty, Macie, IAM Access Analyzer and AWS Security Incident Response events.

    CDR findings, easier to find and easier to read: Source ↗

  • Nov 22026

    new CWPP service account template check

    With PLERION-PLN-5

    Say hello to a new check for CWPP service accounts: [PLERION-PLN-5] Ensure the CWPP service account is using the latest Plerion provided templates fails when the permissions stack of a customer-managed CWPP service account, or the region stack in any enabled region, does not match the latest Plerion template.

    Continuous scanning for AWS accounts: Source ↗

  • Nov 22026

    new Continuous scanning coverage across AWS resource types

    With 166 resource types, more than 50 AWS services

    It covers 166 resource types across more than 50 AWS services, but not workload scanning (CWPP) yet.

    Continuous scanning for AWS accounts: Source ↗

  • Nov 12026

    new Publicly readable Azure blob container and Google Cloud Storage bucket top-risk detection

    Plerion now raises a top risk when an Azure blob container or a Google Cloud Storage bucket holds data that anyone on the internet can read, the same way it does for S3 buckets.

    Top risks now cover Azure and GCP storage: Source ↗

  • Oct 312026

    updated Detect attempts to exfiltrate EBS snapshot by sharing it

    With PLERION-CLOUDTRAIL-73

    [PLERION-CLOUDTRAIL-73] Detect attempts to exfiltrate EBS snapshot by sharing it exempted a finding when every account in the share was one of your trusted accounts. A share that also made the snapshot public, by granting all , could pass that test and be saved as exempted. A share that makes a snapshot public now always raises the finding.

    A public EBS snapshot share is never exempted as trusted: Source ↗

  • Oct 312026

    updated Detect attempts to exfiltrate AMI by sharing it

    With PLERION-CLOUDTRAIL-72

    [PLERION-CLOUDTRAIL-72] Detect attempts to exfiltrate AMI by sharing it and [PLERION-CLOUDTRAIL-74] Detect attempts to exfiltrate RDS snapshot by sharing it now fire only when a call gives someone access.

    A public EBS snapshot share is never exempted as trusted: Source ↗

Changes per month New Updated Retired
2026-1016
2026-114
How we count

Read from 14 of 105 release notes and docs updates we hold for Plerion. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Plerion's life, so an old integration can show a recent first-seen date.

Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.

Releases

Show
Coverage in all entries

105 entries

  1. November 20265
  2. October 202625
  3. September 202621
  4. August 202620
  5. July 20269
  6. June 202614
  7. May 20262
  8. April 20261
  9. March 20264
  10. December 20251
  11. November 20251
  12. October 20252
    Show
    Coverage in all entries

    105 entries

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →