Changeset 1444574
- Timestamp:
- 06/27/2016 10:48:53 PM (10 years ago)
- Location:
- lockr/trunk
- Files:
-
- 2 edited
-
lockr.php (modified) (1 diff)
-
readme.txt (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
lockr/trunk/lockr.php
r1444545 r1444574 7 7 Plugin URI: https://lockr.io/ 8 8 Description: Integrate with the Lockr hosted key management platform. Secure all your API and encryption keys according to industry best practices. With Lockr, key management is easy. 9 Version: 1.0.09 Version: 2.0 10 10 Author: Lockr 11 11 Author URI: htts://lockr.io/ -
lockr/trunk/readme.txt
r1444545 r1444574 12 12 == Description == 13 13 14 # API & ENCRYPTION KEY MANAGEMENT FOR WORDPRESS # 14 = API & ENCRYPTION KEY MANAGEMENT FOR WORDPRESS = 15 15 16 16 Lockr is the first hosted API & Encryption key management solution for WordPress, providing an affordable solution for all sites to properly manage API and encryption keys used by their plugins. Lockr's offsite key management solution protects against critical vulnerabilities, delivers best-practice security to help sites comply with many industry regulations, and provides a Defense in Depth approach to securing your data. And best of all, even though it delivers enterprise-grade key management, your first key and 1500 key requests are free! Learn more at http://www.lockr.io. 17 17 18 ## Lockr Features: ## 18 = Lockr Features: = 19 19 Easy to configure and setup in WordPress 20 20 Safe and Secure offsite key storage … … 25 25 Backed by Townsend Security's FIPS 140-2 compliant key manager, your keys are secured to industry standards. 26 26 27 ## Lockr is the first key management service for WordPress. ## 27 = Lockr is the first key management service for WordPress.= 28 28 More and more plugins are leveraging 3rd party APIs. To securely access these APIs, a token, secret key, or password is necessary. Until now, these highly sensitive keys were stored right in your database. We’ve seen a major need to secure sensitive data and communications by removing these API keys from your database, encrypting them, and storing safely in an offsite key vault. This limits the damage that could be done if your site is compromised or a developer has a local copy of your database. Lockr makes key management easy. Just install the plugin for WordPress, configure your account and begin securely storing your keys. Lockr provides patches for the major plugins used by hundreds of thousands of sites and with WP-CLI a single command will make sure your plugins use Lockr. 29 29 30 ## Who is Lockr for? ## 30 = Who is Lockr for? = 31 31 Lockr is available for WordPress sites of all sizes. Easy to use for the novice site owner and advanced enough for the expert developer, Lockr secures web transactions and data at rest by protecting API and encryption keys. 32 32 For Site Builders: fill out a single registration form and you’re set. To use with other plugins, look for those that have Lockr available or use our patch library to update your favorite plugin to use Lockr. 33 33 For Developers: Lockr provides an easy to use framework to “get and set” keys from your custom plugin. Additionally, Lockr provides a simple to use encryption function, ensuring your data is encrypted according to industry best-practices and securely stored. Using Lockr helps keep the developer safe, by removing the sensitive passwords and key secrets from the central code base, following security best practices, protecting you as the developer if a site were to be compromised. 34 34 35 ## Is Lockr Safe? ## 35 = Is Lockr Safe? = 36 36 Lockr can secure any API key, secret key, and other types of credentials. Once enabled in WordPress, keys entered are encrypted, then sent over to the Lockr system and removed from the code repository and database. This encryption teamed with hosting provider based authentication prevents your key from being used outside your website. Lockr also manages keys on a “per environment" basis which helps eliminate the potential of keys being shared from production to development environments. No longer will you have to worry about sending a notification from development to your production users, or having production data decrypted in development environments. 37 37
Note: See TracChangeset
for help on using the changeset viewer.