Build and Maintain Your SOC 2 Compliance Program In The Public Cloud
SOC 2 is a reporting framework that defines security criteria for managing client data, and is developed by the American Institute of CPAs (AICPA). Enterprise organizations, especially in regulated industries often utilize SOC 2 reports as a measure of security preparedness and validation for SaaS solutions and outside vendors. Companies may ask vendors for a current SOC 2 Type 1 or SOC 2 Type 2 report during procurement and security assessment.
Under the cloud shared responsibility model, public cloud platforms such as Amazon Web Services (AWS) and Microsoft Azure, provide teams with specific physical security controls and SOC reports covering cloud infrastructure. It is up to the cloud customer to implement all other necessary security criteria and SOC 2 internal controls and go through a SOC 2 audit to receive a SOC 2 Type 1 or SOC 2 Type 2 report.
Organizations operating in the public cloud are responsible for specific Trust Service Criteria and internal controls within their public cloud environment. Security teams are responsible for security controls including:
CC5.0: Control Activities – CC5.0 defines requirements for determining control activity types, implementing relevant infrastructure controls, and establishing policies and procedures for maintaining internal controls.
Teams operating in the cloud should create security policies that set standard operating procedures across the IT infrastructure and establish security controls, such as encryption, backup, access control, firewall, and intrusion detection standards across all cloud services. Dash ComplyOps tracks all administrative and technical control activities within your organization and cloud environment.
CC6.0: Logical and Physical Access Controls – CC6.0 defines requirements around managing access to data and systems.
Teams with public cloud infrastructure should define logical access controls using services such Identity Access Management (IAM) and VPCs, Security Groups and Firewall Rules, as well as setting encryption settings for individual cloud resources. Teams can enforce all logical access control requirements through Dash ComplyOps security monitoring.
CC7.0: System Operations – CC7.0 defines requirements for finding system vulnerabilities, responding to security incidents, and resolving security concerns.
Teams should implement cloud solutions vulnerability scanning, intrusion detection and audit logging and develop Vulnerability Scanning and Incident Response Policies. Teams may consider enabling audit logging with Cloudwatch and detecting suspicious network activity with GuardDuty. Dash ComplyOps can ensure that these security solutions are properly enabled across cloud resources.
CC8.0: Change Management – CC8.0 defines requirements for setting baseline system configuration and managing changes to software and systems.
Teams should create a set of baseline cloud security controls with a tool such as Dash ComplyOps and continue to monitor cloud resources for changes to security settings and overall configuration. Dash continuous compliance monitoring can automate this process.
Dash enables teams to plan and implement internal controls in the public cloud and achieve SOC 2
Dash ComplyOps makes it simple for your team to identify SOC 2 security gaps across your cloud infrastructure and implement proper security controls.
Dash enables teams to create custom administrative policies mapped to the latest SOC 2 trust service criteria and enforce controls through continuous compliance monitoring.
Dash allows teams to:
Teams should collect all relevant documents, security evidence and agreements. Teams should consider gathering the following security evidence for assessment:
Dash automatically creates an inventory of SOC 2 security controls and collects all security evidence necessary for your SOC 2 audit.
Automate SOC 2 Controls and achieve SOC 2 Type 2