Solar SIEM 2026.2 Adds Full Solar JSOC Detection Library, TI Feeds Support, Enhanced AI Agent and Multi-Tenancy
GC Solar has released Solar SIEM 2026.2, introducing several major enhancements designed to reduce the manual effort traditionally required when deploying a security information and event management platform.
The most significant addition is the complete library of detection rules developed by Solar JSOC. This knowledge base was accumulated over 14 years of continuous monitoring and incident investigation across the infrastructures of approximately 300 customers. Organizations no longer need to spend months creating their own rule sets tailored to specific environments; instead, they receive battle-tested detection scenarios that enable identification of complex attacks at the earliest stages of deployment.
According to Solar JSOC statistics for 2025, the center processed 1.16 million security events after filtering out false positives. Customers confirmed more than 33,000 incidents. The most common threat types were malicious software, responsible for 36 percent of cases, and attempts at unauthorized access, which accounted for 23 percent.
The update also introduces support for TI Feeds. Solar SIEM can now automatically load indicators of compromise from the Solar 4RAYS database as well as from customer-provided external sources and correlate them in real time against events collected from the monitored infrastructure.
Capabilities of the built-in AI agent have been substantially expanded. Previously limited to analyzing data contained within an incident card, the agent can now independently access and examine raw source data, conduct deeper investigation, and propose subsequent response actions. This functionality is intended to accelerate initial triage and reduce routine workload for security analysts.
Another important new feature is multi-tenancy. Multiple organizations can now be connected to a single Solar SIEM installation while their event streams remain fully isolated. This architecture primarily targets holdings, MSSP providers, and large enterprises with numerous separate divisions.
More than 40 companies of varying sizes participated in the pilot testing of the new version. Overall, Solar SIEM 2026.2 shifts the emphasis from lengthy manual configuration toward immediate use of a ready-made knowledge base, enabling effective security monitoring even without maintaining a large internal SOC team.
Related articles
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.
Rospotrebnadzor Introduces Age-Based Screen Time Limits for Russian School Students
Russia's consumer protection agency Rospotrebnadzor has established recommended maximum durations for schoolchildren working with computers and interactive whiteboards during lessons. The limits vary by grade, ranging from 20 minutes for first and second graders up to 35 minutes for students in grades 10 and 11. Separate rules apply to interactive boards, capping usage at 20 minutes for children under 10 and 30 minutes for older students. Schools must ensure students perform eye exercises when electronic devices are used, while traditional paper-based classes require such exercises only during breaks. Starting September 1 2026, a nationwide ban on mobile phones during lessons will also take effect, with individual schools deciding rules for recess periods.
From Root CA to User Authorization in nginx and Apache: Client Certificate Login Explained
This is the third installment in a detailed tutorial series covering the deployment of a two-tier PKI infrastructure with Root CA and intermediate CAs for Person, Server, and Code. The article provides comprehensive configuration guidance for enabling mTLS in nginx and Apache, including full references for all ssl_client_* variables and SSL directives. It explains the differences between password-based and certificate-based authentication, the TLS handshake steps involving CertificateRequest and CertificateVerify, and the importance of proper extendedKeyUsage settings such as clientAuth. Readers learn how to issue client certificates, package them in PKCS#12 format, enforce revocation checks via CRL and OCSP, and safely pass certificate fields to backend applications while mitigating risks from header spoofing. The guide also covers scenarios where the application itself terminates TLS without a reverse proxy and demonstrates login flows protected against CSRF using one-time tokens.