Avito Details Security Gates Implementation to Enforce Vulnerability Remediation Without Disrupting Developers
Avito has published an in-depth technical case study on implementing security gates that enforce vulnerability remediation policies while minimizing friction for development teams. Alexander Trifanov, head of Application Security at the company, describes nearly ten years of experience building controls that prevent SLA violations without turning security into a bottleneck.
The article defines a security gate as any automated check that can block or allow actions based on policy. Quality gates focus on code standards and functionality, while security gates target vulnerabilities and compliance. Both rely on a signal source, policy engine, and enforcement mechanism, but the latter protects against risk accumulation at company scale.
Trifanov explains that manual SLA extensions quickly erode control. Developers learn that deadlines can be moved, leading to repeated violations. A properly designed gate forces explicit risk acceptance by security before problematic actions proceed.
Pipeline Architecture and False-Positive Handling
Avito rejected synchronous scanner execution inside CI/CD pipelines. Instead, pushes trigger asynchronous orchestration of SAST, SCA, secret detection, and YAML configuration checks. Results are normalized in ASOC or SOAR, then automatically assigned to service owners with SLA-based priorities.
Each finding tracks three fields: status (active/inactive), verification_status (valid, false candidate, false positive), and verification_reason. Automated heuristics, validators, and limited AppSec review reduce noise before tasks reach developers.
Key requirements for any gate include robust false-positive workflows, deduplication of near-identical findings, and an emergency bypass switch. The bypass proved critical for business continuity during incidents.
First Gate at Deployment Stage
The initial gate queries SOAR at deployment time and blocks releases containing active vulnerabilities past SLA. High-severity issues trigger immediate blocks; medium-severity issues allow two full sprints before enforcement.
Services in maintenance mode rarely trigger gates because deployments are infrequent. Avito therefore created a manual “red button” that can block entire organizational units (groups of teams) from deploying any services until issues are addressed. The capability has never been used, yet its existence drives higher compliance.
Pre-receive Gate and Library Handling
A second, earlier gate uses server-side pre-receive hooks in GitHub, GitLab, and Bitbucket. Only fast scanners run within a strict ten-second limit. Rejected pushes return the finding identifier so developers can request false-positive validation.
Feedback revealed developers reluctant to pin library versions and analysts storing non-deployed code. These edge cases led to a dedicated library-update flow that scans requests before packages are fetched in development environments or CI/CD.
Kubernetes and Kyverno Experiments
Attempts to embed policy enforcement directly into Kubernetes using Kyverno are discussed as an ongoing direction for covering services that bypass traditional pipelines. The article concludes that multiple overlapping gates at different lifecycle stages reduce the impact of any single missed detection.
Related articles
HTTP Methods Explained: GET, POST, PUT, PATCH, DELETE and the New QUERY Standard
HTTP methods define the actions a client requests from a server regarding a resource. The core semantics are outlined in RFC 9110, with extensions for specialized protocols. A new standardized method called QUERY was introduced in June 2026 via RFC 10008 to handle complex queries that include a request body while remaining safe and idempotent. The article details safe and idempotent properties, compares each method including GET, HEAD, POST, PUT, PATCH, DELETE, OPTIONS, TRACE, CONNECT, and QUERY, and explains their correct usage to avoid breaking caches, proxies, and infrastructure expectations. It also covers WebDAV extensions and other registered methods in the IANA registry.
From Web Perimeter Breaches to Domain Takeover: How Standoff Hackbase Trains Pentesters on Real Corporate Infrastructure
wr3dmast3r, a senior pentester and BSCP certification guide author, rose to first place on the Standoff Hackbase ranking by shifting focus from initial perimeter access to full internal infrastructure compromise. The platform replicates large-scale corporate networks from various industries, forcing participants to map service relationships, harvest credentials, escalate privileges, and chain pivots across segments. Unlike CTF challenges that end with a single flag, Hackbase tasks require building complete attack paths that can lead to data theft, process disruption, or cross-domain movement. The interview highlights practical techniques such as time-boxing hypotheses, manually modeling infrastructure after automated scans, and using AI only as an information accelerator rather than an autonomous operator. wr3dmast3r also details a memorable chain that began with a bot, moved through VPN and Outlook access, leveraged SCCM tokens for privilege escalation, and ended with compromise of a second domain containing the target system.
OTUS Publishes September Digest of Free Lessons on Linux Administration, PostgreSQL, CI/CD and Infrastructure Security
OTUS has released a new digest listing free September webinars aimed at infrastructure engineers, DevOps specialists and system administrators. The program covers practical topics including Linux server configuration, PostgreSQL 18 performance tuning, high-availability clusters with Patroni, CI/CD pipelines in GitLab, eBPF observability and infrastructure security practices. All sessions are delivered by practicing OTUS instructors who share real-world production experience. Separate tracks address RAID and LVM management, GPO policies, release management in 1C environments, Go profiling, mitmproxy traffic analysis and responsible use of AI tools for incident investigation and code review. The webinars run throughout September at 19:00 or 20:00 Moscow time and require only free registration. The digest also includes sessions on career growth from tech lead to CTO and effective responsibility distribution for team leads.
Top LLMs Misidentify Poisonous Mushrooms in Every Ninth Case, Benchmark Shows
Polish developer Piotr Migdal evaluated leading large language models on their ability to identify mushrooms from photographs, using a dataset of 1040 images covering 55 species common in Poland. The images came from the FungiTastic dataset derived from the Atlas of Danish Fungi, with expert labels and partial DNA confirmation. Models were asked to return the five most likely species names in Latin without additional training or tools. Gemini 3.8 Flash performed best with 65 percent top-1 accuracy and 85 percent top-5 accuracy, followed closely by other Gemini variants. However, safety-critical errors remained high: Gemini models labeled poisonous mushrooms as edible in roughly 11 percent of cases, while GPT-5.6 Sol reached 24 percent, Claude Opus 5 reached 29 percent, and Qwen 3.8 27B reached 36 percent. The study did not ask models directly whether a mushroom was edible; species identifications were later cross-checked against toxicity tables.