Interview scorecard for cybersecurity analysts, with anchors for each competency
On this page
- Which competencies should a cybersecurity analyst scorecard cover?
- The scorecard: weights and what a 1, 3 and 5 look like
- Copy-ready cybersecurity analyst scorecard
- What should each interviewer ask, and what counts as evidence?
- Two work samples that produce scoreable evidence
- A filled example
- How do you adjust it for the seat and the level?
- Mistakes specific to scoring cybersecurity analysts
- Where does this scorecard fit in the hiring process?
- Questions people ask
A cybersecurity analyst interview scorecard should score six things: alert triage and investigation method, incident response and containment, vulnerability and threat risk judgment, detection and tool fluency, written escalation, and collaboration with IT and the business. Below is a copy-ready scorecard with example weights, what a 1, 3 and 5 look like on a 1–5 scale, two work samples and a filled example. Certifications such as Security+ or CISSP and any required clearance are pass/fail checks, never points, and how the candidate handles access to data they should not see is a gate, not a weighted row.
The five points follow the 1–5 interview rating scale: 1 is no evidence or evidence of the opposite, 3 is a clear example that meets the bar for the level, 5 is rare. The layout comes from the interview scorecard template. The full loop, with an eight-alert triage packet, a ransomware tabletop and a detection-writing exercise, is in the interview guide for cybersecurity roles; this page adds the anchors each row is scored against and two different exercises, a reported phishing email and a vulnerability ranking. The scorecard builder prints a 1–4 version if your team uses four points.
Which competencies should a cybersecurity analyst scorecard cover?
- Alert triage and investigation method. Do they look for the one fact that settles an alert, connect related events, and close false positives with a reason?
- Incident response and containment. Do they contain first without destroying evidence, scope how far it spread, and know who must be told?
- Vulnerability and threat risk judgment. Do they rank findings by exploitation and exposure, not by severity score alone?
- Detection and tool fluency. Can they query the SIEM or EDR your team uses, tune a noisy rule and say how a detection could be evaded?
- Written escalation and reporting. Could a tier 3 analyst or an IT owner act on their note without calling them?
- Collaboration and learning. Do they work with IT and engineering to get fixes made, and keep their skills current in a field that changes monthly?
The scorecard: weights and what a 1, 3 and 5 look like
Weights are an example for a mid-level SOC analyst at a company with its own security team. Agree yours with the security manager at intake and lock them before the first interview; weighted interview scorecard shows how.
| Competency | Weight | 1 looks like | 3 looks like | 5 looks like |
|---|---|---|---|---|
| Alert triage and investigation method | 25% | Escalates everything, or closes alerts without checking a single log line. | Names the one extra fact that settles each alert, checks it, closes benign alerts with a reason and links related events on the same host or user. | All of a 3, plus finds the quiet, low-severity signal that matters most and explains the attacker behavior it fits. |
| Incident response and containment | 20% | Wipes the machine at once, or keeps investigating while the attacker still has access. | Contains (isolate the host, disable the account, revoke sessions) while keeping evidence, scopes other affected systems and follows the incident plan for who is told. | Ran or led part of a real incident, set update times for stakeholders, and drove the fixes that came out of the review. |
| Vulnerability and threat risk judgment | 15% | Ranks findings by severity score only. | Weighs known exploitation, internet exposure and what the asset holds alongside severity, and can defend the order to an IT owner. | Changed how a team prioritizes (exposure data, an exploitation feed, an asset tier) and can say what got fixed faster as a result. |
| Detection and tool fluency | 15% | Knows tool names but cannot describe a query or a rule they wrote or tuned. | Writes or reads a basic query in the team's tool, tunes a noisy rule without blinding it, and names one way a detection fails. | Wrote detections others rely on, mapped to attacker techniques, with false-positive rates they tracked and reduced. |
| Written escalation and reporting | 15% | "Suspicious activity on host, please check." | What happened, the evidence, the scope so far, what was done and the recommended next step, in plain words. | Writes for two audiences at once: a technical note an analyst can act on and a two-line summary a manager can repeat. |
| Collaboration and learning | 10% | Files tickets at IT and moves on; describes users as the problem. | Gives IT owners clear asks and priorities, helps with the fix, and names something learned recently and applied at work. | Built a working relationship that changed how fast fixes ship, or taught a skill the team now uses. |
Copy-ready cybersecurity analyst scorecard
Candidate: [name] Role: [SOC analyst / incident responder / vulnerability analyst], [tier]
Interviewer: [name] Stage: [screen / triage / tabletop / phishing / vulnerability ranking / manager]
Pass/fail (checked before scoring)
Ethics with sensitive access: stopped, reported, did not browse: [ ] pass [ ] fail
Certification required by the job or contract (e.g. Security+): [ ] verified [ ] n/a
Clearance required by the contract: [ ] verified [ ] n/a
Can meet the shift and on-call schedule in the job description: [ ] yes [ ] no
Alert triage and investigation method (25%) Score 1-5: [ ]
Evidence: [fact sought per alert, events linked, false positives closed with reasons]
Incident response and containment (20%) Score 1-5: [ ]
Evidence: [containment steps, evidence kept, scope, who was told]
Vulnerability and threat risk judgment (15%) Score 1-5: [ ]
Evidence: [ranking given and the reasons]
Detection and tool fluency (15%) Score 1-5: [ ]
Evidence: [query read or written, a rule tuned, how it fails]
Written escalation and reporting (15%) Score 1-5: [ ]
Evidence: [escalation note from the phishing exercise]
Collaboration and learning (10%) Score 1-5: [ ]
Evidence: [a fix driven with IT, something learned and applied]
Weighted score: sum of (weight x score) / sum of weights scored = [ ]
Recommendation: [Strong yes / Yes / No / Strong no]
What should each interviewer ask, and what counts as evidence?
The table gives the 1, 3 and 5. Here is the question that tests each row and what a 2 and a 4 sound like.
Alert triage and investigation method
Ask: the guide's triage packet, or "Walk me through the last alert you escalated. What made it real?"
- 2: Reaches the right verdict but cannot say which evidence decided it.
- 4: Clear evidence for each verdict, and checks whether the same user or host appears in other alerts.
Incident response and containment
Ask: "A user's mailbox is sending invoices with changed bank details to customers. What do you do in the first hour?" A useful reference for the anchors is NIST's SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile (April 2025, superseding Rev. 2 from 2012; checked November 2026). Score the habit the candidate describes, not whether they cite it. More in interview questions for composure under pressure.
- 2: Resets the password but does not revoke sessions, check forwarding rules or look for other affected mailboxes.
- 4: Contains, scopes, preserves the logs, and raises the customer and finance impact with the incident lead early.
Vulnerability and threat risk judgment
Ask: the vulnerability ranking below. Evidence for a 3 or higher: the candidate uses known exploitation as an input. CISA calls its Known Exploited Vulnerabilities catalog "the authoritative source of vulnerabilities that have been exploited in the wild" and says organizations should use it as an input to their vulnerability management prioritization (as of November 2026).
- 2: Mentions exposure but still puts the highest score first in every case.
- 4: Ranks by exploitation, exposure and asset value, and proposes a compensating control where patching must wait.
Detection and tool fluency
Ask: "Tell me about a rule you tuned because it was too noisy. What did you change, and how did you make sure it still caught the real thing?" For a hands-on version, use the guide's detection exercise.
- 2: Tuned by suppressing whole users or hosts, with no check of what was lost.
- 4: Narrowed the logic, tested against past true positives, and documented the change.
Written escalation and reporting
Ask: the escalation note at the end of the phishing exercise. More in interview questions for written communication.
- 2: Accurate but missing scope or the recommended next step.
- 4: Complete and short, with times, indicators and a clear ask of the reader.
Collaboration and learning
Ask: "Tell me about a finding IT pushed back on. What happened?" and "What have you learned in the last six months, and where did you use it?"
- 2: Escalated over the IT owner's head without first understanding the objection.
- 4: Found a fix or a compensating control the owner could live with, and helped test it.
Two work samples that produce scoreable evidence
Both are invented and the same for every candidate. Never use real emails, logs or scan results; they contain personal data and internal details. Tell candidates the format in advance and how to ask for an adjustment; see ADA accommodations in interviews.
Reported phishing email (20 minutes). Show an invented email a finance clerk reported, with its headers: the display name is the CEO's, the sending domain is a lookalike with one letter changed, sender authentication failed, the reply-to address is a free webmail account, and a "View invoice" link goes to a sign-in page on an unrelated domain. Tell the candidate that mail logs show the same message reached 14 people and that one of them clicked the link. Brief: "What is your verdict, what do you do, and write the escalation note."
What to listen for: reading the headers rather than the display name; finding everyone who received it and removing it from mailboxes; blocking the sender domain and the link; for the person who clicked, checking for a sign-in from an unusual place, resetting the password, revoking sessions and reviewing multifactor changes and mailbox rules; a short reply to the clerk thanking them for reporting; and an escalation note with times, indicators and scope. This scores triage and investigation, incident response and written escalation.
Vulnerability ranking (15 minutes). Hand over five invented findings: a critical-severity flaw on a test server with no internet access; a medium-severity flaw on the internet-facing VPN appliance that is listed as exploited in the wild; a high-severity flaw in a browser on 400 laptops with a vendor patch available; a high-severity flaw on a server that holds customer records, with no patch yet; and a low-severity information leak on the marketing website. Brief: "You can get IT to fix two things this week. Which two, in what order, and what do you do about the rest?"
What to listen for: the exploited VPN flaw first because it is exposed and known to be used by attackers; a case for either the laptop browsers (wide exposure, easy patch) or the customer-data server (a compensating control until a patch exists); the test server lower despite its score; and a plan with dates for the rest. Any well-argued order with exploitation and exposure in it can score a 3. This scores vulnerability and threat risk judgment and collaboration.
A filled example
A made-up candidate for a mid-level SOC analyst at a healthcare company, scored after the guide's triage packet and tabletop, these two exercises and the manager interview:
Pass/fail: ethics gate passed (described reporting an exposed file share instead of opening it); Security+ verified with CompTIA.
Alert triage and investigation method — 3. Closed the benign alerts with reasons and linked the phishing click to the download; did not flag the new admin account on the domain controller.
Incident response and containment — 4. In the phishing exercise, revoked the clicker's sessions and checked for new forwarding rules before resetting the password.
Vulnerability and threat risk judgment — 4. Put the exploited VPN flaw first and proposed restricting access to the customer-data server until a patch arrived.
Detection and tool fluency — 2. Strong user of the EDR console but had not written or tuned a detection.
Written escalation and reporting — 3. Note had times, indicators and scope; the recommended next step was vague.
Collaboration and learning — 3. Described agreeing a patch window with a server owner after a first refusal.
Weighted score: 3.20 ((3×25 + 4×20 + 4×15 + 2×15 + 3×15 + 3×10) ÷ 100). Recommendation: Yes. Sound response and risk judgment; detection writing is the gap, so put a tuned detection in the first 90 days.
How do you adjust it for the seat and the level?
| Seat or level | Adjustment |
|---|---|
| Tier 1 SOC analyst | Raise triage to 30% and written escalation to 20%; score detection on reading queries, not writing them. |
| Incident responder | Raise incident response to 30%; add forensic evidence handling to its anchors. |
| Vulnerability management analyst | Raise risk judgment to 30% and collaboration to 20%; replace detection with a row on reporting remediation progress. |
| Governance, risk and compliance analyst | Replace triage and detection with rows on control assessment and audit evidence; a different seat, so consider a separate scorecard. |
| Junior or career changer | Accept home lab, capture-the-flag or course examples; score method and writing at full weight and accept smaller scope for a 3. |
| Senior analyst or lead | Add a row on mentoring and running an incident; a 3 on collaboration needs a change to how the team works. |
Mistakes specific to scoring cybersecurity analysts
| Mistake | Why it fails | Fix |
|---|---|---|
| Points for certifications | An exam pass shows study, not triage judgment | Pass/fail line only when the job or contract requires it |
| Scoring tool names | Query languages and consoles change; method carries over | Score how they reach a verdict and tune a rule |
| Rewarding "escalate everything" | Floods the next tier and hides the real incident | Score the evidence behind each close and each escalation |
| Adding a citizenship requirement because the work feels sensitive | The Justice Department's IER FAQ says an employer may restrict hiring to U.S. citizens only when a law, regulation, executive order or government contract requires it (checked November 2026) | Require it only when the contract does; see citizenship status discrimination in hiring |
| "Young and hungry" or "digital native" as a plus | Both are proxies for age, which the EEOC lists among protected bases (40 or older) | Score current practice and learning shown in the exercises |
| Asking about family to judge night shifts | Not job-related and invites a discrimination claim | State the shift pattern and ask every candidate whether they can work it |
Where does this scorecard fit in the hiring process?
The cybersecurity analyst phone screen places the candidate by SOC tier and runs the shift and clearance knockouts, and the screening questions cover tools and incident stories. Verify any required certification or clearance as a pass/fail line (see how to verify CompTIA certifications, how to verify a CISSP certification and how to verify a security clearance), keep the rows consistent with the must-haves in the cybersecurity analyst job description template, and carry the weakest row into the 30-60-90 day plan for cybersecurity analysts.
If you hold the tabletop or the manager interview on a video call with Interview Signal, the desktop app we make, these rows can become the scorecard areas in its kit, each with a weight of 1, 2 or 3 and rubric lines on a 1–10 scale; each score carries the candidate's own quotes, checked word for word against the transcript, and an area with no surviving quote is capped at 5 and marked "Probe further" (see how the scorecard with verified quotes works). It reads only the words spoken, so a query typed in a shared screen is scored from what the candidate says about it. Whatever you use, have each interviewer score before reading the others, then compare in a calibration session.
Questions people ask
What should a cybersecurity analyst interview scorecard measure?
Six things for most SOC and response seats: alert triage and investigation method, incident response and containment, vulnerability and threat risk judgment, detection and tool fluency, written escalation, and collaboration with IT and the business. Weight them for the seat, and write what a 1, 3 and 5 sound like for each row before the first interview.
Should Security+, CySA+ or CISSP add points on a cybersecurity analyst scorecard?
No. If the job or a contract requires a certification, verify it with the issuer as a pass/fail line before scoring. The scored rows should measure how the candidate triages, investigates and communicates, which an exam does not show on its own.
How do you score a security candidate's ethics?
Make it a pass/fail gate rather than a weighted row. Ask every candidate what they did when they had access to something they were not supposed to look at or found data they did not expect. Stopping, reporting and not browsing passes; looking around because they could fails, whatever the total.
How is a cybersecurity analyst scorecard different from a DevOps or IT support scorecard?
An IT support scorecard weights fixing users' problems and a DevOps scorecard weights shipping and running systems safely. A cybersecurity analyst scorecard weights deciding which signals are real, how far an incident has spread, which vulnerabilities to fix first, and writing an escalation another analyst can act on without a call.