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
Why 99% Attack Detection Rules Generate 99.9% False Positives in Real SOC Environments
A detection rule claiming 99% attack coverage with only 1% false positive rate sounds effective on paper, yet in practice it produces roughly one thousand false alerts for every genuine incident. Using a realistic example of 200,000 daily logins containing just two real compromises, the article demonstrates that 1.98 true positives are buried among 2,000 false positives. Bayes' theorem explains why sensitivity improvements barely move the needle while reducing the false-positive rate or narrowing the population yields dramatic gains in precision. The piece outlines three practical levers—lowering FPR, scoping rules to high-risk accounts, and cascading cheap-then-expensive checks—that cut analyst workload by orders of magnitude without sacrificing meaningful coverage. It also warns that chronically low-precision rules train analysts to ignore alerts, eventually leading to the rule being disabled despite remaining in compliance matrices. The recommended metric pair is therefore confirmed detections alongside coverage, rather than coverage alone.
ChatGPT Knows Your Company but Google Doesn't: Step-by-Step Guide to Diagnosing AI Visibility Issues
The complaint that a brand is missing from AI answers often masks six distinct technical problems that require opposite fixes. The guide separates three visibility layers—model knowledge without search, pre-indexed search bots such as OAI-SearchBot, and on-demand agent bots such as ChatGPT-User—and explains how to measure each one. It details checks for robots.txt entries, nosnippet and max-snippet meta tags, Cloudflare AI bot toggles, and server logs that reveal 403, 429, and 404 responses from specific crawlers. Additional steps cover JavaScript-rendered content, repeated query testing across 20 prompts, official reports in Yandex Webmaster and Google Search Console, and hidden prompt-injection instructions that may have been planted in page metadata. The article stresses that aggregated “AI visibility” percentages are meaningless without layer separation and warns that blocking training can unintentionally harm ordinary search indexing.
redb.Identity Adds gRPC Transport for OpenID Server Alongside Existing HTTP Facade
redb.Identity has introduced a second transport layer using gRPC next to its existing HTTP interface, sharing the same core routes, client registry, token store, and authorization logic. The new facade exposes standard OAuth and OpenID Connect operations such as Token, Introspect, Revoke, UserInfo, Discovery, and Jwks through protobuf-defined methods under identity.v1.Identity. Both transports enforce identical verdicts based on a single centralized scope table located behind direct-vm addresses, ensuring that a client authorized via HTTP receives the same result when calling gRPC. Error handling on gRPC uses status codes and trailers to carry machine-readable OAuth error codes and retry-after values, preserving compatibility with existing interceptors and tracing. Browser-facing flows, DPoP proofs, and user self-service remain on HTTP, while administrative operations are available on a separate management port. The implementation was validated through 64 unit tests, cross-language interop with @grpc/grpc-js clients, and a conformance run against the official OpenID Foundation suite.
Nvidia to Cease Regular GeForce Driver Updates for Windows 10 After October 2026
Nvidia has announced the end of regular driver support for Windows 10 in its GeForce Game Ready and Nvidia Studio driver lines starting October 2026. The first driver package without Windows 10 support will arrive in November of that year. Microsoft ended the base lifecycle of Windows 10 on October 14, 2025, and Nvidia is extending support by one additional year. Existing games and applications will continue to function after the change, while quarterly security patches for critical vulnerabilities will remain available until October 2029. Users will no longer receive optimizations for new games, fixes for graphics issues, or new GPU features. Newer technologies such as DLSS may also skip Windows 10 compatibility. The transition is described as gradual rather than abrupt, allowing older titles to keep running while newer releases increasingly encourage migration to a supported Windows version.