Average Ratings 0 Ratings
Average Ratings 0 Ratings
Description
Address team frustrations related to password management by allowing access to a centralized password pool through a dedicated Slack group. Ensure that all team passwords are securely encrypted and stored in a protected environment, thus reducing the chances of passwords being compromised by existing in multiple insecure locations. We provide a comprehensive documentation of the encryption design and make the complete source code available for public review, enabling thorough code assessments and verification of the zero-knowledge protocol in place. To generate a link for the editor to create a secret, note that this link will expire after 15 minutes. Additionally, to ensure the secret becomes inaccessible, it is essential to manually delete it from the S3 password storage. The setup process for the password storage requires only a single execution, streamlining the implementation. For those looking to obtain a one-time-use link to access secret content, remember that this link also expires in 15 minutes. For detailed instructions on establishing your own password server, visit our GitHub project, and feel free to test commands on your Slack team using our designated test server to familiarize yourself with the functionality. This approach not only enhances security but also fosters a more efficient way to manage sensitive information within teams.
Description
Utilize the management console or API to generate secrets, ensuring that they are securely stored in a centralized location that seamlessly integrates with your cloud services and can be accessed by external systems through gRPC or REST APIs. To enhance security, encrypt your secrets with keys from the Yandex Key Management Service, as all stored secrets are maintained in an encrypted state. You have the option to select from pre-defined service roles that offer fine-grained access control to your secrets, allowing you to establish specific permissions for reading or managing both the secrets themselves and their associated metadata. When creating a secret, you can choose a KMS key to securely store sensitive information such as login-password pairs. A secret can encompass various types of confidential data, including but not limited to login-password pairs, server certificate keys, or keys for cloud service accounts. The service also supports multiple versions of each secret, ensuring that all data remains securely stored in an encrypted format. To further ensure availability, all secrets are replicated across three different availability zones, providing robust data redundancy and reliability in case of any failures.
API Access
Has API
No
API Access
Has API
Yes
Pricing Details
No price information available.
Free Trial
No
Free Version
No
Pricing Details
$0.0277 per 10000 operations
Free Trial
Yes
Free Version
No
Deployment
Web-Based
Yes
On-Premises
No
iPhone App
No
iPad App
No
Android App
No
Windows
No
Mac
No
Linux
No
Chromebook
No
Deployment
Web-Based
Yes
On-Premises
No
iPhone App
No
iPad App
No
Android App
No
Windows
No
Mac
No
Linux
No
Chromebook
No
Customer Support
Business Hours
No
Live Rep (24/7)
No
Online Support
Yes
Customer Support
Business Hours
No
Live Rep (24/7)
Yes
Online Support
Yes
Types of Training
Training Docs
Yes
Webinars
No
Live Training (Online)
No
In Person
No
Types of Training
Training Docs
Yes
Webinars
Yes
Live Training (Online)
Yes
In Person
No
Vendor Details
Company Name
Talpor
Founded
2018
Website
scale.talpor.com
Vendor Details
Company Name
Yandex
Founded
1997
Country
Russia
Website
cloud.yandex.com/en/services/lockbox
Product Features
Password Management
Credential Management
No
Multifactor Authentication
No
Password Generator
No
Password Reset
No
Password Synchronization
No
Single Sign On
No
User Management
No