OpenTelemetry

Do You Really Know What Your AI Agent Is Doing in the Sandbox?

The rise of agentic AI systems has exposed critical gaps in observability when agents run inside strong isolation environments. Traditional eBPF-based monitoring on the host kernel fails when agents execute under separate kernels provided by gVisor, Kata, or Firecracker. Experiments with a controlled syscall generator show that visibility depends heavily on filesystem configuration rather than the choice of runtime. Standards such as MCP, OpenTelemetry, and RuntimeClass address parts of the agent lifecycle but leave actual syscall-level reporting undefined. Measurements across multiple configurations reveal that some operations, especially execve, never reach the host regardless of the sandbox used. The findings highlight that security tooling must be re-evaluated after every change in sandbox settings.

redb 4.0 Released: XML Routes, Lazy References, Unique Keys and WS-Trust Across the Ecosystem

The redb ecosystem has delivered a major simultaneous release across all core components, bringing redb.Core, redb.Route, redb.Tsak and redb.Identity to version 4.0.0. The update introduces declarative XML routing, lazy object references, unique key constraints, and a full WS-Trust SOAP facade while closing multiple security issues reported through external audits and community feedback. Seventy-six NuGet packages, seven container images and platform archives for Windows and Linux are now available, with the Pro edition remaining free and license-free throughout the 4.x line. Significant internal changes include a unified expression language, support for modern data formats such as Protobuf and Avro, and improved handling of distributed caches and OpenTelemetry metrics. Security hardening covers header sanitization in all identity facades, consent-page protections, dashboard access controls and a switch to bcrypt password hashing. Existing clusters must be stopped before upgrade because mixed versions are not supported, and large databases require a maintenance window for schema changes and partial index creation.

Secure Error Logging Practices to Prevent Information Leaks Across Java, Kotlin, JavaScript and Python

The article examines how improper error logging can expose sensitive details such as stack traces, file paths, library versions and database structures, enabling attackers to map applications and craft targeted exploits. It covers core logging levels from DEBUG to FATAL, mechanisms including text files, binary logs and databases, plus the roles of Trace ID and Correlation ID in tracing requests across microservices. Real-world vulnerable code examples in Flask and SQLite demonstrate direct exception output, manual traceback exposure and SQL error leakage that confirm technologies like Python 3.10 or SQLite usage. CWE categories including CWE-209, CWE-532, CWE-538 and CWE-1295 are referenced to classify risks of information disclosure through logs. Mitigation steps include stripping version headers in Nginx, sanitizing inputs with regular expressions, using OpenTelemetry for structured JSON logging and avoiding debug modes in production. The guidance stresses balancing detailed logs for incident response with protections against injection and reconnaissance.

redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem

redb 3.4.0 delivers operational improvements for the .NET integration platform that includes typed storage over Postgres, MSSQL and SQLite, the redb.Route engine modeled after Apache Camel, the Tsak runtime with dashboard and clustering, and redb.Identity for OIDC and OAuth 2.1. The release focuses on post-deployment resilience with replay checkpoints that capture message state at named points inside routes, allowing safe re-execution of downstream steps without duplicating side effects. A shared runtime layer moves framework assemblies into a separate Libs/shared directory so that individual DLLs can be replaced without rebuilding or redeploying the entire Tsak or Identity packages. Secrets are now declared with a [Sensitive] attribute on endpoint options, ensuring URIs containing passwords or keys are sanitized before they reach logs, metrics or health checks. Additional controls include role-based access to management APIs, persistent audit trails and cryptographic signing of dynamically loaded modules. All Pro features remain free on the entire 3.x line with no licensing server required.

OTUS Publishes Extensive Digest Covering Kubernetes, GitLab CI, DevSecOps and Infrastructure Reliability

OTUS has released a large-scale digest that compiles free lessons, practical articles and advanced courses focused on real-world infrastructure challenges. The collection addresses interconnected topics including Kubernetes container orchestration, GitLab CI pipeline automation, observability with OpenTelemetry, network troubleshooting, and DevSecOps practices. Readers can explore specific lessons on secrets management with Vault, load testing, RAID recovery, and kernel-level protections in Linux. The digest also features in-depth articles on Docker Compose configuration, CrowdSec migration, L2 network loops, and self-service deployment models. For experienced professionals, OTUS offers specialized courses on high-load systems, PostgreSQL administration, Linux kernel development, and advanced networking with BGP and OSPF.