We need to import them as we learned earlier so that everything pulls in. This is because they are still on the Nessus server we connected to. Once your scan has finished you might notice that the results have not yet actually been imported into Metasploit's database. NOTE: if you need to pause a scan for some reason you can issue the 'nessus_scan_pause ' command which will pause your scan. If you still have Nessus up in the browser you should be looking at a completed scan report, similar to this: OK, I will start where I last left off in the previous Nessus write-up which was with a completed vulnerability scan already done on the Metasploitable 2.0 virtual machine from Rapid7 team. The key for now is you have a finished report. In some cases this approach is also useful to those who like to work in teams as one person can conduct a scan and then pass the results file to another team member who can then follow the coming instructions to import the results directly into their own local MSF database for continued efforts. Nessus scan profiles and scan types already setup as well as a already completed scan.Stable up to date Metasploit installation, see here if you need some help gettting started you can see this here.A Vulnerable Machine (Metasploitable 2.0 being used for today's demo, download available here.Assuming you have the basics down we can now begin.

You will need to read the previous write up if you are unfamiliar with Nessus, it can be found here. Today I would like to show a few more steps on how you can make the most of this and import your scan results directly into Metasploit, as well as how you can actually run the entire scan from within Metasploit itself. Previously I showed you how to install Nessus vulnerability scanner on your Linux system and run some basic scans.

How to use nessus on metasploitable 2