Keeper Security is tying selected Tenable cloud identity and access findings to response controls in KeeperPAM, while a separate connector lets Tenable scanners pull credentials from Keeper Commander during vulnerability checks. Keeper said Friday, Oct. 16, the two integrations are available to customers with an active KeeperPAM license.
For cloud findings, a Keeper administrator first maps or onboards the affected resource. KeeperPAM can then rotate its credentials, grant just-in-time access or remove standing privileges. Keeper says Tenable receives the updated finding status automatically.
The credential connection serves a different purpose: giving vulnerability scanners the login information needed to assess systems. Tenable’s guide says passwords and SSH private keys are supplied from Keeper Commander when a scan runs, rather than being kept in scan policies. Its coverage includes SSH logins, Windows systems accessed over SMB and database targets.
Each Tenable Nessus scanner in use must be able to reach the Keeper Commander service endpoint. Teams must specify scan targets; the integration does not provide automatic discovery or dynamic scanning. Tenable’s documentation also calls for Keeper Commander’s Service Mode REST API with API-key authentication, version 2, available in Keeper Commander version 17.1.7 or later.
Tenable’s product note dates the Keeper Commander connector’s release for Tenable One Vulnerability Management and Tenable Nessus to Oct. 8, 2026. It lists availability for Tenable Security Center as “TDB.” Keeper announced the two integrations together on Friday, Oct. 16.
Keeper says the connections are intended to reduce delays caused by approval steps and switching between security tools. Keeper’s announcement did not disclose integration pricing or measured remediation-time results.
