Blue Team Labs Online
Dabbling in Blue Team Labs

Today I completed the Follina challenge on Blue Team Labs Online, and it turned out to be a great exercise in incident response, document analysis, and defensive thinking. The lab focused on the Follina vulnerability, which is tracked as CVE-2022-30190 and is known for abusing malicious Office documents to trigger code execution.
What the lab was about
The scenario placed me in the role of a defender responding to a newly discovered RCE vulnerability that was being actively exploited. Instead of treating it like a traditional CTF, the challenge required me to investigate a suspicious sample, analyze its contents, and answer questions based on the artifact and its behavior. That made the lab feel very close to real-world triage work, where the goal is to understand what happened, how it worked, and what indicators can be extracted for detection.
My investigation approach
I started by examining the provided file and using VirusTotal to understand its structure and behavior. Since Follina is tied to malicious Office document processing, one important clue was that the document contained references that ultimately led to remote content retrieval and exploitation. From there, I focused on the investigation-style questions in the lab, including file hashing, file type identification, URL extraction, and the XML relationship file involved in storing that URL.
Another key part of the challenge was understanding the execution chain. The lab highlighted how the exploit used HTML processing and how the payload depended on a size threshold, which helped reinforce how small implementation details can have security consequences. I also had to identify the process targeted during execution and think about how a process-based detection rule could be built around the activity.
Tools and techniques
The most useful part of the lab was how it combined static inspection with threat-intelligence style research. I used VirusTotal to understand file details, relationships, and behavior, while also leaning on outside write-ups to confirm how the exploit chain worked in practice. That kind of workflow mirrors the way blue team analysts often move between sample analysis, enrichment, and detection development.
The lab also reinforced the value of document forensics. Modern Office documents are essentially containers of XML and related files, which means defenders can inspect them without opening the document normally. That is a useful habit to build because it helps reveal suspicious external references before execution ever happens.
What I learned
This challenge was a good reminder that effective defense is about pattern recognition and disciplined investigation. I came away with a better understanding of how malicious Office documents can be abused, how to extract indicators from a sample, and how to connect an exploit to MITRE ATT&CK-style execution techniques. It also strengthened my appreciation for event-based detection, especially when looking at process creation behavior like Windows Event ID 4688.
Most importantly, the lab felt practical. It wasn’t just about finding answers; it was about thinking like an analyst and building the habit of asking the right questions. For anyone working toward SOC or incident response work, this is exactly the kind of exercise that helps bridge the gap between theory and real investigation.
Final thoughts
I enjoyed this challenge because it blended malware analysis, incident response, and detection thinking into one workflow. Completing Follina was a useful checkpoint in my own learning path, and I’d recommend it to anyone who wants to strengthen their blue-team fundamentals. Based upon this one challenge, Blue Team Labs Online is going to become a stable in my arsenal of tools I have been using to continue my cybersecurity journey.
Comments
Join the discussionNo comments yet. Be the first to comment.
