AntiMalware•July 18, 2026•🇷🇺Translated from Russian

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

Habr•Other

Home Lab Overhaul: Securing Proxmox Infrastructure After Discovering 63,000 Forgejo Spam Accounts

A home lab administrator migrated Docker stacks to new LXC containers on Proxmox and uncovered multiple security misconfigurations. The setup relied on Cloudflare proxying, MikroTik port forwarding to NPMplus with CrowdSec, and Cloudflare Tunnels for admin panels. After fixing IP address logging in the WAF, logs revealed 63,021 spam accounts created on a Forgejo instance that had open registration. The operator disabled registrations, recreated the instance from verified Git mirrors, and eliminated direct internet exposure by routing all traffic through Cloudflare Tunnel. Additional controls included Zero Trust policies, device enrollment restrictions, and TOTP on Guacamole. The changes removed open ports, enforced proper client IP visibility for CrowdSec, and segmented public, limited, and admin access paths.

Habr•Other

Benchmarking AES-GCM and Ascon AEAD Performance on ESP32 and ESP8266 for Industrial Telemetry

Researchers conducted detailed experiments measuring the real-world costs of three AEAD implementations on ESP32 and ESP8266 microcontrollers used in industrial telemetry scenarios. The study compared mbedTLS AES-128-GCM, legacy Ascon-128 via CryptoLW, and a portable C++ port of NIST Ascon-AEAD128 across three load profiles ranging from stable low-frequency packets to maximum-rate 10 ms intervals. Key metrics included AEAD execution time, CPU cycles, memory usage, UDP transmission success rates, and power consumption captured via TC66C. Initial tests revealed significant UDP packet loss on ESP32 under MAX load due to ENOMEM and ENOBUFS errors in the lwIP stack, which were largely resolved after network handling improvements. Results showed AES-GCM completing in roughly 618 µs on ESP32 versus 803 µs for legacy Ascon-128, while the reverse held on the slower ESP8266 where legacy Ascon outperformed AES by a factor of approximately 3.5. The work highlights that network stack limitations often dominate over cryptographic overhead in high-throughput industrial sensor deployments.

AntiMalware•Other

ARinteg Earns Golden Partner Status from Ideco for NGFW Security Projects

ARinteg has been awarded Golden Partner status by Ideco following successful joint projects in network security. The integrator supplies and implements the Ideco NGFW Novum next-generation firewall for perimeter protection and secure remote access. Collaboration also covers customer migrations from foreign NGFW solutions to the Russian vendor’s product. Commercial Director Dmitry Slobodenyuk stated the new status will allow ARinteg to deliver fuller support across all implementation stages. Ideco’s Partner Relations Head Sergey Markin highlighted ARinteg’s technical expertise in large-scale deployments. The partnership supports import substitution and hybrid infrastructure requirements.

Habr•Other

Zero Trust in Practice: Avoiding YAML Pitfalls with Kubernetes NetworkPolicy and Istio

A detailed case study demonstrates how a single misplaced hyphen in a Kubernetes NetworkPolicy YAML file can unintentionally grant cluster-wide access instead of restricting it to a single client Pod. The example uses a shop namespace API connecting to an orders service in the backend namespace over TCP/8080, showing the correct use of namespaceSelector and podSelector together within the same from element. Tests on K3s with four vCPU and 4 GB RAM confirmed that only the intended client succeeds while others receive Connection refused. The implementation then extends to Istio with PeerAuthentication in STRICT mode and an AuthorizationPolicy limiting requests to GET /orders/* from the orders-api ServiceAccount. Additional checks cover RBAC permissions for creating Pods with specific ServiceAccounts and the need to verify DNS routes and existing allow-all policies. The article stresses maintaining an explicit list of required connections, testing both success and denial cases, and preserving rollback manifests before applying changes in production.