Welcome to this comprehensive guide on the Greenbone Vulnerability Manager (GVM) framework, which includes the well-known OpenVAS Scanner. GVM is a powerful, open-source vulnerability scanning solution designed to help you identify and manage security issues within your IT infrastructure. Whether you're a system administrator, security analyst, or penetration tester, this guide provides the knowledge to leverage GVM effectively.
What is GVM (Formerly known mainly as OpenVAS)?
Greenbone Vulnerability Manager (GVM) is the modern name for the vulnerability management framework previously often referred to simply as OpenVAS. It's a collection of services and tools working together:
- Greenbone Security Assistant (GSA): The web-based user interface (
gsaddaemon) for managing scans, users, reports, etc. - Greenbone Vulnerability Manager Daemon (
gvmd): The central service that controls the scanner, manages vulnerability data (stored in a PostgreSQL database), and handles user requests. - OpenVAS Scanner (
openvas-scanner): The core engine that performs the actual network vulnerability tests (NVTs) against targets. - Network Vulnerability Tests (NVTs): A constantly updated feed of scripts that check for specific vulnerabilities. Provided by Greenbone.
- Data Feeds: Include NVTs, SCAP (Security Content Automation Protocol) data, and CERT-Bund advisories, synchronized regularly.
GVM provides continuous vulnerability updates, robust network scanning capabilities, and detailed reporting to aid remediation efforts.
Why Use GVM / OpenVAS?
- Comprehensive Coverage: Scans for thousands of vulnerabilities across operating systems, network devices, and applications.
- Open Source & Free Core: The core GVM framework is open-source, offering a powerful free solution (Greenbone also offers commercial appliances and feeds).
- Regularly Updated Feeds: Access to the Greenbone Community Feed ensures detection capabilities stay current with emerging threats.
- Detailed & Actionable Reports: Generates reports outlining vulnerabilities, severity ratings (CVSS), impact, and remediation guidance.
- User-Friendly Web UI: The Greenbone Security Assistant (GSA) provides an accessible interface for most operations.
- Automation Potential: Offers APIs and command-line tools (
gvm-tools) for scripting and automation (advanced usage).
Installation Considerations
Installing GVM from source can be complex and time-consuming due to numerous dependencies and components. Here are the common approaches:
Important: GVM installation requires significant system resources (CPU, RAM, Disk Space) and a stable internet connection. The initial setup and feed synchronization can take several hours. Always consult the official Greenbone documentation for the specific GVM version you are installing.
1. Docker (Recommended for Ease of Use):
Using official or community-maintained Docker containers is often the simplest way to get GVM running quickly, abstracting away many dependency issues. Search for Greenbone/GVM Docker images on Docker Hub.
2. Kali Linux Package:
Kali Linux often includes GVM packages, simplifying installation on that specific distribution (commands may vary slightly based on Kali/GVM versions):
sudo apt update
sudo apt install gvm -y
sudo gvm-setupThe gvm-setup script automates initial configuration, database setup, user creation, and the first feed download. Monitor its progress closely.
3. Source Installation (Advanced):
Building from source provides the most control but requires careful management of dependencies (PostgreSQL, Redis, build tools, libraries) and compilation steps for each GVM component. This is recommended only for experienced users.
Initial Feed Synchronization:
Regardless of the method, the first synchronization of the vulnerability feeds is crucial and time-consuming. The modern command is:
sudo runuser -u _gvm -- greenbone-feed-sync(Previously, commands like `gvm-feed-update` or direct rsync were used. Check your version's documentation.)
Basic Usage: Running Your First Scan via GSA
Once GVM is installed and running, access the Greenbone Security Assistant (GSA) web interface. This is typically available at https:// (Port 9392 was common, but check your specific setup, especially with Docker).
- Log In: Use the admin credentials created during setup.
- Define Targets:
- Navigate to Configuration > Targets.
- Click the "New Target" icon (often a star).
- Enter a Name and the IP address(es), CIDR range(s), or hostname(s) to scan.
- Configure other options like alive test method if needed. Click Save.
- Create and Run a Scan Task:
- Navigate to Scans > Tasks.
- Click the "New Task" icon (often a star or plus sign).
- Enter a Task Name.
- Select the Scan Target you just created.
- Choose a Scan Config (e.g., "Full and fast" is a common starting point).
- Ensure the correct Scanner (e.g., OpenVAS Default) is selected.
- Click Save.
- Find your new task in the list and click the "Play" (start) button to launch the scan.
- View the Report:
- Scan progress is shown in the Tasks list.
- Once completed (status "Done"), click on the date/link under the "Last Report" column.
- Analyze the report: results are grouped by severity. Click on individual vulnerabilities for details.
Key GVM Concepts
- NVTs (Network Vulnerability Tests): The individual scripts checking for vulnerabilities.
- Targets: The definition of what systems to scan (IPs, hostnames).
- Tasks: A specific scan job combining a Target, a Scan Configuration, and schedule/settings.
- Scan Configurations: Templates defining which NVT families/scripts to run and scanner preferences (e.g., "Full and fast", "Discovery", "Host Discovery"). You can customize these.
- Reports: The output of a completed scan task, detailing findings.
- Severities/CVSS: Vulnerabilities are ranked by severity (Log, Low, Medium, High, Critical) often based on their CVSS score.
- Filters & Overrides: Mechanisms to tune results, mark false positives, or adjust severity based on your environment.
Interpreting GVM Reports
Effective vulnerability management hinges on understanding reports:
- Prioritize by Severity: Focus on High and Critical vulnerabilities first.
- Understand the Vulnerability: Read the description, impact, and references (CVE links).
- Verify the Findings: Occasionally, scanners produce false positives. Attempt to manually verify critical findings if possible.
- Apply the Solution: Follow the recommended remediation steps (patching, configuration changes, etc.).
- Use Overrides/Filters: If a finding is a verified false positive or acceptable risk, use GVM's override features to manage it in future reports (document why!).
Using GVM for Compliance Assistance
GVM can significantly *aid* in compliance efforts (like PCI DSS, HIPAA, CIS Benchmarks) by identifying technical vulnerabilities that violate specific controls. While it doesn't automatically generate compliance reports, its findings provide essential data for auditors and internal assessments regarding patch levels, secure configurations, etc.
TIP: Establish a regular scanning schedule (e.g., weekly or monthly). Integrate GVM findings into your patch management and change control processes. Don't just scan – act on the results!
WARNING: Always obtain explicit permission before scanning any network or system you do not own or manage. Unauthorized scanning is illegal and unethical. Perform scans during off-peak hours if possible, as intensive scans can potentially impact network or system performance.
Conclusion: Strengthening Security with GVM
Greenbone Vulnerability Manager (GVM) with the OpenVAS scanner is an indispensable tool for proactive security. By mastering its installation, configuration, scanning capabilities, and report analysis, you can significantly improve your organization's ability to identify and mitigate vulnerabilities, thereby reducing the overall attack surface and enhancing security posture.