CPCSC Level 2 Control

Last updated June 25, 2026

03.13.11System and communications protection

CPCSC Level 2 03.13.11: Cryptographic Protection

Apply cryptographic protection to protect system boundaries, communications, cryptography, shared resources, and sessions for CPCSC Level 2 readiness. This guide separates the official ITSP.10.171 control language from practical implementation, evidence, auditor questions, and related controls.

Open Level 2 Guide Browse Level 2 Controls

Formal Control Language

Official ITSP.10.171 wording for 03.13.11. Use the Cyber Centre publication and contract requirements as the source of truth for certification, assessment, or procurement submissions.

  • Implement the following types of cryptography when used to protect the confidentiality of specified information: [Assignment: organization-defined types of cryptography].

Contains information sourced from Government of Canada material used under the Open Government Licence - Canada.

What This Means In Plain English

Cryptographic Protection is part of the CPCSC Level 2 System and communications protection family. This is about protecting how systems communicate: boundaries, encryption, shared resources, collaborative tools, mobile code, and session integrity.

For a founder, CISO, engineer, or compliance owner, the practical question is whether cryptographic protection is visible in real operating evidence: a setting, workflow, ticket, log, approval, review, or exception record that can survive an external assessment.

Level 2 is different from Level 1 because the evidence has to survive an external assessment. A policy statement helps, but the stronger answer is a record that shows who did the work, when it ran, what system setting or workflow enforced it, and how exceptions were handled.

How To Implement It

1

Define the in-scope systems, owners, users, vendors, and data flows affected by cryptographic protection.

2

Document architecture, enforce boundary rules, protect data in transit and storage, manage cryptography, and restrict risky communication paths.

3

Translate the formal requirement into one or two operating procedures: who performs it, how often, where it is recorded, and who approves exceptions.

4

Configure the relevant systems so the control is enforced by identity, endpoint, cloud, network, ticketing, monitoring, vendor, or documentation workflows rather than memory.

5

Keep evidence in a consistent folder, GRC system, ticket queue, or audit workspace so an assessor can trace the control from requirement to implementation to review.

Evidence Normally Gathered

Cryptographic Protection: network architecture diagram.

Cryptographic Protection: firewall or security group rules.

Cryptographic Protection: encryption settings.

Cryptographic Protection: key management records.

Cryptographic Protection: session controls.

Cryptographic Protection: collaboration tool settings.

Cryptographic Protection: owner assignment and review cadence.

Cryptographic Protection: exception, remediation, or POA&M records when the control is not fully implemented.

Common Auditor Questions

Where is cryptographic protection implemented in the in-scope environment?

Who owns cryptographic protection, and how do they know it is operating?

Show the evidence that proves cryptographic protection ran during the assessment period.

What happens when cryptographic protection fails, is bypassed, or has an exception?

How does this control connect to the system security plan, risk register, POA&M, and related CPCSC controls?

Sources

Source and attribution.

Formal control language is sourced from the Canadian Centre for Cyber Security ITSP.10.171 publication. CPCSC Level 2 assessment context references the Government of Canada CPCSC program overview and ITSP.10.171-01 assessment guidance.

CPCSC Program OverviewITSP.10.171ITSP.10.171-01Open Government Licence - Canada