SOC and defensive security glossary
The terms that show up in a SOC analyst job description, defined plainly and linked to where you can practise them.
Alert triage
The first assessment of a security alert: deciding whether it describes real malicious activity, how serious it is and what happens next (close it, investigate further or escalate). Good triage rests on evidence: what triggered the rule, which asset is involved and what the surrounding logs show. It is the core task of a Tier 1 SOC analyst.
Practise it in: SOC simulators →
C2 (Command and Control)
The channel an attacker uses to send instructions to compromised machines and to receive data from them. Malware typically contacts its C2 server at intervals, a pattern known as beaconing, which is one of the things network analysts look for in traffic.
Practise it in: Network Security path →
EDR (Endpoint Detection and Response)
Software installed on laptops and servers that records what happens on them (processes started, files written, network connections), detects suspicious behaviour and lets an analyst respond remotely, for example by isolating the machine. Where antivirus mainly blocks known malicious files, EDR records behaviour so that an intrusion can be investigated.
Practise it in: Threat Hunting path →
False positive
An alert that fires on activity that turns out to be legitimate, such as an administrator's script that looks like an attacker's. A true positive is an alert on real malicious activity. Telling them apart, and writing down why, is most of what triage consists of; too many false positives cause alert fatigue, where real alerts get missed.
Practise it in: SOC simulators →
Incident response
The organised handling of a confirmed security incident: establishing its scope, containing it, removing the attacker's access, recovering the affected systems and recording what was learned. It begins where triage ends, when an alert has been judged to be real.
Practise it in: Free SOC analyst course →
IOC (Indicator of Compromise)
A piece of evidence that points to an intrusion: a file hash, an IP address, a domain, a URL, a registry key. IOCs are easy to search for and to share, but also easy for an attacker to change, which is why they are complemented with behaviour-based detection.
Practise it in: Free cybersecurity course →
MITRE ATT&CK
A public knowledge base, maintained by MITRE, that catalogues the tactics and techniques real attackers have been observed using. Defenders use it as a shared vocabulary: to label what an alert detected, to measure which techniques their tooling can and cannot see, and to plan threat hunts.
Practise it in: Threat Hunting path →
OSINT (Open Source Intelligence)
Intelligence gathered from publicly available sources: domain registration records, DNS, certificate transparency logs, public scan results, social networks. In defensive work it is used to investigate a suspicious domain or IP address without interacting with the attacker's server.
Practise it in: Phishing with OSINT path →
PCAP (packet capture)
A file containing network traffic recorded packet by packet, which can be opened in tools such as Wireshark. It lets an analyst reconstruct what two machines actually said to each other: which names were resolved, which connections were opened and how much data moved.
Practise it in: Free networking course →
Phishing
A message, usually an email, that impersonates a trusted sender to make the recipient hand over credentials, open a malicious attachment or make a payment. Analysing one means reading the headers to see where it really came from, inspecting links and attachments without opening them directly, and investigating the infrastructure behind it.
Practise it in: Phishing with OSINT path →
Sandbox
An isolated environment, usually a virtual machine, where a suspicious file can be run and observed without risk to real systems. The analyst records what the sample does: the processes it starts, the files it writes and the servers it tries to reach.
Practise it in: Windows Malware path →
SIEM (Security Information and Event Management)
A platform that collects logs from across an organisation (endpoints, servers, network devices, cloud services), stores them in a searchable form and applies detection rules that raise alerts. It is where a SOC analyst spends most of the day: reading the alert, then querying the logs around it. Splunk, Elastic and Microsoft Sentinel are common examples.
Practise it in: Free SOC analyst course →
Sigma rule
A detection rule written in an open, vendor-neutral format that describes suspicious activity in logs. A Sigma rule can be converted into the query language of different SIEM products, so a detection is written once and shared between teams that use different tools.
Practise it in: Threat Hunting path →
SOC (Security Operations Center)
The team, and the processes and tools around it, that monitors an organisation for security incidents, investigates the alerts its tools raise and coordinates the response. Analysts are usually organised in tiers: Tier 1 triages alerts, Tier 2 investigates what Tier 1 escalates, and Tier 3 handles the hardest cases and hunts for threats.
Practise it in: Free SOC analyst course →
Threat hunting
The proactive search for intrusions that no alert has flagged. A hunt starts from a hypothesis (a technique an adversary would plausibly use in this environment), checks the telemetry for evidence of it, and ends either in an incident or in a new detection rule. It differs from detection, which is automated and only catches what somebody anticipated.
Practise it in: Threat Hunting path →
TTPs (Tactics, Techniques and Procedures)
A description of how an adversary operates: the goal of each step (tactic), the general way it is achieved (technique) and the specific implementation (procedure). TTPs change far less often than IOCs, so detections written against them last longer.
Practise it in: Threat Hunting path →
