Question Q-5765 A SOC analyst receives a SIEM alert for a successful…
2 comments · last active May 13, 2026
By Jordan Blake · Updated May 25, 2026
| Questions | 25 |
| Passing Score | 75% |
| Format | 100% Multiple Choice |
| Sessions Logged | 658 |
| Your progress | Log in / Register to track times taken, best score, questions mastered, and coverage on this quiz. |
| Rating |
Uncategorized25 questions
Log in to post a comment, reply, or expand a question.
Compliance scans (PCI, HIPAA) vs credentialed vuln scan — authenticated finds missing patches inside host.
Agent-based vs agentless scanning — agents see installed software versions accurately.
Exploit available in wild bumps priority over CVSS alone. CISA KEV catalog is real-world cheat sheet.
Critical vuln on DMZ web server — patch window vs compensating WAF rule vs asset isolation. Risk-based prioritization.
Phishing triage: sandbox attachment, check headers, search O365 for same subject across users, pull IOCs to block.
User-reported phish button integrations help — still validate before mass delete legit mail.
Threat intelligence feeds: STIX/TAXII, sharing ISACs. Strategic vs operational vs tactical intel — match to audience.
Enrich SIEM alert with TI hash reputation before closing as benign.
False positive tuning: adjust threshold, enrich with context (patch level, asset owner), don't blanket disable rule.
SOAR playbooks need human approval for destructive actions — isolate host yes, delete mailbox no without review.
Forensics order: capture volatile (RAM, connections) then disk. Chain of custody documentation for legal.
Order of volatility: cache → RAM → disk → remote logs → archival tape.
Threat hunting = hypothesis-driven search, not waiting for alerts. Look for LOLBins (PowerShell, wmic) baselined against normal.
IOC vs TTP — behaviors persist when attackers rotate hashes. ATT&CK mapping helps structure hunts.
Lessons learned / post-incident review: what detection failed, what playbook worked, update runbooks and detection rules.
CySA is analyst not manager — focus on technical remediation and metrics (MTTD/MTTR), not budget slides.
Catalog listing of the 5 preview questions for this quiz.
A vulnerability assessment reveals a server running software with a CVSS base score of 7.5. However, a threat intelligence feed indicates this CVE is being actively exploited in the wild by nation-state actors targeting your industry. How does this intelligence affect prioritization?
CVSS base scores don't account for active exploitation context. CISA's Known Exploited Vulnerabilities (KEV) catalog tracks CVEs actively exploited in the wild. Intelligence showing targeted exploitation by relevant threat actors dramatically elevates practical risk beyond what CVSS indicates.
A SOC analyst receives a SIEM alert for a successful brute-force login to an admin account. The login came from an IP address in Russia, while the legitimate admin works from the US. Which action should the analyst take FIRST?
Confirmed brute-force success from an anomalous location requires immediate containment. Disabling the compromised account stops ongoing unauthorized access. Preserving logs ensures forensic evidence. Contacting the admin should happen during investigation, but account containment comes first.
An analyst is reviewing a vulnerability scan report. A critical vulnerability (CVSS 9.8) is found on a server with no internet access, protected by a firewall, requiring authenticated access from an IP-restricted management VLAN. What should the analyst recommend?
Contextual risk analysis uses environmental score modifications. A CVSS 9.8 vulnerability in an isolated environment with multiple compensating controls has lower actual exploitability. However, it should still be patched in a planned maintenance window. Permanent risk acceptance for a critical CVE is inappropriate.
A security analyst is investigating a compromise and runs the command `netstat -ano` on a Windows system. What information does this provide for the investigation?
`netstat -ano` shows all network connections (-a), numerically (-n), and the owning process ID (-o). This is critical for incident response: investigators correlate suspicious outbound connections (to C2 IPs) with the PID, then identify the process in Task Manager to find malware.
An analyst wants to understand the scope of a potential insider threat by analyzing which files a specific user accessed over the past 30 days. Which data source is MOST relevant?
Windows Security Event ID 4663 (An attempt was made to access an object) logs when files/objects are accessed, by which user, from which process, when. Combined with file auditing enabled on sensitive shares, this provides a complete audit trail of file access for insider threat investigations.
Brute force on admin after hours → disable account, block source IP, check auth logs for success before lockout, force MFA reset.
Containment before eradication — don't leap to reimage if you still need forensic timeline from SIEM.