<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Plerion — The Cyber Toolchain</title>
    <link>https://cybertoolchain.io/tools/plerion</link>
    <description>New releases and features in Plerion, tracked by The Cyber Toolchain.</description>
    <language>en</language>
    <lastBuildDate>Wed, 04 Nov 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://cybertoolchain.io/tools/plerion/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Plerion CDR findings, easier to find and easier to read:</title>
      <link>https://docs.plerion.com/changelog#2026-11-04</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-11-04</guid>
      <pubDate>Wed, 04 Nov 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds two-view findings list and a narrative Event tab for CDR findings across CloudTrail, GuardDuty, Macie, IAM Access Analyzer, and AWS Security Incident Response⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Plerion&apos;s findings list now has two views next to &apos;Group by&apos;: &apos;Configuration findings&apos; (opens by default, showing cloud, workload, and code configuration checks) and &apos;Event findings&apos; (showing CDR findings, newest first).⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Every asset, an owner:</title>
      <link>https://docs.plerion.com/changelog#2026-11-03</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-11-03</guid>
      <pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate>
      <description>Plerion: Assign a team, a person, or both to each asset so owners are notified when action is needed, and filter assets by owner.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Discover owners automatically from existing tags, merge owners that are clearly the same, and keep them current as tags change.
• Add ownership rules for assets your tags miss, by tag, integration, resource type, region or name, and see which assets nobody owns yet.
Breaking changes:
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Say hello to a new Compute Engine secret check:</title>
      <link>https://docs.plerion.com/changelog#2026-11-03</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-11-03</guid>
      <pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds GCP Compute Engine secret and end-of-life checks, plus AWS Security Incident Response case detections in CDR⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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 in your profile.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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 key, and the matched value is masked before storage.
• Plerion adds a new GCP check (`PLERION-GCP-341`) that reads the public image license on a Compute Engine instance&apos;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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Continuous scanning for AWS accounts:</title>
      <link>https://docs.plerion.com/changelog#2026-11-02</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-11-02</guid>
      <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds continuous scanning for AWS accounts, triggering re-scans within minutes of CloudTrail events across 166 resource types⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Turn on continuous scanning for an AWS account on the account integration&apos;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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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.
• New check `[PLERION-PLN-5]` (&apos;Ensure the CWPP service account is using the latest Plerion provided templates&apos;) fails at Medium severity when a customer-managed CWPP service account&apos;s permissions stack or any enabled region stack does not match the latest Plerion template, listing deployed and latest versions and each outdated region.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Top risks now cover Azure and GCP storage:</title>
      <link>https://docs.plerion.com/changelog#2026-11-01</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-11-01</guid>
      <pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds top-risk detection for publicly readable Azure blob containers and Google Cloud Storage buckets⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion A public EBS snapshot share is never exempted as trusted:</title>
      <link>https://docs.plerion.com/changelog#2026-10-31</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-31</guid>
      <pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate>
      <description>Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion IAM role fact check says Unknown when it cannot test the trust:</title>
      <link>https://docs.plerion.com/changelog#2026-10-30</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-30</guid>
      <pubDate>Fri, 30 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds SAST scanning for GitLab and Azure DevOps integrations and a new AWS SHIP lens on the Well-Architected page⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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 default.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Plerion&apos;s Well-Architected page now includes the AWS Security Health Improvement Program (SHIP) lens, grouping AWS Well-Architected Security best practices under SHIP&apos;s 11 security use cases with answers populated from Plerion findings.
• 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.
• The fact check for `PLERION-AWS-194` (EC2 instance publicly accessible) now sends an HTTP request through each listener that forwards to the instance&apos;s target group, promoting Unknown results to Factual or Non-factual based on actual reachability.
• 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.
• 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 their publicly-accessible decisions from configuration alone rather than live probes from the internet.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Custom checks, now in Terraform:</title>
      <link>https://docs.plerion.com/changelog#2026-10-29</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-29</guid>
      <pubDate>Thu, 29 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion: Manage custom checks as code via the plerionhq/plerion Terraform provider, with plan previews, dry-run testing, and imports by slug or ID.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Exempt findings from your infrastructure as code:</title>
      <link>https://docs.plerion.com/changelog#2026-10-29</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-29</guid>
      <pubDate>Thu, 29 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds exemption support for infrastructure-as-code findings across Terraform, CloudFormation, and other template checks⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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&apos;s profile — name exemptions scoped to a full repository (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ `my-org/infra`) or a single file (e.g. `my-org/infra/s3.tf`) persist across every later scan.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Catch leaked AWS keys before someone runs up your Bedrock bill:</title>
      <link>https://docs.plerion.com/changelog#2026-10-28</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-28</guid>
      <pubDate>Wed, 28 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds LLMjacking detections, new Azure/GCP checks, and expands access-logging asset coverage across API Gateway, load balancers, VPCs and EKS.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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 technique; `PLERION-AWS-1252` (Low) to check whether CloudTrail logs data events for `AWS::BedrockMantle::Project`, the endpoint for OpenAI-compatible and Anthropic Messages APIs, via an advanced event selector on a multi-region trail; and `PLERION-AZURE-463` (Medium) to detect Azure Function App runtimes past Microsoft&apos;s end-of-support date, covering .NET, .NET isolated, Java, Node.js, PowerShell and Python, flagging Python 3.8/3.9, .NET 6, PowerShell 7.2, and Node.js 20 on next scan.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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.
• 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`).
• Pleri (AI assistant) now names the specific file or package path carrying a CVE on each affected asset.
• Widens `PLERION-AWS-231` CloudFront general-logging check to pass distributions whose standard logging (v2) delivers via a CloudWatch Logs delivery to CloudWatch Logs, Amazon S3 or Amazon Data Firehose, and widens `PLERION-AZURE-74` Key Vault logging check to pass vaults whose diagnostic setting enables the `audit` or `allLogs` category group, not only an explicit `AuditEvent` selection.
Breaking changes:
• `PLERION-AWS-835` (EFS access logging) is retired; its passed findings are removed on the next scan.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion ECS cluster settings in your inventory:</title>
      <link>https://docs.plerion.com/changelog#2026-10-27</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-27</guid>
      <pubDate>Tue, 27 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion now inventories Amazon ECS cluster settings — KMS keys, Fargate ephemeral storage, and ECS Exec config — enabling custom checks.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Find every asset that runs a package:</title>
      <link>https://docs.plerion.com/changelog#2026-10-26</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-26</guid>
      <pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds package-based asset search with version range filtering to answer &apos;do we run this, and where?&apos; across your inventory.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds &apos;Find by package&apos; search on the Assets page to locate every asset running a given package, with version range filtering (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ `&gt;= 2.0, &lt; 2.15.0`) and results showing exact version, environment, owner, and exposure per asset.
• Every package on an asset&apos;s SBOM tab now links directly to the &apos;Find by package&apos; view for that package.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion changelog-20261022-10b6f4ce</title>
      <link>https://docs.plerion.com/changelog</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog</guid>
      <pubDate>Thu, 22 Oct 2026 07:50:52 GMT</pubDate>
      <description>Plerion adds Lambda Web Function inventory, four new Lambda checks, workload scanning, Sumo Logic integration, and APEC CBPR compliance mapping.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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` detects Lambda web functions whose resource policy grants external AWS principals (outside your Organization) invoke or management access, raising High for unrecognized accounts and Medium for trusted or conditional grants, showing principal, actions, and granting statement in Access Grants; `PLERION-AWS-1248` (Medium) flags Lambda web function execution roles that allow every action on every resource with no condition, naming the role and policy statements; and `PLERION-AWS-1249` (Low) flags Lambda web function execution roles with wildcard service-level permissions such as `s3:*` and no condition, naming the role and policy statements.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds Lambda Web Functions to asset inventory, showing each function&apos;s endpoints with authentication type and domain, revisions, execution roles, resource policy, and tags.
• 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.
• 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.
• 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 &apos;Manage frameworks&apos;.
• Migrates check `PLERION-AWS-1110` (&apos;Agent registry publishes new records without review&apos;) 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`.
• 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.
Breaking changes:
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Workload scanning covers Lambda web functions:</title>
      <link>https://docs.plerion.com/changelog#2026-10-21</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-21</guid>
      <pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion workload scanning now covers Lambda web function revisions, including code, secrets, environment variables, and SBOM generation.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Raises Lambda workload checks on web functions automatically when the existing Lambda toggle is enabled — no new setting required.
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Say hello to a new Lambda check:</title>
      <link>https://docs.plerion.com/changelog#2026-10-20</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-20</guid>
      <pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds check PLERION-AWS-1246 to flag Lambda web function endpoints using ApplicationManaged auth instead of IamAuth.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Lambda Web Functions are now in your inventory:</title>
      <link>https://docs.plerion.com/changelog#2026-10-19</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-19</guid>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion now inventories AWS Lambda Web Functions, surfacing endpoints, auth types, revisions, execution roles, and resource policies.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds inventory support for AWS Lambda Web Functions, displaying each function&apos;s HTTPS endpoints with authentication type and domain name, the revisions receiving traffic, the execution role per revision, resource policies, and tags.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Global CBPR mapping refreshed:</title>
      <link>https://docs.plerion.com/changelog#2026-10-15</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-15</guid>
      <pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds Sumo Logic integration for findings and audit logs, and refreshes Global CBPR compliance mapping.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Enables sending tenant audit logs to Sumo Logic in real time via the `Send tenant audit logs` option on the integration.
• Provides a `Sync now` action on the Sumo Logic integration to push changes immediately on demand.
• 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.
Breaking changes:
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion APEC Cross-Border Privacy Rules requirements are now available:</title>
      <link>https://docs.plerion.com/changelog#2026-10-14</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-14</guid>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds APEC Cross-Border Privacy Rules (CBPR) System Program Requirements as a new compliance framework mapping to AWS, Azure, GCP, and Kubernetes.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• The APEC CBPR framework is off by default and must be enabled from Compliance under Manage frameworks.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Agent Registry check follows Agent Registry to its new home:</title>
      <link>https://docs.plerion.com/changelog#2026-10-13</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-13</guid>
      <pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion migrates Agent Registry checks to AWS&apos;s new standalone Agent Registry service ahead of the 30 October 2026 Bedrock AgentCore API shutdown.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Updates check `PLERION-AWS-1110` (&apos;Agent registry publishes new records without review&apos;) to run against registries in the new AWS Agent Registry service instead of the deprecated Bedrock AgentCore registry API.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Reads new Agent Registry registries once the Plerion stack is updated to the latest version, which adds `agent-registry` read permissions.
Breaking changes:
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion changelog-20261012-dbe0ab06</title>
      <link>https://docs.plerion.com/changelog</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog</guid>
      <pubDate>Mon, 12 Oct 2026 17:39:59 GMT</pubDate>
      <description>Plerion adds 30+ new AWS checks spanning AgentCore IAM roles, Multi-AZ resilience, deletion protection, quota usage, and Route 53 failover health.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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.
• Adds `PLERION-AWS-1244`: EKS managed node group uses subnets in a single Availability Zone (new, Low) — flags node groups where a single AZ outage removes every node.
• 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.
• 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.
• Adds `PLERION-AWS-1198`: EC2 instance does not have termination protection enabled (new) — Spot instances and instances in Auto Scaling groups are skipped.
• Adds `PLERION-AWS-1199`: Auto Scaling group uses a single Availability Zone (new) — scanning appliance groups are skipped.
• 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.
• 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.
• 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&apos;s credentials; AWS-provided browser is skipped.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Sharper Reliability answers in Well-Architected workloads:</title>
      <link>https://docs.plerion.com/changelog#2026-10-08</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-08</guid>
      <pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds 39 live Reliability checks and 4 deletion-protection checks to Well-Architected AutoFill coverage.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds checks `PLERION-AWS-1197` (RDS DB instance deletion protection) and `PLERION-AWS-1198` (EC2 instance termination protection) as new live-resource checks answering REL 9 and REL 11 in Well-Architected workloads.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Extends `PLERION-AWS-311` (RDS cluster deletion protection) and `PLERION-AWS-614` (load balancer deletion protection) to run against live AWS accounts in addition to infrastructure-as-code templates.
• Adds 39 live checks to the Reliability pillar covering backups for RDS, Aurora, DocumentDB, Neptune, ElastiCache, OpenSearch, and Redshift; snapshot encryption and sharing; RDS Multi-AZ; DynamoDB global tables; CloudFront origin failover; VPN tunnel redundancy; and SQS dead-letter queues.
• Removes 33 retired checks and 15 misclassified security checks (such as IMDSv2 on Auto Scaling groups) from the Reliability pillar, raising AutoFill answer quality across 8 of 13 Reliability questions.
Breaking changes:
• If you use AutoFill, Reliability pillar answers in Well-Architected workloads will change on the next daily run: 33 retired checks and 15 security checks have been removed, and 39 new live checks have been added.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Seventeen SageMaker privilege escalation checks are removed:</title>
      <link>https://docs.plerion.com/changelog#2026-10-06</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-06</guid>
      <pubDate>Tue, 06 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds AI agent security inventory for Amazon Bedrock AgentCore and Agents Classic, plus KMS key visibility on Bedrock assets.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Scans container images and code inside AgentCore runtimes for exploitable vulnerabilities and secrets left in the image.
• Raises findings for risky agent configuration, such as a gateway reachable without credentials or a memory store open to any AWS account.
• 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.
Breaking changes:
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Preferences and dashboards over the API:</title>
      <link>https://docs.plerion.com/changelog#2026-10-05</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-05</guid>
      <pubDate>Mon, 05 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion exposes preferences and dashboards management via API, enabling programmatic control of home dashboards and sidebar navigation.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds API key-authenticated endpoints to set a user&apos;s or user group&apos;s home dashboard and sidebar navigation, set the tenant default home dashboard, and list custom dashboards.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Know which vulnerabilities are likely to be exploited:</title>
      <link>https://docs.plerion.com/changelog#2026-10-04</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-04</guid>
      <pubDate>Sun, 04 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds EPSS exploit-likelihood scores to vulnerabilities, surfaced in dashboard, API, CLI, CSV, and workflow rules.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Enables filtering and sorting of vulnerabilities by EPSS score in the Vulnerabilities dashboard.
• Supports EPSS score as a condition in workflow and exemption rule configurations.
• Surfaces EPSS scores in alerts, tickets, CSV downloads, the customer API, and the CLI.
• 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).
Breaking changes:
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Say hello to a new AgentCore check:</title>
      <link>https://docs.plerion.com/changelog#2026-10-03</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-03</guid>
      <pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate>
      <description>Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Threat mapping covers AI:</title>
      <link>https://docs.plerion.com/changelog#2026-10-02</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-02</guid>
      <pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds MITRE ATLAS AI Framework to Threat mapping alongside ATT&amp;CK Cloud and Containers matrices.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Renames the &apos;Mitre attack&apos; tab on asset views to &apos;Threat mapping&apos; and adds the matrix picker there.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion AgentCore runtimes get workload scanning:</title>
      <link>https://docs.plerion.com/changelog#2026-10-01</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-01</guid>
      <pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate>
      <description>Plerion now scans Amazon Bedrock AgentCore runtime container images for vulnerabilities, secrets, and SBOM.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds vulnerability, sensitive-data, and SBOM scanning for Amazon Bedrock AgentCore runtimes that run a container image, with results on the runtime&apos;s asset page — activated automatically when Lambda scanning is on for the integration.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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.
• 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`.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Azure workload scanning covers every workload family:</title>
      <link>https://docs.plerion.com/changelog#2026-10-02</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-10-02</guid>
      <pubDate>Sun, 27 Sep 2026 10:34:22 GMT</pubDate>
      <description>Plerion Azure workload scanning expands to App Service, VM Scale Sets, Container Apps, Container Instances, and Batch pools⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Covers Service Fabric node types through their underlying scale sets.
• Samples Uniform-orchestration scale sets by image, scanning one member per distinct image.
• Generates attack path findings for publicly exposed workloads with high or critical vulnerabilities (`PLERION-AZURE-446`).
• Grants `AcrPull` to the appliance identity via the install script so container images in Azure Container Registries can be pulled for scanning.
• Adds OpenShift, Service Fabric, and Batch resources to the inventory.
• Adds six new Azure checks for exploitable and known-exploited vulnerabilities in container workload and Batch pool images: `PLERION-AZURE-452` (Container App exploitable), `PLERION-AZURE-453` (Container App known-exploited), `PLERION-AZURE-454` (Container Instance exploitable), `PLERION-AZURE-455` (Container Instance known-exploited), `PLERION-AZURE-459` (Batch pool image exploitable), `PLERION-AZURE-460` (Batch pool image known-exploited).
• Enables each workload type individually under the subscription&apos;s workload scanning settings.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion api-docs-2981f275f2f9</title>
      <link>https://docs.plerion.com/api-reference</link>
      <guid isPermaLink="true">https://docs.plerion.com/api-reference</guid>
      <pubDate>Sat, 26 Sep 2026 12:59:04 GMT</pubDate>
      <description>Plerion adds role-scoped API keys and a `GET /v1/tenant/openapi` endpoint that returns a filtered OpenAPI 3.1 spec for any key.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds `GET /v1/tenant/openapi` endpoint that returns the full API reference as an OpenAPI 3.1 document filtered to only the operations the calling key&apos;s role permits — send `Accept: application/yaml` to receive YAML instead of JSON.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion api-docs-2981f275f2f9</title>
      <link>https://docs.plerion.com/api-reference</link>
      <guid isPermaLink="true">https://docs.plerion.com/api-reference</guid>
      <pubDate>Fri, 25 Sep 2026 13:25:49 GMT</pubDate>
      <description>Plerion API now exposes `GET /v1/tenant/openapi` to return a role-scoped OpenAPI 3.1 spec for any API key.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Introduces role-based access control for API keys, with built-in `Tenant admin` (full access) and `Tenant read-only` roles plus support for custom roles that restrict which operations and integrations a key can reach; unauthorized requests receive `403 Forbidden` with body `{&quot;message&quot;:&quot;Forbidden&quot;}`.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion api-docs-2981f275f2f9</title>
      <link>https://docs.plerion.com/api-reference</link>
      <guid isPermaLink="true">https://docs.plerion.com/api-reference</guid>
      <pubDate>Thu, 24 Sep 2026 13:20:33 GMT</pubDate>
      <description>Plerion: Introduces role-based API key permissions: `Tenant admin` keys can call every operation, while `Tenant read-only` and custom roles restrict which operations and integrations a key may access, with unauthorized requests refused as `403 Forbidden`.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion api-docs-2981f275f2f9</title>
      <link>https://docs.plerion.com/api-reference</link>
      <guid isPermaLink="true">https://docs.plerion.com/api-reference</guid>
      <pubDate>Wed, 23 Sep 2026 13:25:51 GMT</pubDate>
      <description>Plerion API keys gain role-based access control and a new `GET /v1/tenant/openapi` endpoint that returns a role-scoped OpenAPI 3.1 spec.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds `GET /v1/tenant/openapi` endpoint that returns the full API reference as an OpenAPI 3.1 document scoped to the calling key&apos;s permissions — operations the role cannot call are omitted; send `Accept: application/yaml` to receive YAML instead of the default JSON.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Tag an integration in Plerion:</title>
      <link>https://docs.plerion.com/changelog#2026-09-23</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-09-23</guid>
      <pubDate>Wed, 23 Sep 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds per-integration tags (API-accessible), two new S3 checks, and standalone SCIM provisioning⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds a `Tags` section to each integration&apos;s settings page where you can define key-value tags that override AWS account tags with the same key — tag groups update within seconds.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Exposes integration tags through the API: every integration returned by the API now carries its tags along with the source of each tag.
• Adds new S3 check `PLERION-AWS-1182`: S3 bucket default encryption does not use a customer-managed KMS key — passes buckets encrypted with `aws:kms` or `aws:kms:dsse` under an owned key; fails buckets on AES256, no encryption, or an AWS-managed SSE-KMS key (including the console&apos;s &apos;AWS managed key (aws/s3)&apos;); Medium severity.
• Adds new S3 check `PLERION-AWS-1181`: S3 Multi-Region Access Point does not block public access — passes only when all four Block Public Access flags are enabled on the access point; Medium severity.
• Adds SCIM provisioning: point your identity provider at the SCIM base URL under Admin &gt; Security &gt; Single sign-on &gt; SCIM provisioning and authenticate with a `readWrite` organization API key.
• Separates just-in-time provisioning from SCIM: the &apos;Create users at first sign-in&apos; setting now operates independently, with no dependency on SCIM state.
• Raises `PLERION-AWS-532` (S3 cross-account access) from Medium to High severity; all open findings on the check move to High on the next scan, and the check is now filed under data at risk, access control, and cross-account categories.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion api-docs-2981f275f2f9</title>
      <link>https://docs.plerion.com/api-reference</link>
      <guid isPermaLink="true">https://docs.plerion.com/api-reference</guid>
      <pubDate>Tue, 22 Sep 2026 13:07:37 GMT</pubDate>
      <description>Plerion: Adds `GET /v1/tenant/openapi` endpoint that returns this API reference as an OpenAPI 3.1 document scoped to the calling key&apos;s role — operations the role cannot call are omitted; send `Accept: application/yaml` to receive YAML instead of the default JSON.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion api-docs-2981f275f2f9</title>
      <link>https://docs.plerion.com/api-reference</link>
      <guid isPermaLink="true">https://docs.plerion.com/api-reference</guid>
      <pubDate>Mon, 21 Sep 2026 14:40:53 GMT</pubDate>
      <description>Plerion API now exposes `GET /v1/tenant/openapi` to return a role-scoped OpenAPI 3.1 spec for any API key.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Introduces role-based access control for API keys, supporting `Tenant admin` (full access) and `Tenant read-only` roles plus custom roles; requests outside the role&apos;s permissions return `403 Forbidden` with `{&quot;message&quot;:&quot;Forbidden&quot;}`.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion API keys now hold a role:</title>
      <link>https://docs.plerion.com/changelog#2026-09-21-2</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-09-21-2</guid>
      <pubDate>Mon, 21 Sep 2026 00:00:00 GMT</pubDate>
      <description>Plerion API keys now carry a role, and a new IaC scan upload permission gates POST /v1/tenant/shiftleft/iac/scan.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds role assignment to every tenant API key; new keys can be created with `Tenant read-only` or a custom role, and an existing key&apos;s role can be changed from the API keys list.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds `GET /v1/tenant/openapi` endpoint that returns the API reference scoped to the calling key&apos;s role, so a key can discover exactly what it is permitted to call.
• Gates IaC scan uploads behind a new `CodeRepository:RequestScan` permission on `POST /v1/tenant/shiftleft/iac/scan`; custom roles can add it via &apos;Request code scans&apos; under &apos;Manage integrations&apos;.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Say hello to a new Redshift check:</title>
      <link>https://docs.plerion.com/changelog#2026-09-21</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-09-21</guid>
      <pubDate>Mon, 21 Sep 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds four new checks: Redshift enhanced VPC routing, Security Hub AI Best Practices, Kinesis channel encryption, and Organizations member-account exit controls.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds check `PLERION-AWS-329` (High severity) that fails any Redshift cluster whose `EnhancedVpcRouting` setting is off, ensuring COPY and UNLOAD traffic to S3 stays inside the VPC and is visible to security groups, network ACLs, endpoint policies, and VPC Flow Logs; maps to AWS Foundational Security Best Practices Redshift.7, CIS Controls v8, and NIST 800-53.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds check `PLERION-AWS-1177` (Medium severity) that fails any AWS region where the Security Hub AI Security Best Practices standard is not in `READY` state, covering 31 automated controls for Amazon Bedrock, Amazon Bedrock AgentCore, and Amazon SageMaker; maps to the AWS Well-Architected Machine Learning Lens and Generative AI Lens.
• Adds check `PLERION-AWS-1176` that fails any Kinesis Data Streams channel encrypted with an AWS-owned key rather than a customer-managed KMS key; Plerion now collects Kinesis channels as a new asset type.
• Adds check `PLERION-AWS-1178` (High severity) that fails any AWS organization where at least one active member account is not covered by an unconditional SCP Deny of both `organizations:LeaveOrganization` and `account:CloseAccount`.
• Expands check `PLERION-AWS-791` (&apos;Application Load Balancer does not have access logging enabled&apos;) to pass ALBs that deliver access logs to CloudWatch Logs in addition to those logging to S3.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Custom reports are now custom dashboards, and you can assign one as a homepage:</title>
      <link>https://docs.plerion.com/changelog#2026-09-17</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-09-17</guid>
      <pubDate>Thu, 17 Sep 2026 00:00:00 GMT</pubDate>
      <description>Plerion renames custom reports to custom dashboards and adds homepage assignment, widget builder, and per-user home dashboard override.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds `Assign as homepage` action in `Settings &gt; Custom dashboards` to designate a dashboard as the landing page for selected users and user groups on sign-in.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds `Add widget` panel of ready-made widgets and `Build your own` flow with `Show me`, `Broken down by`, and `Shown as` fields for creating custom dashboard widgets.
• Adds `Profile &gt; Home dashboard` setting that lets individual users override any admin-assigned homepage dashboard, with clearing restoring the assignment.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Onboard with Terraform and scan in a service account you own:</title>
      <link>https://docs.plerion.com/changelog#2026-09-16</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-09-16</guid>
      <pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate>
      <description>Plerion Terraform onboarding now supports all three workload scanning modes, including operator-owned service accounts.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Terraform onboarding now supports all three workload scanning deployment models, including a service account you own and Plerion operates, keeping scanning inside your organization without appliances in scanned accounts.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Two Terraform templates provision a service account setup: one grants Plerion the required access, and one deploys per-region resources (appliance network, auto-scaling scan pool, and snapshot encryption key), both registering with Plerion automatically during `terraform apply` with no manual console steps.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion SCIM provisioning:</title>
      <link>https://docs.plerion.com/changelog#2026-09-15</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-09-15</guid>
      <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds SCIM 2.0 provisioning, user groups with role inheritance, org-scoped API keys, and break-glass admin accounts.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds SCIM 2.0 provisioning support so Okta, Microsoft Entra ID, or any SCIM 2.0 identity provider can create, update, and deactivate Plerion users, with existing users matched by email address and adopted automatically.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds user groups that grant roles to every member, syncable from an identity provider over SCIM or created directly in Plerion.
• Adds organization API keys scoped to the whole organization with `read` or `readWrite` access, used by identity providers for SCIM provisioning.
• Adds break-glass admin accounts — organization admins who can always sign in with a password and cannot be deactivated by an identity provider, with at least one required when SSO or SCIM is enabled.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Google Cloud workload security:</title>
      <link>https://docs.plerion.com/changelog#2026-09-10</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-09-10</guid>
      <pubDate>Thu, 10 Sep 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds Google Cloud workload security scanning for Compute Engine, Cloud Run, and Cloud Functions with keyless WIF access.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Scans inside GCP workloads — Compute Engine instances, managed instance groups, and custom images — for vulnerabilities, software bill of materials, and secrets.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Extends workload scanning to Cloud Run services and Cloud Functions (1st and 2nd gen) for vulnerabilities, SBOMs, and secrets.
• Runs all GCP workload scans inside a dedicated scanning project within your own organization, keeping data in-boundary.
• Authenticates to GCP without keys via workload identity federation (WIF).
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion The Kubernetes collector manager runs on arm64:</title>
      <link>https://docs.plerion.com/changelog#2026-09-08</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-09-08</guid>
      <pubDate>Tue, 08 Sep 2026 00:00:00 GMT</pubDate>
      <description>Plerion Kubernetes collector manager now ships as a multi-arch image supporting arm64 (Graviton) alongside amd64.
• Publishes the Kubernetes collector manager as a multi-architecture image for both `amd64` and `arm64`, enabling deployment on Graviton node pools without requiring a dedicated x86 node or `nodeSelector` configuration.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Review external access to AWS with resource access grants:</title>
      <link>https://docs.plerion.com/changelog#2026-08-21</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-08-21</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds external access inventory and in-product access reviews across 97 AWS resource types and four sharing mechanisms.
• Builds an external access grant inventory for every tenant, analyzing 97 AWS resource types across four sharing mechanisms: resource policies, role trust policies, Resource Access Manager (RAM) shares, and cross-account permissions set directly as an attribute.
• Supports exporting access grants to a spreadsheet for offline access reviews.
• Enables end-to-end access reviews inside Plerion: assign a team accountable for a grant, record a `Keep`, `Remove`, `Review later`, or `Trust until review` decision, add notes, and set a future review date.
• Maintains a full audit history of every decision change per grant, with a `Past due` preset to surface grants whose review date has passed.
• Raises a finding for every asset that grants access to an external principal not confirmed as trusted, with trusted principals configurable in `Settings &gt; Profiles &gt; Trusted principals`.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Review external access to AWS with resource access grants:</title>
      <link>https://docs.plerion.com/changelog#2026-08-21</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-08-21</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds external access inventory and in-product access reviews across 97 AWS resource types and four sharing mechanisms.
• Builds an external access grant inventory for every tenant, analyzing 97 AWS resource types across four sharing mechanisms: resource policies, role trust policies, Resource Access Manager (RAM) shares, and cross-account permissions set directly as an attribute.
• Supports exporting access grants to a spreadsheet for offline access reviews.
• Enables end-to-end access reviews inside Plerion: assign a team accountable for a grant, record a `Keep`, `Remove`, `Review later`, or `Trust until review` decision, add notes, and set a future review date.
• Maintains a full audit history of every decision change per grant, with a `Past due` preset to surface grants whose review date has passed.
• Raises a finding for every asset that grants access to an external principal not confirmed as trusted, with trusted principals configurable in `Settings &gt; Profiles &gt; Trusted principals`.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Detection exemptions, now over the API:</title>
      <link>https://docs.plerion.com/changelog#2026-08-20</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-08-20</guid>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds API access to detection exemptions — read, write, or clear without opening the platform.
• New API endpoints to read, write, and clear detection exemptions on any detection without using the platform UI.
• Exemption matching supports asset name, tags, region, principal, or API Gateway route as match criteria.
• Existing findings on the dashboard are re-evaluated immediately when exemptions are written, rather than waiting for the next scan.
• List profiles via the API first — the default profile covers only integrations that have no profile of their own.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Detection exemptions, now over the API:</title>
      <link>https://docs.plerion.com/changelog#2026-08-20</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-08-20</guid>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <description>Plerion adds API access to detection exemptions — read, write, or clear without opening the platform.
• New API endpoints to read, write, and clear detection exemptions on any detection without using the platform UI.
• Exemption matching supports asset name, tags, region, principal, or API Gateway route as match criteria.
• Existing findings on the dashboard are re-evaluated immediately when exemptions are written, rather than waiting for the next scan.
• List profiles via the API first — the default profile covers only integrations that have no profile of their own.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Plerion’s compliance frameworks, rebuilt against today’s detections:</title>
      <link>https://docs.plerion.com/changelog#2026-08-17</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-08-17</guid>
      <pubDate>Mon, 17 Aug 2026 09:02:52 GMT</pubDate>
      <description>Plerion rebuilds 40 compliance frameworks with 15,250 mappings, adds CIS AWS Benchmark v7.0.0, and retires superseded editions.
• Rebuilds 40 compliance frameworks from scratch against the current detection catalog, producing 15,250 control-to-detection mappings across AWS, Azure, GCP, and now Kubernetes (29 frameworks).
• Promotes 18 frameworks to their publisher&apos;s latest edition, including PCI DSS 4.0.1, NIST SP 800-53 Rev 5 Release 5.2.0, CSA CAIQ v4.1, UK NCSC CAF 4.0, and FedRAMP Rev 5 CR26 baselines.
• Adds CIS Amazon Web Services Foundations Benchmark v7.0.0 with all 70 recommendations mapped to Plerion detections, including six new AWS Organizations controls (centralized root access, authorization guardrails, organizational unit structure, delegated administrators) and a check for reaching AWS services over VPC endpoints, each tagged with CIS Level 1 or Level 2 profile.
• Retires 23 superseded framework editions — including PCI DSS 4.0 and 3.2.1, NIST CSF v1.1, ISO/IEC 27001:2013, and FFIEC CAT — removing them from the framework list while preserving existing mappings.
Breaking changes:
• Compliance posture percentages will shift in both directions across all 40 rebuilt frameworks because the control-to-detection mappings were reconstructed rather than patched.
• 23 retired framework editions (including PCI DSS 4.0, PCI DSS 3.2.1, NIST CSF v1.1, ISO/IEC 27001:2013, CIS AWS Foundations Benchmark v4.0.1, and FFIEC CAT) are removed from the framework list; FFIEC CAT has no successor framework.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Plerion’s compliance frameworks, rebuilt against today’s detections:</title>
      <link>https://docs.plerion.com/changelog#2026-08-17</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-08-17</guid>
      <pubDate>Mon, 17 Aug 2026 09:02:52 GMT</pubDate>
      <description>Plerion rebuilds 40 compliance frameworks with 15,250 mappings, adds CIS AWS Benchmark v7.0.0, and retires superseded editions.
• Rebuilds 40 compliance frameworks from scratch against the current detection catalog, producing 15,250 control-to-detection mappings across AWS, Azure, GCP, and now Kubernetes (29 frameworks).
• Promotes 18 frameworks to their publisher&apos;s latest edition, including PCI DSS 4.0.1, NIST SP 800-53 Rev 5 Release 5.2.0, CSA CAIQ v4.1, UK NCSC CAF 4.0, and FedRAMP Rev 5 CR26 baselines.
• Adds CIS Amazon Web Services Foundations Benchmark v7.0.0 with all 70 recommendations mapped to Plerion detections, including six new AWS Organizations controls (centralized root access, authorization guardrails, organizational unit structure, delegated administrators) and a check for reaching AWS services over VPC endpoints, each tagged with CIS Level 1 or Level 2 profile.
• Retires 23 superseded framework editions — including PCI DSS 4.0 and 3.2.1, NIST CSF v1.1, ISO/IEC 27001:2013, and FFIEC CAT — removing them from the framework list while preserving existing mappings.
Breaking changes:
• Compliance posture percentages will shift in both directions across all 40 rebuilt frameworks because the control-to-detection mappings were reconstructed rather than patched.
• 23 retired framework editions (including PCI DSS 4.0, PCI DSS 3.2.1, NIST CSF v1.1, ISO/IEC 27001:2013, CIS AWS Foundations Benchmark v4.0.1, and FFIEC CAT) are removed from the framework list; FFIEC CAT has no successor framework.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion Pleri now raises pull requests in Azure DevOps:</title>
      <link>https://docs.plerion.com/changelog#2026-08-10</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-08-10</guid>
      <pubDate>Tue, 11 Aug 2026 09:15:49 GMT</pubDate>
      <description>Pleri can now open, review, and abandon pull requests in Azure DevOps repositories to remediate IaC issues.
• Pleri can check pull request status, request a review, or abandon a pull request with a reason inside Azure DevOps.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
    <item>
      <title>Plerion GCP AI coverage widens further:</title>
      <link>https://docs.plerion.com/changelog#2026-08-07</link>
      <guid isPermaLink="true">https://docs.plerion.com/changelog#2026-08-07</guid>
      <pubDate>Sat, 08 Aug 2026 04:44:44 GMT</pubDate>
      <description>Plerion adds 46 new GCP AI posture checks across Vertex AI, Model Armor, Dialogflow CX, Cloud TPU, and more.
• 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.
• Adds project-level org-policy guardrails covering Vertex AI Workbench access and Model Garden model use.
• Extends asset discovery to 16 new GCP resource types behind the newly supported AI services.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/plerion</description>
    </item>
  </channel>
</rss>
