Keeper Security and Tenable Integrate Cloud Risk Remediation and Scan Credential Management

What Readers Should Know
Keeper Security announced Tenable integrations that connect cloud findings with remediation actions and supply centrally managed credentials for authenticated vulnerability scans. Available to customers with active KeeperPAM licenses, the integrations support credential rotation, Just-In-Time access controls and SSH, Windows and database scanning.
Key Takeaways
- Keeper announced two integrations addressing cloud remediation and vulnerability scan credentials.
- Teams can act on Tenable findings through credential rotation, Just-In-Time access and standing privilege removal.
- Keeper says completed remediation automatically triggers a Tenable notification and finding status update.
- The Keeper Commander integration retrieves credentials at scan time for SSH, Windows and database targets.
- Both integrations are available to Keeper customers with active KeeperPAM licenses.
Keeper Security has announced native integrations with Tenable designed to connect cloud risk detection with remediation and centralize the credentials used for vulnerability scanning.
Announced on October 16, 2026, the integrations address two security workflows: acting on cloud findings identified by Tenable and securely supplying credentials for authenticated scans.
The integrations are available to Keeper customers with active KeeperPAM licenses.
Connecting Cloud Findings With Remediation
Tenable identifies exposed identities, risky access paths and cloud misconfigurations. Keeper’s integration sends relevant findings into its remediation engine, where teams can select actions such as credential rotation, Just-In-Time access enforcement and removal of standing privileges.
Once remediation is complete, Keeper says it automatically notifies Tenable and updates the finding to resolved status, reducing manual follow-up.
The company says this workflow can shorten the time between identifying a risk and executing a fix, while reducing the need to switch platforms or manage separate tickets.
“Organisations can’t remediate findings if they aren’t properly equipped to take action immediately,” said Darren Guccione, CEO and Co-founder of Keeper Security.
“As AI-powered threats increase the onslaught of cyber attacks and decrease the window of time in which cyber defenders can take action, this integration enables cloud security teams to implement fixes in seconds instead of weeks.”
Customer-Hosted Gateway Protects Data Exchange
According to Keeper, the remediation integration uses Keeper Encrypter, a self-hosted gateway deployed within the customer’s environment.
The gateway receives webhook traffic from Tenable and encrypts the exchange using customer-managed private keys. Keeper says this preserves its zero-knowledge architecture by keeping unencrypted findings and credentials out of its cloud infrastructure.
Supported actions include rotating exposed credentials across databases, machines, cloud environments and directories. Teams can also enforce Just-In-Time access and onboard PAM User records for cloud identities flagged by Tenable without creating separate database, machine or directory resources.
Each remediation action is logged to provide an audit trail.
Retrieving Scan Credentials From Keeper
A separate integration with Keeper Commander addresses the credentials Tenable needs to access systems during vulnerability assessments.
Instead of storing passwords and SSH keys directly in scan policies, organizations can manage them centrally in Keeper. Tenable requests the relevant credentials when a scan runs.
The integration supports credentialed assessments of SSH, Windows through SMB, and database targets.
These scans allow authenticated checks of installed software, configuration settings, patch levels and compliance status. According to Keeper, when credentials rotate in its platform, Tenable retrieves the updated values during the next scan without requiring manual policy changes.
Two Workflows for Security Teams
Together, the integrations are intended to help teams act on detected cloud risks while reducing the handling of static credentials in scan configurations.
The remediation integration connects findings with corrective actions and status updates. The Commander integration supplies centrally managed credentials for deeper vulnerability assessments.
Organizations can find further information through Keeper Security’s website.
Frequently Asked Questions
What do the Keeper–Tenable integrations do?
They connect Tenable cloud findings with Keeper remediation controls and allow Tenable to retrieve scan credentials from Keeper.
Which remediation actions are supported?
Actions include credential rotation, Just-In-Time access enforcement and removal of standing privileges.
What is Keeper Encrypter’s role?
It serves as a customer-hosted gateway that receives Tenable webhook traffic and encrypts the data exchange using customer-managed private keys.
Which credentialed scans are supported?
SSH, Windows through SMB, and database scans.
Who can access the integrations?
Keeper customers with active KeeperPAM licenses, according to the announcement.