• SOC 2 Readiness
  • 24/7 incident line
  • 24/7 security operations team
Built around SOC 2, AICPA

SOC 2 Compliance ServicesPrepare for Your SOC 2 Report with Confidence

Win enterprise deals and build customer trust with a SOC 2 report. We guide you from readiness assessment to audit completion with senior practitioners. The audit itself stays with your independent CPA firm.

Call (587) 821-5997
Scoped to your environment24/7 security operationsWorldwide coverage

SOC 2 Compliance Services Challenges Facing Modern Organizations

Enterprise customers require SOC 2

Uncertain about audit readiness

Previous audit gaps or failures

Comprehensive SOC 2 Compliance Services

Everything you need to protect your organization, delivered directly by senior security practitioners.

SOC 2 Readiness Assessment

Comprehensive evaluation of your current controls against SOC 2 Trust Services Criteria. Identify gaps before the audit.

Policy & Control Development

Development of required policies, procedures, and controls to meet SOC 2 requirements.

Evidence Collection Support

Guidance on collecting and organizing evidence for auditor review. Streamlined audit preparation.

Technical Controls Implementation

Implementation of access controls, logging, monitoring, and security tools required for SOC 2.

Auditor Liaison

We work directly with your auditor to answer questions and facilitate a smooth audit process.

Ongoing Compliance Support

Continuous support to maintain SOC 2 compliance through surveillance audits and annual renewals.

What You Get With SOC 2 Compliance Services

Tell us what you need tested, monitored or evidenced, and we will scope it with you.

Starting at

$5,000

Readiness assessment; ongoing support packages available

Gap assessment that shows what your auditor will test

Evidence organized the way auditors request it

Win enterprise deals requiring SOC 2

Demonstrate security commitment to customers

Streamlined audit process with less disruption

Clear roadmap from assessment to your SOC 2 report

Ongoing support for surveillance audits

Competitive advantage in B2B sales

How SOC 2 works

The five Trust Services Criteria, in plain language

SOC 2 is an attestation report issued by an independent CPA firm under the AICPA's Trust Services Criteria. You choose which categories go in scope. Security is always included; the other four are optional and should follow what your customers rely on.

Security: the common criteria

Every SOC 2 report includes it.

Security is organized as the common criteria, CC1 to CC9, built on the COSO internal control framework. They cover the control environment and governance (CC1 to CC5), logical and physical access (CC6), system operations including monitoring and incident response (CC7), change management (CC8) and risk mitigation, including vendors and business disruption (CC9). Because the common criteria also underpin the other four categories, most of a SOC 2 effort goes here.

What auditors typically test

  • Board or leadership oversight and an approved set of policies
  • Risk assessment, including fraud risk, at least yearly
  • Provisioning, removal and periodic review of user access
  • Monitoring, alert handling and incident response records
  • Change approval and testing before production
  • Vendor risk management for critical suppliers

Availability

Add it when customers rely on your uptime or you publish an SLA.

Availability looks at whether the system is available for operation as committed. It adds criteria on capacity planning, environmental protections, backup and recovery infrastructure, and testing of recovery plans. It does not set an uptime target; it tests that you meet the commitments you make.

What auditors typically test

  • Capacity monitoring and planning
  • Backups and restore testing against defined objectives
  • Business continuity and disaster recovery plans, exercised

Confidentiality

Add it when you hold customer business data under confidentiality terms.

Confidentiality covers information designated as confidential, such as customer intellectual property, financial data or contract terms. The criteria focus on identifying that information, protecting it through its life and disposing of it when retention ends.

What auditors typically test

  • Data classification and handling rules
  • Encryption and access limits on confidential data
  • Secure disposal at the end of retention, with records

Processing Integrity

Add it when customers depend on the accuracy of what your system computes.

Processing Integrity asks whether processing is complete, valid, accurate, timely and authorized. It suits payroll, billing, claims or transaction processing platforms. It does not mean the data itself is correct, only that the system processes it as specified.

What auditors typically test

  • Input validation and error handling
  • Reconciliations and output review
  • Documented processing specifications

Privacy

Add it when personal information about end users is central to your service.

Privacy follows the life of personal information: notice, choice and consent, collection, use and retention, access, disclosure, quality and monitoring. Canadian organizations often find it overlaps heavily with PIPEDA and provincial privacy law, but a SOC 2 Privacy section does not on its own show legal compliance.

What auditors typically test

  • Privacy notice and consent records
  • Retention and disposal of personal information
  • Handling of access and correction requests

A common mistake is adding every category to look thorough. Each one adds criteria to design, operate and evidence for the whole audit period. Start with Security, add Availability or Confidentiality when contracts call for them, and expand later.

Type I or Type II

What the two report types prove, and how the timeline fits together

Both report types describe your system and your controls. The difference is what the auditor tests and over what period.
SOC 2 Type I compared with Type II
Type IType II
What it testsWhether controls are suitably designed and in placeWhether controls are designed and operated effectively
PeriodA single dateA period, commonly 3 to 12 months
How evidence is testedWalkthroughs and inspection of one instanceSamples drawn from the whole period, for example 25 changes or every quarterly review
What buyers think of itA useful first signal, often accepted for a first yearWhat most enterprise security teams expect
When it makes senseYou need something to show soon and controls are newControls have run long enough to produce a trail
  1. Readiness

    Choose scope and criteria, run a gap assessment, fix gaps and set up evidence collection. Typically the longest phase for a first audit.
  2. Type I (optional)

    The CPA firm tests design at a date. Useful when a buyer needs something before the first period closes.
  3. Observation window

    Controls operate and produce records. A first window is often 3 to 6 months; later reports usually cover 12.
  4. Type II and renewal

    Fieldwork, report issue, then the next window starts straight away so coverage stays continuous.

Why the calendar matters more than the effort

You cannot speed up an observation window. If a customer will need a Type II report in nine months, readiness has to be finished early enough to leave room for the window and for the auditor to write the report. Many teams use a Type I or a bridge letter to cover the gap.

Evidence

What auditors actually ask for

Policies are only the start. For a Type II report, the auditor requests populations (all users, all changes, all terminations in the period), picks samples and asks you to show each control worked for each sample.

  • Approved policies with version history and staff acknowledgements
  • Organization chart and documented security roles
  • Annual risk assessment and the resulting risk register
  • Minutes or records showing leadership reviewed security

  • Background checks completed before start dates
  • Security awareness training completion records
  • Signed confidentiality or code of conduct agreements
  • Termination tickets matched to access removal dates

  • User lists exported from production, cloud and key SaaS systems
  • MFA configuration screenshots or exports
  • Quarterly access review sign-offs, with what was removed
  • Encryption settings for data at rest and in transit

  • Alert rules, log retention settings and SIEM coverage
  • Tickets showing alerts were investigated and closed
  • Vulnerability scan results and remediation timelines
  • Incident response plan, tabletop record and any incident reports

  • A population of production changes for the period
  • For sampled changes: approval, testing and deployment records
  • Branch protection and separation of duties settings
  • Emergency change records with after-the-fact approval

  • Vendor inventory with risk ratings
  • Vendor SOC 2 reports reviewed, including their user entity controls
  • Backup configuration and a recorded restore test
  • Business continuity plan and test results

Common exceptions

Where first SOC 2 audits usually slip

An exception is a sample where a control did not work as described. A few are normal and are reported with your response, but they are avoidable. These come up most often.

Access not removed on time

A leaver kept a SaaS account for weeks because offboarding was handled by email. Fix it by tying every system to an offboarding checklist triggered by HR.

A missed quarterly review

One access review in the window was skipped or not signed off. Calendar the reviews with a named owner and a backup.

Changes merged without approval

Admins could bypass branch protection and did. Restrict bypass, and document emergency changes with a later approval.

MFA gaps

A service account or a legacy admin login sat outside single sign-on. Inventory every privileged path, not just the identity provider.

Alerts with no trail

Alerts fired but there is no record of who looked. Every alert needs a ticket or case showing triage and closure.

Training or background checks late

New starters completed training months after joining. Make both a gate in onboarding with a due date.

Check yourself

SOC 2 readiness quick check

Ten yes, partly or no questions. You get an indicative readiness score, your gaps grouped by area and where you sit on the path to a Type II report.
Readiness quick check

How ready are you for SOC 2?

Ten questions drawn from what CPA firms test most often under the Security criteria (the common criteria every SOC 2 report includes).

0 of 10 answeredAbout 3 minutes
  1. Question 1: Do you have approved security policies (information security, access, change, incident response) that staff have acknowledged in the last 12 months?

    Governance and risk

  2. Question 2: Have you completed and documented a risk assessment in the last 12 months, with each risk linked to the controls that address it?

    Governance and risk

  3. Question 3: Is multi-factor authentication enforced on email, cloud consoles, code repositories and production access?

    Access control

  4. Question 4: Do you run documented user access reviews (at least quarterly) for production systems and key SaaS tools?

    Access control

  5. Question 5: Are joiners and leavers handled through a ticket or checklist, with access removed promptly when someone leaves?

    Access control

  6. Question 6: Do production changes go through peer review and approval, with the record kept (for example approved pull requests)?

    Change management

  7. Question 7: Are security logs from production, identity and cloud centralized, retained and reviewed, with alerts someone responds to?

    Monitoring and response

  8. Question 8: Do you scan for vulnerabilities, fix them within set timeframes, and have you had a penetration test in the last 12 months?

    Monitoring and response

  9. Question 9: Do you keep a vendor inventory and review the SOC 2 reports or security posture of critical vendors each year?

    Vendors

  10. Question 10: Are backups restore-tested, and has your incident response plan been exercised in the last year?

    Resilience

How we work

How GuardsArm prepares you for SOC 2

We prepare you for the audit; an independent CPA firm performs it and issues the report. Keeping those roles separate is what makes the report credible to your customers.
  1. Scope the framework

    Confirm the system boundary, the criteria in scope, and what your buyers actually need to see.
  2. Gap assessment

    Each criterion is checked against what is in place and can be evidenced today, not what policy says should happen.
  3. Remediation plan

    Gaps are prioritized by audit risk and effort, with owners and dates, so the work can be scheduled.
  4. Evidence preparation

    Policies, procedures and operating evidence are organized the way the auditor will ask for them.
  5. Readiness review

    A final mock audit before fieldwork, so surprises are found by us rather than by the auditor.
  6. Operate the controls

    Our security operations team, working around the clock, can operate the CC7 monitoring and incident controls and produce their evidence.

Selling into the US from Canada? See SOC 2 for Canadian SaaS, or compare with ISO 27001 if your buyers are international.

Not sure SOC 2 is the right one?

Find every framework and law that applies to you

SOC 2 rarely travels alone. Privacy law, PCI DSS or health information rules often apply too, and much of the control work overlaps.
Compliance framework finderGuidance, not legal advice

Which frameworks and laws apply to you?

Answer eight quick questions. You will get the laws and frameworks that likely apply, why, and a sensible order to tackle them.

0 of 8 answeredAbout 2 minutes
Where does your organization operate?

Pick every place you have offices, staff or customers you serve directly.

Select all that apply.

Do you collect, use or store personal health information?

Health information includes diagnoses, test results, prescriptions and health card numbers.

Select all that apply.

Do you take card payments?
Do you sell software or services to larger businesses?

Enterprise buyers usually send security questionnaires before they sign.

Are you a regulated financial organization?
Are you a public body?
Whose personal data do you handle beyond Canada?

Select all that apply.

What is pushing compliance up the list right now?
Prefer a full checklist? SOC 2 readiness checklist

Plan the engagement

How SOC 2 Compliance Services delivery works

Prepare for a focused scoping conversation. The statement of work confirms the final scope, timing, responsibilities and deliverables.

Scoping inputs

Applicable criteria
Framework version, report or assessment objective, relevant obligations and customer commitments.
Organizational boundary
Entities, products, systems, locations, data types and third parties included in scope.
Control and evidence inventory
Existing policies, control owners, operating records, prior assessments and known gaps.
Assessment pathway
Whether an independent assessor or authority is involved and what handoff it expects.

Before work starts

Record these decisions with the project owner so delivery does not depend on assumptions.

Authorization owner
Name the person who can approve the work, access and testing methods.
In and out of scope
List systems, locations, accounts, third parties and explicit exclusions.
Data handling
Agree what may be collected, where it is stored, who can access it and when it is deleted.
Escalation contacts
Provide technical, business and emergency contacts, including backups.
Maintenance and testing windows
Confirm permitted times, blackout periods, change constraints and stop conditions.
Report audience
Identify technical, executive, auditor or customer recipients and confidentiality needs.
Acceptance and retesting
Where applicable, record report review, acceptance criteria and retest scope in the statement of work.

Delivery sequence

  1. 1

    Define scope and criteria

    Translate applicable requirements into an agreed boundary and control matrix.

  2. 2

    Assess gaps and evidence

    Review control design and available records, then document gaps and evidence needs.

  3. 3

    Remediate and collect

    Support owners as they implement changes and assemble source evidence with context.

  4. 4

    Review readiness and hand off

    Record open items and organize the evidence index for management or an independent reviewer.

Client responsibilities

  • Assign control owners and an executive sponsor with authority to resolve scope and remediation decisions.
  • Operate controls, complete remediation and provide accurate source evidence and explanations.
  • Engage any required independent auditor, assessor or certification body directly.
  • Review management representations, exceptions and unresolved items before external handoff.

Written outputs

  • Scope definition and a requirements-to-control matrix.
  • Gap and remediation register with owners, dependencies and current status.
  • Evidence index mapping source records to controls and review periods.
  • Readiness summary, unresolved items and an assessor or management handoff pack.

Related Services

SOC 2 for Canadian SaaS

Readiness built for Canadian SaaS teams selling into US enterprise.

Learn More

ISO 27001 Readiness

Prepare for certification to the international information security management standard.

Learn More

HIPAA Compliance

Healthcare-specific compliance for PHI protection.

Learn More

Security Risk Assessment

Comprehensive security evaluation beyond compliance requirements.

Learn More

The GuardsArm platform

XDR, EDR, ITDR and email protection in one platform

GuardsArm helps organizations detect, investigate and contain threats around the clock. These are the capabilities our analysts work with, available as a managed service or for your own team to operate.

See the full platform

Ready to Secure Your Organization?

Request a security assessment and discover how SOC 2 Compliance Services can protect your business.

Security assessment scoped to your organization
No obligation, no pressure
A written summary of findings and next steps

The request form is at the top of this page. A senior practitioner replies within one business day to scope it with you. For an active incident, call us instead.