Rent, Don't Build: Penetration Testing, Vulnerability Management, and Bug Bounty as a Service
The fifth part of the practical series “Vulnerability Management for Beginners” examines three service-based models that let organizations outsource key tasks instead of building everything in-house: pentest as a service, VM as a service, and bug bounty programs.
Pentest as a Service
Penetration testing simulates an attacker’s attempt to find weaknesses that allow unauthorized actions. Most external pentests follow a black-box approach where testers receive no credentials and must discover entry points the way a real adversary would. Automated scanners rapidly check thousands of hosts for known vulnerabilities, open ports, and version fingerprints, while human teams with certifications such as OSCP combine findings into multi-step attack chains that tools rarely detect.
Automated pentest-as-a-service offerings let companies quickly scan internet-facing assets without deploying their own infrastructure. Customers simply provide IP ranges or domains and prove ownership through domain-registration certificates or signed authorization letters. The provider’s scanners run from external servers and deliver structured reports or API data that can be imported into internal vulnerability-management systems. Limitations include reduced configuration flexibility and the inherent sensitivity of vulnerability data, which must be protected as confidential information.
Market figures show strong growth: the global pentest-as-a-service market reached approximately $1.6 billion in 2024 and continues to expand at roughly 20 percent annually. In Russia the segment also grew by tens of percent in 2025, with several large vendors dominating corporate projects. Tools such as the Russian PT Dephaze platform now provide controlled automated testing that mimics attacker behavior safely.
VM as a Service
Vulnerability Management as a Service extends beyond black-box perimeter scanning by deploying agents or establishing tunnels that allow authenticated, white-box scans of internal assets. This approach produces far more accurate inventories of installed software versions and reduces both missed vulnerabilities and false positives. Results are delivered as reports or API feeds, yet organizations must still maintain internal processes with IT teams to remediate findings within agreed SLAs.
Service customers can define asset criticality, set remediation deadlines, and integrate outputs with patch-management platforms such as Microsoft SCCM or its Russian equivalents. Benefits include rapid deployment, continuous scanner updates handled by the provider, and access to benchmarking data that compares an organization’s remediation speed against industry peers. Risks involve potential data leakage and the need to treat tunnels to internal agents as part of the attack surface.
Prioritization can leverage modern metrics including the fourth version of EPSS, the CISA KEV catalog that now exceeds 1,500 actively exploited vulnerabilities, and the updated FSTEC methodology released on 30 June 2025, which combines CVSS 3.1 base scores with exploit availability and consequence categories.
Bug Bounty Programs
Bug bounty programs invite independent security researchers to examine defined assets in exchange for monetary rewards. Platforms such as HackerOne, Bugcrowd, and Synack manage researcher onboarding, triage, and payments, while Russian platforms Standoff Bug Bounty and BI.ZONE Bug Bounty have become major local players.
In 2025 the two leading Russian platforms received nearly 14,000 vulnerability reports and paid out approximately 260 million rubles. Standoff Bug Bounty alone grew its active programs 2.2 times to 233, registered over 32,000 researchers, and recorded a maximum single payout exceeding 4.9 million rubles. BI.ZONE increased payouts by 50 percent to reach 100 million rubles. Government bodies, including the Ministry of Digital Development, have launched multiple rounds of programs covering systems such as Gosuslugi, while regional administrations and major companies including Sberbank have followed suit.
Successful programs begin in private mode with moderate rewards, clearly defined scope, and established triage workflows. Researchers are incentivized to discover high-impact issues that automated scanners miss, creating a realistic simulation of diverse attacker perspectives. Global payouts underscore the model’s maturity: HackerOne alone distributed about $81 million to researchers between mid-2024 and mid-2025, while Google awarded a record $17 million in 2025.
Related articles
F6 Investigates First In-the-Wild Exploitation of Critical CVE-2026-76466 in Cisco Expressway
Russian cybersecurity firm F6 has documented the first confirmed exploitation of the critical CVE-2026-76466 vulnerability (CVSS 9.8) affecting Cisco Expressway devices. Attackers targeted a Russian company and quickly adapted a public proof-of-concept exploit to gain root-level remote command execution on version X15.5.3. The flaw resides in the Erlang distribution authentication mechanism on TCP port 4372, allowing unauthenticated command execution via a hardcoded cookie. After initial access, the threat actors deployed over 100 custom Python scripts for network reconnaissance, lateral movement, and data collection, including tools that abused WinRM, SMB, LDAP, and SQL Server protocols. F6 observed modifications to the original PoC that enabled arbitrary command execution and result retrieval, along with auxiliary scripts for TCP relaying and repeated connection attempts. The incident highlights how quickly public exploits can be weaponized against perimeter devices that bridge external and internal networks.
NGINX2Root Vulnerabilities: Ten Critical Flaws Patched in NGINX Including Remote Code Execution via HTTP/2
On November 18 2026 NGINX developers addressed ten vulnerabilities with five grouped under the NGINX2Root research name by Theori's Xint team. The most severe CVE-2026-123007 enables unauthenticated remote code execution on servers with HTTP/2 enabled by exploiting memory corruption that originated in 2015. Researchers demonstrated full compromise including root escalation via a separate Linux SCTP kernel flaw and escape from Docker containers. Working exploits have been published by Rapid7 and others with specific requirements such as AVX-512 support and substantial traffic volumes. Patches are available in NGINX 1.30.7 1.31.9 and corresponding NGINX Plus releases while temporary mitigations include disabling HTTP/2 or HTTP/3. The issues affect standalone servers reverse proxies Kubernetes ingress controllers and embedded NGINX instances across distributions.
Linux Kernel CVE-2026-98432 Enables Remote Code Execution Across Nearly All Versions Since 4.4
China's NVDB issued a high-severity advisory on November 18 warning of a remote code execution flaw in the Linux Kernel that grants attackers full root privileges. The vulnerability affects Linux Kernel 4.4 and virtually every subsequent mainline release, impacting major distributions including Ubuntu, Debian, Red Hat, SUSE, Oracle, and Chinese variants such as Kylin, UnionTech, and Deepin. Because the flaw is remotely exploitable without prior authentication and leads directly to highest privileges, exposed public-facing systems face immediate risk. The advisory notably states that AI models can rapidly analyze patches, identify trigger conditions, and generate working exploit chains, shrinking the traditional window between disclosure and weaponization from days to hours. Official fixes have been published for multiple stable branches, yet administrators must still validate driver compatibility, container runtimes, and third-party modules before deploying kernel updates in production. The advisory also highlights incomplete vulnerability disclosures across PHP, Node.js, Apache, Chrome, GitLab, and MySQL, underscoring the need for precise asset inventories rather than reliance on vulnerability databases alone.
Wireshark 4.6.10 Released with Fixes for 39 Vulnerabilities and Multiple Protocol Dissectors
The open-source network protocol analyzer Wireshark has received its 4.6.10 update, addressing 14 bugs along with 39 security vulnerabilities discovered during testing. The release continues the 4.6 development branch that began in October 2025 and follows the long-standing stable line that started with version 1.0.0 in 2008. Patches cover a wide range of protocol dissectors including RTSE, NBAP, IEEE 1609.2, IrDA, Matter, IEEE 1905, OpenWire, USB-PTP, Exported PDU, ACN, PROFINET, SDP, MsgPack, NNTP, TLS, and SCTP. Additional corrections resolve infinite loops in the Kafka dissector and Tektronix K12xx file parser, heap disclosure issues, and a remote code execution flaw in LoRaWAN decryption tracked as ZDI-CAN-32851. The update also ships Npcap 1.89 for Windows installers and changes the default extcap directory on Unix-like systems to libexec for better multiarch compatibility.