ITSG-33, "IT Security Risk Management: A Lifecycle Approach", is the Government of Canada's main guidance for managing information technology security risk. It combines a risk management process with a catalogue of security controls and baseline profiles. It matters well beyond federal departments, because suppliers and cloud providers serving them are routinely asked to show alignment with it.
What it is
ITSG-33 is published by the Communications Security Establishment (CSE) through the Canadian Centre for Cyber Security. It is a set of guidance documents, not a statute or regulation. Its authority comes from Treasury Board security policy instruments, which require federal departments to manage IT security risk and which point to ITSG-33 as a primary reference. It was first published in 2012, and parts of it, notably the control catalogue and profiles, have been updated since. Check the Cyber Centre's publications for the current versions, as the guidance and related Treasury Board instruments have continued to evolve.
Its purpose is to give departments a repeatable way to decide which security controls an information system needs, implement them, and keep them effective. The control catalogue draws heavily on NIST SP 800-53, adapted for Canadian context, so practitioners familiar with NIST will recognise much of the structure.
The guidance has two layers of activity:
- Departmental level: governance, policy, roles, and ongoing management of security risk across the organization.
- Information system level: a lifecycle process that runs from defining needs and selecting controls through implementation, assessment, authorization and ongoing monitoring.
Who it applies to
ITSG-33 is directed at Government of Canada departments and agencies, which are bound by Treasury Board security policy. It is not law for private organizations, and there is no general "ITSG-33 certification" that a company can simply hold.
It becomes relevant to the private sector in these situations:
- You provide IT services, software or hosting to a federal department, and the contract or security requirements reference ITSG-33 controls or a profile.
- You are a cloud service provider offering services to the government, where assessments have been tied to a government-defined control profile.
- You handle sensitive government information, for example information categorized as Protected B, and the contracting authority sets security conditions.
- Provincial bodies, critical infrastructure operators or other organizations choose to use it voluntarily as a reference model.
Exact obligations depend on the contract, the sensitivity of the information and the department's own authorization decisions, so confirm requirements with the contracting authority.
Key requirements and control areas
Risk management lifecycle
The process is centred on categorizing the business need and information sensitivity, selecting a control baseline, tailoring it, implementing controls, assessing them, obtaining formal authorization to operate, and monitoring continuously. Residual risk is accepted by an accountable business owner, not by the security team alone.
Security control catalogue
The catalogue (Annex 3A) organizes controls into families, grouped by class: technical, operational and management. Families cover areas familiar from NIST SP 800-53, such as access control, audit and accountability, configuration management, incident response, system and communications protection, contingency planning, personnel security and supply chain concerns. Controls can have enhancements that apply at higher assurance levels.
Security control profiles
The profiles (Annex 4A) are pre-selected control baselines for common situations, based on the sensitivity of information and the required integrity and availability. The best-known in practice is the Protected B, Medium Integrity, Medium Availability profile, usually shortened to "PBMM". Cloud-specific profiles built from the same approach have been used for government cloud services.
Defence in depth and shared responsibility
ITSG-33 expects security to be built from layered controls across the environment and recognises that responsibility is divided between a department and its providers. This is why cloud and outsourced services must show which controls the provider delivers, which the customer delivers, and how the department gets assurance for each.
Continuous monitoring and authorization
Systems are not assessed once and forgotten. The guidance expects ongoing monitoring of control effectiveness, reassessment after significant change, and renewed authorization decisions based on current risk.
Assessment, audit and enforcement
There is no single ITSG-33 audit body. How it works depends on context:
- Within departments: the department's security function assesses controls, and a designated authority makes the authorization decision. Treasury Board and the Office of the Auditor General can examine how departments manage security more broadly.
- For suppliers and cloud providers: assurance is typically contract-driven. The government may review a provider's evidence against a profile, or rely on assessments run through government programs for cloud services. Check which program and process applies to your engagement, as these have changed over time.
- Penalties: ITSG-33 carries no statutory fines. The consequences are contractual and operational: failing to meet security conditions can delay authorization, block onboarding or put a contract at risk.
A practical path to meeting it
- Confirm the requirement. Identify from the contract, RFP or department which profile applies, what information categories are involved, and whether an assessment program is expected.
- Define the system boundary. Document the components, data flows, hosting, third parties and interfaces in scope.
- Categorize the information and system. Record confidentiality, integrity and availability needs and the business impact behind them.
- Select and tailor controls. Start from the required profile, then document tailoring decisions, compensating controls and any exclusions with rationale.
- Split responsibilities. For each control, state whether it is delivered by you, your cloud provider or the customer department, and capture the supporting evidence for each.
- Run a threat and risk assessment. Identify threats against the architecture, check that the selected controls address them, and record residual risks.
- Implement and gather evidence. Configure the controls, write policies and procedures, and keep artifacts such as configuration states, logs, access reviews and test results.
- Assess and remediate. Test the controls, record gaps in a plan with owners and dates, and prepare an assessment package for the authorizing party.
- Support authorization. Present residual risk clearly so the accountable official can decide whether to authorize operation.
- Monitor continuously. Track control health, reassess after material changes, and refresh evidence on a defined schedule.
How it maps to other frameworks
These are overlaps, not equivalences. Satisfying one framework does not demonstrate another without checking the specifics.
- NIST SP 800-53: the closest relationship. The ITSG-33 catalogue is derived from it, so many control families and numbering conventions line up, though Canadian adaptations and different profiles mean the baselines are not identical.
- ISO/IEC 27001: overlap in risk-based management, policies, access, logging, incident handling and supplier management. ISO 27001 is a certifiable management system, whereas ITSG-33 is a control and process guidance set with authorization decisions.
- NIST CSF: useful for communicating at a program level. CSF functions can be loosely related to ITSG-33 activities, but the CSF is not prescriptive about specific controls.
- SOC 2: some overlap in security, availability and confidentiality controls. A SOC 2 report can supply supporting evidence but does not replace assessment against an ITSG-33 profile.
- FedRAMP: conceptually similar, since both rely on 800-53-derived baselines for cloud services, but they are separate national programs with different requirements.
If you already operate against several of these, cross-framework control mapping lets you reuse evidence rather than collecting it again.
FAQs
Is ITSG-33 mandatory?
For Government of Canada departments, it is the main reference under Treasury Board security policy. For private companies it is not law, but it can become a contractual requirement when you serve the government.
Is there an ITSG-33 certification?
No general certification exists. Assurance comes through department authorization processes and, for some cloud services, government-run assessment programs. Verify the current process with the contracting authority.
What does PBMM mean?
It stands for Protected B, Medium Integrity, Medium Availability. It describes a common baseline of controls used for systems handling Protected B information, and is widely cited in cloud procurement.
How is it different from NIST SP 800-53?
ITSG-33 builds on 800-53 but adds a Canadian risk management process, its own catalogue adaptations and government-specific profiles. A team with 800-53 experience will find it familiar, but should not assume control-for-control equality.
Do we need to redo work if we already have ISO 27001 or SOC 2?
Not entirely. Policies, risk assessments, access controls and monitoring evidence often carry over. You will still need to map them to the required profile, close gaps and produce the assessment documentation the department expects.
How Aristiun helps
Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. For ITSG-33 work, where control selection, evidence and risk assessment must all be traceable, it reduces the manual effort of keeping them current across compliance frameworks.
- Automated evidence collection: gather evidence from connected systems such as AWS, Azure, GCP and GitHub, without manual screenshots or spreadsheets.
- Cross-framework mapping: map each piece of evidence to the relevant controls across all applicable frameworks at once, so one evidence base supports several requirements.
- Control monitoring and gap analysis: get alerts when controls drift out of compliance, and use AI-powered validation to find gaps before assessors do.
- Threat modeling: generate threat models from code, IaC and architecture diagrams to support the threat and risk assessment, and produce auditor-friendly reports organized by requirement.