Keeper Security has introduced KeeperDB, a product engineered to broker and audit direct connections to databases like PostgreSQL and Microsoft SQL Server. The move targets a persistent architectural gap: the management of credentials used by database administrators and developers for interactive access. These credentials, often embedded in environment variables or configuration files, represent a significant exposure.

The system functions as an encrypted gateway. A user authenticates via Keeper's platform, which then establishes a tunnel to the database without exposing the underlying password or connection string to the user's machine. Each session is scoped to a single database instance, operates without a VPN, and can be recorded for audit trails. This design attempts to balance security controls with the operational need for direct database access during tasks like query optimization or incident response.

From an engineering perspective, the integration strategy is notable. KeeperDB plugs into the company's existing privileged access management console, aiming to reduce adoption friction for teams already using Keeper for credential management. The technical trade-off involves centralizing connection brokering through Keeper's infrastructure, which adds a dependency but eliminates credential sprawl. The product must now prove it can handle the scale and variety of connections in enterprise environments, from interactive DBA sessions to automated pipelines, where its separate secrets management product would come into play.

The launch reflects a broader trend of extending identity governance to data stores, a requirement underscored by recent regulatory shifts. Success will depend less on the concept, which competitors also address, and more on execution—specifically, reliability at scale and seamless integration in complex, multi-database stacks.

Source: Webpronews