From Fedora Project Wiki

No edit summary
No edit summary
Line 12: Line 12:
# Update the NVTs: {{command |openvas-nvt-sync}}
# Update the NVTs: {{command |openvas-nvt-sync}}
# Restart OpenVAS scanner (take a while for the first time): {{command |/etc/init.d/openvas-scanner restart}}
# Restart OpenVAS scanner (take a while for the first time): {{command |/etc/init.d/openvas-scanner restart}}
# Test that the OpenVAS scanner process openvassd is running: {{ command |ps aux}}
# Test that the OpenVAS scanner process openvassd is running: {{ command |ps aux | grep [o]penvassd }}
# Test that the OpenVAS scanner listens on configured port: {{ command |sudo lsof -i -nP}}
# Test that the OpenVAS scanner listens on configured port: {{ command |sudo lsof -i -nP | grep [o]penvassd }}
# Connect using the gnutls client to scanner port: {{ command | gnutls-cli --insecure -p 9391 127.0.0.1 }}. Start the communication with < OTP/1.0 >. Try to login with the user created above.
# Connect using the gnutls client to scanner port: {{ command | gnutls-cli --insecure -p 9391 127.0.0.1 }}. Start the communication with < OTP/1.0 >. Try to login with the user created above.
# Start OpenVAS client: {{command |openvas-client}} (or System Tools > OpenVAS Client)
# Start OpenVAS client: {{command |openvas-client}} (or System Tools > OpenVAS Client)
Line 20: Line 20:
# Export the report to HTML or PDF.
# Export the report to HTML or PDF.
|results=
|results=
# Start of openvas-scanner without previous configuration will most probably fail. Syslog should display hint about generating certificates.
# Certificate should be created in /etc/pki/openvas/CA/cacert.pem, /etc/pki/openvas/CA/servercert.pem with private keys in /etc/pki/openvas/private/CA/
# Adding of the user will create the account in /var/lib/openvas/users/
# openvas-nvt-sync will download plugins to /var/lib/openvas/plugins
# Restart of the service should result with OK. It takes longer for the first time. On Fedora 16 it is possible that the systemd will timeout thinking that the service failed to start, while actually it is still starting. Give it a while and try stop/start again.
# Process list should show openvassd process running as root "openvassd: waiting for incoming connections"
# lsof for openvassd should show it is listening on port 9391
# The scan should finish correctly.
# The scan should finish correctly.
# In the report, you should see the network services being scanned and vulnerabilities reported.
# In the report, you should see the network services being scanned and vulnerabilities reported.

Revision as of 02:23, 24 January 2012

This test case could be outdated because newer versions of OpenVAS has new services around OpenVAS Scanner (OpenVAS Manager, OpenVAS Administrator, Greenbone Security Assistant)

Description

This test case tests the ability of OpenVAS to scan a host or network for vulnerabilities.

Setup

  • A remote host with various network services (SSH, HTTP, DNS, SMTP ...) is required. For example: a Linux server with OpenSSH, Apache HTTPd, ISC BIND, Postfix or Sendmail.
  • Open ports of the scanned services in the remote host firewall.
  • Ensure that openvas-libraries, openvas-scanner, openvas-manager, openvas-client packages are installed.

How to test

  1. Start OpenVAS scanner: /etc/init.d/openvas-scanner start
  2. Create a new certificate: openvas-mkcert
  3. Add a OpenVAS user: openvas-adduser
  4. Update the NVTs: openvas-nvt-sync
  5. Restart OpenVAS scanner (take a while for the first time): /etc/init.d/openvas-scanner restart
  6. Test that the OpenVAS scanner process openvassd is running: ps aux | grep [o]penvassd
  7. Test that the OpenVAS scanner listens on configured port: sudo lsof -i -nP | grep [o]penvassd
  8. Connect using the gnutls client to scanner port: gnutls-cli --insecure -p 9391 127.0.0.1 . Start the communication with < OTP/1.0 >. Try to login with the user created above.
  9. Start OpenVAS client: openvas-client (or System Tools > OpenVAS Client)
  10. Connect to OpenVAS server with the user created above.
  11. Create a new scan using the client and wait until it finishes.
  12. Export the report to HTML or PDF.

Expected Results

  1. Start of openvas-scanner without previous configuration will most probably fail. Syslog should display hint about generating certificates.
  2. Certificate should be created in /etc/pki/openvas/CA/cacert.pem, /etc/pki/openvas/CA/servercert.pem with private keys in /etc/pki/openvas/private/CA/
  3. Adding of the user will create the account in /var/lib/openvas/users/
  4. openvas-nvt-sync will download plugins to /var/lib/openvas/plugins
  5. Restart of the service should result with OK. It takes longer for the first time. On Fedora 16 it is possible that the systemd will timeout thinking that the service failed to start, while actually it is still starting. Give it a while and try stop/start again.
  6. Process list should show openvassd process running as root "openvassd: waiting for incoming connections"
  7. lsof for openvassd should show it is listening on port 9391
  8. The scan should finish correctly.
  9. In the report, you should see the network services being scanned and vulnerabilities reported.
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_OpenVAS&oldid=268488"