Nessus
Configure the Nessus connector to retrieve VM information from Nessus
Objective
The purpose of this document is to provide you with a procedure for setting up the connection with Nessus. This procedure will enable the retrieval of VM information from Nessus.
Upon completion of this procedure, you will be able to provide us with the following information:
- Server IP
- Access Key
- Secret Key
Creating Access Credentials
- In the Nessus console, go to Settings → My Account → API Keys.

- Click on Generate to create a new API key.

- Copy the generated Access Token and Secret Token.

Configuration Steps
1. User Account Verification
- Ensure you have a Nessus user account with appropriate permissions
- The account should have access to scan results and vulnerability data
- Verify that the user can access the API Keys section
2. API Key Generation
- Navigate to the My Account section in Settings
- Access the API Keys management page
- Generate a new API key pair (Access Key + Secret Key)
- Securely store both keys for configuration
3. Network Access Setup
- Ensure the Nessus server is accessible from your network
- Verify that the API endpoints are reachable (typically port 8834)
- Test connectivity using the generated credentials
API Capabilities
The Nessus connector will access vulnerability data including:
- Scan Results: Complete vulnerability scan reports
- Asset Information: Details about scanned systems and devices
- Vulnerability Data: CVE information, CVSS scores, and remediation guidance
- Compliance Reports: Security compliance status and findings
Required Information Summary
To configure the Nessus connector, please provide:
- Server IP/URL: The IP address or hostname of your Nessus server
- Access Key: The access token generated in the API Keys section
- Secret Key: The secret token generated alongside the access key
- Port: Custom port if not using standard 8834
- Protocol: HTTPS (recommended and typically required)
Nessus typically requires HTTPS connections. Ensure your server has valid SSL certificates configured.
The Nessus connector will integrate vulnerability assessment data into your security operations, providing comprehensive visibility into security weaknesses across your infrastructure.
Testing API Access
You can test the API credentials using curl:
curl -k -H "X-ApiKeys: accessKey=YOUR_ACCESS_KEY; secretKey=YOUR_SECRET_KEY" \
"https://YOUR_SERVER:8834/server/properties"
Troubleshooting
Common Issues
- SSL Certificate Errors: Use
-kflag for self-signed certificates or configure proper certificates - Authentication Failed: Verify both access and secret keys are correct
- Network Unreachable: Check firewall rules and ensure port 8834 is accessible
- Permission Denied: Ensure the user account has appropriate scan access permissions
Required Permissions
The Nessus user account should have:
- Access to view scan results
- Permission to access vulnerability data
- API access enabled (if this is a configurable option)
Large Nessus deployments may have extensive vulnerability data. Consider scheduling data synchronization during off-peak hours to minimize impact on system performance.