Skip to Content

Security & Compliance

Lynx Compliance - Incident (Security / Law 25 / Bill C-26)

Security incidents with the Law 25 72-hour countdown

lynx_compliance_incident · v19.0.1.3.0 · Add-on

Incident turns a service desk ticket into a security incident: severity, attack vector, affected systems, personal information involved, containment and resolution times. When personal information is involved, a 72-hour countdown starts for the notice to the Commission d'accès à l'information.

Each incident keeps a forensic timeline and a log of every notice sent, to the regulator, the Canadian Centre for Cyber Security, customers, insurers or the board, and can follow a playbook.

Why teams pick it

What Lynx Compliance - Incident (Security / Law 25 / Bill C-26) does for you

72-hour countdown

Deadline and status (open, due within 24 hours, overdue, notified) computed from the discovery time.

Forensic timeline

Detection, triage, containment, eradication, recovery and communication events, with actor and source.

Notification log

Notices to the CAI, the Canadian Centre for Cyber Security, the federal privacy commissioner, customers and insurers, with an approval step; each notice sent is added to the timeline.

Playbooks

Apply a playbook to an incident to follow its steps.

Root cause and lessons

Root cause, resolution and lessons learned, with a closure check and a trend dashboard.

Try Lynx Compliance - Incident (Security / Law 25 / Bill C-26) on your team.

Free trial, no credit card. Talk to sales when you're ready.