





Policies state what your company commits to, procedures explain how people carry the commitment out, and auditors check that both exist and match what you actually do. SOC 2 does not hand you a mandatory policy list. The Common Criteria expect you to deploy control activities through policies that set expectations and procedures that put them into action, so the practical question is which policies your scope and risks call for.
Term | What it is | Example |
Policy | A management-approved statement of intent and rules | Access to production is limited to approved personnel |
Standard | A specific, measurable requirement that supports a policy | Production access requires multi-factor authentication |
Procedure | The steps people follow to carry out a policy | How a manager approves and an engineer grants access |
Guideline | Recommended practice that is not mandatory | Tips for choosing strong passphrases |
Your set will vary. Treat this as a starting point to tailor.
Policy | What it covers | Related criteria |
Information security | Overall commitments, roles, responsibilities, management oversight | CC1, CC2, CC5 |
Access control | Provisioning, approval, authentication, least privilege, reviews, removal | CC6 |
Acceptable use | Rules for staff use of systems, devices and data | CC1, CC2, CC6 |
Risk management | How risks are identified, rated, owned and treated | CC3 |
Incident response | Detection, escalation, handling, communication, review | CC7 |
Business continuity and disaster recovery | Continuity planning, backups, recovery and testing | CC9, A1 |
Change management | Request, review, test, approve and release changes | CC8 |
Vendor management | Selection, review, contracts and monitoring of third parties | CC9 |
Data classification, retention and disposal | How data is labeled, kept and securely deleted | CC6, C1 |
Human resources security | Onboarding, offboarding, training, background checks | CC1 |
Encryption and key management | Protection of data at rest and in transit | CC6 |
Secure development and vulnerability management | Secure coding, scanning, patching and remediation | CC7, CC8 |
Privacy | Handling of personal information, if privacy is in scope | P1 to P8 |
With Cstream: Prebuilt Policies and Templates give you framework-aligned starting points, so your team refines wording for your environment instead of writing a policy library from scratch.
Purpose. Why the policy exists.
Scope. Who and what it applies to.
Roles and responsibilities. Who owns, approves and follows it.
Requirements. The actual rules, written so they can be tested.
Exceptions. How exceptions are requested, approved and recorded.
Enforcement. What happens if the policy is not followed.
Review. Owner, version, approval date and next review date.
Write requirements that you can prove. A policy that promises "quarterly access reviews" creates a control the auditor will test every quarter.
Stage | What to do | Evidence |
Draft | Write or adapt the policy and align it with a real control | Draft with owner |
Approve | Management reviews and signs off | Approval record |
Publish | Make it available to everyone it applies to | Publication record |
Acknowledge | Staff confirm they have read it, at onboarding and on updates | Acknowledgment records |
Review | Re-review on the schedule the policy states | Version history |
Retire | Archive replaced policies | Archived versions |
With Cstream: Organization Policies manages the complete lifecycle: authoring, publication, versioning and assignment. Each policy carries individual accountability by design, verified continuously through the same control tests that govern it. People Management assigns acknowledgment tasks to each employee and tracks them.
Link every policy requirement to a control, an owner and a source of evidence.
Put technical standards under the same governance as policy, so engineering practice and written commitments do not drift apart.
Review policies when the system, the team or the vendors change, not only on the calendar.
Keep an exceptions log.
A policy was not approved, or approval cannot be shown
A policy was not reviewed within the period it states
Staff acknowledgments are missing for some employees
The policy describes a process the company does not follow
A generic template was adopted without tailoring it to the company
With Cstream: Standard Management keeps technical standards under the same discipline as policy, and Ops Plan tracks what a company commits in policy and what it executes as one continuous thread, closing the gap between what is planned and what is done.
Cstream is the trusted GRC platform that supports startups through every stage of the SOC 2 journey, from planning and control implementation to audit preparation and ongoing compliance. Cstream keeps one data model for IT operations and compliance, so the assets, people, vendors, policies and control test results you use every day are the same ones that support your audit.
Cstream's SOC 2 capabilities include key features supporting preparation and audit, such as:
Cstream works directly with your audit firm to keep reviews moving. Multi-framework Mapping also lets the same controls support ISO 27001, HIPAA and other frameworks later.
Schedule a demo to see how Cstream supports your SOC 2 journey.

