Read a sample: 1. A Portfolio That Shows Analyst Thinking
A security alert rarely arrives with a complete explanation. It may identify an unusual sign-in, a reported email, or a process running on a computer. It may also leave out the very context an analyst needs: whether the user was traveling, whether a message was expected, or whether an administrator approved a change.
The analyst’s job begins in that gap. What is known? What is merely possible? Which question should be answered next, and who needs to know?
A portfolio can make that thinking visible. Instead of asking an employer to infer your abilities from a certification list or a job title, you can offer a short, original sample that shows how you read evidence, handle uncertainty, and communicate a decision. The sample does not need a sophisticated dashboard or a dramatic incident. It needs a clear problem, a traceable set of observations, and reasoning another person can follow.
This book will help you create that kind of work from fictional material. You will examine invented alerts and records, write case notes, make escalation recommendations, and revise your results for presentation. The goal is not to manufacture the appearance of experience you do not have. It is to give a reader a fair view of how you approach work that resembles part of an entry-level security operations role.
A security operations portfolio is a curated collection of work samples. Each sample presents a small problem and your response to it. For this book, the samples are primarily text: alert summaries, triage notes, evidence timelines, follow-up requests, escalation handoffs, and brief reflections.
A useful sample can show that you know how to:
- Identify the information an alert actually provides.
- Separate an observation from an interpretation.
- Consider more than one explanation for activity.
- Recognize when important context is missing.
- Recommend a proportionate next step.
- Write a handoff that saves another analyst time.
Those behaviors matter because security operations is collaborative. An analyst may review an alert, request additional evidence, escalate a concern, or document why no further action is currently justified. The next person needs to understand both the conclusion and the path taken to reach it.
A fictional portfolio cannot prove that you have operated a particular employer’s tools, handled a production incident, or made decisions under the pressures of a live environment. It cannot verify that you performed workplace duties you have not performed. A carefully written sample is evidence of the work shown in the sample, not a substitute for every qualification in a job description.
That limitation is not a reason to avoid building one. It is a reason to label and describe your work accurately. “Fictional alert triage exercise” is an honest description. “Responded to a production account compromise” is not, unless that is something you actually did and are authorized to discuss. The distinction protects your credibility and helps the reader evaluate the work on its own terms.
You also do not need to solve every case. A strong entry-level sample might end with a request for authentication logs, a check of an approved change, or an escalation to a more experienced analyst. Incomplete evidence sometimes supports a limited conclusion better than a confident verdict.
Your portfolio may be read by people with different responsibilities. A recruiter may scan it to understand your interests and communication skills. A hiring manager may look for evidence that you can approach the work systematically. A working analyst may focus on whether your notes make the case easier to continue.
You do not need to predict every reader’s preferences. You can make the work easier for all of them to navigate.
Start each sample with a plain-language description of the situation and the task. Label the scenario and all associated records as fictional. Use headings so a reader can find the evidence, your assessment, and your recommended next step without reading every line. Explain technical terms when they are essential to the decision, but do not turn a short case note into a glossary.
Consider the difference between these two openings:
> Less useful: Investigated a suspicious login and determined the account was compromised.
> More useful: In this fictional exercise, I reviewed an alert for an unusual sign-in. The available records show a successful sign-in from an unfamiliar location, but they do not establish who performed it. I recommend verifying the activity with the user and reviewing related authentication events.
The second opening gives the reader something to evaluate. It identifies the source of concern, limits the conclusion, and names a next step. It does not require the reader to accept your judgment on authority alone.
Different organizations use different procedures, tools, and escalation thresholds. Your sample should therefore explain the reasoning behind its recommendation rather than presenting a single workflow as universal. When a decision depends on an invented assumption—such as a fictional team’s instruction to escalate successful sign-ins that a user cannot verify—state that assumption. Do not present it as a rule that applies everywhere.
A portfolio entry is strongest when the reader can distinguish four things: what the fictional source says, what you think it might mean, what you do not know, and what you propose to do.
Suppose an invented alert says that an account successfully signed in from a location the alert system had not previously associated with that account. That is an observation about the alert and…