redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem
redb 3.4.0 introduces four major capabilities aimed at the day-after-deployment phase of running integration routes on .NET. The ecosystem comprises typed storage redb on top of Postgres, MSSQL and SQLite, the integration engine redb.Route that provides more than thirty connectors modeled on Apache Camel, the redb.Tsak runtime with dashboard, hot-reload and clustering, and redb.Identity implementing OIDC and OAuth 2.1.
The first feature, replay checkpoints, lets developers mark safe points inside a route using the Replayable DSL method. When a downstream step fails, the exchange snapshot captured at the last checkpoint can be replayed without re-executing earlier side effects such as card charges. The mechanism relies on a new IExchange.Snapshot primitive that performs a deep isolated copy, avoiding the shared-body behavior of the existing Clone method used by splitters.
Failed exchanges that carried a checkpoint are automatically placed into a dead-letter queue table. Operators can list, replay or discard these exchanges through the dashboard, REST API or CLI commands. Retention is handled by a standard cron route rather than an internal timer.
The second major change separates the framework assemblies into a Libs/shared directory. Early bootstrap code installs a custom assembly resolver so that redb.Core, providers and connectors are loaded from the shared location. Replacing a single DLL now patches the running system without rebuilding Tsak archives or container images. Version checks ensure that only patch-level differences between the shared layer and the host are permitted.
Secret handling has been moved from heuristic lists to declarative attributes. Endpoint option properties marked with [Sensitive] are automatically redacted by EndpointUri.Sanitize before any logging, OpenTelemetry tagging or health-check output occurs. All thirty-seven credential-bearing options across twenty-two connectors have been annotated.
Finally, the runtime now enforces role-based access on management APIs, records persistent audit events and verifies cryptographic signatures on modules loaded at runtime. redb.Identity has adopted the common ecosystem version number so that compatibility questions are answered by a single version digit.
Related articles
R-Vision SIEM Demonstrates Resilience During Intense Standoff 17 Cyber Defense Exercise
A mixed team from akPots defended the Telecom sector at Standoff 17 using R-Vision SIEM as the central correlation platform while facing more than ten simultaneous red-team groups. The exercise featured nine realized critical events out of 37 planned scenarios, including satellite tracking disruption, IPTV broadcast manipulation, and unlimited eSIM issuance. Team members had to master the SIEM in real time rather than through pre-loaded logs, relying on raw search, custom dashboards, and grouping features to cut through massive alert volumes. Additional tools such as PT Application Firewall, PT NAD, PT Sandbox, and PT Container Security provided visibility into network traffic, file behavior, and Kubernetes environments. The team organized work through dedicated chat threads, a shared living document for IOCs, and a captain role to balance workload across distributed participants. Feedback highlighted the need for one-click widget-to-raw-event navigation, vendor-supplied detection scenarios, and nested grouping to improve future investigations.
Avanpost Launches Identity Cloud Service, CURATOR Becomes First Partner
Avanpost has begun commercial operation of its Identity Cloud platform, a subscription-based service for multi-factor authentication and single sign-on aimed at employees and contractors. The service removes the need for heavy on-premises IAM deployments by allowing organizations to adopt cloud identity protection through flexible subscription plans. CURATOR became the first partner to roll out the platform, offering it under the CURATOR.IDENTITY brand. Four tariff tiers are available, ranging from basic Start to the upcoming Zero Trust package that includes device verification and continuous trust assessment. Each customer receives an isolated environment with its own database, while Access Bridge keeps infrastructure secrets on-premises and supports offline authentication during connectivity loss. Partners can either resell the Avanpost service or deploy the platform in their own infrastructure and sell it under their own branding.
Microsoft 365 Admin Tool Exposes Pitfalls in Graph, Exchange PowerShell and Intune Management
An open-source developer has released version 2.0 of SwissKnife for MS Graph, a tool that adds a safe preview-and-apply layer on top of Microsoft 365 administration. The project addresses the lack of a native what-if mode in Microsoft Graph and the incomplete coverage of Exchange tasks in the Graph API. It implements a two-step plan-and-apply workflow, supports fallback to Exchange Online PowerShell or the Admin API, and runs community scripts under strict constraints. The author details multiple real-world obstacles including named-location ID drift in Conditional Access policies, masked secrets returned by Intune, and limitations when restoring Transport Rules from snapshots. The tool also provides a worker mode for macOS and Linux users and enforces script signing plus AST-based command whitelisting. Feedback is requested on error messages and tasks that still require manual PowerShell use.
Neuromorphic Processors Lag Behind GPUs for Large AI Models Despite Energy Advantages
Neuromorphic chips such as Intel Loihi promise major energy savings by activating only when events occur, yet data centers remain dominated by GPUs optimized for dense matrix operations in generative AI. The mismatch arises because modern large language models rely on high-precision linear algebra, massive memory bandwidth, and mature software stacks that neuromorphic architectures currently lack. Researchers are exploring spiking transformers and on-chip plasticity via mechanisms like STDP, but scaling to billions of parameters remains challenging. Companies including BrainChip, SynSense, and SpiNNaker2 have released commercial neuromorphic hardware, yet the absence of standardized tools and clear performance gains for mainstream workloads slows adoption. Hybrid approaches combining neuromorphic blocks with in-memory computing, analog circuits, and photonic accelerators may define future heterogeneous systems rather than outright replacement of GPUs.