Senior Data Analyst β‘οΈ Cybersecurity. Atmospheric Sciences background. ISC2 CC certified. Documenting the pivot @ DataSec Chronicles. New blog posts Mon & Friππ
ππ½ Hi, I'm Tasha.
As an atmospheric scientist, I spent years reading storm data for anomalies. Now I hunt them in network traffic.
Same instinct, different domain. π
By day, I'm a Senior Data Analyst living in SQL, Python, and dashboards. I founded DataSec Chronicles to document my pivot into cybersecurity β the real learning journey. The wins, technical hurdles, and study strategies, from earning my ISC2 CC β to working toward SC-900 and Security+.
DataSec Chronicles is the story. DataSec Labs is where I put it into practice β interactive challenges and hands-on projects you can actually try.
I've been online since dial-up screamed at you before letting you in and Y2K was going to end the world. π The interwebs raised me; now I'm learning to defend them.
Whether you're a data nerd, a cyber practitioner, a fellow career-changer, or just someone who appreciates good data hygiene and a warm cup of chai, welcome to my corner of the interwebs.
What to expect:
π Data & cyber insights β complex concepts made simple
π The pivot journey β study tips, resource reviews, and what I'm learning
π± Community β a space to learn out loud and grow together
Drop a comment introducing yourself, what you're working on, or what brought you into tech ππ½
π https://t.co/jlp1YMuFrC
π The Security Dictionary: PLAYBOOK
Monday we talked about SOAR β how security teams connect tools, automate repetitive tasks, and coordinate responses.
But how do analysts know what steps to follow when investigating a security alert?
That's where playbooks come in.
β Plain English: A playbook is a documented set of steps that guides security analysts through investigating and responding to specific security situations.
β Think of it like: A response checklist. Instead of figuring out what to do from scratch every time, analysts have a structured process to follow while still using their judgment.
β Example: An analyst receives an alert about suspicious login activity. A playbook might guide them to review authentication logs, check the source IP, look for related activity, document findings, and escalate if necessary.
β Why I'm learning it: Coming from data analytics, I'm familiar with documented procedures and repeatable workflows. I'm learning how those same principles apply in a SOC, where consistency, communication, and timely decisions matter.
And here's the connection to SOAR: Playbooks define the steps, while SOAR platforms can automate parts of those workflows.
The more I learn about security operations, the more I see how important having a process is, not just knowing which tools to use. π
#Cybersecurity #TheSecurityDictionary #LearnWithMe
I'm at 1,969 followers, and my follower count is creeping toward the year I was born. π
Now I kind of want to catch that exact number for a screenshot. π
I'm at 1,969 followers, and my follower count is creeping toward the year I was born. π
Now I kind of want to catch that exact number for a screenshot. π
Day 2 of my SOC Home Lab!
Built a Python parser and extracted 2,843 Windows Security events from a public attack-simulation dataset.
Found 7 failed logons across 7 accounts in 12 milliseconds.
So far: no source IP in those events, no lockouts observed, and some successful logons preceded the failures.
Day 3: Moving to TimescaleDB to correlate events and investigate what happened.
Suspicious patterns are clues, not conclusions.
Full write-up Friday! π
@EchoToolsPro I can definitely see that. I think the challenge will be making sure automated triage actually reduces the workload without introducing new problems. That was one of the points from today's webinar that stuck with me. Automation still needs oversight and validation.
Just attended the SANS webinar, βThe SOC Analyst in the Age of AI,β with John Hubbard.
This was one of those sessions where I kept connecting what I was hearing to my own experience as a Senior Data Analyst.
A few takeaways that really stuck with me. π§΅π
@EchoToolsPro Very true! That's where I imagine prioritization and knowing what deserves a deeper investigation become especially important. It's one thing to recognize patterns, but another to sort through the noise when there are so many alerts competing for attention.
@EchoToolsPro Exactly! That's something I'm keeping in mind as I transition. I know the pace and priorities will be different, but I think the more familiar I become with security events and what to look for, the more efficiently I'll be able to investigate.