Skip to content

A collection of awesome framework, libraries, documents, learning tutorials, resources about SOC 2 tools and processes.

License

Notifications You must be signed in to change notification settings

paulveillard/cybersecurity-soc-compliance

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

21 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

SOC compliance: SOC 1 vs. SOC 2 vs. SOC 3

Welcome to The World of SOC Complaince:

A collection of awesome framework, libraries, documents, learning tutorials, resources about SOC 2 tools and processes. Thanks to all contributors, you're awesome and wouldn't be possible without you! Our goal is to build a categorized community-driven collection of very well-known resources.

Introduction

What is SOC?

  • Security has always been a big concern for business organizations. AICPA (American Institute of CPAs) developed SOC 2 as a component of its Service Organization Control reporting platform.

  • SOC 2’s goal is to make systems manage customer data in such a way that they ensure the following five principles: security, availability, processing integrity, confidentiality, and privacy.

trust

  • Nowadays, it’s an even more significant concern, and it isn’t hard to understand why. The technology world changes at an amazingly fast pace. Companies around the world increasingly rely on the cloud with each passing year. And with each passing year, we see the number of security threats increase. That’s why compliance requirements are crucial in this day and age. We’re here today to talk about one specific compliance requirement: SOC 2 compliance. SOC 2 is one of the most common compliance requirements organizations have to adhere to. But what is SOC 2, and why should your company care?

soc-compliance

Types of SOC Compliance

compliance

What is SOC 2 compliance?

The definition of SOC 2 is twofold.

  • First, SOC 2 is a technical audit process.
  • It’s a requirement for an organization to write, implement, and follow security procedures.

Table of Contents


^ back to top ^

^ back to top ^

License

MIT License & cc license

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

To the extent possible under law, Paul Veillard has waived all copyright and related or neighboring rights to this work.

Releases

No releases published

Packages

No packages published