Xello and Kode Bezopasnosti Sign Technological Partnership to Integrate Equipment Emulation into Xello Deception Platform
Xello and Kode Bezopasnosti have concluded a technological partnership agreement aimed at strengthening protection against targeted attacks through enhanced deception capabilities.
Xello, a Russian developer of platforms for data and infrastructure protection, and Kode Bezopasnosti, a Russian developer of software and hardware information security tools, will work together to integrate equipment emulation into the Xello Deception platform.
The partnership will allow Xello Deception, the first domestic Distributed Deception Platform, to emulate hardware from Kode Bezopasnosti. This addition will make the false layer of IT assets more realistic and broaden scenarios for early identification of threats in real-world infrastructures.
Statements from company executives
"We carefully consider customer requests and develop Xello Deception with the specifics of actual infrastructures in mind. Cooperation with Kode Bezopasnosti will expand the platform's functionality and make the false layer even more plausible in organizations that use this vendor's solutions. The partnership also opens new opportunities for expertise exchange. Joint work by our teams will help improve the direction of proactive threat detection," noted Rustam Zakirov, head of the Xello Deception product.
"Deception technologies are becoming an increasingly sought-after tool in the arsenal of information security teams. Against the backdrop of growing targeted attacks, organizations need not only to strengthen the perimeter but also to promptly notice signs of an intruder's presence inside the infrastructure. The partnership with Xello is an opportunity to support the development of a promising direction on the Russian market and contribute to expanding practical scenarios for the use of cyber deception," emphasized Pavel Korostelev, head of strategic marketing at Kode Bezopasnosti.
Related articles
OAuth Authorization Server Built Without Storing User Profiles
The article details the evolution of an OAuth Authorization Server that deliberately avoids storing user profiles, relying instead on external identity providers for authentication. It addresses three core constraints: hundreds of dynamically created isolated APIs, a public SPA client without a BFF, and the inability of resources to query the AS on every request. The design separates concerns so the AS handles only clients, tenants, grants, audiences, scopes, keys, sessions, and token issuance while the Main API owns profiles and roles. Tokens are managed securely inside a Service Worker using a custom FedCM grant, eliminating races across tabs and reducing XSS exposure. The approach minimizes blast radius, simplifies compliance, and keeps the AS replaceable without affecting product domain logic.
Why a 202-Character License Key Uses ECDSA P-256 Instead of Ed25519 or RSA
A developer building offline license verification for a .NET desktop application evaluated Ed25519, RSA, and ECDSA P-256 before selecting the last option. The decision was driven by the requirement for zero external dependencies, keys short enough for manual entry from email, and support for key rotation without breaking existing licenses. Although Ed25519 offers faster verification and a smaller public key, it is absent from System.Security.Cryptography in both .NET 8 and .NET 10, with API approval only targeted for version 11. RSA-2048 produces signatures too long for practical use, resulting in a 571-character Base32 string that users would find cumbersome. ECDSA P-256 with SHA-256 delivers a fixed 64-byte signature that becomes a manageable 202-character key when encoded in Base32, while remaining fully available in the runtime. The article also covers performance measurements, the risks of ECDSA nonce generation, and the deliberate choice of the IEEE P1363 signature format to guarantee fixed-length output.
Pilcrow Publishes Free Comprehensive Guide on Web Authentication
Author Pilcrow has released a detailed, ad-free handbook covering authentication and authorization practices for web applications. The resource draws on personal experience and includes practical examples in JavaScript and Go. It examines password-based methods, email verification, multi-factor authentication, passwordless flows, and passkeys while highlighting associated risks and usability trade-offs. The book also provides in-depth guidance on session management, token security, expiration policies, and email address handling as account identifiers. Recommendations emphasize choosing methods that match application security requirements and user expectations. Additional context is given on OWASP resources and community support channels.
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.