Securitylab•August 26, 2026•🇷🇺Translated from Russian

Grep_Tribe Blue Team Shares SOC Defense Lessons from Standoff 17 Cyber Battle

The Grep_Tribe blue team returned to Standoff 17 for the third consecutive year, this time protecting the infrastructure of the retail company RetailSTF Group inside the virtual State F. In contrast to routine SOC work with familiar systems and historical context, the cyber battle featured simultaneous attacks from multiple red teams, rapidly changing tactics, and a dramatically higher volume of security events.

Over the course of the exercise the defenders recorded 37 confirmed incidents, 22 detected incidents, five investigated critical events, and sustained an 88 percent average infrastructure availability. Team members who normally work in an internal SOC used the event to stress-test established processes under conditions that cannot be replicated in production environments.

Team Organization and Preparation

Before the competition began, roles were assigned across infrastructure analysis, vulnerability assessment, firewall rule review, and network topology mapping. During the battle the team applied a “tribal” model first tested the previous year: analysts initially triaged the general event stream, while complex attack scenarios triggered the formation of small two- or three-person groups for in-depth investigation and response. Newer participants focused on indicator analysis and basic containment, freeing experienced members for attribution and Threat Intelligence tasks.

Tools and Automation

The primary detection and response stack consisted of Positive Technologies solutions: MaxPatrol SIEM, MaxPatrol VM, MaxPatrol EDR, PT Application Firewall, and PT Sandbox. For the first time the team also operated R-Vision SOAR, using it as a central interface for automated playbooks that blocked IP addresses, submitted files to sandbox analysis, and enforced time-limited blocks that automatically expired to avoid service disruption.

Participants noted that the SOAR platform reduced context switching and allowed analysts to launch common actions in a few clicks while maintaining visibility into every response status. Support from the R-Vision engineering team enabled rapid customization of playbooks during the event.

Key Takeaways

After the competition the team concluded that pre-built automation for repetitive tasks significantly lowers analyst workload during sustained high-intensity periods. They intend to apply the same approach in their daily SOC operations. The event also reinforced the value of early infrastructure reconnaissance and the use of Threat Intelligence to link disparate events to specific red-team actors.

Grep_Tribe’s traditional mascot—frogs in various forms—accompanied the team once again, and several new internal memes were added to the collection. For first-time participants the advice was straightforward: study the rules in advance, ask experienced colleagues questions without hesitation, prepare contingency plans, and enjoy the unique learning opportunity that a live cyber battle provides.

Related articles

Habr•Other

Prod is Down: Free gVisor-Based Simulator Gives Strangers Root Access for Realistic Linux Incident Training

A Russian systems administrator has launched Prod is Down, a free online platform that lets users practice real incident response by granting them root consoles on deliberately broken Linux servers. The tool currently offers 13 scenarios covering PostgreSQL failures, OOM Killer events, full disks, expired certificates, nginx 502 errors, inode exhaustion, DNS issues, and open file limits. Each exercise runs inside gVisor sandboxes with strict resource limits, internal-only networking, and automated verification that checks service health rather than player commands. The author implemented an emulated systemd in Python so trainees can use familiar systemctl and journalctl commands without running a real init system. Multiple layers of isolation, including overlay filesystem tweaks and size monitoring, prevent abuse while still allowing sudo and realistic debugging. The platform records three random variants per scenario so memorized fixes from previous runs do not work on subsequent attempts.

Habr•Other

Home Lab Guide: Deploying Active Directory, Windows 7 Client and ELK Stack for Security Logging

A detailed tutorial walks readers through building an isolated VirtualBox lab featuring a Windows Server 2019 domain controller with DNS and DHCP, a Windows 7 client joined to the domain, and an ELK stack running Elasticsearch, Logstash and Kibana 9.4.2. The guide covers creation of organizational units, Group Policy Objects for advanced auditing, and configuration of Winlogbeat 7.17 to forward Security, System and Application logs to Logstash. Special attention is given to common pitfalls such as missing GPO extension attributes that prevent audit policies from applying and memory constraints when running the full ELK stack on limited RAM. The author emphasizes that Windows 7 is unsupported and should only be used in isolated lab networks. All steps are provided with exact PowerShell commands, netplan configurations, and Logstash pipeline examples suitable for a 192.168.100.0/24 NAT network.

Securitylab•Other

Building Your First Home Network Lab: Essential Tools and Experiments to Understand Corporate Networks

A cybersecurity professional without network knowledge resembles a guard without a building blueprint, spotting alarms but unable to trace the intruder. Setting up a personal lab on a standard computer bridges this gap through virtualization and hands-on practice with protocols and attacks. The guide recommends GNS3 for topology emulation, VirtualBox or VMware for running Windows and Linux workstations, Cisco Packet Tracer for quick simulations, Wireshark for traffic analysis, and draw.io for diagramming. Key experiments include configuring Cisco IOS routers with IP addressing, testing default gateways, observing ARP requests and replies, triggering broadcast storms via switch loops, and enabling STP to prevent loops. The lab demonstrates how legacy protocols like ARP expose networks to spoofing and why segmentation with VLANs and firewalls matters. Resources from CyberED provide demo access to courses on SOC analysis, penetration testing, and AI applications in security to extend learning.

Habr•Other

PSLC and Agent-Ops: From Product Support to Infrastructure Transformation

Sergey Zhitinsky, founder of Git in Sky, attended the OPS Talk by Sber meetup on October 19 and discussed the PSLC methodology with architect Alexander Shapovalov. PSLC, or Product Service Lifecycle, outlines two loops for restoring services immediately and improving reliability to prevent recurrence through teams, knowledge, and platform support. Agent-Ops focuses on eight detailed steps for individual infrastructure tasks: intention, evidence collection, diagnostics, planning, approval, controlled change, verification, and lessons learned. The article illustrates their complementary use in a scenario where post-release log growth fills a database disk, requiring both service restoration and root-cause fixes. Both approaches emphasize knowledge retention, action control, and human accountability, though Agent-Ops v0.5.1 mandates explicit human approval and separate execution for production changes. PSLC suits larger organizations with shared platforms, while Agent-Ops targets smaller teams handling infrastructure operations with AI agents.