SOC Analyst
You live in the alert queue: triage, escalate, and keep watch.
Competency areas
- Defensive Cybersecurity
- Threat Analysis
- Incident Response
- Infrastructure Support
Aramis:Current Daily
A short reading list for a SOC Analyst, under 30 minutes per edition.
2026-09-28. 11 minutes in total
Canadian Centre for Cyber Security, 2026-09-27. Read, 5 min.
Why it matters for this role: When a NetScaler shows outbound connections nobody can explain or unusual administrative access, the Cyber Centre asks for that activity to be investigated, not closed as noise.
A Closer Look at Malware From the Macfinger ClickFix Campaign
SANS Internet Storm Center, 2026-09-25. Read, 6 min.
Why it matters for this role: Hold off on the AMOS Stealer label for Macfinger ClickFix alerts on macOS until the family is settled, as the SANS handler who examined a September 24 infection doubts that attribution.
Sample questions
Three real questions from this role's assessment, with the answer, the reasoning, and the NICE statement each one measures. The full assessment draws from hundreds like these.
Sample question 1
A SOC analyst at a regional healthcare network reviews six months of SIEM alert history as part of the team's routine trend analysis. Failed VPN login attempts have risen 40 percent month over month, but the failures are spread thin across many different accounts, so no single account crosses the existing brute-force alert threshold. What should the analyst do next?
- A.Close the observation without further review, since no single account crossed the alert threshold and the SIEM would have flagged a genuine attack.
- B.Force an immediate password reset for every VPN user across the organization before completing any further analysis of the login pattern.
- C.Aggregate the failed logins across accounts and time to check for a distributed, low-and-slow credential attack, then report the trend to leadership with supporting evidence.
- D.Hold the observation for the next scheduled quarterly compliance report, since it has not yet triggered an active incident ticket.
Show the answer and reasoning
Correct answer: C
Option C is correct because trend analysis and reporting requires aggregating signal across accounts and time to detect patterns invisible to single-account thresholds, then communicating the finding with evidence so leadership can act. Closing the observation is wrong because relying solely on the existing per-account threshold ignores the very pattern under analysis: a distributed attack is designed to stay under per-account thresholds. Forcing an organization-wide password reset is wrong because it is a disruptive, resource-intensive response taken before the analysis confirms whether the pattern is malicious, benign, or something else. Holding the observation for the next quarterly report is wrong because trend analysis and reporting exists to surface emerging risks proactively; deferring to a fixed reporting cadence defeats that purpose and risks letting a live credential attack continue unaddressed.
This question measures: T0164: Perform cyber defense trend analysis and reporting
Sample question 2
Meridian Financial's database administrator has standing authorization to export nightly reporting extracts to a vendor over SFTP, typically 1 to 3 GB per night. Reviewing six weeks of export logs, a SOC analyst notices the DBA has added a second export most nights, consistently sized between 4.6 and 4.9 GB, just under the DLP tool's 5 GB per-transfer alert threshold, and that these second exports are uploaded to a personal GitHub Gist rather than sent over the vendor SFTP path. Which finding is the strongest indicator that this is deliberate evasion of monitoring controls rather than a routine change in export volume?
- A.The DBA's combined nightly export volume, across both transfers, is higher than it was six months ago.
- B.The second export tends to occur on nights when the DBA also logged long hours in the ticketing system.
- C.The second export's size stays just under the DLP threshold night after night while it moves through an unmonitored personal channel.
- D.Both the vendor SFTP export and the second export draw from the same finance reporting tables the DBA normally works with.
Show the answer and reasoning
Correct answer: C
Option C is correct because a transfer size that consistently lands just under a known alert threshold, paired with routing through a channel outside DLP visibility, matches structuring: a deliberate attempt to stay under a control's detection line rather than an incidental pattern. Option A (rising total volume) could reflect a legitimate growth in reporting needs and says nothing about intent to evade a specific control. Option B (long hours coinciding with the export) is circumstantial and equally consistent with the DBA simply working late on the extra export, not evasion. Option D (both exports touching the same tables) is expected given the DBA's normal job function and has no bearing on whether the second export is unauthorized.
This question measures: K0785: Knowledge of insider threat tools and techniques
Sample question 3
A threat intelligence feed the organization subscribes to issues an urgent bulletin describing a new campaign that targets Java-based CI/CD orchestration servers through an exposed management port, and lists eight IP addresses as active command-and-control infrastructure. The SOC analyst must decide how to respond. The organization's CI/CD orchestrator runs on a different, non-Java platform, and ninety days of firewall logs show no inbound or outbound traffic involving any of the eight listed IPs. Applying threat intelligence principles and practices, what is the most appropriate next step?
- A.Record the eight indicators in the threat intelligence platform for future correlation, note that the targeted platform and the observed traffic pattern do not match the organization's environment, and prioritize the bulletin lower than intelligence describing threats to the organization's actual technology stack.
- B.Block the eight IP addresses at the network perimeter immediately and treat the bulletin as top priority, even though the campaign targets a different platform and no matching traffic has appeared, since any subscribed feed's command-and-control indicator should be acted on the same way regardless of relevance.
- C.Discard the bulletin and do not record the eight indicators anywhere in the threat intelligence platform, since the campaign targets a different CI/CD platform and no matching traffic has appeared, and a mismatch on both counts means the intelligence has no further value worth preserving.
- D.Forward the eight IP addresses to the network team for blocking, but make no changes to the CI/CD orchestrator's own exposed management interfaces, since the platform mismatch and ninety days without matching traffic together already confirm the environment was never exposed to this campaign.
Show the answer and reasoning
Correct answer: A
Good threat intelligence practice weighs a bulletin's relevance and confidence against the organization's own environment rather than reacting to every published indicator identically, so confirming the platform mismatch and the absence of matching traffic, then prioritizing the bulletin below intelligence that actually matches the deployed stack, is the correct response; recording the indicators rather than dropping them preserves the ability to correlate them if the same infrastructure resurfaces in a campaign that does match the organization's technology. Option B acknowledges the same platform mismatch and lack of matching traffic, but spends immediate blocking effort and top-priority attention anyway, treating a raw indicator from a subscribed feed as inherently actionable regardless of relevance, which is the kind of reaction that produces alert fatigue without reducing real risk. Option C also notes both mismatches but concludes the intelligence has no value at all, discarding the eight indicators as corroborating data that could matter later if the same command-and-control infrastructure appears in a campaign that does target the organization's actual stack. Option D treats the platform mismatch and ninety days without matching traffic as proof the environment was never exposed, which confuses an absence of observed past traffic with an absence of exposure, and skips the more relevant question of whether the organization's own CI/CD platform has an analogous exposed management interface worth checking.
This question measures: K1009: Knowledge of threat intelligence principles and practices
Job description templates
Three ready-to-edit drafts for hiring managers and recruiters: copy one, replace the bracketed lines, and post it. Responsibilities and requirements are drawn from the same NICE statements this role is measured against.
Statements use the official NICE Framework wording, which is published in English.
SOC Analyst: Junior
We are hiring a junior SOC Analyst. You live in the alert queue: triage, escalate, and keep watch. At this level you take on well-defined parts of the work, with senior colleagues to learn from, and grow into the rest.
[Company] provides [what you do]. The security function is [size and shape: e.g., a five-person team reporting to the CTO]. Replace this paragraph with your own.
Responsibilities
- Perform cyber defense trend analysis and reporting
- Determine causes of network alerts
- Recommend computing environment vulnerability corrections
- Identify network mapping and operating system (OS) fingerprinting activities
- Coordinate incident response functions
- Evaluate threat decision-making processes
- Facilitate continuously updated intelligence, surveillance, and visualization input to common operational picture managers
- Identify intelligence gaps and shortfalls
- Pair with senior colleagues and grow through structured feedback.
- Document what you do so the team learns with you.
Required knowledge
- Insider threat tools and techniques
- Threat intelligence principles and practices
- Programming language structures and logic
- Malware
- Intelligence fusion
- Cognitive biases
- Computer networking protocols
- Risk management processes
Skills
- Reporting malware
- Performing network traffic analysis
- Performing network traffic packet analysis
- Securing network communications
- Performing damage assessments
How to use this template
Copy the draft, replace every bracketed line, cut statements that do not apply to your opening, and add your compensation range and location policy. The statement lists come from the NIST NICE Framework v2.2.0, so candidates can be assessed against the same statements with Aramis:Insight.
SOC Analyst: Mid-level
We are hiring a mid-level SOC Analyst. You live in the alert queue: triage, escalate, and keep watch. You own this work day to day and work closely with the rest of the security team.
[Company] provides [what you do]. The security function is [size and shape: e.g., a five-person team reporting to the CTO]. Replace this paragraph with your own.
Responsibilities
- Perform cyber defense trend analysis and reporting
- Determine causes of network alerts
- Recommend computing environment vulnerability corrections
- Identify network mapping and operating system (OS) fingerprinting activities
- Coordinate incident response functions
- Evaluate threat decision-making processes
- Facilitate continuously updated intelligence, surveillance, and visualization input to common operational picture managers
- Identify intelligence gaps and shortfalls
- Identify cyber threat tactics and methodologies
- Review cyber defense service provider reporting structure
- Determine how threat activity groups employ encryption to support their operations
- Scope analysis reports to various audiences that accounts for data sharing classification restrictions
Required knowledge
- Insider threat tools and techniques
- Threat intelligence principles and practices
- Programming language structures and logic
- Malware
- Intelligence fusion
- Cognitive biases
- Computer networking protocols
- Risk management processes
- Cybersecurity laws and regulations
- Cybersecurity policies and procedures
- Privacy laws and regulations
- Privacy policies and procedures
Skills
- Reporting malware
- Performing network traffic analysis
- Performing network traffic packet analysis
- Securing network communications
- Performing damage assessments
- Interfacing with customers
- Performing packet-level analysis
- Conducting non-attributable research
How to use this template
Copy the draft, replace every bracketed line, cut statements that do not apply to your opening, and add your compensation range and location policy. The statement lists come from the NIST NICE Framework v2.2.0, so candidates can be assessed against the same statements with Aramis:Insight.
SOC Analyst: Senior
We are hiring a senior SOC Analyst. You live in the alert queue: triage, escalate, and keep watch. You set the direction for this work, mentor the people who do it, and answer for its results.
[Company] provides [what you do]. The security function is [size and shape: e.g., a five-person team reporting to the CTO]. Replace this paragraph with your own.
Responsibilities
- Perform cyber defense trend analysis and reporting
- Determine causes of network alerts
- Recommend computing environment vulnerability corrections
- Identify network mapping and operating system (OS) fingerprinting activities
- Coordinate incident response functions
- Evaluate threat decision-making processes
- Facilitate continuously updated intelligence, surveillance, and visualization input to common operational picture managers
- Identify intelligence gaps and shortfalls
- Identify cyber threat tactics and methodologies
- Review cyber defense service provider reporting structure
- Determine how threat activity groups employ encryption to support their operations
- Scope analysis reports to various audiences that accounts for data sharing classification restrictions
- Identify potential threats to network resources
- Resolve cyber defense incidents
- Coordinate technical support to enterprise-wide cybersecurity defense technicians
- Validate network alerts
- Mentor junior team members and review their work.
- Represent this function to leadership and to auditors or clients.
- Set standards, select tooling, and own the roadmap for this area.
Required knowledge
- Insider threat tools and techniques
- Threat intelligence principles and practices
- Programming language structures and logic
- Malware
- Intelligence fusion
- Cognitive biases
- Computer networking protocols
- Risk management processes
- Cybersecurity laws and regulations
- Cybersecurity policies and procedures
- Privacy laws and regulations
- Privacy policies and procedures
- Cybersecurity principles and practices
- Privacy principles and practices
Skills
- Reporting malware
- Performing network traffic analysis
- Performing network traffic packet analysis
- Securing network communications
- Performing damage assessments
- Interfacing with customers
- Performing packet-level analysis
- Conducting non-attributable research
- Communicating complex concepts
- Collaborating with others
How to use this template
Copy the draft, replace every bracketed line, cut statements that do not apply to your opening, and add your compensation range and location policy. The statement lists come from the NIST NICE Framework v2.2.0, so candidates can be assessed against the same statements with Aramis:Insight.
Related roles
Roles with similar work or at a similar career stage. Each has its own job description templates and a free assessment.