Mobile Credentials
Tenable Nessus Manager can leverage credentials for patch management systems to perform patch auditing on systems for which credentials may not be available.


Tip: To view whether your AirWatch credentials were successfully authenticated, view the plugin output of the integration_status.nasl plugin once the scan is complete. For more information, see Plugins.

Tip: To view whether your Blackberry UEM credentials were successfully authenticated, view the plugin output of the integration_status.nasl plugin once the scan is complete. For more information, see Plugins.

Tip: To view whether your Intune credentials were successfully authenticated, view the plugin output of the integration_status.nasl plugin once the scan is complete. For more information, see Plugins.
Option | Description |
---|---|
Tenant | The Microsoft Azure Directory (tenant) ID visible in your App registration. |
Client | The Microsoft Azure Application (client) ID generated during your App registration. |
Secret | The secret key generated when you created your client secret key in Microsoft Azure. |
Username | The username for the account you want Tenable Nessus to use to authenticate to Intune. |
Password | The password for the account you want Tenable Nessus to use to authenticate to Intune. |

Tip: To view whether your MaaS360 credentials were successfully authenticated, view the plugin output of the integration_status.nasl plugin once the scan is complete. For more information, see Plugins.

Tip: To view whether your MobileIron credentials were successfully authenticated, view the plugin output of the integration_status.nasl plugin once the scan is complete. For more information, see Plugins.

Tip: To view whether your Workspace ONE credentials were successfully authenticated, view the plugin output of the integration_status.nasl plugin once the scan is complete. For more information, see Plugins.