Risk Intelligence Help

Choosing a Scan Delivery Method

The host-based scans can be delivered in various ways depending upon the target user-base, network topologies involved and device types. Currently, Risk Intelligence supports the following primary scan delivery methods:

Method Description Use Case
Scan via Command Line Executable (CLI) and Systems Management These are the most versatile deployment methods. Can be scripted or deployed via Systems Management tools.

Use this when you have other scripting requirements or are using systems management tools:

Scan via Browser A URL that can be opened in a web browser to scan the local computer.

Use this when you want to scan your own computer, or for completely un-managed devices on your network. Available options:

  • Email - Generated text with URL can be pasted into your mail tool and sent to users so that they can scan their device(s). Simply enter the URL in the browser and follow the on-screen instructions.
  • URL - Generates the URL to initiate the scan. Enter in a browser and follow the on-screen instructions.
  • Scan Now Button - Copy and paste the generated code to integrate a scan now button. When pressed, the scan is initiated on your computer.
  • HTML / Javascript Integration - Copy and paste the generated code using the browser scan or Mobile App.

For information on scanning mobile devices, see Scan Mobile Devices.

Choosing the SolarWinds MSP N-Central Delivery Method

To scan computers using the N-central scan delivery method:

  1. Follow the steps described in Scan Computers.
  2. In the Scan Delivery Method dropdown, select SolarWinds MSP N-central.
  3. Download the CLI scan executable required for your operating system (this executable must be installed on all device(s) to be scanned). Choose from:
    • Download the runtime executable for Windows
    • Download the runtime executable for OS X
    • Download the runtime executable for Linux
  4. For information on running the script on SolarWinds N-central, see Add a scripting task.
  5. Make sure you include the -k argument in the Command Line Parameters field in the scripting task.