TOC & Recently Viewed

Recently Viewed Topics

Deploy Nessus Agent Using JSON

When you first launch the agent after installation, the agent first checks for the presence of environment variables, then checks for the config.json file. When the agent launches for the first time, the agent uses that information to link to a manager and set preferences.

config.json Format

The following describes the format of the different sections in config.json.

Note: All sections are optional; if you do not include a section, it is not configured when you first launch the agent. You can manually configure the settings later.


  • The link section sets preferences to link the agent to a manager.
  • Only name, host, port, and key are required. All other settings are optional.


  • The preferences section configures any advanced settings. For more information, see Advanced Settings.

Example Agent config.json file:

{ "link": { "name": "Scanner name", "host": "", "port": 443, "key": "abcdefghijklmnopqrstuvwxyz", "ms_cert": "CA cert for linking", "retry": 1, "groups": ["group 1", "group 2"], "proxy": { "proxy": "proxyhostname", "proxy_port": 443, "proxy_username": "proxyusername", "proxy_password": "proxypassword", "user_agent": "proxyagent", "proxy_auth": "NONE" } }, "preferences": { "global.max_hosts": "500" }

Copyright © 2020 Tenable, Inc. All rights reserved. Tenable,, Tenable Network Security, Nessus, SecurityCenter, SecurityCenter Continuous View and Log Correlation Engine are registered trademarks of Tenable, Inc.., Lumin, Assure, and the Cyber Exposure Company are trademarks of Tenable, Inc. All other products or services are trademarks of their respective owners.