<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
    <title>LimaCharlie Release Notes: Extensions</title>
    <link>https://docs.limacharlie.io/10-release-notes/</link>
    <description>Releases of LimaCharlie extensions.</description>
    <language>en</language>
    <generator>LimaCharlie Documentation release feed hook</generator>
    <lastBuildDate>Mon, 07 Sep 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://docs.limacharlie.io/10-release-notes/extensions.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Extensions: Email Security bulk remediation, verdict revisions and the managed-detection switch</title>
      <link>https://docs.limacharlie.io/10-release-notes/#extensions-email-security-bulk-remediation-verdict-revisions-and-the-managed-detection-switch</link>
      <guid isPermaLink="false">tag:docs.limacharlie.io,2026-09-07:release/extensions-email-security-bulk-remediation-verdict-revisions-and-the-managed-detection-switch</guid>
      <pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate>
      <category>extensions</category>
      <description>&lt;h4 id="new-features_11"&gt;New Features&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Bulk remediation over a selection you name.&lt;/strong&gt; Any search result — a filtered page of the queue, a hunt, a list of ids in a file — can now be remediated at the provider in one operation, with the campaign sweep's preview-then-confirm discipline: &lt;code&gt;POST /actions/bulk/preview&lt;/code&gt; reports each message's current state and the distinct-mailbox blast radius and mints a confirmation derived from that exact selection, &lt;code&gt;POST /actions/bulk/execute&lt;/code&gt; returns a &lt;code&gt;bulk_id&lt;/code&gt; immediately and paces the provider writes in the background, and &lt;code&gt;GET /actions/bulk/{bulk_id}&lt;/code&gt; reports per-message outcomes and running counts. Capped at 500 per call, refused rather than truncated above it. &lt;code&gt;limacharlie mailsec message bulk-action&lt;/code&gt; wraps the pair, reads its selection from &lt;code&gt;--msg-uuids&lt;/code&gt;, &lt;code&gt;--input-file&lt;/code&gt; or standard input, and carries the outcome in its exit code.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Verdict revisions are documented end to end.&lt;/strong&gt; &lt;code&gt;POST /messages/{msg_uuid}/verdict&lt;/code&gt; re-judges one message in the &lt;code&gt;analyst&lt;/code&gt; or &lt;code&gt;ai&lt;/code&gt; seat with a required rationale, and &lt;code&gt;GET /messages/{msg_uuid}/revisions&lt;/code&gt; serves the whole append-only chain with the prior state each revision displaced. Re-recording a verdict a message already carries is a success reporting &lt;code&gt;applied: false&lt;/code&gt;, not an error. Revising requires &lt;code&gt;mailsec.act&lt;/code&gt; rather than &lt;code&gt;mailsec.set&lt;/code&gt;, because it can promote a message's evidence to the 400-day lane and emits an &lt;code&gt;EMAIL_VERDICT&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A resolved user report can be reopened.&lt;/strong&gt; &lt;code&gt;POST /reports/{report_id}/reopen&lt;/code&gt; (&lt;code&gt;limacharlie mailsec report reopen&lt;/code&gt;) puts a report back in the queue and keeps its resolution columns, so the row still reads "previously resolved by …" rather than erasing what is being disputed. It is the escape hatch the abuse-mailbox auto-resolver depends on.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The managed detection pack has a documented switch.&lt;/strong&gt; The &lt;code&gt;managed_rules&lt;/code&gt; policy record, the console's Settings toggle, and the &lt;code&gt;set_managed_rules&lt;/code&gt; / &lt;code&gt;get_managed_rules&lt;/code&gt; extension actions all write the same thing. Absent means enabled; a record that states no value is refused; a change reaches the pipeline in seconds, with a five-minute backstop.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Link detonation is documented&lt;/strong&gt;: what triggers it (a &lt;code&gt;suspicious&lt;/code&gt; verdict with links, up to five URLs per message), the organization-wide claim that makes a campaign cost one fetch, every refusal reason, and what a &lt;code&gt;mode: detonation&lt;/code&gt; verdict revision means — including that it never overrules a person or an agent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Time to verdict is a real number.&lt;/strong&gt; &lt;code&gt;coverage&lt;/code&gt;'s &lt;code&gt;overview.processing_latency_p95&lt;/code&gt; reports p50/p95/p99 with the basis it measures, the denominator it measured over, and — when there is no number — which of the two honest reasons applies. Backfilled and re-driven mail is excluded so a recovery cannot report a latency measured in days.&lt;/li&gt;
&lt;li&gt;New &lt;a href="https://docs.limacharlie.io/email-security/troubleshooting/"&gt;Troubleshooting&lt;/a&gt; page: the entitlement gate (mail that arrives while unsubscribed is never read and is never backfilled), watch renewals, silent-mailbox stalls, &lt;code&gt;EMAIL_INGEST_ERROR&lt;/code&gt;, connection handover during a platform update, and the 30-day deletion clock.&lt;/li&gt;
&lt;li&gt;Custom rules now document &lt;code&gt;scope&lt;/code&gt; versus the &lt;code&gt;?&lt;/code&gt; path wildcard — only &lt;code&gt;scope&lt;/code&gt; correlates two conditions on the &lt;em&gt;same&lt;/em&gt; link or attachment — and state plainly that a rule using &lt;code&gt;lookup&lt;/code&gt;, or a &lt;code&gt;post_verdict&lt;/code&gt; rule, cannot be backtested.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See &lt;a href="https://docs.limacharlie.io/email-security/remediation/"&gt;Bulk Remediation&lt;/a&gt;, &lt;a href="https://docs.limacharlie.io/email-security/detections/#revising-a-verdict"&gt;Detections &amp;amp; Verdicts&lt;/a&gt;, &lt;a href="https://docs.limacharlie.io/email-security/policy/#managed_rules"&gt;Policy Reference&lt;/a&gt; and &lt;a href="https://docs.limacharlie.io/email-security/troubleshooting/"&gt;Troubleshooting&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Extensions: Email Security tenant purge</title>
      <link>https://docs.limacharlie.io/10-release-notes/#extensions-email-security-tenant-purge</link>
      <guid isPermaLink="false">tag:docs.limacharlie.io,2026-09-04:release/extensions-email-security-tenant-purge</guid>
      <pubDate>Fri, 04 Sep 2026 00:00:00 GMT</pubDate>
      <category>extensions</category>
      <description>&lt;h4 id="new-features_12"&gt;New Features&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Tenant purge for Email Security&lt;/strong&gt;: everything Email Security holds for an organization can now be deleted on request — the message index and the up-to-400-day evidence lane, campaigns, sender profiles, the product's action audit trail, user (abuse-mailbox) reports, stored raw messages and their parsed copies, link-detonation results, and the organization's provider connection and policy configuration. The purge also stops the mail connections at Microsoft 365 and Google Workspace, so the provider stops sending notifications instead of repopulating the index. It is irreversible, requires Owner-level authority (&lt;code&gt;mailsec.act&lt;/code&gt;, &lt;code&gt;billing.ctrl&lt;/code&gt; and &lt;code&gt;user.ctrl&lt;/code&gt; together), and is recorded in the organization's audit log with the caller's identity and an optional reason.&lt;/li&gt;
&lt;li&gt;The purge is two steps, and previews by default: &lt;code&gt;limacharlie mailsec tenant purge&lt;/code&gt; prints the warning and mints a single-use confirmation token that expires in five minutes, and destroys nothing until that token is passed back with &lt;code&gt;--confirm&lt;/code&gt;. A purge that reports &lt;code&gt;complete: false&lt;/code&gt; did not finish and can simply be re-run with a fresh token. The Python SDK exposes the same pair as &lt;code&gt;Mailsec.prepare_tenant_purge()&lt;/code&gt; and &lt;code&gt;Mailsec.purge_tenant()&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Email Security data is now also deleted &lt;strong&gt;automatically&lt;/strong&gt;: 30 days after an organization unsubscribes from the extension — resubscribing at any point inside that window cancels the scheduled deletion — and immediately when the organization itself is deleted.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See &lt;a href="https://docs.limacharlie.io/email-security/policy/#data-retention-and-deletion"&gt;Data retention and deletion&lt;/a&gt;, the &lt;a href="https://docs.limacharlie.io/email-security/cli/#the-tenant-purge-is-irreversible"&gt;&lt;abbr title="Command-line Interface"&gt;CLI&lt;/abbr&gt; notes&lt;/a&gt; and &lt;a href="https://docs.limacharlie.io/email-security/api-reference/#delete-tenant"&gt;&lt;code&gt;DELETE /tenant&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Extensions</title>
      <link>https://docs.limacharlie.io/10-release-notes/#extensions</link>
      <guid isPermaLink="false">tag:docs.limacharlie.io,2025-05-20:release/extensions</guid>
      <pubDate>Tue, 20 May 2025 00:00:00 GMT</pubDate>
      <category>extensions</category>
      <description>&lt;p&gt;Endpoint Protection extension: a component of the EPP solution that codifies key configurations for Microsoft Defender.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Extensions and Adapters</title>
      <link>https://docs.limacharlie.io/10-release-notes/#extensions-and-adapters</link>
      <guid isPermaLink="false">tag:docs.limacharlie.io,2025-03-28:release/extensions-and-adapters</guid>
      <pubDate>Fri, 28 Mar 2025 00:00:00 GMT</pubDate>
      <category>extensions</category>
      <category>adapters</category>
      <description>&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Git-Sync&lt;/strong&gt;: Take the best from LimaCharlie &lt;abbr title="Infrastructure as Code (IaC) automates the management and provisioning of IT infrastructure using code, making it easier to scale, maintain, and deploy resources consistently. In LimaCharlie, IaC allows security teams to deploy and manage sensors, rules, and other security infrastructure..."&gt;Infrastructure as Code&lt;/abbr&gt; by connecting with Git and syncing the desired sections of your configurations in an easy-to-use UI. See &lt;a href="https://docs.limacharlie.io/5-integrations/extensions/limacharlie/git-sync/"&gt;documentation&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;ext-renigma v1.0.0&lt;/strong&gt;: Initial release of integration with REnigma, an advanced malware analysis platform leveraging its unique Record and Replay technology.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mimecast adapter&lt;/strong&gt;: Connect to the Mimecast API to stream audit events as they happen.&lt;/li&gt;
&lt;/ul&gt;</description>
    </item>
    <item>
      <title>Add-Ons and Adapters</title>
      <link>https://docs.limacharlie.io/10-release-notes/#add-ons-and-adapters</link>
      <guid isPermaLink="false">tag:docs.limacharlie.io,2025-03-14:release/add-ons-and-adapters</guid>
      <pubDate>Fri, 14 Mar 2025 00:00:00 GMT</pubDate>
      <category>extensions</category>
      <category>adapters</category>
      <description>&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;PandaDoc adapter&lt;/strong&gt;: Connect and fetch PandaDoc API logs.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CrowdStrike Falcon Cloud adapter&lt;/strong&gt;: Connect to CrowdStrike Falcon Cloud to stream events as they happen in the CrowdStrike Falcon Console.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Cloud-&lt;abbr title="Command-line Interface"&gt;CLI&lt;/abbr&gt; v1.4.8 &lt;abbr title="LimaCharlie Extensions allow users to expand and customize their security environments by integrating third-party tools, automating workflows, and adding new capabilities. Organizations subscribe to Extensions, which are granted specific permissions to interact with their infrastructure. Extensions..."&gt;Extension&lt;/abbr&gt;&lt;/strong&gt;: Improved observability in &lt;abbr title="Command-line Interface"&gt;CLI&lt;/abbr&gt; extensions such as ext-cloud-cli. Additionally, improved error handling and reporting around long-running &lt;abbr title="Command-line Interface"&gt;CLI&lt;/abbr&gt; commands which may have gotten stuck or timed out.&lt;/li&gt;
&lt;/ul&gt;</description>
    </item>
    <item>
      <title>ext-usage-alerts v1.0.0</title>
      <link>https://docs.limacharlie.io/10-release-notes/#ext-usage-alerts-v100</link>
      <guid isPermaLink="false">tag:docs.limacharlie.io,2025-01-09:release/ext-usage-alerts-v1-0-0</guid>
      <pubDate>Thu, 09 Jan 2025 00:00:00 GMT</pubDate>
      <category>extensions</category>
      <description>&lt;p&gt;Newly released extension which allows you to create, maintain, and automatically refresh usage alert conditions for an organization.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
