Read-Only Utility Automates Detailed Audits of UserGate NGFW Firewall Policies
A cybersecurity engineer at Gazprom CPS has created a specialized read-only utility that helps administrators audit complex UserGate NGFW firewall policies without risking any automatic modifications to live configurations.
The project began when manual review of more than 1000 firewall rules and 4500 related objects proved impractical. Temporary rules created for short-term tasks often remained active for years, becoming difficult to evaluate because descriptions were outdated, owners unknown, and hit counts low. The utility addresses this by pulling data exclusively through the UserGate XML-RPC API, normalizing references to zones, IP lists, services, users, and groups, and then running a series of checks that generate an Excel report.
Eleven Targeted Checks Without Automated Changes
The checks are divided into four logical groups. Lifecycle checks identify rules whose last hit was too long ago, rules with very low hit counts despite being enabled, long-disabled rules, and rules that have not been updated for extended periods. Permissive-access checks look for rules using Any source or destination combined with Any services, networks wider than a configured mask threshold, and services that implicitly include management ports such as SSH or RDP when the services list is empty.
Observability checks flag drop and reject rules that have logging disabled, as well as rules that are enabled but currently inactive due to time restrictions. Documentation checks detect empty rule descriptions or descriptions lacking references to change requests or task numbers, and they also identify duplicate rule signatures.
All findings are presented with explanations so administrators can make final decisions. The tool never deletes or alters rules; it only supplies evidence for manual review.
Handling UserGate Data Model Complexities
The utility carefully interprets UserGate semantics. An empty services list means Any, not nothing. Negated lists and empty negated lists are rendered distinctly to avoid false findings. Network lists, URL lists, and certain system objects are resolved through additional API calls, with statistics aggregated across cluster nodes. The entire dataset is saved as a JSON snapshot, allowing repeated analysis with different thresholds without reconnecting to the firewall.
The final deliverable is a multi-sheet Excel workbook containing a summary dashboard, a rules-by-checks matrix with red and green indicators, a main rules sheet with human-readable object names, and separate sheets for each check. Administrators can assign verdicts such as OK, requires attention, false positive, or exception directly on the main sheet; these verdicts propagate via formulas to all other sheets.
The first production run completed in approximately 24 minutes and flagged roughly 39 percent of rules, more than half of which matched multiple checks. The resulting report provides a focused queue for manual investigation rather than requiring sequential review of the entire policy.
Related articles
Grep_Tribe Blue Team Shares SOC Defense Lessons from Standoff 17 Cyber Battle
The Grep_Tribe team participated in Standoff 17 for the third time, defending the RetailSTF Group infrastructure in a simulated State F environment against continuous red team attacks. They handled 37 confirmed incidents, 22 detected incidents, five investigated critical events, and maintained 88 percent average infrastructure availability. The team used familiar Positive Technologies tools alongside the new R-Vision SOAR platform to automate routine responses such as IP blocking and file sandboxing. Work was organized through a tribal system with role-based preparation and dynamic small-group investigations for complex attack chains. Participants highlighted how the event tested prioritization, Threat Intelligence attribution, and automation under high-intensity conditions unlike daily SOC operations. The experience reinforced plans to expand SOAR playbooks for repetitive tasks in their real internal SOC environment.
Password Reset Fails to Evict Attackers: What Persists in Compromised Email Accounts
Even after users change passwords and enable two-factor authentication, attackers often retain access through active sessions, application tokens, and forwarding rules. The original password serves only as an entry point, while already-issued session cookies, refresh tokens, and app passwords continue functioning independently. Services like Google, Microsoft, and Yandex provide specific pages to review devices, permissions, and app passwords, yet many users overlook the critical "sign out all devices" option. In corporate environments, Microsoft Entra ID commands can revoke sessions, but access tokens may still remain valid for up to an hour afterward. Attackers frequently replace recovery details and set up mail delegation or hidden forwarding rules to maintain long-term control. The recommended sequence prioritizes session revocation first, followed by password change, MFA review, and recovery data verification to prevent re-entry via forgotten-password flows.
86% of Large Russian Companies Use or Pilot LLMs While Autonomous AI Agents Remain Rare in Production
A joint study by Infosystems Jet and Smart Ranking reveals that 86% of major Russian organizations are already deploying or testing large language models, with 53% having moved generative AI solutions into full production. Adoption drops sharply for more autonomous systems: only 15% run semi-autonomous AI agents in production, while fully autonomous and multi-agent setups reach just 8% each. The primary barriers are not model availability but insufficient process maturity, data infrastructure readiness, and integration complexity, cited by 44% of respondents. Additional obstacles include server costs (58%), legal risks (56%), budget limits (42%), and talent shortages (40%). Nearly half of surveyed companies report no measurable financial return from AI projects so far, highlighting the gap between pilot success and scalable value. The research covered 52 large firms employing roughly 450,000 people in total.
Russia to Enforce Smartphone Ban During School Lessons Starting September 2026
From September 1, 2026, Russian school students will be prohibited from using mobile phones during classes under a new ministerial order from the Ministry of Education. The restriction, already outlined in federal law, will be detailed by the order to specify its application in schools, according to Minister Sergey Kravtsov. Phones may only be used in emergencies, such as threats to life or health of students and teachers. Activities like messaging, gaming, social media access, or using AI tools for quick answers are explicitly not permitted. Schools retain flexibility on phone use during breaks, allowing individual institutions to set their own rules. The Ministry of Digital Development has confirmed no nationwide ban on social networks for minors is planned, leaving platforms like TikTok and Telegram accessible outside class hours.