> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/hacking-tools/enumeration/nessus-scan-network-and-system.md).

# Nessus Network and System Scanning

Nessus vulnerability scanning notes for network, host, service, application, and operating system assessment.

## **Scan with Nessus:**

{% hint style="info" %}
Nessus is a powerful vulnerability scanning tool that performs in-depth scans to detect security vulnerabilities within a network or IT infrastructure.
{% endhint %}

{% embed url="<https://www.tenable.com/downloads/nessus?loginAttempted=true>" %}

* **Listening port**: The Nessus scan will be stored on `127.0.0.1:8834`.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-e3b56a6f4c95754a5faaab0433292f1783fdf74c%2Fimage%20(2913).png?alt=media" alt=""><figcaption></figcaption></figure>

* **Scan Options:**

Nessus offers a wide range of configurable scanning options, allowing you to specifically target vulnerabilities present on hosts, services, applications or even operating systems. These options can be adjusted according to the needs of the penetration test or security audit.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-19bcaa69dd7b4400812a8f653a5c984b5f992288%2Fimage%20(2914).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-80298ac733f81809bdc546e82ef8e30f6e23cb97%2Fimage%20(2915).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-f7ab4d8f0a5d23129a9dbf78e19c679b56f4ae62%2Fimage%20(2917).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-96c99039f8b52e755f6b56da7a47473145796573%2Fimage%20(2918).png?alt=media" alt=""><figcaption></figcaption></figure>

### Export Results to Metasploit

Once the Nessus scan is completed, it is possible to export the results for analysis and exploitation in Metasploit, a popular framework for exploiting vulnerabilities.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-46d4f4ca96f778df978a9da7f9f26e0d2ff9f400%2Fimage%20(2919).png?alt=media" alt=""><figcaption></figcaption></figure>

To export the Nessus scan to Metasploit, follow these steps:

* **Export scan:** Save the Nessus scan results file (usually in `.nessus` format).
* **Import into Metasploit:** Use the following command to import the Nessus file into the Metasploit database:

```bash
db_import /home/jordan/Desktop/scan.nessus
```

**View host information:** Once the results are imported, you can obtain information about the scanned hosts with the following command:

```
host 
```

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-ad669cc8ab6bd9e3ec98e0411cb8641ec6dc2081%2Fimage%20(617).png?alt=media" alt=""><figcaption></figcaption></figure>

**List detected services:** To view vulnerable services found on hosts, use the command:

```
services
```

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-f020cdfca40d5dc3d7a886129efba4778bfa5a8d%2Fimage%20(618).png?alt=media" alt=""><figcaption></figcaption></figure>

**View vulnerabilities:** You can list all discovered vulnerabilities using the command:

```
vulnerabilities
```

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-2d5e8b75a75575737be1f30d566ec800a5ff223a%2Fimage%20(619).png?alt=media" alt=""><figcaption></figcaption></figure>

**Filter vulnerabilities by specific port:** To search for vulnerabilities on a particular port (for example, port 445 for SMB), use the command:

<pre class="language-bash"><code class="lang-bash"><strong>vulns -p 445
</strong></code></pre>

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-4b3424ebef582a9536e74af7c8a18bff008ceb80%2Fimage%20(620).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hacking-notes.jord4n.pro/hacking-tools/enumeration/nessus-scan-network-and-system.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
