<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>emisar — The Cyber Toolchain</title>
    <link>https://cybertoolchain.io/tools/emisar</link>
    <description>New releases and features in emisar, tracked by The Cyber Toolchain.</description>
    <language>en</language>
    <lastBuildDate>Tue, 18 Aug 2026 02:17:43 GMT</lastBuildDate>
    <atom:link href="https://cybertoolchain.io/tools/emisar/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>emisar v0.41.0</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/v0.41.0</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/v0.41.0</guid>
      <pubDate>Tue, 18 Aug 2026 02:17:43 GMT</pubDate>
      <description>emisar v0.41.0 adds role-scoped consoles, live session reconnection on permission changes, and 100-pack catalog with new GCP, Consul, and HCP Terraform actions.
• Role and scope changes (member role, runner access, pack access) now take effect immediately in open web sessions, reconnecting the session before stale authority can be acted on.
• Billing managers now receive a finance-only console; operators can manage agents, approvals, and runbooks without gaining team or policy administration rights.
• Scoped admins are blocked from delegating more reach than they hold or triggering account-wide pack cleanup.
• Reads that expose every pack version or an exact run command now require a checked subject rather than relying on already-filtered callers.
• The read-only staff console now requires MFA proof tied to the current enrollment.
• Console navigation, actions, filters, and empty states now adapt to the member&apos;s role and access level, with role-aware explanations for restricted pack and action views.
• SSO group mappings now paginate in both directions.
• The pack catalog expands to 100 packs and 1,689 actions.
• Consul pack gains the ability to snapshot registration churn; the debugging pack adds bounded process context, environment-key, argv, and connection reads.
• GCP Monitoring pack adds Cloud Logging name and entry reads.
• HCP Terraform pack exposes replacement paths in plan summaries.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
    <item>
      <title>emisar v0.40.0</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/v0.40.0</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/v0.40.0</guid>
      <pubDate>Thu, 13 Aug 2026 21:44:31 GMT</pubDate>
      <description>emisar v0.40.0 adds self-updating runners, paginated MCP responses, and 100-pack catalog coverage including JFrog, Databricks, and Sentry.
• Adds `emisar update` subcommand so installer-managed runners can update themselves, with automatic release-checksum and GitHub build-attestation verification before executing stop, swap, restart, and rollback.
• Adds `--json` flag to `emisar pack update` that now emits its partial report before returning a post-update validation error, preserving machine-readable output for automation pipelines.
• `wait_for_run` now returns paginated 64 KiB continuation pages when a terminal runbook result exceeds one MCP response, keeping the summary in the first response.
• Catalog expands to 100 packs and 1,682 actions, adding JFrog Artifactory, Databricks, Sentry, Symbolicator, and NTPsec, with larger Cassandra and Cloudflare coverage.
• Runner, pack, action, approval, and audit discovery now enforces the member&apos;s current runner and pack scope across both the console and MCP.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
    <item>
      <title>emisar v0.39.0</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/v0.39.0</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/v0.39.0</guid>
      <pubDate>Mon, 10 Aug 2026 06:45:19 GMT</pubDate>
      <description>emisar v0.39.0 overhauls runbook versioning to track decisions, adds MCP slug-keyed API, and expands secret redaction.
• Adds `get_runbook` and `update_runbook_draft` MCP endpoints keyed by slug, so agents replace only the single unpublished change under the hash they read; publication remains human-only.
• Runbook versioning now tracks published releases (e.g. `Run v3`) rather than counting every save, with a single in-flight draft per runbook instead of unbounded version rows.
• Publishing now shows a diff of changed lines against the exact canonical text whose hash defines the release, requiring explicit consent plus the hash of what you read before an unpublished change can run.
• Attempting to run a named older release now returns `not_live` instead of silently dispatching current content.
• Executions snapshot the definition they dispatched at start time, so later edits, publishes, or deletes cannot rewrite audit history.
• Runner `v0.19.0` expands automatic secret redaction to cover connection strings, database URLs, key-derivation inputs (salt, pepper), cookie and session signing keys, and passphrase spellings — acting as a safety net beneath per-action redaction declarations.
• pfSense gains resolver, NTP, and WireGuard peer reads (secrets excluded), plus a DHCP reservation action staged for operator approval.
• Behavior harness now runs tests against a real service manager (PID 1), a per-case Docker daemon, iptables in its own namespace, and a real dpkg database for install, remove, and autoremove; uncovered cases are recorded with explicit reasons.
Breaking changes:
• The portal migration collapses all runbook version rows into a single runbook per slug, renumbers published versions into releases, and repoints execution history — this runs automatically before the instance serves on upgrade.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
    <item>
      <title>emisar v0.38.0</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/v0.38.0</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/v0.38.0</guid>
      <pubDate>Sat, 08 Aug 2026 23:56:01 GMT</pubDate>
      <description>Emisar v0.38.0 adds invalid-glob warnings for policy overrides and fixes silent runbook drops and session disconnect failures.
• Adds a real-time advisory warning when a policy override glob cannot match any action ID (e.g. regex-style patterns like `cassandra\.drop_*`), flagging deny rules that appear protective but cover nothing — warning is non-blocking to allow rules targeting not-yet-installed packs.
• Ending a member&apos;s sessions now disconnects the live console session itself, not only the cookie behind it, so administrator-initiated session termination during an incident takes effect immediately.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
    <item>
      <title>emisar runner-v0.17.2</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/runner-v0.17.2</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/runner-v0.17.2</guid>
      <pubDate>Fri, 07 Aug 2026 02:34:35 GMT</pubDate>
      <description>emisar runner 0.17.2 adds BunnyCDN operations, explicit runbook targets, and production MIG rollout zone placement.
• Adds BunnyCDN operations and explicit runbook targets.
• Allows production MIG rollout placement in available zones.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
    <item>
      <title>emisar v0.36.0</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/v0.36.0</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/v0.36.0</guid>
      <pubDate>Fri, 31 Jul 2026 20:58:14 GMT</pubDate>
      <description>Emisar v0.36.0 adds staged runbooks with typed inputs and parallel execution, MCP 2026-07-28 routing, and 91 action packs with bounded diagnostics.
• Adds staged runbooks with typed inputs, sequential or parallel stage execution against selected runner groups, named step outputs, success condition testing, and explicit wait bounds.
• Adds a single pre-execution approval gate that freezes the complete runbook execution plan before work begins.
• Adds canonical JSON runbook definition format shared across the console, MCP, and execution pages, with attempt, output, wait, and terminal cause history.
• Adds OIDC discovery and JWKS refresh under a shared bounded address policy that rechecks the actual response received; changing an issuer clears credentials tied to the old one.
• Adds atomic SCIM group patch application in wire order, with body bounding before authentication and automatic session and identity link retirement when a connection is disabled.
• Adds per-action account membership resolution for run and approval attribution, preventing cross-workspace profile leakage into the audit log.
• Adopts MCP 2026-07-28 routing headers and dual-era endpoint on both the bridge and portal, including OAuth Client ID Metadata Documents.
• Expands the action catalog to 91 packs and 1,386 actions, adding bounded diagnostics for GCP, Pure FlashArray, Terraform, Nomad, OIDC/JWKS, nftables, TCP, and Docker Compose.
• Makes pack actions fail explicitly on missing source commands or HTTP error responses instead of reporting empty success through a downstream pipe.
Breaking changes:
• Disabling a SCIM connection now retires the sessions and pending identity links it vouched for — active sessions tied to a disabled SCIM connection will be terminated on upgrade.
• Pack actions now fail on missing source commands and HTTP error responses rather than returning an empty success — any automation that depended on silent empty-success behavior will begin receiving failures.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
    <item>
      <title>emisar mcp-v0.5.0</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/mcp-v0.5.0</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/mcp-v0.5.0</guid>
      <pubDate>Fri, 31 Jul 2026 20:57:06 GMT</pubDate>
      <description>emisar mcp-v0.5.0 expands its infrastructure diagnostics catalog.
• Expands the infrastructure diagnostics catalog with additional checks.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
    <item>
      <title>emisar runner-v0.16.0</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/runner-v0.16.0</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/runner-v0.16.0</guid>
      <pubDate>Fri, 31 Jul 2026 20:54:22 GMT</pubDate>
      <description>emisar runner v0.16.0 expands its infrastructure diagnostics catalog.
• Expands the infrastructure diagnostics catalog with additional checks.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
    <item>
      <title>emisar v0.35.0</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/v0.35.0</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/v0.35.0</guid>
      <pubDate>Mon, 27 Jul 2026 17:36:52 GMT</pubDate>
      <description>Emisar v0.35.0: hostname-based runner identity, retention safety for connected runners, and faster behavior matrix CI.
• Runners without an explicit `runner.id` now use their hostname as identity, so reboots reconnect the same runner and replaced ephemeral hosts auto-enroll without a persisted identity file.
• Pack retention no longer sweeps versions still advertised by a connected runner, preventing `pack_untrusted` dispatch failures after idle-window cleanups.
• Hosted admin runner bootstraps from a version-pinned release download with retries, eliminating GitHub API anonymous rate-limit failures on control-plane VM start.
• Behavior cases for high/critical pack actions now run in disposable Compose projects as a non-root identity against real services, with network-path readiness probes enforced before cases start.
• The snmp pack&apos;s OSPF adjacency fixture supports AppArmor-confined hosts via network namespace construction.
• Behavior matrix CI runs in under half previous wall-clock time via pre-pulled images, sharded slow suites, and concurrency caps on heavyweight services.
• CI now enforces that every high/critical action changed by the argument-boundary sweep has a successful behavior case or a declared machine-readable risk exception.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
    <item>
      <title>emisar v0.34.0</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/v0.34.0</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/v0.34.0</guid>
      <pubDate>Sun, 26 Jul 2026 15:52:05 GMT</pubDate>
      <description>emisar v0.34.0 adds streaming run output via MCP cursor paging and authoring-time pack argument validation.
• New `wait_for_run` MCP call accepts an output cursor and returns the next cursor, enabling agents to stream run output incrementally as it arrives rather than polling.
• Curl-backed API actions now fail on 4xx/5xx HTTP responses instead of reporting transport success, making pack error handling reliable.
• Pre-run dispatch rejections (contract changes, refusals, rate limits) are now logged with bounded, allowlisted fields, making refused MCP calls visible in operations.
• Pack-trust conflict errors now name the specific runners that disagree about an action instead of failing generically.
• Operator input (approval notes, grant scopes, policy overrides) now survives console re-renders triggered by co-approver broadcasts or refused submits.
• Added `llms.txt` index and a Keycloak setup guide to documentation.
• Documentation reorganized by task: SSO and directory sync split, cloud and CLI agent connection split, containers separated into Kubernetes and Nomad sections with a host-install page, and operational limits and autoscaling fleets given dedicated pages.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
    <item>
      <title>emisar v0.29.0</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/v0.29.0</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/v0.29.0</guid>
      <pubDate>Thu, 16 Jul 2026 20:46:26 GMT</pubDate>
      <description>Emisar v0.29.0 tightens MCP argument coercion, improves error clarity, and raises pack risk levels for secret-dense config dumps.
• Scalar MCP arguments sent as canonical strings (e.g. `&quot;limit&quot;: &quot;50&quot;`, `&quot;dry_run&quot;: &quot;true&quot;`) now coerce to their expected types instead of failing the call.
• MCP argument faults now name the specific field and type mismatch — e.g. `limit must be a JSON integer from 1 to 100; it was sent as a string.` — replacing generic contract errors; enum faults list allowed values and unknown arguments are spelled out against the allowed set.
• MCP run summaries omit zero-information fields: `stdout`/`stderr`, byte-count, and truncation fields are absent when a stream produced no bytes; `output_complete` appears only when false; per-stream SHA-256 digests removed from the MCP projection (retained on the run detail page and audit record).
• Disabling two-factor authentication now requires a fresh step-up challenge, preventing a hijacked session from quietly weakening an account.
• Production session cookies always carry the `Secure` flag.
• Cloud-init user/vendor data, cloud-config, pm2 env, nginx config dumps, and caddy config dumps moved from risk level `low` to `medium`, matching `linux.sudoers_dump`, removing them from the ungated low-read path.
• Redis ACL password hashes are redacted from `acl_list` and `acl_getuser` output, preventing ungated reads from leaking crackable material.
• Exec-style arguments across docker, systemctl, podman, minio, and related packs now anchor their first character to an alphanumeric, blocking hostile values from being parsed as leading-dash flags.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
    <item>
      <title>emisar v0.28.0</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/v0.28.0</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/v0.28.0</guid>
      <pubDate>Thu, 16 Jul 2026 18:13:53 GMT</pubDate>
      <description>emisar v0.28.0 adds `emisar doctor` dispatch-log checks, SSO/MFA route coverage, SCIM rate-limiting, and honest fleet degradation diagnostics.
• Adds `emisar doctor` checks for the dispatch log, degraded packs, and last cloud rejection; adds `emisar state check-dispatch-log` for scriptable verdict on dispatch-log health.
• Adds `QUARANTINE_DISPATCH_LOG=1` environment variable to `install.sh` to automatically quarantine an unreadable dispatch log instead of leaving a host crash-looping after an upgrade.
• `install.sh` now verifies dispatch state with the staged binary before touching a running service, aborting with remediation options on failure.
• Degraded packs now surface as named load failures in MCP `list_runners` responses and as an amber notice with reasons and reinstall remedy on the runner detail page.
• Denied runs now return a bounded policy reason in MCP summaries; `find_actions` supports natural multi-term queries.
• Console-created runbooks are now visible and executable over MCP.
• Sign-in enforcement for Require SSO and Require MFA now covers every controller route.
• SCIM, audit-export, and runner-register endpoints are now rate-limited.
• Account and user erasure (GDPR delete) available as an operator-run release task.
• Adds direct alerts for database-down, zero-healthy-backend, and portal VM saturation conditions.
• Adds `docs/COMPATIBILITY.md` naming on-host runner state (dispatch log, installed pack trees) as a compatibility surface with documented migration rules.
• Outbound connections now assert a TLS 1.2 minimum floor.
• Runner binary ships as `runner-v0.13.0` with SLSA-3 build provenance and `SHA256SUMS`.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
    <item>
      <title>emisar v0.27.0</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/v0.27.0</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/v0.27.0</guid>
      <pubDate>Thu, 16 Jul 2026 10:28:48 GMT</pubDate>
      <description>Runner v0.12.0 adds corrupt-state pre-flight checks, bounded MCP failure messages, and account-chooser OAuth consent.
• Corrupt durable dispatch state now halts the runner before it connects to the control plane, preventing a misconfigured runner from silently operating.
• MCP run summaries now include a bounded terminal failure message when the runner supplies one, making MCP failures visible in the portal without a new MCP bridge binary.
• OAuth consent now lets a user choose which account to connect during connector setup.
• Key-bearing connector commands are kept out of shell history.
• Failure causes redact sensitive action arguments before they reach local audit records or the portal.
• A newer non-destructive production plan supersedes an older pending plan, with Terraform confirmation remaining the single human apply gate.
• Unsigned installations no longer open or lock signing nonce state during startup.
Breaking changes:
• Upgrading to runner-v0.12.0 starts a new durable dispatch journal and does not import older unacknowledged entries; downgrading to an earlier runner after v0.12.0 has written new dispatch records is unsupported.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
    <item>
      <title>emisar v0.26.0</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/v0.26.0</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/v0.26.0</guid>
      <pubDate>Thu, 16 Jul 2026 08:43:16 GMT</pubDate>
      <description>Emisar v0.26.0: in-flight run recovery on reconnect and out-of-date MCP bridge flagging in the console.
• Console LLM agents list now groups connections by the operator behind each key, displays the `emisar-mcp` bridge version inline per connection, and flags out-of-date bridges with a one-step path to the upgrade command.
• Control plane recovers runs that were in flight when a runner drops and reconnects, instead of stranding them.
• Runner version-upgrade notice now scopes its count to the current page rather than reading as a single runner across a multi-runner list.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
    <item>
      <title>emisar v0.24.0</title>
      <link>https://github.com/AndrewDryga/emisar/releases/tag/v0.24.0</link>
      <guid isPermaLink="true">https://github.com/AndrewDryga/emisar/releases/tag/v0.24.0</guid>
      <pubDate>Sun, 12 Jul 2026 18:51:52 GMT</pubDate>
      <description>emisar v0.24.0: hardened infrastructure, release integrity attestations, dedicated pack registry, and MCP server listing.
• Pack registry now serves from its own hostname at `registry.emisar.dev/v1/catalog.json`, with anonymous access narrowed to exact object reads.
• Hosted MCP server (`dev.emisar/emisar`) is now published to the official MCP registry.
• Portal releases now publish the exact image exercised by CI, pinned by digest, with provenance and SBOM attestations; fixable HIGH/CRITICAL vulnerabilities block publication.
• Binary releases are now immutable and reproducible, with signed and verified release tags.
• Public status page available at `status.emisar.dev`, with external availability monitoring and on-call escalation.
• Hosted control plane moves to hardened infrastructure with zero-downtime rolling deploys, a private-network database with TLS pinned to a private CA, and no public compute surface.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/emisar</description>
    </item>
  </channel>
</rss>
