everyone has Claude open. almost no one is using it well.
and i was no different. open a tab, ask a question, copy the answer, close the tab. repeat. that’s not working with Claude. that’s just a fancier search engine.
it took me actually sitting down and learning the tool properly to realise how much i was leaving on the table.
why this matters for SOC analysts specifically#
we deal with information overload every single day. 40 open investigations. alert queues that never empty. context switching every 20 minutes. documentation that’s always behind.
Claude doesn’t fix all of that. but used properly — it becomes a serious thinking partner. not a chatbot you ask one-off questions to. an actual collaborator that knows your context, remembers your preferences, and helps you move faster without cutting corners.
that’s the difference between opening Claude and working with Claude.
what this series covers#
6 posts. built on Anthropic’s Claude 101 course. filtered through a SOC analyst’s lens.
- what Claude actually is and how to talk to it properly
- how to organise your work with projects, artifacts, and skills
- connecting Claude to the tools you already use
- research mode — the feature that genuinely changes how you investigate
- Claude beyond the browser — desktop, Slack, Excel, and more
no hype. no “AI will replace you” narratives. just practical, honest notes from someone figuring this out one post at a time.
who this is for#
SOC analysts, security engineers, anyone in tech who has Claude open but isn’t sure they’re getting the most out of it. you don’t need to have read the AI fundamentals series first — but if you haven’t, that’s a good place to start.
see you in post 1.
what’s your current Claude habit — one-off questions or something more structured? curious where most people are starting from.
took ai help to clean up typos. my brain works faster than my fingers. xd
next up: AI Series #13 — “how to actually talk to Claude — and get something useful back” back to series index
