R-Vision SIEM Demonstrates Resilience During Intense Standoff 17 Cyber Defense Exercise
R-Vision SIEM served as the primary platform for monitoring, correlation, and incident investigation during the Standoff 17 cyber exercise, where the akPots blue team defended the Telecom sector under realistic high-pressure conditions.
Most participants encountered the system for the first time during the event. The exercise simulated nine critical events out of 37 architected scenarios while more than ten red-team groups operated simultaneously across the infrastructure. Unlike typical SOC operations that involve large volumes of failed scans and false positives, the competition produced a dense stream of successful exploits and high-severity alerts.
The team highlighted several operational differences from routine work. In everyday environments, targeted attacks unfold over extended periods and defenders can consult system owners. At Standoff, attribution proved difficult because multiple groups attacked concurrently, and no clarification from administrators was available. Initial access vectors were especially challenging to isolate amid heavy scanning noise.
Organization relied on three key practices. A shared chat contained dedicated threads for each critical event. A living document captured IOCs, artifacts, and evidence in chronological order, allowing any team member to regain context quickly. A designated captain distributed tasks and handled organizer communications.
Alongside R-Vision SIEM, the defenders used PT Application Firewall for request and response inspection, PT NAD for traffic analysis, PT Sandbox for malware evaluation, and PT Container Security for eBPF-based visibility inside Kubernetes clusters. The Xello deception service was also deployed. Interfaces proved intuitive, enabling the team to become comfortable within three hours, although complex queries still required occasional reference to documentation.
Most valuable SIEM capabilities included raw search with wildcards, adjustable display fields, event grouping, and exclusion of known benign activity. Pre-built dashboards helped surface attacker intent before critical events were achieved. The team noted that the system handled high data volumes stably and offered clear query syntax.
Requested improvements included one-click navigation from dashboard widgets to underlying raw events, ready-made detection scenarios based on vendor expertise, and nested grouping by host and event type. Overall, the exercise provided intensive hands-on experience with new tools and reinforced the value of structured team coordination under stress.
Related articles
Securing 1C Web Client Access with External MFA via Nginx, Keycloak and Active Directory
A detailed implementation separates user browser access from integration traffic by placing MFA enforcement on an external Nginx and Keycloak layer while preserving the original IIS endpoints for automated systems. The architecture uses a new IIS server for employees only, with oauth2-proxy handling OIDC flows against Keycloak federated to Active Directory. Access is restricted to members of a dedicated AD group such as 1C_Web_2FA, and TOTP serves as the second factor. Existing integrations continue to reach the legacy IIS directly from whitelisted IP addresses without triggering interactive authentication. The solution avoids 1C OpenID Authentication, keeps native 1C login intact, and supports desktop shortcuts that launch the web client in a dedicated browser window. Network controls ensure the new IIS cannot be reached directly from the internet, preventing bypass of the MFA gateway.
Avanpost Unveils DAG System for Sensitive File Discovery and Excessive Access Rights Management
Avanpost has launched its new DAG solution designed to control access to unstructured data across file servers, cloud environments, and corporate knowledge bases. The system scans file contents to identify confidential information, maps actual user permissions, and highlights policy violations that official regulations often overlook. Built-in workflow automation routes access review requests to data owners, collects approvals, assigns remediation tasks to IT teams, and verifies changes through follow-up scans. DAG integrates with existing IdM/IAM platforms to factor in employee roles and employment status, automatically triggering access reviews during job changes or terminations. The platform also forwards detected violations to SIEM and SOAR systems for coordinated response and supports both high-load enterprise deployments and simpler mid-market installations. Customers can request on-site pilots to evaluate the solution against their current infrastructure.
Why Complex Password Policies Fail to Protect Companies: Practical Account Security Guidance
Many organizations implement strict password rules requiring at least eight characters with numbers, uppercase letters, and special symbols, plus mandatory changes every 30 days. Employees respond by creating predictable variations such as Company2026!, Company2026@, and Company2026#, which offer little real protection against phishing or credential stuffing. The core issue lies in poor visibility into all accounts across Active Directory, VPN, cloud services, databases, and contractor access rather than password length alone. Effective security begins with full inventory of every account, classification into user, privileged, service, and external types, and clear ownership assignment. Privileged accounts require separate credentials, MFA, minimal rights, and activity logging, while service accounts must avoid hardcoded secrets in configuration files or source code. Password managers must enforce client-side encryption so that even compromised administrator accounts cannot access stored secrets. MFA deployment should prioritize high-risk entry points such as VPN, email, and backup systems, and access revocation must integrate with HR processes to prevent former employees or contractors from retaining credentials.
Wireshark Wi-Fi Traffic Analysis: Diagnosing Connectivity Failures in 802.11 Networks
Wireshark captures help distinguish between radio-layer issues, DHCP failures, and application-layer problems when a device connects to Wi-Fi but cannot load pages. The guide explains how to select the right capture point—client, monitor-mode adapter, or wired side of the access point—and why ordinary Ethernet headers often hide critical 802.11 management and control frames. Detailed sections cover CSMA/CA contention, frame types (Management, Control, Data), EAPOL-Key exchanges for WPA2-Personal, and the limitations of retry flags as loss indicators. Practical Linux commands using iw, dumpcap, and NetworkManager demonstrate how to enable monitor mode on channel 6 HT20 and record a two-minute trace. Filters for wlan.addr, eapol, and wlan.fc.retry allow analysts to isolate association failures, key-handshake problems, or DHCP delays. The article also addresses decryption of WPA2 traffic with a known passphrase and warns that Wireshark cannot replace a spectrum analyzer for detecting non-Wi-Fi interference.