Security Concepts · Topic 3 of 8
Core Security Terms
Define threat intelligence, threat hunting, malware analysis, threat actors, run book automation, reverse engineering, anomaly detection and DevSecOps.
- 5 min
- Threat intelligence is information about threats used to make decisions.
- A threat actor is the person or group behind an attack.
- Threat hunting is proactive and starts without an alert.
What it is
This page defines nine terms that security operations teams use every day.
They fall into three groups. Some describe how a team learns about attackers, some describe how it studies and detects attacks, and some describe how it builds and responds more safely.
You need to recognise each term from a short description, so focus on what each one does and how it differs from its neighbours.
How it works
Each term names one activity in the cycle of learning, looking, analysing and responding.
Threat intelligence and threat actors
Threat intelligence (TI) is information about threats that helps defenders make decisions. It includes indicators such as bad IP addresses, file hashes and domains. It also includes the methods attackers use and who is behind them.
A threat actor is the person or group behind an attack. Examples include criminal gangs after money, nation state groups after secrets, hacktivists with a cause, and insiders with access.
Threat hunting
Threat hunting is a proactive search for attackers who have not triggered an alert. The hunter starts from an idea, such as an attacker technique or a piece of intelligence, and looks through the data for signs of it.
Normal monitoring waits for an alert. Hunting assumes that something may already be inside and goes looking.
Malware analysis and reverse engineering
Malware analysis studies a suspicious file to learn what it does. There are two approaches:
- Static analysis examines the file without running it, for example by reading strings and checking its hash.
- Dynamic analysis runs the file in a safe, isolated environment and watches its behaviour.
Reverse engineering goes deeper. The analyst works back from the compiled program toward its logic, often with a disassembler or debugger. It is used to understand how a piece of malware works or to find flaws in software.
Run book automation (RBA)
A run book is a written set of steps for handling a situation, such as a phishing report. Run book automation turns those steps into automated actions.
It cuts response time and gives a consistent result every time. SOAR platforms are a modern form of this idea.
Sliding window anomaly detection
Anomaly detection looks for activity that differs from normal. A sliding window measures activity over a recent span of time, such as the last hour, and the window moves forward as time passes.
The tool compares the current window to a baseline. If logins per hour suddenly jump far above the usual level, the window raises an alert. Because the window slides, old activity drops out and recent activity is always counted.
Threat modeling
Threat modeling is a structured way of finding what could go wrong with a system, before it is attacked. The team identifies assets, entry points and possible attackers, then decides which threats matter most and what controls to add.
It is best done early in design, when changes are cheap.
DevSecOps
DevSecOps builds security into the software delivery process instead of adding it at the end. Security checks run automatically as code is written, built, tested and deployed. Developers, operations and security staff share responsibility.
| Term | One line summary |
|---|---|
| Threat intelligence | Knowledge about threats that informs decisions |
| Threat hunting | Proactive search for undetected attackers |
| Malware analysis | Studying a file to learn what it does |
| Threat actor | The person or group behind an attack |
| Run book automation | Automating written response steps |
| Reverse engineering | Working back from compiled code to its logic |
| Sliding window anomaly detection | Comparing recent activity to a normal baseline |
| Threat modeling | Finding likely threats during design |
| DevSecOps | Security built into the delivery pipeline |
What to remember for the exam
Eight facts cover most questions on this topic.
- Threat intelligence is information about threats used to make decisions.
- A threat actor is the person or group behind an attack.
- Threat hunting is proactive and starts without an alert.
- Static analysis does not run the file. Dynamic analysis does.
- Reverse engineering works back from compiled code to understand its logic.
- Run book automation turns written response steps into automated ones.
- A sliding window compares recent activity to a baseline.
- Threat modeling happens early, and DevSecOps builds security into the pipeline.
If the question says proactive search without an alert, the answer is threat hunting. If it says automating steps, think run book automation.
Common mistakes
These four errors appear often.
Calling threat hunting the same as alert handling. Alert handling reacts to something detected. Hunting looks for what was not detected.
Mixing up threat actor and threat. The actor is who, and the threat is the possible harm.
Thinking malware analysis always runs the file. Static analysis examines it without running it.
Treating DevSecOps as a final security review. It puts checks throughout the pipeline, not only at the end.
Threat intelligence feeds many of the other activities, because hunters, analysts and automation all use its indicators.
Check yourself
Work through these three questions.
How does threat hunting differ from normal alert monitoring?
Hunting is a proactive search for attackers who have not triggered an alert. Monitoring waits for an alert to fire.
What is the difference between static and dynamic malware analysis?
Static analysis examines a file without running it. Dynamic analysis runs it in a safe environment and watches what it does.
What does a sliding window add to anomaly detection?
It measures activity over a recent span of time that moves forward. The tool compares that window to a normal baseline and alerts on large differences.
Topic 3 of 8 in Security Concepts
Test yourself on Security Concepts
The full Cisco CCNA 200-201 CBROPS question bank has 754 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Cisco. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.