Colour theme
Book a consultation

Five questions for a data security review

Review security-tool decisions, ransomware recovery, data collection, access controls and biometric handling with evidence from your own business systems.

An illustration of a yellow padlock against an orange circle.

A data security review should produce decisions about the information your business holds. An industry trend or a new product name doesn’t show whether your own records are protected.

Use these five questions with IT and the people responsible for the records. Choose a real workflow, such as collecting a client form and preparing its final report, and follow the information through the systems involved.

1. Who checks automated security decisions?

Ask your security provider which decisions its tools make automatically and which need human review. Include alerts, account restrictions and device isolation. Record who can investigate and reverse a mistaken action.

The Cyber Centre’s AI guidance describes useful security applications alongside limitations and risks in the underlying data. An AI label on a product says nothing about what it detects or how often it’s right.

Ask for a controlled demonstration using agreed test data. Include an ordinary business event that could look unusual and a missed or delayed alert. Follow what happens after the alert: who sees it, and what they do.

2. Can essential records be restored safely?

Identify the records needed to resume a critical service. Verify that they’re in the backup scope, that a usable copy survives the incident being planned for, and that the right people can recover it.

Have the business owner check a sample restore with IT. Confirm file contents, application dependencies and how recent changes will be reconciled. A backup job can report success and the data still fail to restore.

Recovery also needs a response to possible stolen information. Restoring files doesn’t undo disclosure. The ransomware readiness guide covers the wider exercise.

3. Are safeguards decided before collection?

For a new form, application or integration, decide why each field is needed, who can see it, where it goes and when it can be removed. Include copies in email, exports and connected services.

Canada’s privacy commissioners’ privacy-management guidance supports accountable programs with assigned responsibilities and ongoing review.

Have the privacy lead check applicable federal, provincial and sector requirements. A checklist written for another country’s law, such as the EU’s GDPR, won’t tell you which rules apply here. Keep the retention and access decisions you make with the workflow documentation.

4. Does access match the person’s current work?

Test a staff account, an administrator and an external participant. Confirm what each can read, change, download and share. Check historical memberships and links as well as the main folder.

Review account recovery and departure procedures. Verify that a policy is enforced for the intended users and applications. MFA doesn’t remove excess permissions or guarantee that every session is protected.

Use the zero-trust rollout checks to examine policy coverage and exceptions without treating a product purchase as a complete strategy.

5. Does a biometric feature need a separate review?

Fingerprint and face features can handle information in different ways. A device-local sign-in arrangement and a service collecting staff face images need separate data-flow checks.

The OPC’s business guidance on biometrics covers when a purpose is acceptable, consent, safeguards and retention. Have the privacy lead assess the proposed use before collection begins, including alternatives and provider access.

Ask where images and templates are stored, who can retrieve them and how deletion is verified. Encryption alone doesn’t resolve the privacy questions.

Assign an owner and due date to each gap. Keep evidence of the corrected behaviour so the next review can check what changed.


Featured Image Credit