Canadian PBMM (Protected B Medium Medium) with ITSG-33 controls
- version
- 0.1.0
- GitHub stars
- 436
Install
/plugin install pbmm@grc-engineering-suiteRun it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.
Contents
Discovered from sourceSkills 1
PBMM Expert
Deep expertise in Canadian Protected B, Medium Integrity, Medium Availability (PBMM) compliance based on ITSG-33 and CCCS Medium Cloud Security Profile.
Expertise Areas
Framework Overview
PBMM (Protected B, Medium Integrity, Medium Availability):
- Authority: Canadian Centre for Cyber Security (CCCS), Treasury Board Secretariat
- Base Standard: ITSG-33 (based on NIST SP 800-53)
- Assessment: ITSM.50.100 Cloud Security Assessment
- Scope: Government of Canada departments, contractors, critical infrastructure
Purpose: Standardize cloud security for Protected B data across Government of Canada
Canadian Security Classification
| Level | Full Name | Injury if Compromised | Use Cases |
|---|---|---|---|
| U | Unclassified | None | Public websites, published documents |
| PA | Protected A | Limited injury | Internal emails, drafts |
| PB | Protected B | Serious injury | Personal info, health records, financial data |
| PC | Protected C | Grave injury | Law enforcement, sensitive intelligence |
| SECRET | Secret | Exceptionally grave injury | National security |
| TOP SECRET | Top Secret | Catastrophic injury | Highest classification |
PBMM Applicability: Protected B data only
PBMM Control Framework (10 Controls)
PBMM-DATA-1: Canadian Data Residency
Requirement: All Protected B data must be stored, processed, and backed up exclusively in Canadian geographic regions
Approved Canadian Regions:
| Provider | Regions | Location |
|---|---|---|
| AWS | ca-central-1 | Montreal, QC |
| AWS | ca-west-1 | Calgary, AB |
| Azure | canadacentral | Toronto, ON |
| Azure | canadaeast | Quebec City, QC |
| GCP | northamerica-northeast1 | Montreal, QC |
| GCP | northamerica-northeast2 | Toronto, ON |
Prohibited:
- Any non-Canadian region worldwide
- Cross-border replication or backup
- Edge caching outside Canada
- Data processing outside Canada
NIST Mapping: SA-9(5), SC-8
Implementation:
- Service Control Policies to enforce Canadian regions
- Monthly residency verification audits
- Tagging all resources with data classification
PBMM-AC-1: Access Control Policy
Requirement: Establish and maintain formal access control policies aligned with ITSG-33
Key Elements:
- Documented access control policy
- User provisioning and de-provisioning procedures
- Least privilege principle
- Separation of duties
- Account reviews (quarterly)
NIST Mapping: AC-1, AC-2
Cloud Implementation:
- IAM policies with least privilege
- Role-based access control (RBAC)
- Strong password policy (14+ characters, complexity, 90-day rotation)
- Account lockout after 5 failed attempts
PBMM-AC-2: Multi-Factor Authentication
Requirement: Enforce MFA for all users accessing Protected B systems
Acceptable MFA Methods:
- Hardware tokens (FIDO2, YubiKey)
- Authenticator apps (TOTP)
- SMS (minimum acceptable, not recommended)
- Biometric + PIN (for mobile access)
Implementation:
- AWS: IAM MFA, AWS SSO with MFA
- Azure: Azure AD Conditional Access with MFA
- GCP: 2-Step Verification, Context-Aware Access
Enforcement: No MFA = No access
NIST Mapping: IA-2(1), IA-2(2)
PBMM-AU-1: Audit and Accountability
Requirement: Maintain comprehensive audit logs for at least 2 years
Logging Scope:
- All authentication events (success/failure)
- All authorization decisions
- Resource creation, modification, deletion
- Data access (read/write)
- Configuration changes
- Administrative actions
Log Retention: Minimum 2 years
Log Protection:
- Centralized logging
- Log integrity protection (digital signatures, write-once storage)
- Restricted access to logs (security team only)
- Regular log review and analysis
Implementation:
- AWS: CloudTrail with S3 Glacier long-term storage
- Azure: Azure Monitor with Log Analytics 2-year retention
- GCP: Cloud Logging with log sinks to Cloud Storage
NIST Mapping: AU-2, AU-3, AU-6, AU-9
PBMM-SC-1: Encryption at Rest
Requirement: Encrypt all Protected B data at rest using FIPS 140-2 validated encryption
Encryption Standard: FIPS 140-2 Level 2 or higher
Coverage:
- Primary storage (S3, Blob, Cloud Storage)
- Block storage (EBS, Managed Disks, Persistent Disks)
- Databases (RDS, SQL Database, Cloud SQL)
- Backups and snapshots
- Temporary files and caches
Cloud KMS Solutions:
- AWS KMS: FIPS 140-2 Level 2 validated (Certificates #3139, #3195, #3520)
- Azure Key Vault HSM: FIPS 140-2 Level 2 (Certificates #3347, #3653)
- GCP Cloud KMS: FIPS 140-2 Level 3 (Certificates #3666, #4124)
Key Management:
- Customer-managed encryption keys (CMEK) recommended
- Automatic key rotation (annual)
- Key access audit logging
NIST Mapping: SC-28
PBMM-SC-2: Encryption in Transit
Requirement: Encrypt all data transmissions using TLS 1.2+ with FIPS-approved cipher suites
Minimum TLS: TLS 1.2 (TLS 1.3 preferred)
FIPS Cipher Suites:
- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
- TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
Prohibited: SSL, TLS 1.0, TLS 1.1
Implementation:
- HTTPS only for all web services (disable HTTP)
- API endpoints with TLS 1.2+ only
- Database connections encrypted (RDS force_ssl, Azure SQL Encrypted Connection)
- VPN tunnels for site-to-site connections
NIST Mapping: SC-8
PBMM-SC-3: Network Segmentation
Requirement: Implement network segmentation with security groups, firewalls, and network access controls
Segmentation Strategy:
- Dedicated VPC/VNet for Protected B workloads
- Subnet isolation (web tier, app tier, data tier)
- Security groups with least privilege
- Network ACLs for subnet-level filtering
- No direct internet access to database tier
Implementation:
- AWS: VPC with private subnets, Security Groups, NACLs, PrivateLink
- Azure: Virtual Network with NSGs, Application Security Groups, Private Endpoints
- GCP: VPC with Firewall Rules, VPC Service Controls
Best Practices:
- Default deny, explicit allow
- Micro-segmentation for critical workloads
- Separate management and production networks
NIST Mapping: SC-7
PBMM-RA-1: Vulnerability Management
Requirement: Scan for vulnerabilities and remediate within defined timeframes
Remediation Timeframes:
| Severity | Remediation Deadline | Action |
|---|---|---|
| Critical | 48 hours | Emergency patching |
| High | 7 days | Scheduled patching |
| Medium | 30 days | Regular patch cycle |
| Low | 90 days | Next maintenance window |
Scanning Frequency:
- Continuous automated scanning
- Weekly vulnerability reports
- Monthly compliance reporting
Tools:
- AWS: Amazon Inspector, AWS Security Hub
- Azure: Microsoft Defender for Cloud, Qualys
- GCP: Security Command Center, Cloud Asset Inventory
NIST Mapping: RA-5
PBMM-IR-1: Incident Response
Requirement: Establish incident response procedures and notify CCCS of security incidents
Incident Response Plan must include:
- Incident classification (severity levels)
- Response procedures by incident type
- Contact information (internal and CCCS)
- Evidence collection and preservation
- Communication plan
- Post-incident review process
CCCS Notification:
- Timeline: Within 24 hours of confirmed incident
- Contact: contact@cyber.gc.ca or 1-833-CYBER-88
- Information: Incident type, affected systems, data types, impact assessment
Incident Severity:
- Critical: Data breach, system compromise, service disruption
- High: Attempted breach, malware detection, policy violation
- Medium: Suspicious activity, anomaly detection
- Low: False positives, minor policy violations
NIST Mapping: IR-1, IR-4, IR-6
PBMM-CP-1: Backup and Recovery
Requirement: Implement automated backups with Canadian region storage and tested recovery procedures
Backup Requirements:
- Automated daily backups minimum
- Backup storage in Canadian regions only (ca-central-1, canadacentral)
- Encrypted backups (FIPS 140-2)
- Backup retention: 30 days minimum, 1 year for compliance
- Off-site backups (different Canadian region)
Recovery Testing:
- Quarterly recovery drills
- Documented recovery procedures
- Recovery Time Objective (RTO): < 24 hours
- Recovery Point Objective (RPO): < 24 hours
Implementation:
- AWS: AWS Backup with cross-region copy (ca-central-1 ↔ ca-west-1)
- Azure: Azure Backup with geo-redundant storage (canadacentral ↔ canadaeast)
- GCP: Backup and DR Service with Canadian region snapshots
NIST Mapping: CP-9
CCCS Assessment Process
Assessment Type: ITSM.50.100 Cloud Security Assessment
Timeline:
- Pre-assessment: 1-2 months (documentation, internal audit)
- Application: 1 month (CCCS review)
- Assessment: 2-4 months (testing, validation)
- Remediation: 1-3 months (if gaps found)
- Certification: 1 month (ATO issuance)
- Total: 6-12 months
Required Documentation:
- System Security Plan (SSP)
- Privacy Impact Assessment (PIA)
- Security Assessment Report (SAR)
- Plan of Action and Milestones (POA&M)
- Incident Response Plan
- Contingency Plan
Certification Validity: 2 years (re-assessment required)
Certified Cloud Providers
| Provider | Status | Regions | Assessment Standard |
|---|---|---|---|
| AWS Canada | ✅ ITSM.50.100 Assessed | ca-central-1, ca-west-1 | PBMM compliant |
| Azure Canada | ✅ PBMM Assessed | canadacentral, canadaeast | PBMM compliant |
| GCP Canada | ⚠️ In Progress | northamerica-northeast1/2 | Verify status |
Implementation Challenges
-
Canadian Data Residency
- Challenge: Accidental deployment to non-Canadian regions
- Solution: Service Control Policies, organizational policies, resource tagging
-
2-Year Log Retention
- Challenge: Cost of long-term log storage
- Solution: Lifecycle policies to transition to cheaper storage (Glacier, Cool Blob)
-
48-Hour Critical Patching
- Challenge: Emergency patch deployment without disruption
- Solution: Blue-green deployments, automated patching windows, runbook automation
-
MFA Enforcement
- Challenge: Legacy systems and service accounts
- Solution: Identity federation, break-glass procedures for emergencies
-
CCCS Assessment Preparation
- Challenge: Documentation completeness and evidence collection
- Solution: Continuous compliance monitoring, automated evidence collection
Cost Considerations
PBMM Compliance Costs (Annual):
- CCCS Assessment: $100K - $250K (initial), $75K - $150K (re-assessment)
- Canadian Region Premium: +10-20% over US regions
- Long-term Log Storage: $5K - $50K (depends on volume)
- Vulnerability Scanning: $10K - $50K
- Consulting/Staff: $150K - $500K (FTE for compliance)
- Total First Year: $300K - $1M
- Annual Maintenance: $150K - $400K
Resources
CCCS:
- Website: https://cyber.gc.ca
- Email: contact@cyber.gc.ca
- Phone: 1-833-CYBER-88 (1-833-292-3788)
- Incident Reporting: contact@cyber.gc.ca (24-hour notification)
Key Publications:
- ITSG-33: IT Security Risk Management guidance (based on NIST 800-53)
- ITSP.50.103: Cloud Security Categorization
- ITSM.50.100: Cloud Security Assessment methodology
- Medium Cloud Security Profile: PBMM baseline controls
Treasury Board Secretariat:
- Cloud Adoption Strategy
- Directive on Security Management
- Policy on Government Security
Capabilities
- ITSG-33 control assessment and mapping to NIST SP 800-53
- Canadian data residency verification across AWS, Azure, and GCP
- CCCS assessment preparation and documentation (SSP, PIA, SAR, POA&M)
- Protected B vs Protected C vs Secret classification determination
- FIPS 140-2 encryption configuration for Canadian cloud regions
- 2-year audit log retention implementation and cost optimization
- 48-hour critical vulnerability remediation workflows
- Multi-factor authentication enforcement strategies
- CCCS incident notification procedures (24-hour timeline)
- Automated backup and recovery in Canadian regions
- Service Control Policy creation for Canadian region enforcement
- Continuous monitoring and compliance evidence collection
- PBMM vs NIST vs ISO 27001 control crosswalk
- Provincial privacy law compliance (PIPEDA, PHIPA, HIPA, PHI Act)
- Government of Canada contract security requirements interpretation
Commands 4
PBMM Assessment
Evaluates readiness for Canadian Protected B, Medium Integrity, Medium Availability (PBMM) compliance based on ITSG-33 and the CCCS Medium Cloud Security Profile.
Arguments
$1- Classification level (optional: protected-a, protected-b, protected-c) - defaults to "protected-b"$2- Assessment type (optional: readiness, gap-analysis, certification) - defaults to "readiness"
Classification Levels
| Level | Sensitivity | Injury if Compromised | Controls Required |
|---|---|---|---|
| Unclassified | Public information | None | Basic hygiene |
| Protected A | Low sensitivity | Limited injury | Basic ITSG-33 |
| Protected B | Sensitive | Serious injury | Full PBMM profile (10 controls) |
| Protected C | Extremely sensitive | Grave injury | Enhanced beyond PBMM |
PBMM Control Assessment (10 Controls)
PBMM-DATA-1: Canadian Data Residency
Requirement: All Protected B data must reside exclusively in Canadian geographic regions.
Approved Regions:
- AWS: ca-central-1 (Montreal), ca-west-1 (Calgary)
- Azure: canadacentral (Toronto), canadaeast (Quebec City)
- GCP: northamerica-northeast1 (Montreal), northamerica-northeast2 (Toronto)
Assessment Questions:
- Are all resources deployed in Canadian regions only?
- Is cross-border data transfer disabled?
- Are backups stored in Canadian regions?
PBMM-AC-1: Access Control Policy
Requirement: Establish and maintain access control policies aligned with ITSG-33.
NIST Mapping: AC-1, AC-2
Assessment Questions:
- Is a formal access control policy documented?
- Are all users authorized and documented?
- Is password policy enforced (complexity, rotation)?
PBMM-AC-2: Multi-Factor Authentication
Requirement: Enforce MFA for all users accessing Protected B systems.
NIST Mapping: IA-2(1), IA-2(2)
Assessment Questions:
- Is MFA required for all users?
- Are hardware tokens or authenticator apps used?
- Is MFA enforced at cloud provider level?
PBMM-AU-1: Audit and Accountability
Requirement: Maintain comprehensive audit logs for at least 2 years.
NIST Mapping: AU-2, AU-3, AU-6, AU-9
Assessment Questions:
- Is logging enabled for all services?
- Are logs stored for 2+ years?
- Is log integrity protection enabled?
- Are logs reviewed regularly?
PBMM-SC-1: Encryption at Rest
Requirement: Encrypt all Protected B data at rest using FIPS 140-2 validated encryption.
NIST Mapping: SC-28
Assessment Questions:
- Are all storage resources encrypted?
- Is FIPS 140-2 Level 2+ encryption used?
- Are customer-managed encryption keys configured?
PBMM-SC-2: Encryption in Transit
Requirement: Encrypt all data transmissions using TLS 1.2+ with FIPS-approved cipher suites.
NIST Mapping: SC-8
Assessment Questions:
- Is TLS 1.2+ enforced for all connections?
- Are FIPS cipher suites configured?
- Is HTTP disabled (HTTPS only)?
PBMM-SC-3: Network Segmentation
Requirement: Implement network segmentation with security groups and firewalls.
NIST Mapping: SC-7
Assessment Questions:
- Are VPCs/VNets isolated for Protected B workloads?
- Are security groups configured with least privilege?
- Is network traffic logged and monitored?
PBMM-RA-1: Vulnerability Management
Requirement: Scan for vulnerabilities and remediate within defined timeframes.
NIST Mapping: RA-5
Remediation Timeframes:
- Critical vulnerabilities: 48 hours
- High vulnerabilities: 7 days
- Medium vulnerabilities: 30 days
Assessment Questions:
- Is vulnerability scanning automated?
- Are remediation timeframes met?
- Is patch management process documented?
PBMM-IR-1: Incident Response
Requirement: Establish incident response procedures and contact CCCS for incidents.
NIST Mapping: IR-1, IR-4, IR-6
Assessment Questions:
- Is incident response plan documented?
- Are incident response roles assigned?
- Is CCCS notification process established?
- Are incidents logged and tracked?
PBMM-CP-1: Backup and Recovery
Requirement: Implement automated backups with Canadian region storage.
NIST Mapping: CP-9
Assessment Questions:
- Are automated backups configured?
- Are backups tested regularly?
- Are backups stored in Canadian regions only?
- Is recovery time objective (RTO) documented?
CCCS Assessment Process
Self-Assessment (Readiness)
Organizations prepare for CCCS assessment by:
- Implementing all 10 PBMM controls
- Documenting policies and procedures
- Conducting internal audits
- Remediating gaps
CCCS Certification Assessment
Process:
- Submit application to CCCS
- CCCS reviews documentation
- On-site assessment (if applicable)
- Corrective action period for gaps
- Certification issuance
Timeline: 6-12 months Validity: 2 years (re-assessment required)
Cloud Provider Certifications
| Provider | PBMM Status | Canadian Regions | Notes |
|---|---|---|---|
| AWS | ✅ Certified | ca-central-1, ca-west-1 | ITSM.50.100 assessed |
| Azure | ✅ Certified | canadacentral, canadaeast | PBMM compliant |
| GCP | ⚠️ In Progress | northamerica-northeast1/2 | Check current status |
Compliance Output
Assessment Report Includes:
- Overall readiness score (0-100%)
- Control-by-control compliance status
- Gap analysis with remediation priorities
- Estimated timeline to certification
- Cost estimate for remediation
Examples
# Protected B readiness assessment
/pbmm:assess protected-b readiness
# Gap analysis for certification
/pbmm:assess protected-b gap-analysis
# Protected A assessment
/pbmm:assess protected-a readiness
Key Requirements Summary
- Canadian Data Residency: Mandatory for Protected B
- 2-Year Log Retention: Minimum requirement
- 48-Hour Critical Patching: For critical vulnerabilities
- FIPS 140-2 Encryption: Level 2+ for at rest/in transit
- CCCS Notification: Required for security incidents
CCCS Assessment Guidance
Guidance on the Canadian Centre for Cyber Security (CCCS) cloud security assessment process and certified cloud service providers.
Arguments
$1- Topic (optional: process, providers, requirements) - defaults to "process"
CCCS Assessment Process
ITSM.50.100 Cloud Security Assessment
The CCCS assesses cloud service providers against the ITSP.50.103 Cloud Security Categorization framework.
Assessment Tiers:
- Tier 1: Self-assessment by CSP
- Tier 2: Independent third-party assessment
- Tier 3: CCCS assessment (for Protected B and above)
Protected B Assessment Steps
1. Pre-Assessment (1-2 months)
Organization Activities:
- Review ITSG-33 security controls
- Implement PBMM controls (10 required controls)
- Document security policies and procedures
- Prepare System Security Plan (SSP)
- Conduct internal audit
Required Documentation:
- System Security Plan (SSP)
- Privacy Impact Assessment (PIA)
- Security Assessment Report (SAR)
- Plan of Action and Milestones (POA&M)
- Incident Response Plan
- Contingency Plan
2. Application Submission (1 month)
Submission to CCCS:
- Complete assessment application
- Submit documentation package
- Provide cloud service description
- Identify Canadian regions used
- Demonstrate data residency controls
CCCS Review:
- Documentation completeness check
- Initial risk assessment
- Assessment schedule determination
3. Assessment Execution (2-4 months)
Assessment Activities:
- Document review and analysis
- Configuration review of cloud environment
- Security control testing (10 PBMM controls)
- Vulnerability assessment
- Penetration testing (if required)
- Interviews with personnel
Evidence Requirements:
- Configuration screenshots
- Log samples (2-year retention proof)
- Encryption validation (FIPS 140-2)
- Data residency verification
- Access control demonstrations
- Incident response procedures
4. Remediation (1-3 months)
For Identified Gaps:
- CCCS provides findings report
- Organization develops remediation plan
- Implement corrective actions
- Re-assessment of remediated controls
POA&M:
- Document residual risks
- Establish remediation timelines
- Assign responsible parties
- Track to completion
5. Certification (1 month)
CCCS Deliverables:
- Security Assessment Report (SAR)
- Authorization to Operate (ATO)
- Continuous monitoring requirements
- Re-assessment schedule
Validity Period: 2 years (re-assessment required)
Assessment Costs
| Item | Estimated Cost (CAD) | Notes |
|---|---|---|
| Pre-assessment consulting | $50,000 - $150,000 | Gap analysis, SSP development |
| Third-party assessment | $100,000 - $250,000 | CCCS Tier 2 assessment |
| Remediation | $50,000 - $200,000 | Depends on gaps |
| CCCS assessment fee | Varies | For Tier 3 assessments |
| Annual maintenance | $25,000 - $75,000 | Continuous monitoring |
| Re-assessment (2 years) | $75,000 - $150,000 | Reduced scope |
Certified Cloud Service Providers
AWS Canada
Certification Status: ✅ ITSM.50.100 Assessed
Canadian Regions:
- ca-central-1 (Montreal, Quebec)
- ca-west-1 (Calgary, Alberta)
Services Assessed:
- EC2, S3, RDS, Lambda
- CloudTrail, CloudWatch
- KMS, IAM, VPC
PBMM Features:
- FIPS 140-2 Level 2 encryption (AWS KMS)
- Canadian data residency enforcement
- MFA support (IAM, Cognito)
- 2-year+ log retention (CloudWatch, S3)
- Network isolation (VPC)
Contact: AWS Canada Public Sector team
Microsoft Azure Canada
Certification Status: ✅ PBMM Assessed
Canadian Regions:
- canadacentral (Toronto, Ontario)
- canadaeast (Quebec City, Quebec)
Services Assessed:
- Virtual Machines, Storage, SQL Database
- Azure Monitor, Log Analytics
- Key Vault, Active Directory
PBMM Features:
- FIPS 140-2 Level 2 encryption (Key Vault HSM)
- Canadian data residency controls
- Azure AD MFA
- 2-year log retention (Monitor, Storage)
- Network Security Groups, Application Security Groups
Contact: Microsoft Canada Public Sector
Google Cloud Platform Canada
Certification Status: ⚠️ Assessment In Progress (verify current status)
Canadian Regions:
- northamerica-northeast1 (Montreal, Quebec)
- northamerica-northeast2 (Toronto, Ontario)
Services:
- Compute Engine, Cloud Storage, Cloud SQL
- Cloud Logging, Cloud Monitoring
- Cloud KMS, Identity and Access Management
PBMM Features:
- FIPS 140-2 Level 3 encryption (Cloud KMS)
- Data residency controls
- IAM with MFA
- Log retention configuration
- VPC Service Controls
Contact: Google Cloud Canada team
Note: Verify current CCCS certification status before use
Protected B Control Requirements
Mandatory Controls (Medium Cloud Security Profile)
| Control ID | Control Name | CCCS Requirement |
|---|---|---|
| PBMM-DATA-1 | Canadian Data Residency | All data in CA regions only |
| PBMM-AC-1 | Access Control Policy | Documented, enforced |
| PBMM-AC-2 | Multi-Factor Authentication | Mandatory for all users |
| PBMM-AU-1 | Audit and Accountability | 2-year log retention |
| PBMM-SC-1 | Encryption at Rest | FIPS 140-2 Level 2+ |
| PBMM-SC-2 | Encryption in Transit | TLS 1.2+ with FIPS |
| PBMM-SC-3 | Network Segmentation | VPC/VNet isolation |
| PBMM-RA-1 | Vulnerability Management | 48-hour critical patching |
| PBMM-IR-1 | Incident Response | CCCS notification process |
| PBMM-CP-1 | Backup and Recovery | Canadian region backups |
Continuous Monitoring Requirements
Post-Authorization
Monthly Reporting:
- Security control status
- Vulnerability scan results
- Incident summary
- Configuration changes
Quarterly Reviews:
- Access control verification
- Log analysis and anomaly detection
- Policy and procedure updates
Annual Activities:
- Full control re-testing
- Updated System Security Plan
- Privacy Impact Assessment review
- Third-party penetration testing
Incident Reporting:
- Report security incidents to CCCS within 24 hours
- Provide incident details and impact assessment
- Submit remediation plan
CCCS Resources
Key Publications
ITSG-33: IT Security Risk Management - A Lifecycle Approach
- Based on NIST SP 800-53
- Canadian government standard
- Control catalogue and implementation guidance
ITSP.50.103: Cloud Security Categorization
- Risk-based approach to cloud classification
- Categorization tool available online
- Maps to PBMM requirements
ITSM.50.100: Cloud Security Assessment
- CSP assessment methodology
- Assessment tiers and criteria
- Certification process
Medium Cloud Security Profile:
- Control baseline for Protected B
- 10 mandatory controls (PBMM)
- Implementation guidance
Contact Information
Canadian Centre for Cyber Security (CCCS):
- Website: https://cyber.gc.ca
- Email: contact@cyber.gc.ca
- Phone: 1-833-CYBER-88 (1-833-292-3788)
Cloud Assessment Inquiries:
Incident Reporting:
- Email: contact@cyber.gc.ca
- Phone: 1-833-CYBER-88
- Report within 24 hours for Protected B incidents
Examples
# View assessment process
/pbmm:cccs-guidance process
# Check certified providers
/pbmm:cccs-guidance providers
# Review certification requirements
/pbmm:cccs-guidance requirements
Frequently Asked Questions
Q: How long does CCCS assessment take? A: 6-12 months total (pre-assessment through certification)
Q: Can I use US cloud regions for Protected B? A: No, Canadian regions mandatory for Protected B
Q: Is CCCS assessment required for all Protected B systems? A: Strongly recommended, may be required by contract or regulation
Q: How often is re-assessment required? A: Every 2 years for Protected B
Q: What if my cloud provider is not CCCS-certified? A: You can pursue your own CCCS assessment or use certified providers
Q: Are there alternatives to CCCS assessment? A: For non-government, use CCCS-assessed CSPs or conduct independent third-party assessment aligned with ITSG-33
Canadian Data Residency Verification
Verifies that all Protected B data resides exclusively in Canadian geographic regions as required by PBMM and Government of Canada policies.
Arguments
$1- Cloud provider (optional: aws, azure, gcp, all) - defaults to "all"$2- Verification mode (optional: check, remediate) - defaults to "check"
Canadian Data Residency Requirement
Policy: All Protected B data must be stored, processed, and backed up exclusively within Canadian geographic boundaries.
Authority:
- ITSG-33 security controls
- Treasury Board Secretariat cloud adoption strategy
- PBMM-DATA-1 control requirement
- Privacy Act (Canada)
- Provincial privacy legislation
Approved Canadian Regions
AWS Canada
Primary Regions:
- ca-central-1: Canada (Montreal), Quebec
- ca-west-1: Canada West (Calgary), Alberta
Services Verified:
- Compute: EC2, Lambda, ECS, EKS
- Storage: S3, EBS, EFS
- Databases: RDS, DynamoDB, Aurora
- Networking: VPC, CloudFront (with restrictions)
Prohibited Regions: All non-Canadian regions
Edge Services:
- CloudFront: Must use only Canadian edge locations (configure distribution restrictions)
- Route 53: Canadian regions for hosted zones
Azure Canada
Primary Regions:
- canadacentral: Canada Central (Toronto), Ontario
- canadaeast: Canada East (Quebec City), Quebec
Services Verified:
- Compute: Virtual Machines, App Service, AKS
- Storage: Blob Storage, File Storage, Managed Disks
- Databases: SQL Database, Cosmos DB, PostgreSQL
- Networking: Virtual Networks, Application Gateway
Prohibited Regions: All non-Canadian regions
Global Services:
- Azure AD: Tenant data must be in Canadian data centers
- Traffic Manager: Configure Canadian endpoints only
Google Cloud Platform Canada
Primary Regions:
- northamerica-northeast1: Montreal, Quebec
- northamerica-northeast2: Toronto, Ontario
Services Verified:
- Compute: Compute Engine, Cloud Run, GKE
- Storage: Cloud Storage, Persistent Disks
- Databases: Cloud SQL, Firestore, Spanner
- Networking: VPC, Cloud Load Balancing
Prohibited Regions: All non-Canadian regions
Global Services:
- Cloud CDN: Configure Canadian-only cache locations
Verification Commands
AWS Verification
S3 Bucket Locations:
# List all buckets with locations
for bucket in $(aws s3api list-buckets --query 'Buckets[*].Name' --output text); do
location=$(aws s3api get-bucket-location --bucket "$bucket" --query 'LocationConstraint' --output text)
if [[ "$location" == "ca-central-1" ]] || [[ "$location" == "ca-west-1" ]] || [[ "$location" == "null" && "$AWS_DEFAULT_REGION" =~ ^ca- ]]; then
echo "PASS: $bucket -> $location"
else
echo "FAIL: $bucket -> $location (NOT Canadian)"
fi
done
EC2 Instance Locations:
# Check all EC2 instances
aws ec2 describe-instances \
--query 'Reservations[*].Instances[*].{Id:InstanceId,AZ:Placement.AvailabilityZone,State:State.Name}' \
--output table
# Verify only Canadian availability zones (ca-central-1*, ca-west-1*)
RDS Database Locations:
# Check all RDS instances
aws rds describe-db-instances \
--query 'DBInstances[*].{Id:DBInstanceIdentifier,AZ:AvailabilityZone,MultiAZ:MultiAZ}' \
--output table
# Ensure all in ca-central-1 or ca-west-1
EBS Snapshots:
# Check snapshot locations (must be in Canadian regions)
aws ec2 describe-snapshots --owner-ids self \
--query 'Snapshots[*].{SnapshotId:SnapshotId,VolumeId:VolumeId}' \
--output table
Azure Verification
All Resources:
# List all resources with locations
az resource list \
--query '[].{Name:name,Location:location,Type:type}' \
--output table
# Filter non-Canadian resources
az resource list \
--query "[?location!='canadacentral' && location!='canadaeast'].{Name:name,Location:location,Type:type}" \
--output table
Storage Accounts:
# Check storage account locations
az storage account list \
--query '[].{Name:name,Location:location,Kind:kind}' \
--output table
# Should only show: canadacentral or canadaeast
Virtual Machines:
# Check VM locations
az vm list \
--query '[].{Name:name,Location:location,ResourceGroup:resourceGroup}' \
--output table
GCP Verification
Cloud Storage Buckets:
# List all buckets with locations
gcloud storage buckets list --format='table(name,location,locationType)'
# Verify: northamerica-northeast1 or northamerica-northeast2
Compute Instances:
# List all instances with zones
gcloud compute instances list \
--format='table(name,zone,status)'
# Verify zones: northamerica-northeast1-* or northamerica-northeast2-*
Cloud SQL Instances:
# Check database locations
gcloud sql instances list \
--format='table(name,region,databaseVersion)'
# Verify regions: northamerica-northeast1 or northamerica-northeast2
Common Violations and Remediation
Violation 1: Non-Canadian S3 Buckets
Finding: S3 bucket in us-east-1
FAIL: my-bucket -> us-east-1 (NOT Canadian)
Remediation:
- Create new bucket in ca-central-1
- Use S3 replication or copy objects
- Update application to use new bucket
- Delete original bucket after migration
- Update DNS/CDN configuration
# Create Canadian bucket
aws s3 mb s3://my-bucket-ca --region ca-central-1
# Copy data
aws s3 sync s3://my-bucket s3://my-bucket-ca --region ca-central-1
# Update application configuration
# Delete old bucket after verification
Violation 2: EC2 Instance in US Region
Finding: EC2 instance in us-west-2
Instance i-1234567890 in us-west-2a
Remediation:
- Create AMI snapshot
- Copy AMI to ca-central-1
- Launch new instance in Canadian region
- Migrate data and traffic
- Terminate US instance
# Create AMI
ami_id=$(aws ec2 create-image --instance-id i-1234567890 --name "Migration-AMI")
# Copy to Canadian region
aws ec2 copy-image \
--source-region us-west-2 \
--source-image-id $ami_id \
--region ca-central-1 \
--name "Canadian-AMI"
# Launch in ca-central-1
aws ec2 run-instances \
--image-id $canadian_ami_id \
--instance-type t3.medium \
--region ca-central-1 \
--subnet-id subnet-canadian-vpc
Violation 3: Azure Resource in US Region
Finding: Storage account in eastus
my-storage | eastus | StorageV2
Remediation:
- Create new storage account in canadacentral
- Use AzCopy to migrate data
- Update application connection strings
- Delete US storage account
# Create Canadian storage account
az storage account create \
--name mystoragecanada \
--location canadacentral \
--resource-group myResourceGroup
# Migrate data with AzCopy
azcopy sync \
"https://mystorage.blob.core.windows.net" \
"https://mystoragecanada.blob.core.windows.net"
Cross-Border Data Transfer Restrictions
Prohibited Activities:
- Replication to non-Canadian regions
- Backup storage outside Canada
- Content delivery network (CDN) caching outside Canada
- Database read replicas in non-Canadian regions
- Disaster recovery sites outside Canada
Permitted with Controls:
- Encrypted transient network traffic through non-Canadian networks (TLS 1.2+)
- Management traffic to cloud provider control planes (encrypted)
- Monitoring and logging data (if encrypted and contractually protected)
Compliance Verification Matrix
| Resource Type | Location Check | Backup Check | Replication Check |
|---|---|---|---|
| S3/Blob Storage | ✅ ca-central-1, canadacentral | ✅ Canadian regions only | ❌ No cross-border replication |
| EC2/VMs | ✅ ca-* / canadacentral/east | ✅ Snapshots in CA | ❌ No cross-region AMIs |
| RDS/SQL | ✅ Canadian AZs | ✅ Automated backups in CA | ❌ No read replicas outside CA |
| Load Balancers | ✅ Canadian regions | N/A | ✅ Multi-AZ within CA OK |
| CDN | ⚠️ Canadian edge only | N/A | ❌ No global distribution |
Automated Enforcement
AWS Service Control Policy (SCP)
Prevent non-Canadian region usage:
{
"Version": "2012-10-17",
"Statement": [{
"Effect": "Deny",
"Action": "*",
"Resource": "*",
"Condition": {
"StringNotEquals": {
"aws:RequestedRegion": [
"ca-central-1",
"ca-west-1"
]
}
}
}]
}
Azure Policy
Restrict resource deployment to Canadian regions:
{
"properties": {
"policyRule": {
"if": {
"not": {
"field": "location",
"in": ["canadacentral", "canadaeast"]
}
},
"then": {
"effect": "deny"
}
}
}
}
GCP Organization Policy
Restrict resource locations:
name: organizations/ORGANIZATION_ID/policies/gcp.resourceLocations
spec:
rules:
- values:
allowedValues:
- in:northamerica-northeast1-locations
- in:northamerica-northeast2-locations
Examples
# Verify all cloud providers
/pbmm:data-residency all check
# Check AWS only
/pbmm:data-residency aws check
# Remediation mode for Azure
/pbmm:data-residency azure remediate
# GCP verification
/pbmm:data-residency gcp check
Audit Evidence
For CCCS assessment, maintain:
- Monthly residency verification reports
- Configuration screenshots showing Canadian regions
- Service Control Policies or equivalent
- Incident logs (if violations occurred)
- Remediation documentation
Key Requirements
- 100% Canadian Storage: All data at rest in Canadian regions
- No Cross-Border Replication: Backups and replicas in Canada only
- CDN Restrictions: Canadian edge locations only for content delivery
- Encrypted Transit OK: Transient traffic through non-CA networks if encrypted
- Continuous Verification: Monthly residency checks required
Classification Level Selection
Helps determine the appropriate Canadian Government security classification level and corresponding control profile.
Arguments
$1- Data type description (optional)
Classification Levels
| Level | Full Name | Sensitivity | Injury if Compromised | Example Data Types |
|---|---|---|---|---|
| U | Unclassified | No sensitivity | None | Public websites, published reports |
| PA | Protected A | Low | Limited injury | Internal emails, draft documents |
| PB | Protected B | Medium | Serious injury | Personal information, health records, financial data |
| PC | Protected C | High | Grave injury | Law enforcement investigations, sensitive intelligence |
PBMM Profile (Protected B)
The PBMM (Protected B, Medium Integrity, Medium Availability) profile applies when:
Data Characteristics:
- Contains personal information (PI) under privacy laws
- Health records subject to provincial privacy acts
- Financial information
- Commercial information that could cause serious injury if disclosed
- Government operational information
Integrity Requirements: Medium
- Data accuracy is important
- Unauthorized modification would cause serious consequences
- Error detection and correction required
Availability Requirements: Medium
- Service disruptions cause serious inconvenience or financial loss
- Recovery time objective (RTO): Hours to 1 day
- Recovery point objective (RPO): Hours
Selection Decision Tree
Question 1: Is the data publicly available or intended for public release?
├─ YES → Unclassified (U)
└─ NO → Continue to Question 2
Question 2: Would unauthorized disclosure cause injury?
├─ Limited injury (minor embarrassment, inconvenience) → Protected A (PA)
├─ Serious injury (financial loss, reputation damage) → Protected B (PB)
├─ Grave injury (life safety, national security) → Protected C (PC)
└─ No injury → Unclassified (U)
Question 3: Are there specific regulatory requirements?
├─ Personal Information Protection laws → Protected B minimum
├─ Provincial health privacy acts → Protected B minimum
├─ Financial sector regulations → Protected B minimum
└─ Law enforcement / intelligence → Protected C likely
Control Profiles by Classification
| Control Area | Unclassified | Protected A | Protected B (PBMM) | Protected C |
|---|---|---|---|---|
| Canadian Residency | No | Recommended | Mandatory | Mandatory |
| Encryption at Rest | No | Recommended | FIPS 140-2 | FIPS 140-2 Level 3 |
| Encryption in Transit | TLS 1.2+ | TLS 1.2+ | TLS 1.2+ FIPS | TLS 1.2+ FIPS |
| MFA | No | Recommended | Mandatory | Mandatory (hardware) |
| Audit Retention | 1 year | 2 years | 2 years | 7 years |
| Vulnerability Remediation | 30 days | 14 days (high) | 48 hours (critical) | 24 hours (critical) |
| Network Segmentation | Basic | Recommended | Mandatory | Dedicated infrastructure |
| Incident Response | Basic | Documented | CCCS notification | CCCS immediate notification |
| CCCS Assessment | No | No | Required | Required |
Specific Use Cases
Healthcare Data
Provincial Health Information:
- Classification: Protected B
- Regulations: PHIPA (ON), HIPA (SK), PHI Act (BC)
- Controls: Full PBMM profile
- Regions: Canadian only
Personal Information
Under Privacy Acts (PIPEDA, provincial acts):
- Classification: Protected B
- Controls: Full PBMM profile
- Consent and access controls required
- Breach notification procedures
Government Contracts
Contract Data for Government of Canada:
- Classification: As specified in contract (often Protected B)
- Controls: PBMM or as contractually required
- Security requirements schedules apply
Financial Services
Customer Financial Data:
- Classification: Protected B
- Regulations: OSFI, provincial regulators
- Controls: PBMM + sector-specific requirements
Critical Infrastructure
Operational Technology Data:
- Classification: Protected B or C (depending on criticality)
- Regulations: Cyber security requirements per sector
- Additional controls may be required
Cloud Service Provider Selection
Protected B Requirements
Mandatory Features:
- Canadian regions (data residency)
- FIPS 140-2 Level 2+ encryption
- CCCS-assessed cloud service (preferred)
- MFA support
- Comprehensive logging
Certified Providers:
- AWS (ca-central-1, ca-west-1) - ITSM.50.100 assessed
- Azure (canadacentral, canadaeast) - PBMM assessed
- GCP (northamerica-northeast1/2) - Check certification status
Protected C Requirements
Enhanced Features:
- Dedicated infrastructure (no multi-tenancy)
- Hardware-based MFA
- Enhanced monitoring and alerting
- CCCS TOP SECRET assessment (for TOP SECRET data)
Cost Implications
| Classification | Incremental Cost | Drivers |
|---|---|---|
| Unclassified | Baseline | Standard cloud services |
| Protected A | +10-20% | Basic security controls, MFA |
| Protected B | +30-50% | CCCS assessment, enhanced controls, Canadian regions |
| Protected C | +100-200% | Dedicated infrastructure, advanced controls |
Examples
# Determine classification for health data
/pbmm:profile-select "Provincial health information (patient records)"
# Financial services data
/pbmm:profile-select "Customer financial transactions and account data"
# Government operational data
/pbmm:profile-select "Internal government operational information"
Compliance Recommendation
If Protected A:
- Consider Protected B controls as best practice
- Canadian regions recommended but not mandatory
- Basic ITSG-33 controls
If Protected B (PBMM):
- Use
/pbmm:assessfor detailed readiness assessment - Canadian regions mandatory (ca-central-1, canadacentral)
- Full PBMM profile (10 controls)
- CCCS assessment required
If Protected C:
- Enhanced controls beyond standard PBMM
- Consult CCCS for specific requirements
- Dedicated infrastructure may be required
- Consider Secret or TOP SECRET assessment
Resources
- CCCS: https://cyber.gc.ca
- ITSG-33: IT Security Risk Management guidance
- ITSP.50.103: Cloud Security Categorization
- ITSM.50.100: Cloud Security Assessment process
- Security Categorization Tool: https://www.canada.ca/en/government/system/digital-government/digital-government-innovations/cloud-services/categorization.html
Sponsors
Details
- Marketplace
- GRCEngClub/claude-grc-engineering
- Source
- plugins/frameworks/pbmm
- Category
- Community
More from GRCEngClub/claude-grc-engineering
All 70- pci-dssv0.1.0
- poam-automationv0.1.0
- sg-mas-trmv0.1.0
- singapore-pdpav0.1.0
- slack-inspectorv0.1.0
- snowflake-inspectorv0.1.0
- soc2v0.1.0
- splunk-inspectorv0.1.0
- staterampv0.1.0
- teach-mev0.1.0
- tenable-inspectorv0.1.0
- testssl-inspectorv0.1.0
- trust-centerv0.1.0
- us-ccpav0.1.0
- us-exportv0.1.0
- us-finrav0.1.0
- us-hipaa-securityv0.1.0
- us-nerc-cipv0.1.0
- us-soxv0.1.0
- vault-kvv0.1.0
- wiz-inspectorv0.1.0
- academic-research-companionv0.1.0
- au-apra-cps-234v0.1.0
- aws-inspectorv0.1.0
