Security engineering for systems that carry consequence.
Blackpine is a 26-person Canadian cybersecurity firm covering advisory, defensive engineering, incident response, security operations, risk, and technical research. Start with the situation; Blackpine can determine the specialist path internally.
One practice across advisory, engineering, incident response, SOC, and risk disciplines means a customer can describe the problem in ordinary language while Blackpine routes the work to the right function.
You should not need to diagnose the service first.
Choose the statement closest to the situation. Blackpine can triage the issue and decide whether the work belongs in response, investigation, recovery, protection, monitoring, or the Security Desk.
From authority to verification.
Every engagement begins with a defined objective and evidence boundary. Findings are written so the people responsible for the next decision can see what was observed, why it matters, and what should change first.
- 01Confirm authority, systems, objective, and constraints.
- 02Inspect agreed evidence and control paths.
- 03Separate facts, interpretation, and limitations.
- 04Sequence remediation, ownership, and verification.
Show the shape of the work without exposing the client.
Engagement patterns are separated from approved client stories. Client names, quotes, logos, and outcomes only appear when attribution is permitted and the description does not reveal sensitive systems or evidence.
Containment, evidence, recovery, and downstream business verification around a compromised account.
Privileged roles, guests, connected applications, recovery ownership, and high-impact control paths.
Decision authority, communications, logs, backups, vendors, and recovery dependencies tested before pressure arrives.
Engineering work should survive inspection.
Blackpine Cipher is developed on a separate application surface with its own threat model, verification workflow, and technical documentation. The corporate site links to it without sharing application code or an assumed trust boundary.
Notes for people making security decisions.
Blackpine Research focuses on specific questions around identity, cloud access, incident response, recovery, and administrative control. Publications are selected for usefulness rather than frequency, and source links stay attached to the reasoning.
Built across disciplines.
26 people across advisory, defensive engineering, incident response, security operations, and GRC. Michael Calloway is Blackpine's CEO and owner; specialist work remains grouped by the function responsible for delivering it.
Protect control and evidence first.
For account compromise, business email compromise, ransomware, website compromise, or suspicious administrator activity, Emergency Response provides the direct problem-first route into Blackpine.
Publish the boundary.
Blackpine documents website security, data handling, responsible disclosure, and the separation between corporate, support, verification, and Cipher systems. Claims are kept narrower than the evidence supporting them.
Start with what happened.
Tell us what changed, what looks suspicious, what needs to be recovered, or what you want to improve. The intake route carries that context forward so you do not have to translate the problem into security jargon.