Detecting Device Attacks | AP Cybersecurity
Detecting Attacks on Devices: Indicators of Compromise
Topic 4.4 asks how to detect attacks against devices by watching for indicators of compromise: signs that a device has been attacked, such as unexpected processes, performance changes, or unusual network activity.
Contents
How device attacks are detected
Detection looks for indicators of compromise: a device running slowly, unknown processes, files that changed unexpectedly, new accounts, or traffic to suspicious addresses. Anti-malware alerts, system logs, and monitoring tools surface these signs.
Some malware actively hides, like a rootkit, so detection may rely on behavior and integrity checks rather than spotting a known file.
A laptop suddenly runs slowly, has an unfamiliar process, and is sending data to an unknown server. What do these suggest?
Reveal answer
Indicators of compromise. Together they point to a device attack, such as spyware or a RAT, even before the specific malware is named.
Detection is about indicators and evidence, not prevention. The question often asks which sign or control would reveal an attack.
Choosing a detection method
Detection methods are evaluated on trade-offs: how fast they detect, how much they cost, and how accurate they are (false positives and false negatives). No method is perfect, so organizations pick controls that fit the device's risk.
This mirrors the network-detection trade-offs from Unit 3: speed, cost, and error rates drive the choice.
Why might a high-value workstation justify a more expensive, faster detection method than a kiosk?
Reveal answer
Risk. The workstation's higher value and sensitivity make faster, more accurate detection worth the added cost, while a low-risk kiosk may not.
Spotting a quiet infection
Spyware and RATs often run silently, but they leave indicators: unexpected processes, performance drops, and traffic to unknown servers. Monitoring surfaces these signs so teams can respond.
Several indicators together point to compromise.
Key Terms
| Indicator of compromise | An observable sign a device was attacked. |
| Anti-malware alert | A warning from scanning software. |
| System log | A record of actions used to spot anomalies. |
| False positive | A benign event flagged as an attack. |
Match It Up
Common Mistakes
Confusing detection with prevention
Detection reveals an attack; prevention stops it. Topic 4.4 is about revealing.
Expecting one obvious sign
Indicators often appear together; a single symptom may be benign.
Forgetting hidden malware
Rootkits hide, so detection may need behavior or integrity checks.
Ignoring trade-offs
Methods differ in speed, cost, and accuracy; match them to risk.
Check for Understanding
Frequently Asked Questions
Get in Touch
Whether you're a student, parent, or teacher — I'd love to hear from you.
Just want free AP CS resources?
Enter your email below and check the subscribe box — no message needed. Students get daily practice questions and study tips. Teachers get curriculum resources and teaching strategies.
Message Sent!
Thanks for reaching out. I'll get back to you within 24 hours.
Prefer email? Reach me directly at [email protected]