Updated by
Hi, I'm Jack, the owner of Cybersecurity Jobs List and co-founder of Himalayas (himalayas.app) and Cavuno (cavuno.com). Across all my platforms, I work with application security daily: dependency vulnerability scanning, secure authentication, API security, and data protection across hundreds of thousands of users. My technical background is in computer science (UNSW). I studied security engineering and computer networks, and worked as a research assistant on VR experiments that were published in the Journal of Experimental Psychology. I also work with cybersecurity hiring data every day, tracking which companies are posting, what certifications actually appear in listings, how salaries differ by sub-discipline and clearance level, and where the talent gaps are widest. That combination of security practice, engineering at scale, and daily immersion in hiring data shapes the content on this site. I'm currently based in Sydney, Australia.

A useful incident report lets another analyst or system owner see what happened, what the evidence supports, what remains unknown, and who owns the next action. This fictional SOC case turns a reported phishing message and a suspicious sign-in into a compact report, then gives you a template you can adapt for an authorized lab or interview assessment.
What should a SOC incident report answer?
A case report should make the current status and the reader's next decision clear. A practical starting point is: what was detected, which systems or people may be affected, what evidence supports the assessment, what actions have happened, and what needs to happen next.
Those fields are common in public guidance, but the format belongs to the organization. The Australian Cyber Security Centre's practitioner guide separates a situation report from an incident log, evidence register, remediation action plan, and post-incident review. The NIST incident response guidance is also current at Revision 3, published in April 2025. Use your employer's case system, severity scale, handling rules and approved playbooks for real work.
Example: suspicious sign-in after a phishing report
Everything in this example is invented. The account, times, log observations and response actions do not describe a real person or incident. Times are UTC so the sequence stays unambiguous.
Case summary
Case: IR-TRAIN-014 Status: Investigation open, immediate account actions recorded Priority: Not assigned in this exercise; use the organization's own criteria Summary: An employee reported entering a password on a fake sign-in page after opening a message from payroll@example.invalid. Identity logs show a successful sign-in to the employee's account shortly afterward from a location the employee did not recognize. The team reset the password and revoked active sessions under its fictional response procedure. The reviewed logs do not establish whether any mailbox content was accessed.
Evidence and timeline
| Time (UTC) | Source | Observation | What it supports |
|---|---|---|---|
| 09:02 | Service desk ticket | Employee reported opening a payroll-themed email and entering a password on the linked page. | A user statement, not independent proof of what the page collected. |
| 09:11 | Identity sign-in log | Successful sign-in to the employee account from an unfamiliar network location. | A sign-in occurred; the log alone does not identify who controlled the session. |
| 09:19 | Mail trace | Four internal recipients received the message; two copies were still in mailboxes when searched. | Known message distribution in the searched mail system and time window. |
| 09:32 | Identity admin case note | Session revocation and password reset were recorded as complete. | The listed account actions were completed by the named response owner. |
| 10:05 | Mailbox audit search | No new forwarding rule appeared in the reviewed audit window. | No matching rule was found in that source and window; other access remains unconfirmed. |
Assessment and next steps
The available evidence supports a phishing-related account investigation. The user statement and sign-in record raise concern about account access, but they do not prove that messages or files were read or copied. The incident remains open while the identity owner checks the remaining approved audit sources and the mail team confirms the two mailbox copies were handled under its procedure.
| Action | Owner | Status | Evidence to attach |
|---|---|---|---|
| Confirm session revocation and password-reset ticket | Identity response owner | Recorded complete | Ticket reference and completion time |
| Review approved sign-in and mailbox audit window | Identity and mail owners | In progress | Source name, time range, query or case link |
| Confirm disposition of remaining message copies | Mail operations | Pending | Mail trace or quarantine record |
| Update impact and status after review | Incident lead | Pending | New findings and decision rationale |
Notice what the report does not claim: it does not say the attacker was identified, data was exfiltrated, the account was fully clean, or every recipient clicked the link. A short report is stronger when its limits are visible.
How to write the report without overstating evidence
Keep four kinds of statements separate:
- Observed: what a named system or record shows, with its time range.
- Reported: what a user, customer or responder told the team.
- Assessed: the analyst's interpretation of those records, with the reason.
- Unknown: what the current evidence does not establish and what source or owner could resolve it.
For example, “successful sign-in from an unfamiliar location” is an observation. “The attacker accessed the mailbox” is a conclusion that needs supporting evidence. If you do not have that evidence, keep mailbox access in the unknowns and assign a next step.
Use one timezone throughout the timeline or label each entry's timezone. Preserve the source name and the searched period. If you map an event to MITRE ATT&CK, include the technique only when the observed behavior supports that mapping. A technique label does not replace the log, case note or artifact that led you there.
Copyable SOC incident report template
Adapt these fields to your employer's case system or the instructions for your assessment. Leave a field marked unknown when the evidence does not answer it.
| Section | What to record |
|---|---|
| Case identity | Case number, report version, author or role, created/updated time, timezone, audience and distribution restrictions. |
| Status and classification | Current status; incident type; priority or severity only under the organization's rubric; decision owner and time. |
| Summary | What was detected or reported, known scope and impact, actions completed, current status, and next update. Write this after the detail. |
| Scope | Known affected accounts, devices, services, locations or business teams; source and time window checked; what is still unconfirmed. |
| Evidence and timeline | Timestamp with timezone, source or artifact reference, observation, action, owner and result. Separate user statements from system records. |
| Assessment | What the evidence supports, alternative explanations considered, confidence or limits, and the next check needed. |
| Response actions | Action taken, authorizing role or procedure, completion time, owner, result, and any follow-up. Do not turn a suggested action into a completed action. |
| Impact and unknowns | Confirmed service or business effect, affected parties if known, data exposure status, and what has not been established. |
| Recommendations | Specific follow-up, accountable owner, due date or review point, status and evidence of closure. Keep recommendations separate from incident facts. |
| Review and distribution | Reviewer, approval or escalation needed, recipients authorized to see the report, and next update time. |
A running incident log is useful for recording decisions as they happen. A handover passes current work to the next shift. A final incident report brings the findings and response record together, while a post-incident review focuses on lessons and tracked improvements. The ACSC guidance treats these as related but separate artifacts. CSJL's SOC shift handover template covers that transfer between analysts.
Turn the example into a safe portfolio piece
Use a lab, an employer-authorized assessment, or data that was created for practice. Do not publish real usernames, email addresses, IP addresses, customer details, screenshots, case numbers, or internal procedures. Replace them with reserved example values and say clearly that the scenario is fictional.
A strong sample shows how you reason from evidence rather than how many tools you can name. Include a compact timeline, source references, one careful assessment, a meaningful unknown, and a next action with an owner. If the task was an employer-provided assessment, follow its confidentiality and submission instructions instead of turning it into a public portfolio post.
For more practice, see our guide to cybersecurity take-home assessments and the fictional threat-modeling portfolio exercise. You can also browse current cybersecurity jobs and compare the reporting work with the responsibilities listed in each role.
Further reading
- NIST SP 800-61 Rev. 3
- ASD/ACSC Cyber Security Incident Response Planning: Practitioner Guide
- CISA CRR Supplemental Resource Guide
This example is for career practice, not an operational playbook or legal advice. Follow your organization's approved procedures for real incidents.


