Knox vs. CyberArk Conjur

Knox is a secret management solution created to securely store and rotate sensitive information, including secrets, keys, and passwords used across various services. At Pinterest, a wide range of keys and secrets are relied upon for numerous purposes, such as signing cookies, encrypting sensitive data, securing the network with TLS, accessing AWS machines, and interacting with third-party services. The potential for these keys to be compromised presented major challenges, as rotating them often required a deployment and usually involved modifications to the codebase. Previously, keys and secrets were kept in Git repositories at Pinterest, which led to their widespread replication throughout the organization's infrastructure and on numerous employee laptops, making it nearly impossible to monitor access and audit permissions for their use. To tackle these challenges, Knox was designed to make it easier for developers to securely access and manage confidential secrets, keys, and credentials. It guarantees the confidentiality of these sensitive assets while incorporating strong mechanisms for key rotation in case of a security breach, thereby significantly improving security practices. By adopting Knox, Pinterest seeks to not only enhance its secret management processes but also to strengthen its defenses against potential vulnerabilities, ensuring that sensitive information remains protected at all times. This proactive approach reflects Pinterest's commitment to safeguarding its data and maintaining trust with its users.

A robust open-source interface designed for secure authentication, management, and auditing of non-human access across multiple tools, applications, containers, and cloud environments is crucial for effective secrets management. These secrets are essential for accessing various applications, critical infrastructure, and other sensitive data. Conjur strengthens this security framework by implementing strict Role-Based Access Control (RBAC) to manage secrets effectively. When an application requests access to a resource, Conjur first verifies the application's identity, followed by an assessment of its authorization based on the defined security policy, before securely delivering the required secret. The architecture of Conjur operates on the principle of treating security policies as code, with these policies documented in .yml files, version-controlled, and uploaded to the Conjur server. This methodology elevates the importance of security policy to that of other elements in source control, promoting greater transparency and collaboration regarding the security practices of the organization. Moreover, the capability to version control security policies not only simplifies updates and reviews but also significantly bolsters the overall security posture of the organization, ensuring that security remains a priority at all levels. In this way, Conjur contributes to a comprehensive approach to managing sensitive information securely and efficiently.