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
Passwork Comparison with OneKey Sparks Detailed Rebuttal from ABP2B on Security Claims
Passwork published a self-comparison of its corporate password manager against OneKey version 2.0.7, using simplified settings and an outdated release despite version 2.1.0 being available. ABP2B responded by highlighting biases in the analysis and noting that several features criticized as weaknesses are optional and can be disabled via group policies. The company released a major update shortly after, adding reworked authorization, enhanced formatted text protection, expanded cache controls, new group policies, strengthened server-side checks, and revised hash storage rules. Key technical disputes include the use of a single master password versus independent vault secrets, the correct application of Shamir's Secret Sharing to recovery keys rather than the master password, and the comparison of PBKDF2 iteration counts without considering the full cryptographic context. Additional points addressed the choice of GOST 34.12-2018 as the default algorithm for the Russian market versus AES-256, and the protective purpose of compromised password checking that organizations may optionally enable or disable.
How a Personal Site Counts Bots Without Storing Any IPs: Pure PHP, No Database, Strict CSP and 160 Tests
A personal website built entirely in pure PHP without frameworks or databases demonstrates advanced defensive security practices while tracking bot activity from an SSH honeypot. The site stores all content in a single JSON file with atomic writes and automatic backups, eliminating database-related attack surfaces and simplifying deployment to folder copying. Strict Content-Security-Policy rules prohibit inline styles and scripts without nonces, forcing the use of SVG attributes, CSSOM updates, and JSON data blocks instead of direct attribute injection. Over 160 automated tests written in PHP attack the site with XSS payloads, CSRF attempts, path traversals, and malformed Markdown to verify that no malicious output reaches the browser. Bot identification relies on behavioral signatures derived from the first twelve cleaned commands of each session, combined with HASSH fingerprints and activity patterns, allowing the site to report unique bot families and address counts without ever publishing IPs. Additional browser-based tests using Chromium validate accessibility, performance budgets, and CSP compliance across desktop and mobile viewports. The entire system runs with zero external dependencies and integrates tests directly into the deployment pipeline.
Russian Finance Ministry Seeks Central Bank Reports on Systematic P2P Transfers to Tax Authorities
The Russian Ministry of Finance has proposed amendments requiring the Central Bank to share data with the Federal Tax Service on individuals whose bank accounts show signs of regular income received from other private citizens. The changes target article 85 of the Tax Code and form part of the budget package bill numbered 617-9. Under the new rules, the Central Bank would identify such citizens through transaction analysis and transmit the information according to a future agreement with the tax service. The Federal Tax Service would also gain expanded powers to request bank statements from non-entrepreneurs without needing prior debt collection or audit triggers. If approved, the provisions would take effect on 1 January 2027 and apply to operations conducted after 1 January 2026. Separate bills under discussion would impose monthly transfer limits of 30,000 rubles on suspected clients starting in 2028 and require the tax service to notify the Central Bank about account openings and income categories.
Baidu Launches Ciyuan Exchange to Establish Trust Standards for AI Model Trading
Baidu Intelligent Cloud has introduced the Ciyuan Exchange, a dedicated trading platform for large AI models that aims to solve quality verification and credit issues in an increasingly crowded market. The platform, unveiled at the Baidu World 2026 Conference, already hosts over 100 supply resources with daily calls exceeding 50 million and daily token usage surpassing 700 billion. Founder Li Yanhong positioned the exchange as an infrastructure layer that moves beyond simple model aggregation toward verifiable identity, ongoing performance monitoring, and supplier credit records. The initiative addresses real procurement risks where identical models from different providers show up to twofold differences in throughput and reliability, according to a China Academy of Information and Communications Technology report. By combining model fingerprinting, capability testing, periodic audits, and continuous credit scoring, the platform seeks to create transparent market mechanisms similar to commodity exchanges. This development signals a broader industry shift from raw model capability competition toward standardized service quality, pricing transparency, and reliable delivery infrastructure.