
By Krikor Tengerian · Co-founder, SecuritAI Technologies Ltd. · November 2026 · 10 min read
Your team opens the CPCSC Level 1 self assessment, and the first real question is not about passwords or firewalls. It is whether you know where the specified information is. Nobody in the room is sure what counts.
Most defense suppliers meet the term this way. It appears in a guide or a contract clause as if everyone already knows it, and the two letter short form, SI, shows up a line later. Specified information is the reason the whole program exists, and it decides how much of your company the 13 Level 1 controls apply to. Get the definition wrong and every answer after it is built on a guess.
This post stays with that one term: what it means, where it tends to sit, and how to draw a boundary around it. For the program itself, levels and timelines, start with our CPCSC compliance page.
There are two official definitions, and they agree.
The standard behind the program is ITSP.10.171, published by the Canadian Centre for Cyber Security. Its introduction says specified information includes any information, other than classified, that a Government of Canada authority identifies and qualifies in a contract as requiring safeguarding.
Public Services and Procurement Canada says the same thing in plainer words. Its Level 1 requirements page describes it as sensitive, non-classified government information that must be protected when it is handled, processed or stored by organizations outside the federal government. The page states that the program protects federal specified information on suppliers' networks, systems and applications.
Three things are packed into those sentences.
It is government information. It is not classified. And a government authority names it in your contract.
Most teams treat this as a judgment call they have to make alone. They sit down with a file share and try to decide, document by document, what feels sensitive.
That is the wrong starting point. Both definitions put the decision somewhere else. A Government of Canada authority identifies and qualifies, in the contract, which information requires safeguarding. Your job is to read what the contract says and then follow that information through your company.
The Level 1 scoping guide makes this its first step. Find the contract information that matters for the work, write down what your organization will handle, and use your contract, its security clauses and any handling instructions to confirm what counts.
So the first document to open is the contract, not the file server. If the contract and its security clauses do not make it clear, ask the contracting authority. A written answer from them is worth more than a careful guess from you.
The Level 1 requirements page gives three examples of what specified information may include:
The first one catches people. A drawing or a design file is easy to recognize as sensitive. Contract details are not. A statement of work, a delivery schedule or a pricing annex can sit in an ordinary email thread for months before anyone asks whether it belongs inside the boundary.
If your team has worked on American defense contracts, you know the term controlled unclassified information, or CUI. ITSP.10.171 is a Canadian version of NIST SP 800-171, and it says so. The publication also explains the change of name in its own words: it uses the term "specified information" in place of "controlled unclassified information", the term used in the American document.
The idea is the same. The label, and the rules for who applies it, are Canadian. ITSP.10.171 points to Treasury Board policy for how protected information is categorized and handled, and the PSPC page says the same: how this information is shared and protected is set out by the Treasury Board of Canada Secretariat in its security and privacy policies.
One line in the standard is worth reading if you want a sense of how the government weighs this information. Among its assumptions, ITSP.10.171 states that the confidentiality impact value for specified information is no less than low, which it labels Protected A, and that it will be medium for most large government datasets. Our ITSP.10.171 guide covers the rest of the standard.
The scoping guide asks you to find where the information lives and moves. Its list is longer than most people expect. It asks where the information is received, created, edited, stored, printed, emailed, transferred, backed up, and destroyed or sanitized.
Read that list against a normal week at a small manufacturer. A buyer emails a drawing. An engineer saves it to a laptop. Someone prints it for the shop floor. The nightly backup copies it to a drive in a cabinet. A project manager opens the same email on a phone at home.
That is one file and five places. The guide is direct about several of them:
The guide also closes a door many teams try to use. In its words, you cannot exclude a device just because someone thinks it is "not important." Devices are included or excluded based on whether they can access the information.
Scope is where this definition turns into work. The scoping guide describes two shapes. Your scope may be the whole organization, or it may be a limited workspace, such as one team, that the guide calls a bounded enclave.
ITSP.10.171 explains why the smaller shape is allowed. The requirements apply only to the components of a system that handle, process, store or transmit specified information, or that protect those components. The standard says an organization can limit the scope of the requirements by isolating those components in a separate security domain, using physical separation, logical separation or both.
A smaller boundary means fewer devices, fewer accounts and fewer people to manage under the controls. It is also easier to keep true. There is a limit, though, and the scoping guide names it: if your boundary is so small that you cannot honestly check a requirement, your scope is likely too narrow.
A short order of work, taken from the guide's six steps:
One of the 13 Level 1 controls listed in the CPCSC program overview depends on people more than on technology. Requirement 03.01.22 in ITSP.10.171 asks you to train authorized individuals so that publicly accessible information does not contain specified information, and to review public content periodically and remove any that is found.
PSPC's guidance for that control starts with a plain instruction: make sure staff know what SI looks like. It suggests a checklist question before anything is published, and one person assigned to review external communications.
That only works if the definition has reached the people who write the news release, update the website and post on social media. A scope document that only the IT lead has read does not meet this control.
The term follows the information down the supply chain. PSPC's additional information page for suppliers says that before a contractor permits a subcontractor to access, process, transmit or store specified information, the contractor must determine whether the subcontract requires that access and identify the requirements that apply.
The same page covers the opposite case. Where a subcontractor will not access specified information, the contractor must retain a record supporting that determination. Deciding that a supplier is outside the boundary is allowed. Deciding it without writing down why is the gap. Our post on CPCSC and subcontractors goes further into what primes will ask for.
Here is the pattern our team sees with defense suppliers. Most of them protect the information reasonably well. Very few can show, on one page, where it is.
The scoping guide lists what you should be ready to share when you declare Level 1: a scoping rationale explaining why each asset is in or out, a simple network diagram, a list of in scope assets, a list of out of scope and specialized assets, the facilities and storage points, proof of security tasks, a list of employees who access the information with their roles, and notes on external systems and remote access.
Almost all of that is a written answer to one question. Where is the specified information, and who can reach it? A supplier who has answered it once, in writing, with dates, has done the hardest part of Level 1. A supplier who has not is attesting to 13 controls over a boundary nobody has drawn.
The additional information page adds the reason this cannot be a one time exercise. Suppliers must continue to meet the requirements whenever they access, process, transmit or store specified information under an identified defense contract, and the declaration must be reviewed when a material change affects the systems, assets, personnel, facilities or activities in scope. A new laptop, a new cloud tool or a new subcontractor can each move the boundary.
SecuritComply carries the CPCSC control set, with each requirement tied to the evidence behind it, an owner and a review date. The platform keeps that evidence in one place, so it is ready when a contracting authority or a prime contractor asks. 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 start on paper, the free CPCSC Level 1 Readiness Checklist is on our resources page.
What is specified information?
ITSP.10.171 defines it as any information, other than classified, that a Government of Canada authority identifies and qualifies in a contract as requiring safeguarding. Public Services and Procurement Canada describes it as sensitive, non-classified government information that must be protected when organizations outside the federal government handle, process or store it.
Is specified information the same as CUI?
It plays the same role. ITSP.10.171 is a Canadian version of NIST SP 800-171 and says it uses the term specified information in place of controlled unclassified information, the term in the American document.
Who decides what counts as specified information?
A Government of Canada authority identifies and qualifies it in the contract. The Level 1 scoping guide tells suppliers to use the contract, its security clauses and any handling instructions to confirm what counts.
Is a phone that only reads work email in scope?
It can be. The Level 1 scoping guide says any mobile device is in scope if it can access specified information, even if it is only used for email.
Do I need CPCSC Level 1 before I bid?
According to Public Services and Procurement Canada, the Level 1 self assessment is required at contract award, not during the bidding process, and not all defense contracts will require it.
SecuritComply makes it simple: 17 frameworks and Canadian data residency.
Start Free →