A published overview brought together tools for six areas of cybersecurity — from asset discovery to code review and incident analysis. The practical value of the selection isn’t in the number of names: it’s a reminder that a scanner’s result needs to be tied to a specific asset, data source, and test conditions.
The article looks at a hypothetical setup with a website, a database, and a server, where an unknown test environment suddenly turns up. That example neatly illustrates a typical administration problem: a service name in a report still doesn’t explain who owns it or who’s responsible for maintaining it. Tools help gather evidence, but they don’t replace inventory management and checking conclusions.
Reconnaissance starts with an asset list
For finding subdomains and traces associated with a company, the overview names Subfinder, Censys, OWASP Amass, theHarvester, and SpiderFoot. Subfinder searches passive sources for names, while Censys shows information about hosts, services, and certificates the platform has managed to collect. These are useful starting points, but data from an external service comes with its own observation time: an outdated record isn’t proof that a host is still up.
Amass gathers information about assets and the relationships between them; its active methods require care about exactly where requests are sent. theHarvester finds, among other things, email addresses and subdomains in open sources. SpiderFoot runs modules whose results can suggest what to search for next. As a result, a tree of related records can grow easily, but a neighboring site on shared hosting doesn’t automatically become your organization’s asset.
For practical inventory management, it’s important to record not just the name, but also the source, date, and confirmation of ownership. A line with the responsible colleague and the test environment’s purpose is often more useful than a flashy relationship diagram. Otherwise, a tool will find test2, and the next admin will start the investigation from scratch again.
Web checks: the request matters more than the green status
For web application analysis, the selection includes Burp Suite, ZAP, Nuclei, ffuf, and sqlmap. Burp Suite lets you inspect the traffic between a browser and a server and compare requests, for example, from two test accounts. Community Edition has these tools for working with traffic; the built-in automated scanner is part of Professional.
ZAP can also observe traffic through a proxy: passive analysis is different from active testing. After logging in, it’s worth checking which pages and requests the scanner actually covered. If the login form keeps showing up in the history, that doesn’t mean the features behind it have been tested.
Nuclei runs checks using templates. So when investigating a detection, it matters exactly what the template was looking for: a version in the response, or application behavior. ffuf enumerates paths and parameters and helps sort results by response code and size. But some servers return code 200 even for a “nothing found” page, so a status without inspecting the content can create the illusion of success. sqlmap is intended for investigating SQL injection in specific parameters; the development team will need the finding’s context and the place where the query is constructed, not just the “SQLi” label.
Network and server: results depend on the vantage point
Nmap shows port availability from the machine where it was run and helps identify services. The label filtered doesn’t answer the simple question “is the port open or closed?”: that couldn’t be determined from this measurement point. So the result should include where the check was run from, including whether a VPN was enabled.
Wireshark lets you examine network traffic packet by packet. Even when HTTPS content is encrypted, connection-establishment details remain in the capture; you can’t read the data inside TLS without the relevant keys. Greenbone Community Edition is a system that includes the OpenVAS scanner. When comparing its reports, take updates to the check database into account: new detections may appear because the checks changed, not because the server did.
Lynis is run directly on Linux or another supported Unix-like system to check settings and provide recommendations. You shouldn’t apply them mechanically to every machine in the same way: the server’s role matters. testssl.sh checks the TLS versions and ciphers available to a service. If a client connects through a load balancer, its TLS configuration determines the external response, not just the backend settings. A scanner may be diligent, but it can only physically look from its own vantage point.
Detecting events and finding evidence
For network monitoring, the overview describes Zeek and Suricata. Zeek generates structured activity logs; conn.log can show the communicating parties, when the connection began, and how much data was transferred. To find out which process on a host established the connection, you need data from the machine itself. Suricata analyzes traffic and raises alerts when an exchange matches a rule. You can compare the signature name and alert time with other logs, but the alert itself still needs to be checked.
Wazuh collects events from hosts and can monitor file changes, if collection and monitoring are configured. The article suggests testing this with a controlled file change on a test host and checking what reaches the on-call person. Sigma is a format for rules describing events to search for in logs. Moving a rule to another system won’t create missing fields: if the source records only the program name, a rule that needs the process command line won’t have the data it needs.
YARA searches files for specified combinations of strings and bytes. An overly generic indicator can match many ordinary files, so rules should be tested against known harmless samples. Autopsy is named for disk analysis: it helps examine files, directories, and image metadata. A person’s name in a filename doesn’t, by itself, prove who created it.
Velociraptor is intended for remote collection of artifacts from connected hosts and consolidating the results. It’s important to decide in advance what data you need, rather than asking for everything indiscriminately. Plaso extracts events from supported files and logs and builds a timeline, while Timesketch lets you upload and collaboratively analyze such timelines. A login time in a log and a file modification time may end up in the same column, but they mean different things; when correlating them, you also need to check time zones and import settings.
Checks in the development process
Gitleaks searches for secrets, including in Git history. Removing a token from the current version of a file doesn’t remove it from an old commit; if the key is real, it needs to be revoked with its issuer. Trivy checks container images, including for packages with known vulnerabilities. To find the responsible place, figure out how the package got into the image: for example, the source may be the base image.
OWASP Dependency-Check compares project dependencies with published vulnerabilities and can be used with Maven or Gradle in Java projects. A suspicious finding needs to be checked against the precisely identified library and version in the build. Semgrep searches code for constructs described by rules and helps find instances of a known pattern. Checkov analyzes infrastructure configurations, including Terraform, so changes that expose a service to the whole internet can be spotted during review. However, the configuration in the repository and the actual state of the environment may differ if access was changed manually.
The overview’s takeaway is practical: confirm a discovered asset, tie a check to its conditions, and explain a detection using data. For a forgotten test environment, that means finding out who needs it, where it can be accessed from, and where the certificate is actually renewed. A record like that will save more time next time than another report with no owner.









