Practical notes on PCI DSS, privacy law, security testing and audit, written by the team that does the work. Filter by topic, month or keyword.
Multi-factor authentication for all access into the cardholder data environment: requirement 8.4.2 explained
Since 2025-03-31, PCI DSS requires MFA for all non-console access into the cardholder data environment, not only for administrators. Here is what that means in practice.
Read the insight →Privacy impact assessments under Law 25: when you need one and what goes in it
Law 25 requires a privacy impact assessment for new information systems, transfers outside Quebec and some research uses. Here is when it applies and what a proportionate PIA…
Read the insight →Sending personal information outside Quebec: assessing cloud and SaaS providers (s. 17)
Hosting client data in Ontario, the US or Europe is allowed under Law 25, but only after a privacy impact assessment and a written agreement. Here is a…
Read the insight →ISO 27001 or SOC 2? Choosing the right proof for Canadian SaaS and service providers
ISO 27001 certifies a management system; SOC 2 reports on controls. How Canadian SaaS and service providers can decide which one customers will actually accept.
Read the insight →SOC 1 vs SOC 2 in Canada: CSAE 3416, CSAE 3000 and what your clients actually need
SOC 1 supports your clients' financial statement audits; SOC 2 addresses security and related criteria. How CSAE 3416 and CSAE 3000 fit, and how to pick.
Read the insight →Penetration testing vs vulnerability scanning vs ASV scans: what PCI DSS actually requires
Vulnerability scans, ASV scans and penetration tests are different activities with different PCI DSS rules. Here is what requirements 11.3 and 11.4 ask for, and how often.
Read the insight →Answering client security questionnaires without starting from zero every time
Security questionnaires eat sales and security time. A practical method to build a reusable answer library, back it with evidence and keep it current.
Read the insight →Segmentation testing: why reducing PCI scope needs proof
Segmentation can shrink PCI DSS scope, but only with proof. Merchants must test it yearly and service providers every six months, plus after changes. Here is what that…
Read the insight →Reporting a breach to the Privacy Commissioner: the “real risk of significant harm” test explained
Under PIPEDA, a breach must be reported when it creates a real risk of significant harm. Here is how to weigh sensitivity and probability of misuse, and what…
Read the insight →Webinars, conference talks and private sessions on PCI DSS, privacy law and cybersecurity, in English and French.
Tell us what you need and when. We’ll tell you what it takes, what it costs and how long it’ll take. No obligation.