Entry-level SOC hiring managers increasingly ask candidates to prove they can triage a real alert queue, and a multiple-choice credential alone does not show that. TryHackMe's Security Analyst Level 1 (SAL1) is built around that gap: a computing fundamentals section followed by graded work in a simulated security operations centre where the candidate investigates alerts, decides true or false positive and writes case reports. This guide sets out what TryHackMe publishes about the exam format, attempts, pricing model and recommended preparation, then gives a study plan, decision guidance for candidates and employers, and the mistakes that cost candidates marks. It is written for people moving into Tier 1 SOC roles and for managers who fund or screen for the credential. Exam facts are as published on tryhackme.com, the TryHackMe help centre and the Credly badge page, checked November 2026; confirm details with TryHackMe before you buy.
This is an independent guide from NHI Mgmt Group, based on TryHackMe's public documentation as of November 2026. It is not sponsored or reviewed by TryHackMe. Exam details change, so confirm them against TryHackMe's current pages.
Key takeaways
- SAL1 is a practical exam with a knowledge gate. TryHackMe describes two parts: multiple-choice questions on computing foundations, then hands-on alert triage in its SOC Simulator, with case reports that are graded.
- You get a 24-hour window, not a fixed sitting. The certification page and the Credly badge both describe completing the exam at your own pace within a 24-hour period, in the browser.
- Two attempts are included. The help centre says a purchase includes two attempts valid for 12 months from purchase, with the free retake opening three days after you start the first attempt.
- Preparation maps to the SOC Level 1 path. TryHackMe recommends its SOC Level 1 learning path: 14 modules and 65 labs covering SIEM triage, phishing analysis, network and endpoint monitoring and threat intelligence.
- Report writing is scored, so treat it as a skill. Candidates who investigate well but document poorly lose marks; practise writing short, evidence-led case notes before the exam.
Who the certification is for
TryHackMe positions SAL1 as an entry-level blue team certification for anyone targeting a Tier 1 SOC analyst, blue team analyst or security operations role. Its help centre contrasts SAL1 with its certificates of completion: a certificate of completion is earned by finishing a learning path, while SAL1 is earned by passing an exam that combines a scenario-based assessment with a computing fundamentals assessment. TryHackMe says the credential was developed with Accenture and Salesforce, with Just Eat named as a validation partner, and that beta testing ran in October 2024 with SOC analysts from several organisations.
- Career changers: people coming from IT support, networking or non-technical roles who need evidence of hands-on triage, not just course completion. See the IT to Cyber Security Career Guide.
- Students and graduates: candidates with theory but no SOC experience who want a credential that includes a simulated alert queue.
- Junior analysts already in post: Tier 1 staff who want a structured benchmark of their triage and documentation habits.
- Hiring managers and SOC leads: people deciding whether to accept SAL1 as a screening signal or to fund it for new joiners.
It is not aimed at experienced analysts. TryHackMe's Security Analyst Level 2 (SAL2) is the follow-on, described as multi-stage investigations covering threat hunting, memory forensics and network traffic analysis for analysts with Tier 1 experience.
Exam format and domains
The exam runs in two parts. The first is a set of multiple-choice questions on computing foundations. TryHackMe's write-up on creating SAL1 explains why: weak computing fundamentals were a common reason candidates failed SOC interviews, and the questions align with its Pre-Security learning content. The second part is the SOC Simulator, which TryHackMe says took nine months to build. The Credly badge description refers to two SOC simulation assessments.
In the simulator, alerts arrive in real time. The candidate prioritises them, investigates in a SIEM (TryHackMe names Splunk), closes each alert as a true or false positive, decides whether to escalate, and writes a report that is assessed and graded. TryHackMe describes the aim as reflecting the pace and pressure of a real SOC.
| Item | What TryHackMe publishes | Where it is stated |
|---|---|---|
| Structure | Multiple-choice computing foundations, then practical triage in the SOC Simulator | Certification page; creating SAL1 article |
| Time | Own pace within a 24-hour period | Certification page; Credly badge |
| Delivery | In the browser, in live lab environments; the certifications hub states exams are not proctored | Certifications hub |
| Tooling named | SOC Simulator with Splunk for investigation | Creating SAL1 article |
| Graded outputs | Alert classification, escalation decisions and written case reports | Certification page; creating SAL1 article |
| Results | Instant results | Certification page |
| Credential | Verifiable digital certificate and Credly badge | Certification page; Credly |
The certification page lists six skill areas: computing foundations, cyber defence frameworks, detecting threats, alert triage, case report writing and analyst mindset. The pages checked in November 2026 do not publish a pass mark, a question count or a scoring rubric, so plan to perform well on every part rather than to a target score.
Mapping the skill areas to SOC work
| SAL1 skill area | What a Tier 1 analyst does with it | NIST CSF 2.0 outcome |
|---|---|---|
| Computing foundations | Reads process trees, network connections and log fields without guessing what they mean | DE.AE-02 (adverse events are analysed) |
| Cyber defence frameworks | Places an alert on the kill chain or an ATT&CK tactic to judge stage and urgency | DE.AE-02 |
| Detecting threats | Spots suspicious patterns in network, web, Windows and Linux telemetry | DE.CM-01 (networks and services are monitored) |
| Alert triage | Validates, prioritises and closes or escalates alerts | RS.MA-02 (incident reports are triaged and validated) |
| Case report writing | Records evidence, verdict and next action so Tier 2 can act without repeating the work | DE.AE-06 (information on adverse events is provided to authorised staff) |
| Analyst mindset | Asks what else would be true if the alert were real, and checks it | RS.AN-03 (analysis establishes what took place) |
The framework column is NHI Mgmt Group's mapping to help managers relate the credential to control outcomes; TryHackMe does not publish it. For the triage method behind these tasks, see the Alert Triage Guide.
Prerequisites and experience
The pages checked list no formal prerequisite, work experience requirement or application step. TryHackMe's certification guide names the SOC Level 1 path as the recommended preparation, and the creating SAL1 article ties the multiple-choice section to Pre-Security content. In practice, candidates do best when they can already:
- Networking: explain TCP and UDP, common ports such as 22, 53, 80, 443 and 3389, DNS resolution and what a normal HTTP request and response look like.
- Operating systems: read Windows Security log events (for example 4624 successful logon, 4625 failed logon, 4688 process creation) and Linux authentication logs.
- Search languages: write basic SIEM queries that filter by host, user, time window and field value, and pivot from one indicator to related events.
- Email: read message headers and identify SPF, DKIM and DMARC results when assessing a phishing alert.
- Writing: produce a short, structured note under time pressure.
Preparation plan
TryHackMe lists the SOC Level 1 path at 14 modules, 65 hands-on labs and an estimated 65 hours 29 minutes. The modules run from blue team introduction, SOC team internals and core SOC solutions (EDR, SIEM, Splunk and Elastic basics, SOAR), through cyber defence frameworks (Pyramid of Pain, Cyber Kill Chain, Unified Kill Chain, MITRE ATT&CK), phishing analysis, network traffic analysis and network security monitoring, web, Windows and Linux security monitoring, malware concepts and threat analysis tools, to SIEM triage and capstone challenges. Several modules include simulator scenarios, which are the closest practice to the exam.
- Weeks 1 to 2, fundamentals check: work through Pre-Security style material on networking, Windows and Linux until you can explain a packet capture and a process tree aloud. This protects the multiple-choice section.
- Weeks 3 to 5, tools and telemetry: complete the core SOC solutions, network traffic analysis, network security monitoring and the Windows and Linux monitoring modules. Keep a personal cheat sheet of event IDs, log locations and query patterns.
- Weeks 6 to 7, frameworks and phishing: complete cyber defence frameworks and phishing analysis. For each lab, write which ATT&CK tactic the activity sits in. See the MITRE ATT&CK Guide for Defenders.
- Weeks 8 to 9, triage under time: complete SIEM triage for SOC and every simulator scenario in the path. Time yourself per alert and write a case note for each, even when the lab does not ask for one.
- Week 10, capstones and rehearsal: complete the capstone challenges, then rehearse a full session: a block of fundamentals questions followed by several hours of continuous triage and reporting. Review your notes against the evidence and tighten wording.
Ten weeks at roughly eight to ten hours a week fits the path's published hours plus practice. Candidates with IT operations experience can compress weeks 1 to 2; complete beginners should extend them.
Exam day approach
- Plan the 24 hours: decide in advance when you will sit the fundamentals section, when you will triage and when you will rest. The window is generous, but fatigue degrades report quality.
- Triage before you deep dive: sort the queue by severity and asset value, then investigate. A missed critical alert costs more than a slow low-severity one.
- Write as you go: record timestamps, hosts, users, indicators and the query that proved each point while it is on screen.
- Justify every verdict: a false positive closure needs a reason as much as an escalation does.
Writing a case report that scores
TryHackMe grades written reports, and this is where otherwise capable candidates drop marks. A good Tier 1 case note follows a fixed shape so a reviewer can scan it in under a minute.
| Section | What to include | Common weakness |
|---|---|---|
| Summary | One or two sentences: what fired, on which host or user, and your verdict | Restating the alert title with no verdict |
| Evidence | Timestamps, source and destination, process or file names, hashes, the queries or log lines that support the verdict | Claims with no supporting log reference |
| Classification | True positive or false positive, with the reason; for true positives, the likely ATT&CK tactic | Verdict with no reasoning |
| Scope and impact | Other hosts or accounts checked, and what was found | Looking only at the alerting host |
| Recommendation | Escalate or close, and the specific next action (isolate host, reset credential, block domain) | Generic advice such as "monitor the situation" |
The same structure works in a real SOC and feeds the metrics a manager tracks. See the Security Operations Metrics Guide and the Incident Response Guide.
Cost, attempts and validity
- Price: TryHackMe says prices are shown in local currency on each certification page and each certification is a one-off purchase that includes the exam. The SAL1 page showed EUR 301 when checked in November 2026, and offered an analyst bundle of SAL1 and SAL2 at a discount. Premium subscribers are offered a reduction; confirm the current percentage at checkout.
- Attempts: the help centre states that a purchase includes two exam attempts, valid for 12 months from purchase. If you fail, the free retake opens three days after you started the first attempt. Further attempts can be bought, with prices varying by location.
- Validity and renewal: the TryHackMe and Credly pages checked do not state an expiry date or a continuing education requirement for SAL1. If your employer needs a time-limited credential for a compliance mapping, ask TryHackMe in writing.
- Verification: the credential is issued as a verifiable certificate and a Credly badge, which employers can check directly.
Where it fits on the career path
SAL1 sits at the start of a blue team route: it evidences Tier 1 triage and documentation, and SAL2 extends into hunting and forensics. For how entry-level blue team credentials sit alongside each other, see the Blue Team Certifications Guide, and for the wider map of security certifications, the Cybersecurity Certifications Guide.
| Situation | Is SAL1 a good fit? | Why |
|---|---|---|
| Applying for first SOC role with no experience | Strong fit | Shows hands-on triage and written reporting, which interviews often probe |
| Already a Tier 1 analyst for over a year | Limited value | Your work record shows the same skills; SAL2 is the closer match |
| Employer requires a credential on a specific compliance list | Check first | Confirm the list names SAL1 before relying on it |
| Manager screening junior applicants | Useful signal | Pair it with a short practical interview using your own alert examples |
| Manager funding new joiners | Good onboarding benchmark | The SOC Level 1 path doubles as structured onboarding content |
For small and large teams: a small SOC or managed service provider can use the path plus SAL1 as its onboarding programme and skills baseline. A large SOC with its own runbooks should treat SAL1 as a hiring signal and still teach its own tooling, severity model and escalation rules. See the Building a SOC from Scratch Guide.
Measuring whether it worked
- Time from joining to handling the live queue unsupervised, for certified versus uncertified joiners.
- Tier 2 rework rate: the share of escalations returned for missing evidence.
- False positive closure accuracy on quality assurance samples.
- Mean time to triage per alert in the first 90 days.
- Case note completeness score against your report template.
Common failure patterns
- Skipping fundamentals: candidates who rush to the simulator struggle with the multiple-choice section and with reading raw log fields. TryHackMe built that section because of this gap.
- Investigating without prioritising: working the queue in arrival order leaves high-severity alerts waiting while low-value ones are explored in depth.
- Verdicts without evidence: closing an alert as a false positive with no supporting log line or query.
- Single-host tunnel vision: failing to check whether the same indicator appears on other hosts or accounts before closing.
- Writing everything at the end: reconstructing reports from memory after hours of triage loses timestamps and detail.
- Treating the badge as the goal: employers interview on the skills; candidates who memorise labs without understanding the telemetry do poorly in practical interviews.
Practitioner checklist
- Confirm the current price, attempt rules and any validity terms on TryHackMe's pages before purchase.
- Check your fundamentals: networking, Windows and Linux logging, and email header analysis.
- Complete the SOC Level 1 path, including every simulator scenario and capstone.
- Build a personal reference of event IDs, log locations and SIEM query patterns.
- Practise a five-part case note (summary, evidence, classification, scope, recommendation) for every lab.
- Rehearse a long continuous triage session before the real attempt.
- Plan your 24-hour window, including rest, before you start.
- Note the retake timing: the free retake opens three days after the first attempt starts, and both attempts expire 12 months from purchase.
- For managers: decide how SAL1 is weighted in hiring and pair it with a practical interview.
Standards and references
- TryHackMe: Security Analyst Level 1 (SAL1)
- TryHackMe: Creating SAL1
- TryHackMe Help Centre: Certification access
- TryHackMe Help Centre: Certificate of completion vs SAL1
- TryHackMe: Certifications
- TryHackMe: SOC Level 1 learning path
- TryHackMe: Certification guide
- Credly: Security Analyst Level 1 (SAL1) badge
Related NHI Mgmt Group resources: Blue Team Certifications Guide · Cybersecurity Certifications Guide · Alert Triage Guide · SIEM Guide · Cybersecurity Careers Guide