The first 24 hours after a ransomware attack can determine how effectively your organization recovers. This guide walks through a structured hour-by-hour response plan, covering containment, negotiation preparation, first contact, and recovery. Learn how to maintain clarity, protect leverage, and minimize chaos when every decision counts.
When a security incident hits, missing or messy telemetry can cripple detection and response. Many SOC teams either drown in...
In the fast-paced and ever-evolving field of cybersecurity, landing your dream job requires not only technical prowess but also the...
Cybersecurity professionals face unique pressures: relentless threats, constant vigilance, and the emotional toll of protecting others. This blog explores how factors like burnout, alert fatigue, imposter syndrome, and isolation impact mental health, while offering strategies for resilience. It also introduces a free Security Blue Team course designed to help individuals...
From understanding the foundations of ransomware to engaging in negotiation simulations, students will gain practical insights into managing cyber extortion scenarios.
This blog series will explore Security Blue Team's adventure into the reverse engineering of a novel SmartLoader malware variant. This malware was discovered during our research into Belsen Group's high-profile FortiGate leak. This leak was advertised as containing a list of affected companies with associated configuration data from their FortiGate...
We need a suitable environment to detonate the malware in a repeatable fashion. This environment should allow us to substitute our mock APIs and host to ensure the malware operates as close to real as possible.
The Black Basta ransomware gang recently made headlines for all the wrong reasons when someone using the online handle “ExploitWhispers” shared internal chat logs of the group with the public — close to a year’s worth of messages in a JSON file.
This write-up is a POC (Proof of Concept) to demonstrate a potential vulnerability in GitHub and Discord that can be exploited. You are free to verify the issue, as we encourage the developers at GitHub and Discord to properly secure their systems to lower the risk of an exploit.
It started like many incident response cases: an urgent Security Operation Center (SOC) alert.
