ISO 27001 — Information Security
An information security management system with a risk-driven Statement of Applicability, ready for the customers demanding proof.
ISO/IEC 27001 is the international standard, published jointly by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC), that sets requirements for an information security management system (ISMS). It applies to any organization that needs to protect the confidentiality, integrity and availability of information, from software companies to manufacturers holding customer drawings.
The current edition is ISO/IEC 27001:2022, with Amendment 1:2024, which adds a requirement to determine whether climate change is a relevant issue when setting the context of the ISMS. The standard is risk-based: it does not prescribe one set of controls for everyone, but requires you to assess your own risks and justify the controls you choose.
In Canada, the push for ISO/IEC 27001 often comes from customers rather than regulators. Enterprise buyers, defense primes, healthcare organizations and procurement teams send long security questionnaires, and a certificate from an accredited body answers many of those questions at once. It supports, but does not replace, obligations under privacy law such as the Personal Information Protection and Electronic Documents Act (PIPEDA).
What the ISO 27001 engagement covers
Every ISO 27001 project runs on the same hybrid model: the compliance management software holds and tracks the system, and a certified lead consultant reviews the work and stands with you through the certification audit. The core elements below are tailored to how your operation actually runs.
Risk Assessment
Statement of Applicability
Access Control
How the software supports ISO 27001
ISO 27001 is in the catalogue. The Standards workspace tracks the status of each requirement and exports the statement of applicability the standard calls for, Documents holds the policies, and Audits holds the internal audit programme.
Every ISO 27001 clause sits in the Standards workspace with a status (Compliant, Partial, Review overdue or No evidence), coverage against a target, linked evidence, and a statement of applicability export.
How we get you certified
Gap Analysis
Weeks 1–2A structured assessment of your current operations against the target standard. Every clause scored, every gap mapped to an owner and a due date.
System Design
Weeks 2–5A compliance management system designed around how your business runs. Processes are mapped with owners in Processes, and clauses are marked in or out of scope in the Standards workspace, not copied from a template.
Documentation
Weeks 4–9Procedures, work instructions and records drafted in Documents, with optional AI drafting and consultant review. Lean documentation your team will use.
Implementation
Weeks 8–16Roll-out with training campaigns, competency records and evidence capture. My actions and the daily summary show who still owes what, so nothing slips before the audit.
Internal Audit
Weeks 14–18A full internal audit in the Audits workspace and a management review that surface findings early. Corrective actions are closed in Improvements before the certification body arrives.
Certification
Weeks 18–24Stage 1 and Stage 2 audit support with your registrar. We are in the room, and we stay on for surveillance-audit readiness.
What does ISO/IEC 27001:2022 require?
The standard has two parts. Clauses 4 to 10 set out the management system requirements, and every one of them applies to a certified organization. Annex A lists reference controls, which you select from based on your risk assessment rather than implement wholesale.
The Statement of Applicability is the document that ties the two parts together. It lists every Annex A control, states whether it applies, explains why, and records whether it is implemented. Auditors use it as a map of the whole ISMS.
Scope and context (clauses 4.1 to 4.3)
You define the internal and external issues and interested parties that shape your information security needs, and set a scope that states which locations, systems and services the ISMS covers.
Risk assessment (clause 6.1.2)
You define risk criteria, identify risks to the confidentiality, integrity and availability of information, assign risk owners, and analyze and evaluate each risk in a repeatable way.
Risk treatment (clause 6.1.3)
You choose how to treat each risk, compare the controls you need against Annex A so none is overlooked, produce the Statement of Applicability, and get risk owners to approve the treatment plan.
Annex A controls
The 2022 edition groups 93 reference controls into four themes: organizational, people, physical and technological.
Performance evaluation (clauses 9.1 to 9.3)
You monitor and measure the ISMS, run internal audits at planned intervals, and hold management reviews that lead to decisions and actions.
Improvement (clause 10)
Nonconformities are corrected, their causes are addressed, and the ISMS is improved over time based on audit results, incidents and changes in risk.
Who needs ISO 27001 certification in Canada?
ISO/IEC 27001 certification is voluntary. Organizations pursue it when information security becomes part of how they win and keep work.
Software and managed service providers selling to larger organizations meet it in vendor risk reviews. Aerospace and defense suppliers hold controlled drawings and technical data their customers expect them to protect. Healthcare and medical device companies handle patient-related and product data that buyers want handled under a recognized framework.
Privacy law sits alongside the standard. PIPEDA applies to private-sector organizations that collect, use or disclose personal information in the course of commercial activity, and Alberta, British Columbia and Quebec have their own private-sector privacy laws that apply within those provinces. ISO/IEC 27001 certification shows that information security is managed systematically, but it is not a privacy compliance certificate. Consent, purpose limits and individual access rights remain separate obligations.
How long does ISO 27001 certification take?
A first ISO/IEC 27001 certification typically takes four to nine months. The range depends mostly on scope: certifying one product or service is a smaller project than certifying the whole organization, and every location, cloud service and supplier inside the scope must be accounted for.
The other driver is how much evidence already exists. An organization with an asset inventory, documented access reviews, tested backups, security awareness training and an incident log is formalizing and connecting work it already does. An organization without them needs time to put the controls in place and then run them long enough to produce records an auditor can sample.
Certification body fees are quoted in audit days, which depend mainly on the number of people working within the scope and the complexity of the systems involved.
A free readiness check gives you a scored view of your current position.
Preparing for the ISO 27001 certification audit
The certification audit runs in two stages. Stage 1 reviews the documented ISMS: the scope, the information security policy, the risk assessment method and results, the risk treatment plan and the Statement of Applicability. Stage 2 tests whether the controls operate as described.
In Stage 2, auditors sample real records. Expect requests for evidence of joiner and leaver access changes, periodic access reviews, a backup restore test, supplier security assessments, security awareness training and the handling of at least one incident or event. A control listed as implemented in the Statement of Applicability needs evidence behind it.
Before Stage 1, complete an internal audit of the whole ISMS and a management review, and close the corrective actions they raise. Keeping the Statement of Applicability, policies and audit program in one compliance system makes it easier to show the auditor that each control has an owner and a current status.
Choose a certification body accredited for ISO/IEC 27001, either by the Standards Council of Canada or by another signatory to the International Accreditation Forum (IAF) Multilateral Recognition Arrangement. After certification, expect annual surveillance audits and a recertification audit in the third year. The six-stage certification process shows how ISO Certification Consultants plan the work from gap analysis to certificate.
ISO 27001 questions, answered
Is ISO 27001 certification mandatory in Canada?
No. ISO/IEC 27001 certification is voluntary in Canada and is not required by general law. It becomes a practical requirement when customers, primes or procurement teams make it a condition of a contract or a vendor approval. Organizations also pursue it to replace repeated security questionnaires with one independently audited certificate from an accredited certification body.
What is a Statement of Applicability in ISO 27001?
A Statement of Applicability is a required document in ISO/IEC 27001:2022 that lists the Annex A controls, states whether each one is included, justifies inclusions and exclusions, and records whether each included control is implemented. It is the bridge between your risk treatment decisions and the controls the auditor will test, so it needs to stay current as risks and systems change.
What is the difference between ISO 27001 and SOC 2?
ISO/IEC 27001 is an international standard for an information security management system, and certification is granted by an accredited certification body. SOC 2 is an attestation report issued by a CPA firm under criteria set by the American Institute of Certified Public Accountants. Buyers in the United States often ask for SOC 2, while ISO/IEC 27001 is recognized internationally. Some organizations hold both.
Does ISO 27001 certification make a company compliant with PIPEDA?
No. ISO/IEC 27001 helps you protect personal information with appropriate safeguards, which supports one of the principles of PIPEDA, but certification does not assess privacy obligations such as consent, limits on collection and use, retention or individual access requests. Treat the ISMS as a strong foundation for privacy compliance and address those obligations separately, under PIPEDA or the applicable provincial law.
Do all 93 Annex A controls have to be implemented?
No. ISO/IEC 27001:2022 requires you to compare your risk treatment against Annex A so that no necessary control is overlooked, but each control is included only where your risks call for it. Excluded controls must be justified in the Statement of Applicability. The management system clauses, 4 to 10, are different: every one of them applies to a certified organization.
Explore other standards
Ready to scope your ISO 27001 certification?
Tell us about your operation and what you're certifying for. You'll get a clear, honest read on scope and timeline from a certified lead consultant.
We reply within one business day
