Connecting attacker goals to business safeguards
Review five attacker objectives against your business information, infrastructure, accounts and recovery, without relying on speculative hacker labels.

An attacker’s objective helps explain which information or access needs protection. It doesn’t reliably identify the person behind an incident, and the same attacker may pursue several goals.
The Cyber Centre’s introduction to the threat environment describes motivations and techniques. Use it to review what your business holds that an attacker would want.
Stealing personal information
Identify where customer and employee information is collected, stored and shared. Limit collection to the business need and restrict access to the roles that need it.
Review exports, integration accounts and retained copies as well as the main application. Have a process for assessing a suspected breach. Under PIPEDA, a breach that creates a real risk of significant harm must be reported to the Privacy Commissioner of Canada and the people affected, and some provinces have their own rules.
Don’t treat a locked folder as protection for copies already emailed or downloaded elsewhere.
Misusing computing resources
An attacker may use infrastructure for unwanted workloads, message delivery or further attacks. Watch cloud bills, capacity and changes to accounts and access, and set billing alerts where the service offers them.
A slow device or larger bill can have legitimate explanations. Investigate changes with the logs and the system’s owner before deciding what caused them.
Remove unused exposed services and review the privileges of automation accounts.
Taking confidential business material
Map sensitive designs, bids, plans and contracts. Check who can access them and how information is shared with external partners.
Share through the collaboration tools your business has chosen, and review access when a project or supplier relationship ends. Keep a record of the exports you allow.
An attacker doesn’t need to steal everything to cause a problem, so prioritize the material whose disclosure would affect a real business decision.
Impersonating an account holder
Protect sign-in and account recovery with MFA, using a phishing-resistant method where the service supports one. Review connected applications, delegation and active sessions.
Have a second person sign off on payments and sensitive account changes, even when a request comes from a familiar address. A convincing request can arrive through a compromised account or a copied identity.
Staff need a practical way to verify and report it.
Interrupting work or extorting the business
An incident may encrypt systems, disrupt a service or involve a threat to publish stolen information. Paying won’t make sure stolen information is deleted, and it won’t make your systems safe to trust again.
Maintain an incident plan and test recovery from protected backups. Include the people who make the calls on business continuity, communications and bringing in outside help.
For each objective, record the important asset, the safeguard and its owner. Use the exposure-mapping guide to turn that review into prioritized work. Reassess when systems or information flows change.


