Cyber Incident Response Checklist: What to Do in the First 60 Minutes
A suspicious sign-in appears in Microsoft 365. An employee reports that files are being renamed. A supplier receives an unusual message from your company account. Your endpoint-security platform raises a critical alert.
The first hour after a suspected cyber incident can determine whether the problem remains limited or spreads into a larger operational, financial or privacy event.
This cyber incident response checklist gives small and medium businesses a practical structure for those first 60 minutes. It does not replace advice from qualified incident responders, legal counsel, insurers or privacy professionals. The correct response depends on the systems affected, the information involved and the terms of your insurance policy.
The key is to act quickly without destroying evidence or making uncoordinated changes.
Before an incident: assign authority and contacts
The first hour is much easier when the business has already decided who can act.
Your incident plan should identify:
- Who can declare a security incident
- Who can isolate computers or suspend services
- Who can disable accounts and revoke active sessions
- Who contacts the IT provider, security responder and insurer
- Who makes operational and communication decisions
- Who assesses privacy and legal obligations
- Where emergency contacts and procedures are stored if normal systems are unavailable
Keep an offline or independently accessible copy of this information. If email or Microsoft 365 is compromised, the response team may need a separate communication channel that the suspected attacker cannot monitor.
The Canadian Centre for Cyber Security recommends activating an incident-response plan, preserving evidence and appointing a clear point of contact when an organization becomes a victim of cybercrime.
Minutes 0–5: stop and report
When an employee notices suspicious activity, the safest first action is usually to stop interacting with the affected system and report it immediately.
Record what was observed:
- The time the activity was discovered
- The device, account or application involved
- Messages, alerts or unusual behaviour shown on screen
- Any link, attachment or file that was opened
- Whether credentials or an MFA prompt were entered or approved
- Other people or devices that may be affected
Do not begin deleting files, running cleanup utilities or experimenting with settings. Those actions can remove evidence and make it harder to understand what happened.
Employees should know one simple reporting route: a phone number, helpdesk number or emergency contact that reaches someone authorized to investigate.
Minutes 5–15: isolate without erasing evidence
Containment reduces the opportunity for an attacker or malicious program to move to other systems.
For a suspected compromised computer, disconnect it from the network by removing its Ethernet cable, disabling Wi-Fi or using an approved endpoint-isolation feature. Keep the device powered on unless an incident responder directs otherwise. Volatile evidence stored in memory may disappear after a shutdown or restart.
The Cyber Centre specifically advises organizations to lock potentially compromised systems and avoid shutting down, rebooting or logging out before volatile evidence is preserved.
Do not disconnect every system automatically. A coordinated decision should consider the apparent scope of the incident, essential business operations and whether isolation can be performed safely.
For a cloud-account incident, network isolation alone may not be enough. The authorized IT or security team may need to revoke sessions, reset credentials, block suspicious sign-ins, remove malicious forwarding rules or suspend connected applications. These changes should be documented as they occur. Strong Microsoft 365 security controls can make this work faster and more reliable.
Minutes 15–30: verify the incident and establish scope
The response lead should create an initial incident record and begin answering four questions:
- What happened? Identify the alert, suspicious action or reported symptom.
- What is affected? List known devices, users, mailboxes, applications and locations.
- Is it still happening? Look for continuing sign-ins, file changes, encryption, data transfer or attacker activity.
- What could be at risk? Identify important systems, personal information, financial data and operational dependencies.
Preserve screenshots, alert details, email headers, timestamps and relevant logs. Record every containment action, who approved it and when it occurred. Avoid changing the original evidence where practical.
Do not assume that the first affected device is the full scope. A compromised identity may have accessed email, SharePoint, OneDrive, administrative portals or third-party applications. Ransomware may also remain quiet while spreading before files are encrypted. Review the SOS guide to ransomware protection for additional preparation steps.
Minutes 30–45: activate the response team
Notify the people who have defined roles in the plan. Depending on the incident, that may include:
- Business leadership
- Internal IT or the managed IT provider
- A cybersecurity incident-response specialist
- The cyber-insurance contact or broker
- Legal or privacy counsel
- A cloud, banking or software provider
- Communications or customer-service leadership
Use a communication channel believed to be safe. Share confirmed facts, current containment actions, important unknowns and the next decision time. Avoid broad speculation or unapproved messages to clients, employees or the public.
Review the cyber-insurance policy before engaging vendors or making commitments. Some policies require prompt notice or the use of approved response providers. Contacting the insurer does not replace technical containment, but contractual requirements should not be overlooked. The SOS cyber-insurance readiness checklist can help prepare the required evidence before renewal or an incident.
Minutes 45–60: set priorities and protect critical operations
By the end of the first hour, the team should have a documented working picture, even if many questions remain.
Set priorities for the next response period:
- Continue containment and identify additional affected systems
- Protect unaffected backups and administrative accounts
- Preserve logs and other evidence before retention periods expire
- Confirm which business services can operate safely
- Identify the systems that would be restored first
- Establish the next leadership update time
- Assign an owner and deadline to each immediate action
Do not restore systems merely to return to normal quickly. Recovery should use trusted backups or clean sources, and the team should understand the likely entry point and persistence mechanisms before reconnecting affected systems. Otherwise, the same compromise may return.
The Cyber Centre’s ransomware playbook covers immediate response, recovery and lessons learned. Its guidance emphasizes containment, evidence preservation, clean restoration and documented lessons after the incident. Confirm your backup recovery process through representative restore tests before an emergency.
Assess privacy and reporting obligations
If personal information may have been accessed, lost or disclosed, begin a privacy assessment promptly.
Under Canada’s Personal Information Protection and Electronic Documents Act, organizations subject to PIPEDA must report breaches that create a real risk of significant harm, notify affected individuals and keep records of every breach involving personal information. The Office of the Privacy Commissioner of Canada states that breach records must be kept even when the incident is not reportable.
Provincial, contractual and industry obligations may also apply. Determining whether notification is required involves legal and factual analysis, so involve qualified privacy or legal advice rather than improvising a conclusion during the technical response.
Actions to avoid during the first hour
Well-intended actions can make the investigation harder. Avoid:
- Restarting or wiping a suspected device without direction
- Deleting suspicious emails, files or accounts
- Using the potentially compromised email system for sensitive response discussions
- Resetting every account without a coordinated plan
- Restoring from backup before confirming that the recovery source is clean
- Contacting a suspected attacker directly
- Making public statements before facts and responsibilities are established
- Paying a ransom or transferring money without executive, legal, insurance and law-enforcement consultation
Turn the checklist into an exercised plan
A checklist is valuable only if people can use it under pressure.
Run a short tabletop exercise using a realistic scenario, such as a compromised Microsoft 365 administrator, a fraudulent payment request or ransomware detected on a shared file system. Ask participants to identify who makes each decision, which tools and contacts are required and how the business would continue operating.
Document gaps and convert them into assigned work. Common findings include outdated phone numbers, missing administrative access, unclear authority, unavailable backup credentials and no safe alternate communication method.
SOS Computer Experts helps Greater Vancouver businesses prepare and test practical incident-response procedures alongside Microsoft 365 security, endpoint protection, backup recovery and managed IT. Ongoing managed IT services are available only in North Vancouver, Vancouver, Burnaby, Coquitlam, Richmond, Surrey and Langley.
For organizations in Victoria, Calgary, Edmonton and Toronto, SOS provides fixed-scope enterprise cybersecurity assessment and project-based incident-readiness work only—not MSP, general cloud, networking, infrastructure or helpdesk services.
Prepare before the next alert
Do not wait for a critical alert to decide who has authority, where emergency contacts are stored or how affected systems will be isolated.
Request an Incident-Readiness Review
Clarify response roles, containment steps, emergency contacts and recovery priorities before a real incident creates pressure.
