What they want
Your Customers
A SaaS platform is a single door to hundreds or thousands of organizations’ data. Compromise one way in and an attacker can reach all of it.
Protecting businesses in every province and territory
Experiencing a breach? Get help nowCybersecurity for technology and saas
SOC 2 readiness, cloud security and a trust story your biggest prospects will sign off on.
Trust / SOC 2
Trust centre
Ledgerloop Trust Centre
Security, privacy and availability
SOC 2 Type II
Period ended Sep 30, 2026
Sub-processors
Documents
Enterprise security questionnaire
168 of 212 answered16 need review by security lead before sending
Certified partner of
Why this cannot wait
Overview
Cybersecurity for a Canadian SaaS company is a sales issue as much as a technical one. Enterprise buyers send security questionnaires and ask for a SOC 2 report before they sign, and a single cloud misconfiguration or leaked key can expose every customer at once.
We help software and tech companies build a security program that holds up in procurement reviews and protects production without getting in engineering’s way.
Your SaaS platform
One door to every customer
Hundreds or thousands of customer organizations
What they want
A SaaS platform is a single door to hundreds or thousands of organizations’ data. Compromise one way in and an attacker can reach all of it.
What they want
API keys, cloud credentials and signing keys turn up far more often than teams expect.
What they want
For most Canadian SaaS companies the most immediate security problem is commercial: enterprise buyers will not sign until their security team is satisfied.
Risks
From the deal pipeline to production, four risks account for most of the exposure. Each maps to specific controls and to the services that address it.
Sales and procurement
Questionnaires and SOC 2 requests at the final stage.
Risk 1
Code and dependencies
Repositories, open source packages and code review.
Risk 2Risk 4
CI/CD pipeline
Build logs, deploy keys and third-party integrations.
Risk 2Risk 4
Cloud production
Storage, roles and logging across every customer.
Risk 2Risk 3
Identity provider
Engineer, admin and support sessions.
Risk 3
Risk 1
Security reviews, questionnaires and SOC 2 requests from enterprise buyers add months to sales cycles when you cannot answer them.
Compliance readinessvCISOPenetration testingManaged detection and response
Risk 2
Public storage buckets, over-permissioned roles and API keys committed to code repositories are common and fast to exploit.
Cloud securityPenetration testingManaged detection and response
Risk 3
A phished engineer with production or source code access is the shortest path to a breach of every customer.
Cloud securityvCISOManaged detection and responseIdentity and access management
Risk 4
Compromised open source packages, CI/CD pipelines and third-party integrations can push malicious code into your product.
Compliance readinessvCISOPenetration testingWebsite and application security
Scenarios
Illustrative scenarios built on common patterns, not client case studies. One stalls revenue, two reach production.
A Waterloo B2B startup reaches the final stage with a large US insurer. Procurement asks for a SOC 2 Type II report. The company has none. The buyer offers to wait, but asks for a readiness letter and a target date.
OutcomeWithout a plan, the deal slips two quarters.
What changes the outcome
A developer at a Vancouver SaaS company pushes a configuration file containing a cloud access key to a public repository. Automated scanners used by attackers find it within hours.
OutcomeSomeone spins up resources and starts listing storage buckets.
What changes the outcome
An attacker phishes a support engineer and uses their session to approve a malicious app in the company’s identity provider.
OutcomeThe app keeps access even after the password is reset.
What changes the outcome
Key exposed or a suspicious app approved right now? Our incident line is answered 24/7.
+1 236 665 1165Standards
What you need depends on who you sell to. Start from the buyer, then work back to the standard. Ask your top five prospects which they prefer before committing budget.
North American enterprise buyers
The standard most commonly requested. A Type II report tests controls over a period, so starting readiness six to twelve months before you need it leaves time to fix gaps and run the observation period.
European and international customers
An international certification for information security management systems. Many controls overlap with SOC 2, so building for one makes the other easier later.
Your customers’, users’ and employees’ personal information
You are usually a service provider processing customer data, but you also hold your own personal information. Law 25 adds privacy impact assessments before transferring personal information outside Quebec.
Banks and federally regulated insurers
They must manage third-party risk, which shows up as security requirements, audit rights and incident notification clauses in your contract.
Every enterprise customer
Your incident response plan needs to say how and when you notify customers, and your answers need to match what you actually do.
An independent auditor’s report on a service organization’s controls, based on the AICPA’s Trust Services Criteria.
In Canada, these engagements are performed by CPA firms. CPA Canada publishes a SOC 2 guide that builds on the Canadian assurance standard CSAE 3000.
SOC 2 readiness guide for Canadian SaaSCompliance / Control mapping
One control, several frameworks
Implement once, satisfy four frameworks
42 controls mapped to 236 requirements
MFA for remote and admin access
14 evidence items, auto-collected
Quarterly user access reviews
4 evidence items
Patching within defined SLAs
26 evidence items
Backups encrypted and restore-tested
6 evidence items
Security awareness training
9 evidence items
Incident response plan tested
3 evidence items
Sample screen: each control is mapped once to SOC 2, ISO 27001 and other frameworks, so the same evidence serves more than one audit.
Checklist of sources
General information, not legal advice. Confirm your obligations with counsel and your auditor.
Baseline
These are the questions an enterprise security questionnaire will ask in some form. Tick each one you could answer “yes” to honestly today.
Not everything has to happen before Series A. If you have fewer than 30 people and no enterprise buyers asking for reports:
You can usually defer
Do not defer: cheap early, painful to retrofit
How we help
Engineers can own a lot of security. What usually falls through the cracks is policy, vendor risk, monitoring, incident response and audit evidence. A vCISO can own the program while engineering owns implementation, which is often cheaper than a full-time security hire at your stage.
A vCISO also joins sales calls when a buyer’s security team wants to talk to someone.
Compliance readiness covers the gap assessment, policies, control implementation and evidence collection, then coordination with your auditor.
Cloud security reviews and monitors your AWS, Azure or Google Cloud environment for the misconfigurations attackers move fastest on.
Penetration testing and website and application security test your application and cloud environment the way an attacker would.
Managed detection and response gives you the 24/7 monitoring enterprise questionnaires ask about, with AI-assisted triage and human analysts making response decisions 24/7/365.
Compliance / Evidence
SOC 2 Type II evidence
Observation window, July 1 to December 31, 2026
412 items collected, 0 missing, 38 scheduled
Access reviews
Entra ID
Vulnerability scans
Tenable
Backup restore tests
Veeam
Change tickets
Jira
Training completions
Cyberphore LMS
EDR policy snapshots
CrowdStrike
Auto-collected
Sample screen: evidence collected across a SOC 2 Type II observation window.
Cloud / Identity paths
Over-privileged identities
Path to sensitive data: 3 hops
Over-privileged identityPermissions used, last 90 days
6 of 1,214 granted
Only reads and writes to stfinance/backups
Recommended change
Owner · /subscriptions/sub-prod
Storage Blob Data Contributor · stfinance/backups
Rotate secret, move to a managed identity
Sample screen: an over-privileged identity and its path to sensitive data.
Engagements / Report
Finding detail
FINDING PT-114-03
SSL VPN accepts password spraying without lockout or MFA
Evidence
Remediation
Sample screen: one finding from a penetration test report, retested to fixed.
Cyberphore SOC App
Thursday, November 12, 2026 at 07:02
Overnight summary: 1 incident, contained
No outage. One decision needed from you by 10:00.
1,284
signals
13
investigated
1
incident
0
still open
Remote access tool on an accounts payable laptop
Contained 03:21Detected 03:12 after a sign-in from an unfamiliar country. What we did:
Your decision
Please confirm Jordan Martin did not install AnyDesk. We will then reset the password and reconnect the laptop.
Sample screen: a morning summary after an overnight incident.
Independence
Cyberphore helps you prepare for SOC 2. The SOC 2 report itself must be issued by an independent CPA firm. We coordinate with your auditor so the evidence is ready when they need it.
Commitments
Every employee certified
FAQ
Usually when enterprise prospects start asking for it and losing those deals would hurt. Before that, a solid security program, clear policies and a well-answered questionnaire often carry smaller deals. Starting readiness six to twelve months before you need the report gives you time to fix gaps and run the observation period a Type II report requires.
It depends on your buyers. SOC 2 is most commonly requested by North American enterprise customers. ISO 27001 is more familiar to European and some international buyers. Many controls overlap, so building for one makes the other easier later. Ask your top five prospects which they prefer before committing budget.
Engineers can own a lot of it: secure coding, infrastructure as code and secrets management. What usually falls through the cracks is policy, vendor risk, monitoring, incident response and audit evidence. A vCISO can own the program while engineering owns implementation, which is often cheaper than a full-time security hire at your stage.
Many security questionnaires ask about it, especially for production environments and identity providers. You can meet that expectation through a managed detection and response provider rather than building your own security operations team. Be ready to describe how alerts are triaged, who responds and how customers are notified of incidents.
Get started
A free 30-minute call with a certified specialist about your cloud, your code and what your enterprise buyers are asking for.