Cybersecurity

Canada ITSP.10.171 — Protecting Specified Information in Non-Government of Canada Systems and Organizations

ITSP.10.171 framework badge
Summarize with
ClaudeChatGPTPerplexityGoogle AI Mode
In this article
At a Glance
ITSP.10.171 — Protecting Specified Information in Non-Government of Canada Systems and Organizations
  • Classification
    Category
    Cybersecurity
    Domain
    Cybersecurity
    Framework Family
    Other
  • Regulatory Context
    Type
    Framework
    Legal Instrument
    Guideline
    Sector
    Government Sector
    Industry
    Aerospace & Defense
  • Region / Publisher
    Region
    North America
    Region Detail
    Canada
    Publisher
    Canadian Centre for Cyber Security (CCCS), Communications Security Establishment
  • Versioning
    Version
    ITSP.10.171, second release (October 28, 2025)
    Effective Date
    April 2, 2025
    Issue Date
    April 2, 2025 (first release); October 28, 2025 (second release)
  • Adoption
    Adoption Model
    Industry Requirement
    Implementation Complexity
    High
  • Official Reference
License Information

License included / downloadable: Yes

ITSP.10.171 is published free by the Canadian Centre for Cyber Security at cyber.gc.ca and is included with the platform for reference.

Framework text is licensed by its publisher and is included only where stated above.

Official Resources
ITSP.10.171 — Protecting Specified Information in Non-Government of Canada Systems and Organizations
The Cyber Centre publication: 17 families of security requirements with tailoring criteria and organization-defined parameters (second release, October 28, 2025).
NIST SP 800-171 Rev. 3 (CSRC)
The U.S. publication that ITSP.10.171 adapts; the technical content is the same.
NIST SP 800-171 Rev. 3
The U.S. publication ITSP.10.171 is derived from; useful for suppliers that serve both governments.
Key takeaways
  • ITSP.10.171 sets the security requirements Government of Canada contracts place on suppliers that handle unclassified but safeguarded information.
  • It is the Canadian version of NIST SP 800-171, effective April 2, 2025, with a second release on October 28, 2025.
  • It binds suppliers through the contract that cites it, not as a free-standing law.
  • Suppliers scope the systems handling specified information, complete the 17 requirement families, and keep a system security plan and plan of action.
  • SmartSuite holds the 17 families, the system boundary, the system security plan, and the organization-defined parameter values for each contract.

Overview

ITSP.10.171, Protecting Specified Information in Non-Government of Canada Systems and Organizations, sets the security requirements that Government of Canada departments and agencies put into contracts with suppliers who handle government information that is not classified but must be safeguarded. It is the Canadian version of NIST SP 800-171, took effect April 2, 2025, and its second release was issued on October 28, 2025.

The Canadian Centre for Cyber Security (Cyber Centre), part of the Communications Security Establishment, issues it under the authority of the Head of the Cyber Centre. It binds suppliers through the contract or agreement that cites it, not as a free-standing law. Public Services and Procurement Canada names it as the Canadian industrial security standard for its cyber security certification program for defense suppliers.

Organizations implement it by scoping the system components that handle specified information, completing the 17 requirement families, filling in the organization-defined parameters the contract leaves open, and keeping a system security plan, a plan of action and the evidence that controls operate.

Why does it matter?

Suppliers that hold government information carry the same duty to protect it that the department has. ITSP.10.171 states that the responsibility of departments to protect specified information remains the same when it is shared with non-GC organizations, so a similar level of protection is needed in supplier systems (section 1).

Key benefits include:

  • Defined scope for suppliers

The requirements apply only to the components of non-GC systems that handle, process, store or transmit specified information, or that protect those components (section 1.1).

  • Isolation limits the cost

Organizations can narrow scope by isolating those components in a separate security domain, using physical separation, logical separation or both (section 1.1).

  • Familiar to NIST users

There are no substantial technical changes from NIST SP 800-171, so a supplier already aligned to it carries over most of the work (section 1).

  • Parameters make requirements specific

Organization-defined parameters let departments and suppliers fill in values, such as frequencies, so requirements are testable (section 2.2).

  • Traceable to a catalog

Each requirement references its source controls in ITSP.10.033, the Canadian version of NIST SP 800-53 Rev. 5 (section 2.2).

How does it work?

The 17 requirement families in section 3 are: access control, awareness and training, audit and accountability, configuration management, identification and authentication, incident response, maintenance, media protection, personnel security, physical protection, risk assessment, security assessment and monitoring, system and communications protection, system and information integrity, planning, system and services acquisition, and supply chain risk management.

The requirements were derived by tailoring the ITSP.10.033-01 Medium impact profile. Controls were removed when they are primarily the responsibility of the GC, not directly related to protecting confidentiality, adequately addressed by other controls or not applicable. For that reason the families for personal information handling and transparency, program management and contingency planning are not included (section 2.2).

Where a requirement contains a bracketed organization-defined parameter, the GC department or the non-GC organization supplies the value. If a department does not specify one, the supplier must assign it. Controls withdrawn in NIST SP 800-171 Revision 3 are labeled "not allocated" so the numbering stays interoperable. The Cyber Centre will publish a companion assessment publication based on NIST SP 800-171A, and until then 800-171A can be used as a reference (Overview).

Key Elements

  • Specified information (section 1)

Information, other than classified, that a GC authority identifies and qualifies in a contract as requiring safeguarding. The term replaces the U.S. phrase controlled unclassified information. Safeguarding rules derive from the Treasury Board's Directive on Security Management and the Policy on Privacy Protection.

  • Scope and security domains (section 1.1)

The requirements apply to components that handle specified information. Organizations can limit the scope by isolating those components in a separate security domain, so that the rest of the environment does not have to meet the full set.

  • Security requirements assumptions (section 2.1)

The publication assumes specified information has the same value in GC and non-GC systems, that the confidentiality impact is no less than low (Protected A) and medium for most large GC datasets, and that suppliers may use external service providers to meet requirements.

  • Seventeen families (section 3)

Families 3.1 to 3.17 hold the requirements, and each one has a discussion section and a references section pointing to source controls in ITSP.10.033. The planning, system and services acquisition and supply chain risk management families reflect the Revision 3 structure.

  • Organization-defined parameters and tailoring (Annex A and Annex B)

Annex A lists the tailoring criteria and results for each ITSP.10.033 control. Annex B lists the organization-defined parameters whose values come from the contract, laws, directives or the organization's own risk tolerance.

  • Contract vehicle and certification (section 1 and PSPC)

The requirements are meant for use in contracts and other agreements between GC departments and non-GC organizations. Public Services and Procurement Canada lists ITSP.10.171 as the Canadian industrial security standard for its defense supplier certification program.

What does it cover?

ITSP.10.171 applies to non-GC organizations, mainly suppliers and contractors, that handle, process, store or transmit specified information under a contract or agreement with a GC department. The audience also includes the GC departments that write the contract, system developers, procurement staff and assessors (section 1.2). It does not cover classified information and it applies where no specific safeguarding requirement is set by law, regulation or government-wide policy for the information category (section 1.1).

What are its objectives?

The publication protects the confidentiality of specified information held outside government systems.

Protect the confidentiality of specified information in supplier systems at a level consistent with GC systems.

Give departments a standard set of requirements for contract clauses.

Limit scope to the components that actually handle specified information.

Allow departments and suppliers to tailor parameters to the specified information and mission.

Align with NIST SP 800-171 so suppliers serving both governments manage one control baseline.

Framework in Context

ITSP.10.171 is the Canadian counterpart of NIST SP 800-171 and aligns with ITSP.10.033, the Canadian version of NIST SP 800-53 Rev. 5. It must comply with the Treasury Board's Policy on Government Security, Policy on Service and Digital and Policy on Privacy Protection (section 1). Suppliers that serve both the U.S. and Canadian governments often map the two baselines.

Common Framework Mappings

ITSP.10.171 is mapped to the U.S. and international frameworks that defense and government suppliers already report against.

Mapped frameworks include:

NIST 800-171 Rev. 3

NIST 800-171A Rev.3

NIST 800-53 Rev.5

CMMC 2.0

CMMC 2.0 L2

ISO 27001:2022

CIS Controls v8.1

NIST CSF 2.0

SMARTSUITE

How SmartSuite Supports ITSP.10.171

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.

Use Third Party Risk Management and Compliance Management records to hold the 17 requirement families, the system boundary, the system security plan, the plan of action and the organization-defined parameter values for each contract.

Requirement Library with Parameters

Load the 17 families as controls, each carrying its organization-defined parameter values and its ITSP.10.033 source reference.

Specified Information Inventory and Boundary

Record the systems, security domains, data flows and subcontractors that store, process or transmit specified information (section 1.1).

System Security Plan and Plan of Action

Keep the plan, open gaps, remediation milestones and approvals in one set of linked records.

Evidence and Assessment Tracking

Attach logs, access reviews, training records and assessment results to each requirement, and record results from 800-171A-style assessments.

Subcontractor Flow-Down

Track which subcontractors hold specified information and their attestations against the requirements (family 3.17).

Contract and Certification Readiness Reporting

Report implementation by family, open plan items and readiness for contract reviews or certification assessments.

Related frameworks

NIST 800-171 Rev. 3

NIST SP 800-171 Rev. 3 (May 14, 2024): 97 CUI security requirements in 17 families with organization-defined parameters, derived from the SP 800-53B moderate baseline.

NIST 800-171A Rev.3

NIST SP 800-171A Rev. 3 (May 14, 2024) gives the assessment procedures for the 97 SP 800-171 Rev. 3 requirements: ODP determinations first, findings satisfied or other than satisfied.

NIST 800-53 Rev.5

NIST SP 800-53 Rev. 5 is the NIST catalog of security and privacy controls in 20 families, mandatory for federal systems under OMB A-130 and FISMA; Release 5.2.0 issued August 27, 2025.

CMMC 2.0

CMMC is the DoD program, 32 CFR Part 170, that requires contractors handling FCI or CUI to hold a Level 1, 2 or 3 status. Phase 2 was suspended on July 13, 2026.

CMMC 2.0 L2

CMMC Level 2 requires contractors handling CUI to meet all 110 NIST SP 800-171 Rev. 2 requirements, shown by a Level 2 (Self) or Level 2 (C3PAO) assessment under 32 CFR 170.

ISO 27001:2022

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

CIS Controls v8.1

CIS Controls v8.1 is a prioritized set of 18 Controls and 153 Safeguards, in three Implementation Groups, with a new Govern function.

NIST CSF 2.0

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

FAQ

Frequently Asked Questions For Canada ITSP.10.171 (Protecting Specified Information)

It sets the security requirements that Government of Canada departments include in contracts with suppliers that handle specified information, meaning unclassified information a GC authority identifies in a contract as requiring safeguarding. It is the Canadian version of NIST SP 800-171.

Non-GC organizations, mainly suppliers, contractors and subcontractors, whose system components handle, process, store or transmit specified information under a contract or agreement that cites the publication. It applies only to those components and does not cover classified information (section 1.1).

There are no substantial technical changes. The differences reflect Canadian laws, policies and directives, including the term specified information instead of controlled unclassified information and references to ITSP.10.033 instead of NIST SP 800-53 (section 1).

They are bracketed values in a requirement, such as a frequency or a list, that the GC department or the supplier fills in. If a department leaves a parameter blank, the supplier must assign the value (section 2.2 and Annex B).

By designating the components that handle specified information and isolating them in a separate security domain, using physical separation, logical separation or both, for example subnetworks with firewalls and information flow controls (section 1.1).

Put this framework to work in SmartSuite

Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.