Seven questions for an IT compliance policy
Seven questions that tie an IT compliance policy to the laws and contracts that apply, daily work, technical controls, owners, exceptions and evidence.

An IT compliance policy should turn each requirement into something staff do. A statement such as protect confidential information isn’t enough if staff don’t know where to store it or who can approve sharing.
Start with the obligations that apply to your organization. Then answer these seven questions with the people responsible for the business process, privacy, records and IT.
1. Which obligations and records are in scope?
List the laws, contracts, professional rules and internal commitments that apply: PIPEDA or a provincial privacy law, your card processor’s PCI DSS requirements, or the security clauses in a client contract, for example. Identify the records, services and locations each one covers.
Canadian privacy requirements depend on jurisdiction and activity. The Privacy Commissioner’s provincial-law overview explains why PIPEDA isn’t the only privacy law to consider.
Record who confirmed that each obligation applies. US laws such as HIPAA or Sarbanes-Oxley belong in the policy only if a contract or a US operation brings them in.
2. What do staff need to do in ordinary work?
Walk through creating a record, accessing it, sharing it, retaining it and disposing of it. Include work done remotely or with a supplier.
At each step, name the place the record goes and the tool to use. Test an exception, such as a recipient who can’t use the normal sharing tool.
Use the workflow to identify a missing procedure before adding a broad prohibition that staff can’t follow.
3. Which technical controls support the procedure?
Map the required behaviour to access settings, device configuration, logging, backup or other controls. Identify the service and licence involved.
The Cyber Centre’s baseline controls can inform the security work. Meeting them is a good start. Check legal and contract obligations separately.
Check the setting that’s in place and a sample result. A feature list only tells you what’s possible.
4. Who owns each decision and task?
Assign a business owner for the record or process and a person responsible for operating the technical control. Name who signs off access, exceptions and changes.
An IT provider may run a system for you, but your organization still owns the information and makes the legal decisions. Write that split into the service agreement.
Name a deputy for each role, and who to go to when both are away.
5. How will people learn and use the policy?
Put the procedure where staff will find it, such as the intranet page or Teams channel they already use. Give role-specific examples, a reporting route and a place to find the current instructions.
Test understanding through a harmless task or discussion. Check whether an instruction needs clearer wording or a technical change.
Base onboarding and refresher training on the current procedure.
6. How are exceptions approved and revisited?
Record the reason, affected information, compensating controls, approver and expiry or review date. Track an exception until it’s closed or renewed.
Don’t let an informal workaround become the permanent operating method without review.
7. What evidence shows that the policy works?
Decide which records show a control is working: access reviews, training completion, configuration checks or test results.
Automation can collect evidence, but someone still needs to investigate a gap and confirm a corrective action. Review the policy after a relevant system, supplier or obligation changes, and keep a copy of the signed-off version.


