Introduction
The CAN CSA ISO IEC TS 33052-18 standard, officially designated as CAN/CSA-ISO/IEC TS 33052:18, is the Canadian adoption of ISO/IEC TS 33052:2016, Information technology — Process assessment — Process reference model (PRM) for information security management. Published by the Canadian Standards Association (CSA) in 2018, this Technical Specification provides a structured framework for assessing the capability of processes used to manage information security within an organization. It aligns with the ISO/IEC 33000 series on process assessment and complements the ISO/IEC 27000 family of standards for information security management systems (ISMS). This article examines the standard’s scope, technical requirements, practical implementation considerations, and compliance notes.
1. Scope of CAN CSA ISO IEC TS 33052-18
The standard defines a process reference model (PRM) for information security management. The PRM identifies a set of processes that are essential for the effective planning, implementation, operation, monitoring, review, maintenance, and improvement of an ISMS. The scope includes processes such as information security policy management, asset management, human resource security, access control, incident management, and business continuity management related to information security.
The intended users are organizations performing process assessments of their own information security management activities, as well as external assessors seeking a common basis for evaluating ISMS process capability. The PRM is designed to be used in conjunction with the measurement framework provided in ISO/IEC 33020 and the assessment process described in ISO/IEC 33001 and ISO/IEC 33002.
Tip: The PRM in CAN CSA ISO IEC TS 33052-18 is process-oriented, not control-oriented. It describes what processes are performed, not which security controls are implemented. Ensure your assessment team understands this distinction.
2. Technical Requirements: The Process Reference Model
2.1 Structure of the PRM
The PRM establishes a set of processes, each defined by its purpose and outcomes. A process may also be broken down into sub-processes. Each process is assigned to a category based on its domain (e.g., planning, operation, support) within the information security context. The standard includes processes that correspond to the clauses of ISO/IEC 27001:2013 (and later editions) but reorganizes them into a format suitable for capability measurement.
2.2 Process Categories
The processes are grouped into the following categories:
- Sec – Security Governance and Planning: Processes related to setting security policy, objectives, and strategic direction.
- Sec – Security Implementation and Operation: Processes that implement and execute security controls.
- Sec – Security Performance Evaluation: Processes that monitor, measure, analyze, and evaluate security performance.
- Sec – Security Improvement: Processes that manage corrective actions and continual improvement.
2.3 Process Definitions
Each process is defined by:
- Purpose: high-level objective of the process.
- Outcomes: observable results that indicate successful achievement of the purpose.
- Base practices: activities or tasks that contribute to achieving the outcomes (though these are typically detailed in a process assessment model (PAM) rather than the PRM).
An example of a process from the standard is “Information Security Incident Management.” Its purpose is to ensure a consistent and effective approach to managing information security incidents. Outcomes include timely detection, reporting, response, and resolution of incidents.
2.4 Process Reference Model Overview Table
Selected Processes from CAN CSA ISO IEC TS 33052-18 | Process ID | Process Name | Category | Purpose Summary |
| SEC.01 | ISMS Policy and Planning | Governance & Planning | Establish, approve, and maintain the ISMS policy, objectives, and scope. |
| SEC.02 | Asset Management | Implementation & Operation | Identify, classify, and control information assets throughout their lifecycle. |
| SEC.03 | Access Control | Implementation & Operation | Manage user access rights and enforce access restrictions to protect information. |
| SEC.04 | Incident Management | Implementation & Operation | Respond to and resolve information security incidents efficiently. |
| SEC.05 | Security Monitoring and Measurement | Performance Evaluation | Monitor, measure, and report on ISMS performance and effectiveness. |
| SEC.06 | Corrective and Preventive Action | Improvement | Identify and address nonconformities to prevent recurrence. |
Note: The process IDs and exact names may vary slightly between the ISO/IEC TS 33052:2016 and the Canadian adoption; always refer to the latest official publication for precise definitions.
3. Implementation Highlights
Implementing the PRM for assessment typically involves the following steps:
- Understand the context: Map your current ISMS processes (based on ISO/IEC 27001) to the processes listed in the PRM.
- Define assessment scope: Determine which processes will be assessed and to which capability level (e.g., Level 1 (Performed) through Level 5 (Optimizing) per ISO/IEC 33020).
- Select an assessment model: Use a process assessment model (PAM) consistent with the PRM, such as ISO/IEC TS 33072 (for security) or develop an organization-specific model.
- Conduct assessment: Gather evidence using interviews, document reviews, and observations to rate base practices and outcomes.
- Analyze results: Identify strengths and gaps, and plan improvement actions based on capability profiles.
Success Factor: Organizations that have a well-documented ISMS aligned with ISO/IEC 27001 can more easily adopt the PRM because many required outcomes are already addressed. The PRM often helps uncover process inefficiencies that control-based audits miss.
Common Pitfall: Avoid the temptation to treat the PRM as a checklist of controls; it is a process model. Focusing solely on outcomes without assessing the repeatability, measurement, and optimization of the process will not yield a valid capability level determination.
4. Compliance and Alignment with ISO/IEC 27001
CAN CSA ISO IEC TS 33052-18 is intended to complement, not replace, ISO/IEC 27001. While ISO/IEC 27001 specifies requirements for an ISMS and provides controls, the PRM focuses on the capability of the processes that implement those requirements. An organization can achieve certification to ISO/IEC 27001 and also perform a process assessment using this standard to gain deeper insight into process maturity.
Key points regarding compliance:
- The PRM is not a conformity assessment standard; it does not provide pass/fail criteria. It measures capability on a continuous scale.
- Assessments according to ISO/IEC 33001, using this PRM, can support process improvement programs and provide input for internal audits.
- Many national accreditation bodies recognize process assessments as part of overall ISMS evaluation, especially when integrated with management system auditing.
- The Canadian adoption (CAN/CSA-ISO/IEC TS 33052:18) carries the same technical content as the international version, with editorial adjustments to reference Canadian standards when applicable.
Tip for Auditors: When assessing an organization’s ISMS processes using this PRM, ensure that the assessment team is qualified in both process assessment (ISO/IEC 15504 / 33000 series) and information security management (ISO/IEC 27001). This dual expertise is critical for accurate interpretation of outcomes.
Frequently Asked Questions
Q: What is the difference between CAN CSA ISO IEC TS 33052-18 and ISO/IEC 27001?
A: ISO/IEC 27001 specifies requirements for an ISMS and a set of controls; it is used for certification. CAN CSA ISO IEC TS 33052-18 provides a process reference model for assessing the capability of an organization’s security management processes. The two are complementary: an organization can be certified to 27001 and also use the PRM to measure process maturity.
Q: Is the PRM mandatory for organizations already implementing ISO 27001?
A: No, the PRM is not a requirements standard; it is a technical specification that provides a model for process assessment. It is optional but can be valuable for organizations seeking a deeper understanding of how well their ISMS processes are performed and capable.
Q: How often should a process assessment be performed?
A: The standard does not prescribe a frequency; that depends on organizational objectives, maturity levels, and risk environment. Typically, a full assessment is done annually or when significant changes occur to the ISMS or business context.
Q: Does the adoption by CSA introduce Canadian-specific requirements?
A: CAN/CSA-ISO/IEC TS 33052:18 is technically identical to the ISO/IEC version. The CSA adoption may include a national foreword and references to related Canadian standards (e.g., CAN/CSA-ISO/IEC 27001), but the PRM content is unchanged.
This article provides general guidance and does not constitute legal or certification advice. Always consult the official published standard for the complete requirements.
Footer year: 2026