ITSP.10.171 Explained: The Standard Behind CPCSC

ITSP.10.171 Explained: The Standard Behind CPCSC

By Krikor Tengerian · Co-founder, SecuritAI Technologies Ltd. · November 2026 · 9 min read

A contracting officer sends over a security clause, and in the middle of it is a reference you have never opened: ITSP.10.171. Most defense suppliers meet the standard this way, as a citation inside someone else's document, long after the work it describes should have started.

ITSP.10.171 is the Canadian Centre for Cyber Security publication that sets out how organizations outside the federal government protect sensitive government information on their own systems. It is the document under every control in the Canadian Program for Cyber Security Certification. This post explains what it is, how it lines up with the American standard it came from, and how to read it before a contract makes you.

For the program itself, levels, timelines and who assesses what, start with our CPCSC compliance page. This post stays with the standard.

What ITSP.10.171 is

The full title is Protecting specified information in non-Government of Canada systems and organizations. It is published by the Canadian Centre for Cyber Security, and the publication states that it takes effect on April 2, 2025. The current text is the second release, dated October 28, 2025.

Public Services and Procurement Canada is direct about its role. The CPCSC program overview says the Cyber Centre, part of the Communications Security Establishment, developed the Canadian cyber security standard ITSP.10.171 that forms the foundation of CPCSC controls. The Level 1 requirements page adds that defense contracts, and other sensitive contracts outside defense, will need to be certified under the ITSP.10.171 standard based on their risk level.

So when people say "CPCSC controls", they mean requirements drawn from this publication. The program decides how many apply at each level and who checks them. The standard decides what each one says.

Here is the part people get wrong about ITSP.10.171

Most suppliers assume a Canadian standard means a Canadian rewrite, a separate set of rules they will have to learn from scratch. It is closer to the opposite.

The publication describes itself as a Canadian version of NIST SP 800-171 Revision 3, and it says there are no substantial technical changes between it and the NIST document. The changes are about context. The clearest one is vocabulary. In the publication's own words, it uses the term "specified information" in place of "controlled unclassified information", the term the American document uses.

That matters for two reasons. First, if your team has ever worked to NIST SP 800-171, most of what you learned carries over. Second, the American guidance, tools and training built around Revision 3 are useful references, as long as you keep the Canadian document as the one you are measured against.

Read one detail before you build a spreadsheet. The publication explains that, because this is the first Canadian iteration, controls that were withdrawn in NIST SP 800-171 Revision 3 are labeled "not allocated" to keep the same numbering for interoperability. You will see those placeholders throughout the requirement list. Do not count requirement numbers to work out how much work you have. Count the requirements that carry text.

Which NIST revision it follows

This trips people up, so here it is precisely. ITSP.10.171 links to NIST SP 800-171 Revision 3. According to the NIST page for Revision 3, that revision supersedes Revision 2, and the Revision 2 page shows it was withdrawn on May 14, 2024.

If you also sell into the United States, read each contract for the revision it names. A control set written to one revision does not always line up line for line with the other, and that is a question for your contract, not for this post.

The 17 families in ITSP.10.171

The requirements are grouped into 17 families. Each requirement carries a number in the form 03.01.01, where the middle pair is the family. The families, as the publication lists them, 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
  • Supply chain risk management

The last three are where suppliers who learned an older NIST control set tend to find new work. Planning, acquisition and supply chain risk are about how you run the program and buy from others, not only how you configure a laptop.

Organization defined parameters, the part you fill in

Some requirements contain a blank. ITSP.10.171 calls these organization defined parameters, or ODPs. The publication explains that square brackets in a control statement mark a value the reader has to insert so the control fits their context: how often a review runs, how many failed sign ins trigger a lock, how long a log is kept.

The rule for who fills them in is specific. If a federal department, or a group of departments, does not specify a value for an ODP, the publication says the non government organization must assign the value itself to complete the requirement.

In practice that means two things. Read your contract and its security requirements for any values the department has already set. Then write down your own value for every ODP that is left open, with a short reason, and make sure what actually happens on your systems matches what you wrote. An assessor will compare the two.

How CPCSC uses the standard

The program overview sets out three levels built on these controls. Level 1 requires an annual cyber security self assessment against 13 controls. Level 2 requires external assessments led by an accredited certification body, plus an annual affirmation, and covers 98 controls. Level 3 is assessed by National Defence and covers 130 or more controls.

The 13 Level 1 controls are a small, fixed selection, and the Level 1 criteria page uses the same 03 numbering, so you can find each one in ITSP.10.171 and read the full requirement behind it. Our CPCSC Level 1 checklist walks through those 13, and our CPCSC Level 2 guide covers what is known about the outside assessment.

The additional information page for suppliers describes the standard as baseline security controls and good practice for protecting sensitive information, written with small and medium sized suppliers in mind. It also tells suppliers to review the standard and to contact the program if they already hold a certification under the United States program.

The companion that tells you how it is assessed

A requirement tells you what to do. An assessment procedure tells you how someone checks it. For ITSP.10.171 that second document now exists.

The Cyber Centre has published ITSP.10.171-01, Assessing security requirements for specified information. Its first release is dated April 20, 2026, and it states there are no substantial technical changes between it and NIST SP 800-171A Revision 3, the American assessment guide. The Level 1 criteria page also says it is based on the Canadian version of SP 800-171A.

One small trap. The main ITSP.10.171 page still says a companion based on SP 800-171A will be produced and that SP 800-171A can be used in the interim. Treat that as text that predates the companion. The companion is published, so read it.

If you want to know what evidence a reviewer will look for, ITSP.10.171-01 is the most useful public document you can read today.

How to read ITSP.10.171 without drowning

The publication is long, and most of it is not hard. It is just dense. This is the order we suggest to defense suppliers.

  • Start with scope, not controls. Write down where specified information lives and moves in your company: which systems, which people, which suppliers. Every requirement applies to that boundary, so a wrong boundary makes every later answer wrong.
  • Read the 13 Level 1 requirements in full. Use the Level 1 criteria page to find them, then read each one in ITSP.10.171 itself, including any ODPs inside it.
  • Read one family at a time. For each requirement, mark it as met with proof, met without proof, or not met. The middle group is usually the largest, and it is the cheapest to close.
  • Fill in your ODPs. Use the contract's values where it gives them and your own where it does not, with a reason for each.
  • Open ITSP.10.171-01 beside it. For each requirement you marked as met, check what the assessment procedure would ask to see. If you cannot produce it, the requirement is not really met yet.

The evidence problem underneath it

Here is the pattern our team sees with defense suppliers. The controls are rarely the hard part. Most shops already use multifactor authentication, lock the server room and patch their machines. What they cannot do is show it, dated, in one place, when someone asks.

ITSP.10.171 makes that gap visible, because every requirement is written as something that happens and can be checked. A policy saying you review accounts is a start. The review record with a date and a name on it is what proves the requirement is met.

Where SecuritComply fits

SecuritComply carries the CPCSC control set, with each requirement tied to the evidence behind it, an owner and a review date. The Level 1 controls and the Level 2 controls sit side by side, so the history you build for the self assessment is already in place when an outside assessor asks for it. Certification at Level 2 is issued by a certification body accredited by the Standards Council of Canada. Your compliance data stays in Canada.

Built to save your team time and money: every control is tied to its evidence, so your Level 1 self assessment takes less of your time, and at Level 2 you go into the assessment with your evidence already in order.

To see where you stand against the 13 Level 1 controls, run the free self assessment on our CPCSC Level 1 tool, or book a free CPCSC Level 1 Gap Review with our team on the CPCSC compliance page. If you would rather work through it on paper, the free CPCSC Level 1 Readiness Checklist is on our resources page.

Frequently asked questions

What is ITSP.10.171?

It is a Canadian Centre for Cyber Security publication titled Protecting specified information in non-Government of Canada systems and organizations. It sets out the security requirements organizations outside the federal government use to protect sensitive government information, and it is the foundation of CPCSC controls.

Is ITSP.10.171 the same as NIST SP 800-171?

It is a Canadian version of NIST SP 800-171 Revision 3. The publication says there are no substantial technical changes between the two. It uses the term specified information where the American document says controlled unclassified information.

How many families does ITSP.10.171 have?

Seventeen, from access control to supply chain risk management. Some requirement numbers are marked not allocated, because controls withdrawn in NIST SP 800-171 Revision 3 keep their place in the numbering.

Do I need all of ITSP.10.171 for CPCSC Level 1?

No. Level 1 uses 13 controls drawn from the standard, checked through an annual self assessment. Level 2 covers 98 controls with an outside assessment, and Level 3 covers 130 or more. Your contract names the level that applies.

How will my ITSP.10.171 controls be assessed?

The Cyber Centre published ITSP.10.171-01 in April 2026. It is the Canadian adaptation of NIST SP 800-171A Revision 3 and describes how each requirement is assessed.

References

Ready to get compliant?

SecuritComply makes it simple: 17 frameworks and Canadian data residency.

Start Free →