Security Disclosure


Overview

Keeper Security, Inc. (KSI) is passionate about protecting its customer's information with Keeper mobile and desktop security software. Millions of consumers and businesses trust Keeper to secure and access their passwords and private information.

Keeper's software is constantly improved and updated to provide our customers with the latest in technology and protection. This page provides an overview of Keeper's security architecture, encryption methodologies and hosting environment as of the current published version. An overview into the technical details involving our encryption and security methods are described in this document.

Our Privacy Policy and Terms of Use are available on our website via the following links:

Privacy Policy
https://keepersecurity.com/privacy

Terms of Use
https://keepersecurity.com/terms

About the Team

Keeper is a U.S. company with offices located in Chicago, IL and Folsom, CA. Our engineering team is highly skilled and dedicated in software development, data encryption, threat detection and prevention methods against security intrusions and potential vulnerabilities. Our core objectives are to design engaging and useful software, provide timely and accurate product support and to secure and safeguard our customer's data. Keeper software is published in several languages and is sold globally.


Data Protection

KSI does not have access to a customer's master password nor does KSI have access to the records stored within the Keeper vault. KSI cannot remotely access a customer's device nor can it decrypt the customer's data. The only information that Keeper Security has access to is a user's email address, device type and subscription plan details (e.g. Keeper Backup). If a user's device is lost or stolen, KSI can assist in accessing an encrypted backup file to restore the user's data once they have replaced their device.

Information that is stored and accessed in Keeper is only accessible by the customer because it is instantly encrypted and decrypted on-the-fly on the device that is being used - even when using the Keeper Web App. The method of encryption that Keeper uses is a well-known, trusted algorithm called AES (Advanced Encryption Standard) with a 256-bit key length. Per the Committee on National Security Systems publication CNSSP-15, AES with 256-bit key-length is sufficiently secure to encrypt classified data up to TOP SECRET classification for the U.S. Government.

The cipher keys used to encrypt and decrypt customer records are not stored or transmitted to Keeper's Cloud Security Vault. However, to provide syncing abilities between multiple devices, an encrypted version of this cipher key is stored in the Cloud Security Vault and provided to the devices on a user's account. This encrypted cipher key can only be decrypted on the device for subsequent use as a data cipher key.


Strong Master Password

It is highly recommended that customers choose a strong Master Password for their Keeper account. This Master Password should not be used anywhere outside of Keeper. Users should never share their Master Password with anyone.


Two-Factor Authentication

To protect against unauthorized access to a customer's account, Keeper also offers Two-Factor Authentication. Two-factor authentication is an approach to authentication requiring two or more of the three authentication factors: a knowledge factor, a possession factor, and an inherence factor. For more information on Two-Factor Authentication see this link.

Keeper uses something you know (your password) and something you have (the phone in your possession) to provide users extra security in the case where your master password or device is compromised. To do this, we generate TOTPs (Time-based One-Time Passwords).

Keeper generates a 10-byte secret key using a cryptographically secure random number generator. This code is valid for about a minute, and is sent to the user by SMS or voice call.

When using the Google Authenticator application on your mobile device, the Keeper server internally generates a QR code containing your secret key, and it is never communicated to a third party. Each time a user deactivates, then reactivates Two-Factor Authentication, a new secret key is generated.

To activate Two-Factor Authentication, visit the Settings screen of the Keeper Web App.


Client Encryption

Data is encrypted and decrypted on the user's device, not on the Cloud Security Vault. We call this "Client Encryption" because the client (i.g. iPhone, Android Device, Web App, etc.) is doing all of the encryption work. The Cloud Security Vault stores a raw binary which is essentially useless to an intruder. Even if the data is captured when it's transmitted between the client device and Cloud Security Vault, it cannot be decrypted or utilized to attack or compromise the user's private data.

Breaking or hacking a symmetric 256-bit key would require 2128 times the computing power of a 128-bit key. In theory, this would take a device that would require 3×1051 years to exhaust the 256-bit key space.


Keeper's Cloud Security Vault

The Cloud Security Vault refers to KSI's proprietary software and network architecture that is physically hosted within Amazon Web Services (AWS) infrastructure.

When the user synchronizes their Keeper records with other devices on their account, the encrypted binary data is sent over an encrypted SSL tunnel and stored in Keeper's Cloud Security Vault in encrypted format.


Local & Cloud Storage

Keeper software is offered to customers in multiple platforms and environments. The list of platforms and data storage locations is listed below.

Platform Data Storage Facility
Android Local & Cloud Storage
iPhone®, iPad® & iPod® touch Local & Cloud Storage
Desktop App (Windows, Mac & Linux) Local & Cloud Storage
Windows Phone Cloud Storage
BlackBerry Cloud Storage
Web App Cloud Storage
Mac App (Mac App Store) Cloud Storage
Browser Extensions Cloud Storage

Keeper for Groups

Customers who purchase Keeper for Groups are provided an extra layer of control over their users and devices. Keeper for Groups administrators are provided access to an administrative console. The console allows the administrator to manage the users who belong to the organization, control the sharing of records and which devices are permitted to sync.


Network Architecture

KSI utilizes Amazon AWS to host and operate the Keeper solution and architecture. Utilizing Amazon AWS allows Keeper to seamlessly scale resources on-demand and provide customers with the fastest and safest cloud storage environment. KSI operates both multi-zone and multi-region environments to maximize uptime and provide the fastest response time to customers.


Transport Layer Encryption

KSI supports 256-bit and 128-bit SSL to encrypt all data transport between the client application and KSI's cloud-based storage. This is the same level of encryption trusted by millions of individuals and businesses everyday for web transactions requiring security, such as online banking, online shopping, trading stocks, accessing medical information and filing tax returns.

KSI utilizes Transport Layer Security (TLS) (versions 1.0, 1.1, and 1.2) to securely transfer encrypted customer data between the client and the Keeper servers. KSI also supports Forward Secrecy key exchanges using Diffie-Hellman (DHE) enabled cipher suites.

KSI currently supports the following cipher suites:

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA

TLS_DHE_RSA_WITH_AES_128_CBC_SHA

TLS_DHE_RSA_WITH_AES_256_GCM_SHA384

TLS_DHE_RSA_WITH_AES_256_CBC_SHA256

TLS_DHE_RSA_WITH_AES_256_CBC_SHA

TLS_DHE_RSA_WITH_AES_128_GCM_SHA256

TLS_DHE_RSA_WITH_AES_128_CBC_SHA256

KSI continues to research, develop and implement best practices on its encryption levels and methods.


Data Encryption Details

All user-generated data is encrypted with 256-bit AES in CBC mode. The data is encrypted in this way while stored on a user's device, while being transmitted to and from the Cloud Security Vault, and while stored on Keeper's Cloud Security Vault. The only time the data is, or can be, decrypted is on the user's device when the Master Password is entered.


Sharing

Each user has a 2048-bit RSA key pair that is used for sharing. Shared data is encrypted with the recipient's public key. The recipient decrypts the data with their private key. This allows a user to share records only with the intended recipient, since only the recipient is able to decrypt it.


Key Generation

Keeper uses PBKDF2 with HMAC-SHA256 to convert a password to a 256-bit encryption key with a minimum of 1,000 rounds.

The key generated from the Master Password isn't used directly to encrypt user data, but is instead used to encrypt another key (the "Data Key"). The Data Key is used for encrypting data and other keys, such as the RSA private key.

Any key that isn't generated directly from the user's Master Password is generated by a cryptographically secure random number generator on the user's device. For example, both the data key and the RSA key pair are generated on the device. Because the keys are generated on the device (not on Keeper's Cloud Security Vault), we have no visibility into the user's keys.


Key Storage

All secret keys that must be stored (such as each user's RSA private key and the Data Key), are all encrypted prior to storage or transmission. The user's Master Password is required to decrypt any keys. Since Keeper's Cloud Security Vault does NOT have access to the user's Master Password, we cannot decrypt any of your keys or data.


Server Authentication

To prevent unauthorized data access, Keeper's Cloud Security Vault must authenticate each user when transmitting data. Authentication is performed by comparing a PBKDF2-generated hash of the Master Password. The user's device uses PBKDF2 to generate the hash from the Master Password and the server compares the hash to a stored hash.

By using the PBKDF2 hash instead of the Master Password itself, the Cloud Security Vault authenticates the user without requiring the Master Password. PBKDF2 is also used for generating encryption data keys, but the authentication hash is not used for data encryption.


Security Audits, Scanning & Testing


Third-Party Security Scanning & Penetration Tests

KSI is tested daily by McAfee Secure to ensure that the Keeper web application and KSI's Cloud Security Vault are secure from known remote exploits, vulnerabilities and denial-of-service attacks. McAfee Secure badges may be found on the Keeper website to verify daily testing of the Keeper website, Web application, and Cloud Security Vault.

A comprehensive external security scan is conducted monthly on the Keeper website, Keeper web application, and Keeper Cloud Security Vault by Trustwave. Keeper staff periodically initiate on-demand external scans through Trustwave.

Certified SOC2 Compliant

Customer data is protected using stringent and tightly monitored internal control practices. Keeper is certified as SOC 2 Type 1 compliant in accordance with the AICPA Service Organization Control framework. SOC2 certification helps ensure that your data is kept secure through the implementation of standardized controls as defined in the AICPA Trust Service Principles framework.

TRUSTe Certified Privacy

Keeper's products have been audited and certified by TRUSTe to ensure a customer's private data is handled using policies, procedures and best-practices that meet or exceed U.S. and EU government privacy mandates.

Payment Processing and PCI Compliance

The KSI uses Paypal Payments Pro for securely processing credit and debit card payments through the KSI payment website. Paypal Payments Pro is PCI-DSS compliant transaction processing solution.

KSI is certified PCI-DSS compliant by Trustwave.

The Keeper web client, Android App, Windows Phone App, Iphone/Ipad App and browser extensions have been certified EU Safe Harbor compliant with the U.S. Department of Commerce's EU-U.S. Safe Harbor program, meeting the European Commission's Directive on Data Protection.

For more information about the U.S. Department of Commerce U.S.-EU Safe Harbor program, see http://export.gov/safeharbor/index.asp

U.S. Department of Commerce Export Licensed Under EAR

Keeper is certified by the U.S. Department of Commerce Bureau of Industry and Security under Export Commodity Classification Control Number 5D992, in compliance with Export Administration Regulations (EAR).

For more information about EAR: http://www.bis.doc.gov/policiesandregulations/index.htm#ear

24x7 Remote Monitoring

Keeper is monitored 24x7x365 by a global third-party monitoring network to ensure that our website and Cloud Security Vault are available worldwide.

If you have any questions regarding this security disclosure, please contact us.

Phishing or Spoofed Emails

If you receive an email purporting to be sent from KSI and you are unsure if it is legitimate, it may be a “phishing email” where the sender's email address is forged or “spoofed”. In that case, an e-mail may contain links to a website that looks like KeeperSecurity.com but is not our site. The website may ask you for your Keeper Security master password or try to install unwanted software on your computer in an attempt to steal your personal information or access your computer. Other e-mails contain links that may redirect you to other potentially dangerous web sites. The message may also include attachments, which typically contain unwanted software called "malware." If you are unsure about an email received in your inbox, you should delete it without clicking any links or opening any attachments.

If you wish to report an e-mail purporting to be from KSI that you believe is a forgery or you have other security concerns involving other matters with KSI, please contact us.

Hosting Infrastructure Certified to the Strictest Industry Standards

The Keeper website and cloud storage runs on secure Amazon Web Services (AWS) cloud computing infrastructure. The AWS cloud infrastructure which hosts Keeper's system architecture has been certified to meet the following third-party attestations, reports and certifications:

SOC 1 / SSAE 16 / ISAE3402 (SAS70)
SOC 2
SOC 3
PCI DSS Level 1
ISO 27001
FedRamp
DIACAP
FISMA
ITAC
FIPS 140-2
CSA
MPAA

Vulnerability Reporting

General

KSI understands and values the trust our customers place in us. We take security very seriously and investigate all reported vulnerabilities. This page describes our practice for addressing potential vulnerabilities in any aspect of our services.

Appropriate Use and Your Privacy

The information you share with KSI to report a potential vulnerability or security issue is kept confidential. It will not be shared with any third parties outside of KSI without your express, written consent.

Contact Methods

If you believe that you have experienced a vulnerability or security issue with Keeper software, please email us directly at security@keepersecurity.com. If you wish to protect your email, you may use PGP; our secured key is http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x83E4A47BF43583AE.

Contact SLAs

KSI is committed to being responsive and keeping you informed of our progress. You will receive a non-automated response to your initial contact within 24 hours, confirming receipt of your reported vulnerability. You will receive progress updates from us at least every five working days.

Initial Contact

If you believe you have discovered a vulnerability in any KSI product, contact KSI as described above. So that we may more rapidly and effectively respond to your report, please provide any supporting material (e.g. proof-of-concept code, security tool output, etc.) that would be useful in helping us understand the nature and severity of the vulnerability.

Acknowledgment

KSI will review the submitted report and assign it a tracking number. We will then respond to you, acknowledging receipt of the report and outline the next steps in the process.

Evaluation

Once the report has been reviewed, KSI will work to validate the reported vulnerability and reproduce it. If additional information is required in order to validate or reproduce the issue, KSI will work with you to obtain additional information. When the initial investigation is complete, results will be delivered to you along with a plan for resolution and public disclosure, if necessary.

Resolution

If the issue cannot be validated or is not found to be a flaw within KSI's product and system, this will be shared with you.

Notification

If applicable, KSI will coordinate public notification of a validated vulnerability with you. KSI security bulletins are posted on our Security Monitoring page. Individuals, business entities, non-business entities and security teams typically post their advisories on their own web sites and in other forums. When possible, we prefer our respective public disclosures be posted simultaneously.

Threat Classification

KSI uses version 2.0 of the Common Vulnerability Scoring System (CVSS) to evaluate potential reported vulnerabilities. The resulting score helps quantify the severity of the vulnerability and to prioritize our response. Additionally, KSI includes CVSS base and temporal scores in our security advisories, helping customers to understand their risk and to prioritize their own responses.

Disclosure Protection

In order to protect our customers, KSI requests that you not post or share any information about a potential vulnerability in any public setting until we have researched, responded to and addressed the reported vulnerability and informed customers if needed. Also, we respectfully ask that you do not post or share any data belonging to our customers. Addressing a valid reported vulnerability will take time. This will vary based on the severity of the vulnerability and the affected systems.

Improper Disclosure of Vulnerabilities, Source Code or Customer Data

KSI takes extensive measures to protect and safeguard its internal infrastructure, software, intellectual property, stakeholders and its customers. Please read our Privacy Policy. If you are a security researcher or security expert, please be advised that any notifications made to KSI by you, involving a purported security vulnerability of our software and/or infrastructure will be investigated and acted upon swiftly for timely remediation. Please contact us.

The unauthorized access to KSI's systems, software and/or a user's device which runs Keeper is prohibited. Furthermore, the threat of disclosing or actual disclosure of any purported weakness, security flaw or degradation of our software or systems (which are proprietary and property of KSI) in a public forum - is prohibited.

If we determine that an entity or individual has attempted to reverse engineer, enter, infiltrate or breach our software, infrastructure and/or a user's device (which could include a breach or weaknesses in an operating system created by or utilized by one of our strategic OEM partners), we will take swift action - either in the form of a lawsuit and/or a disclosure to appropriate local, state and federal law enforcement agencies.

If, however, your efforts were inadvertent and/or conducted in an internal setting (e.g. on a test device and not that of a Keeper user) and such efforts and results were not subject to a contingent threat of public disclosure or actual public disclosure, we will not bring a lawsuit against you or report you to a local, state or federal law enforcement agency.