The Bitwarden Blog

How to Comply with SOC 2 Password Requirements with a Password Manager

AL
verfasst von:Andrea Lebron
veröffentlicht:
Link Copied!
  1. Blog
  2. How to Comply with SOC 2 Password Requirements with a Password Manager

Companies that provide services to other organizations and are seeking to boost their information security stance often complete a Service Organization Control 2 (SOC 2) audit, with a growing focus on meeting SOC 2 password requirements. The SOC 2 certification process includes demonstrating the use of adequate system access controls to ensure that sensitive data remains protected and secured at all times. Many companies seeking SOC 2 compliance might leverage solutions such as a SOC 2-compliant password manager to help meet requirements.

A summary of SOC 2

The American Institute of Certified Public Accountants (AICPA) introduced the Service Organization Control or SOC 2 report to help evaluate service companies (examples include financial firms, healthcare providers, cloud service providers, and SaaS providers) and their ability to maintain strong controls “ … relevant to security, availability, and processing integrity of the systems … to process users’ data and the confidentiality and privacy of the information processed by these systems.”

SOC 2 includes two types of reports:

  • Type 1: reports on a company’s system description and the suitability of the design of its controls

  • Type 2: reports on a company’s system description and the suitability and operational effectiveness of its controls

Both SOC 2 report types detail how companies process data, but SOC 2 Type 2 more deeply describes data security controls in place, including credential management. Both report types are restricted to certain entities (e.g., customers or auditors). However, companies may also produce a publicly available SOC 3 report, which summarizes some of the data security criteria found in the SOC 2 report.

Check out the Bitwarden SOC 3 Report.

Overview of the SOC 2 certification process

Companies seeking SOC 2 certification have to pass an audit conducted by an accredited AICPA representative. Five “Principles,” known as the Trust Services Criteria, form the foundation of the audit or “examination engagement” and provide the SOC 2 security criteria. First developed in 2017 and last updated in late 2022 to “reflect an environment of ever-changing technologies, threats and vulnerabilities…changing legal and regulatory requirements and related cultural expectations regarding privacy” and “addressing data management, particularly when related to confidentiality,” the criteria is as follows

  • Security - Information and systems are protected against unauthorized access, unauthorized disclosure of information, and damage to systems that could compromise the availability, integrity, confidentiality, and privacy of information or systems and affect the entity’s ability to achieve its objectives 

  • Availability - Information and systems are available for operation and use to meet the entity’s objectives

  • Processing Integrity - System processing is complete, valid, accurate, timely, and authorized to meet the entity’s objectives

  • Confidentiality - Information designated as confidential is protected to meet the entity’s objectives

  • Privacy - Personal information is collected, used, retained, disclosed, and disposed of to meet the entity’s objectives

Companies only have to comply with the principles that apply to them. For example, the ‘Availability Principle’ typically applies to companies providing colocation, data center, SaaS-based services, or hosting services to customers.

YOU MIGHT ALSO LIKE: The Benefits of Password Managers for Finance Companies

The ‘Security Principle’ and SOC 2 Password Requirements

The ‘Security Principle’ applies to most companies seeking SOC 2 compliance. The bulk of the ‘Security Principle’ requirements exist under section CC6 of the Trust Services Criteria, which also details SOC 2 password requirements. The following sections demonstrate how a password manager can support key requirements.

CC6.1 (Pg. 34-35):

“The entity implements logical access security software, infrastructure, and architectures over protected information assets to protect them from security events to meet the entity's objectives.”

  • Companies must demonstrate how they manage credentials for infrastructure and software, including removing access once it’s no longer needed or required. With a password manager, administrators can easily automate access, assign roles, and restrict users to read-only access for system credentials. Granular access control allows administrators to completely hide passwords to prevent copying passwords, TOTP seeds, or custom fields.

  • Companies must encrypt their data and protect encryption keys at all times. With a 100% end-to-end encrypted password manager using AES 256-bit encryption, companies benefit from true zero knowledge, protecting their credentials and other sensitive data that can be shared amongst employees such as company financial documents. Additionally, PBKDF2 SHA-256 strengthens encryption key protection by limiting key retrieval to only the user logging in with their master password.

CC6.2 (Pg. 36):

“Prior to issuing system credentials and granting system access, the entity registers and authorizes new internal and external users whose access is administered by the entity. For those users whose access is administered by the entity, user system credentials are removed when user access is no longer authorized.”

  • Companies must show how they register and authenticate new users, including levels of access. With a password manager, administrators can link their directory service (LDAP) to streamline user provisioning and deprovisioning. Users and groups in your company LDAP sync with your password manager’s Organization, replicating the same structure. Better yet, whenever a new user is added to the LDAP, they are also created in the password manager; and vice versa, are removed when deprovisioned from the LDAP.

  • Companies must authorize access to protected assets. A password manager with Single Sign On allows your existing Identity Provider to provide authentication for password manager users. Administrators can set password policies requiring users to log in through the Single Sign On method to access credentials.

CC6.3 (pg. 36):

“The entity authorizes, modifies, or removes access to data, software, functions, and other protected information assets based on roles, responsibilities, or the system design and changes, giving consideration to the concepts of least privilege and segregation of duties, to meet the entity’s objectives.”

  • Companies must demonstrate role-based access controls or RBAC. With a password manager, administrators can set user types and create custom roles to assign granular control and user permissions for components of the password manager. RBAC can be configured for functions such as who can manage users, access event logs, or import/export data.

Explore Bitwarden to support SOC 2 password requirements

Adding a password manager, such as Bitwarden, can demonstrate the commitment of service providers to data security and SOC 2 auditors. Bitwarden offers enterprise-grade security, conducts regular third-party security audits, and complies with major privacy and security standards, including SOC 2. Take advantage of an all-access free Enterprise trial to see how Bitwarden can help service providers prepare for a SOC 2 security audit and meet SOC 2 password requirements.

Security TipsBusinessPassword Manager
Link Copied!
Zurück zum Blog

Get started with Bitwarden today.

Erstellen Sie Ihr kostenloses Konto

Erweitern Sie Ihr Wissen über Cybersicherheit.

Abonnieren Sie den Newsletter.


© 2024 Bitwarden, Inc. Bedingungen Datenschutz Cookie-Einstellungen Sitemap

Diese Website ist auf Deutsch verfügbar.
Go to EnglishStay Here