SOC2

Summary

Regulation: Service Organization Control 2

Abbreviation: SOC2

Governs these parties: all technology service providers or SaaS companies that store or handle client data

Enforced by: the majority of global companies require their partners and vendors to meet these standards

Details

Service Organization Control (SOC) 2 is a set of compliance requirements and auditing processes targeted at third-party service providers. It was developed to help companies determine whether their business partners and vendors can securely manage data and protect the interests and privacy of their clients.

The rest of this document is designed to help our community understand SOC2 better by outlining the following information.

How this regulation relates to cybersecurity

SOC2 is based on specific criteria for managing customer data correctly, which consists of five trust service categories: security, availability, processing integrity, confidentiality, and privacy.

These areas cover:

  • Logical and physical access controls — how to restrict and manage logical and physical access, to prevent any unauthorized access
  • System operations - how to manage system operations to detect and mitigate deviations from set procedures
  • Change management - how to implement a controlled change management process and prevent unauthorized changes
  • Risk mitigation - how to identify and develop risk mitigation activities when dealing with business disruptions and the use of any vendor services

How Coro handles compliance for you

At Coro, we've done the research thoroughly and regularly track updates to the regulation in order to ensure that you are implementing best practices in the areas we cover when we're protecting your systems.

The following table outlines the requirements described by SOC2 that Coro implements in conjunction with Microsoft 365 or Google Workspace.

Disclaimer

This table does not guarantee that your organization is compliant with these regulations. As a best practice, seek assistance from a certified auditor when completing your analysis.

Category Requirement How Coro does it
Cloud Security & Privacy Malware and ransomware injection Detects malware and ransomware files in cloud drives
Cloud app account takeover Monitors access to cloud apps and user/admin activities on them
Data governance over cloud drives Data loss prevention (DLP) for regulatorily and business-sensitive data
Multi-Factor Authentication (MFA) Multi-factor authentication at cloud app access
Data Encryption Safeguarding stored sensitive information against unauthorized use and information leaks
Audit and activity logs Enables searching & working with all activities across environments
Email Security & Privacy Malware and ransomware injection Detection of malware and ransomware in email attachments
Identity spoofing Detection of social engineering attacks based on adaptive identity monitoring
Generic and spear phishing Detection of social engineering attacks based on email content analysis
Embedded links to malicious URLs Detects embedded links to malicious servers
DLP over outgoing/incoming email Encrypts emails before they are sent, which are then decrypted by their recipients at the other end.
Business email compromise (BEC) Scans business email, detects and protects against social engineering attacks
Email account takeover Email attacks from within the organization
Encryption of email during transmission Email is encrypted during transit between the sender and the recipient
Audit and activity logs Enables searching & working with all activities across environments
Endpoint Security & Privacy Antivirus (AV) Detects and remediates files with high-risk content based on their signatures
Data recovery Secures local snapshots of data
DLP on endpoint devices Provides data loss prevention (DLP) for regulatorily and business-sensitive data
Audit and activity logs Archives all system activities for a period of seven years, supporting referencing and auditing
Data Governance Data distribution governance and role management Provides data loss prevention (DLP) for data defined as sensitive by regulations
PCI monitoring Monitors PCI (payment card industry) payment transaction data and cardholder data
Audit and activity logs Archives all system activities for a period of seven years, supporting referencing and auditing