Agent, Scan or Beyond: Modern Methods for Comprehensive Infrastructure Vulnerability Scanning
The eighth part of the practical series Vulnerability Management for Beginners examines how infrastructure scanning has evolved beyond three traditional methods. Modern environments with short-lived cloud instances, remote developer laptops, and industrial controllers require a broader toolkit that includes agent-based collection, cloud snapshots, passive traffic analysis, SCA, SBOM, and DAST.
Host Discovery, Pentest, and Audit
Host Discovery uses ICMP, UDP, ARP, and TCP ping techniques to identify live nodes and open ports without deep accuracy. It must be combined with ARP tables, hypervisor data, SIEM, EDR, and CMDB to reduce blind spots. Pentest (black-box) scanning reveals services and exploitable vulnerabilities from an attacker’s perspective through banner grabbing and safe exploitation checks. Audit (white-box) connects via WMI, RPC, or SSH with privileged credentials to obtain precise OS versions, patches, and installed software.
Agent-Based Scanning
When network reachability or privileged accounts are unavailable, lightweight agents collect local inventory and report on schedule or connectivity. Tenable and Qualys explicitly state in their documentation that agents must be paired with network scanning. Agents cannot discover unknown assets, run on network devices or OT controllers, and introduce privileged code that itself becomes an attack surface.
Cloud Snapshot and Passive Methods
Orca Security’s SideScanning and Wiz pioneered read-only disk snapshot analysis in public clouds, now also offered by Amazon for EC2 and Microsoft Defender for Cloud. The technique mounts volume copies outside the running workload. In OT and legacy segments, passive sensors on SPAN/TAP ports analyze industrial protocols without sending packets, though they miss silent devices.
Containers, SCA, and Integrations
Container images should be scanned in registries with Trivy, Grype, PT Container Security, Kaspersky Container Security, and Luntry before admission to clusters. SCA and SBOM tools address transitive dependency vulnerabilities invisible to network or agent scanners. Connectors to existing EDR, SIEM, and CMDB systems further enrich asset data.
The article concludes that organizations typically combine all approaches rather than choosing one, with coverage metrics tracked continuously to avoid false confidence in unmonitored assets.
Related articles
Enodia: Open-Source Go Tool Automates Service Inventory, EOL Tracking and CVE Correlation
A DevOps engineer has released enodia, a single-binary Go CLI that discovers real versions of services across large heterogeneous environments and correlates them with end-of-life calendars and vulnerability databases. The tool was built after manual Ansible-based inventories and existing solutions such as endoflife.date, nvchecker, Renovate and Uptime Kuma proved insufficient for covering both infrastructure and application services while also providing actionable lifecycle, patch and branch status. Enodia uses product-specific probes for 123 technologies including PostgreSQL, MySQL, MariaDB, Jira, Confluence, Bitbucket, VMware vCenter, ESXi, pfSense and multiple Linux distributions, falling back to a generic URL-plus-regex probe when needed. Data collection is deliberately separated from evaluation so that inventory.jsonl files can be generated inside air-gapped networks and later analysed where CVE feeds are available. The project also contributed dozens of missing products and corrected EOL dates to the endoflife.date project and integrates both NVD and Russia’s FSTEC BDU vulnerability databases. Special handling was added for MySQL/MariaDB connection-error counters, version-string masquerading, and vendor-specific update nomenclature to avoid false reports.
Telegram Voice Call Flaw Allows Remote Code Execution on Android Devices
Security researchers disclosed a vulnerability in Telegram for Android that enables remote code execution on a victim's device simply by answering a voice call. The attacker requires only a standard account, and the flaw was present in versions 8.6.2 through 12.10.3 released between March 2022 and September 2026. Telegram addressed the issue in version 12.10.4, released at the end of September 2026. The root cause lies in improper handling of the MediaState message exchanged during calls, specifically when processing rotation values and missing video state fields, leading to out-of-bounds memory reads. The same underlying fix was deployed earlier to shared call libraries, iOS, and desktop clients, but reached Android later. Researchers confirmed the impact only on private calls running on ARM64 Android devices, with no evidence of exploitation in the wild or public CVE assignment as of October 29, 2026.
360 Security Cloud Opens PHP2Shell Vulnerability Self-Check Platform to Government and Enterprise Users
360 Security Cloud has launched a dedicated self-assessment platform that allows organizations to scan their PHP-based websites and systems for the PHP2Shell vulnerability. The service is now available to government agencies, large enterprises, and small-to-medium businesses. Users can apply by scanning a provided QR code to determine how many of their assets run PHP, identify affected versions, and check whether any systems have already been compromised. The platform addresses key questions about exposure: the number of PHP-powered sites and systems, the presence of vulnerable versions, and signs of prior intrusion. The announcement emphasizes that the tool helps organizations proactively assess risk without requiring external assistance. The original Chinese report was published on October 30, 2026, and the service is positioned as a practical response to ongoing PHP-related security concerns.
Liferay Community Edition Misconfiguration Exposes Plaintext Passwords in Government Systems via CWE-319
A detailed analysis reveals how the use of Liferay Community Edition in a closed government information system led to the transmission of user passwords in plaintext through transactional emails. The issue stemmed from default notification templates that included the [$PASSWORD$] macro, combined with unadjusted system variables pointing to localhost instead of the production domain. Despite proper OAuth 2.0 delegation and CSRF protections, the misconfigured password change workflow sent permanent credentials in clear text to user inboxes. The root cause was traced to custom portlets that incorrectly reused the New Password Notification trigger intended only for administrator-initiated resets. Remediation involves removing the password macro from email templates and updating portal-ext.properties to enforce production host settings. The case highlights how open-source enterprise platforms require thorough hardening beyond initial code audits when deployed in high-security environments.