UK

United Kingdom · Technical roles · Mid-Level (2-5 years)

Security Analyst

Here is the whole job, in plain words. What it is, a real day, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

  • Experience bandMid-Level (2-5 years)
  • Direct reportsNo direct reports
  • Reports toSenior Security Engineer
  • UK framework levelUsually a coordinator, or early in a professional job

Also advertised as Cyber Security Analyst · Information Security Analyst · IT Security Specialist

Built on an analysis of 43,079 real UK job descriptions · grounded in qualifications employers recognise

Start with a free Future Fluency check, tuned to Security Analyst

Ten quick questions, one per Future Fluency, asked against this role rather than a generic one. About five minutes, and no card.

Start the check, free

1What this role really is

You're the person on the front line, spotting and stopping digital threats before they cause real damage. This isn't just about technical wizardry; it's about being the detective who pieces together clues, the firefighter who contains the blaze, and the guardian who protects our digital assets. You'll be knee-deep in alerts, logs, and incident responses, making sure our systems stay safe.

2What you'd actually use

The tools this job runs on, and how well you'd need to know each one.

Splunk / Microsoft Sentinel (SIEM)Intermediate

Running pre-built and custom queries to investigate security alerts, building basic dashboards for incident tracking, and hunting for suspicious activity in log data.

CrowdStrike Falcon / SentinelOne (EDR/XDR)Intermediate

Monitoring endpoint alerts, performing deep-dive forensic analysis on compromised hosts, isolating systems, and understanding attack chains on endpoints.

Tenable.io / Qualys (Vulnerability Management)Intermediate

Configuring and running authenticated vulnerability scans, validating findings to eliminate false positives, and prioritising vulnerabilities based on business context and exploitability.

Palo Alto Prisma Cloud / Wiz.io (CSPM/CWPP)Basic

Reviewing pre-configured alerts for cloud misconfigurations (e.g., public S3 buckets, overly permissive IAM roles) and following remediation guides.

Okta / Azure AD (Entra ID) (IAM)Intermediate

Configuring Single Sign-On (SSO) applications, implementing conditional access policies, troubleshooting complex authentication failures, and managing user access.

ServiceNow GRC / OneTrust (GRC)Basic

Entering evidence for control testing, responding to information requests from auditors, and tracking compliance tasks within the platform.

3What you get to decide, and how that grows

Power in a job isn't your title. It's what you're allowed to decide. Here's how it grows as you move up.

The choiceComing inWhere you are nowThe step above
Incident Containment (Routine Threat)Escalate to supervisor for approval before any action.Independently contain known, documented threats (e.g., isolate a host with a specific malware signature, block a known malicious IP) within established playbooks. Escalate if the threat is novel or impacts critical systems.Lead containment efforts for complex or novel threats, making real-time decisions on scope and method. Consult with leadership on potential business impact.
Security Tool Configuration ChangesPropose changes to supervisor; supervisor makes the change.Propose and, with manager approval, implement minor configuration changes to SIEM rules or EDR policies for improved detection/prevention. Significant changes require Senior Engineer review.Design and implement significant configuration changes across security tools, often leading a project to deploy new rules or policies. Consult with architects on strategic impact.
Vulnerability PrioritisationFollow pre-defined prioritisation matrix; escalate questions.Prioritise vulnerabilities based on severity, exploitability, and business context, then assign to relevant teams. Escalate if there's disagreement on priority or impact.Define and refine the organisational vulnerability prioritisation framework, negotiating SLAs with business unit leads and reporting on overall risk posture.
User Access Decisions (Non-Routine)Escalate all non-routine access requests to supervisor.Review and approve non-routine access requests based on least-privilege principles and documented policies. Escalate if the request is high-risk or policy is unclear.Design and implement new access control policies and frameworks (e.g., for new applications or Zero Trust initiatives), defining the rules for access decisions.

4How you'll be judged

The scoreboard, honestly: the hard targets, how often each one is actually looked at, and the quiet human signals that never make it onto a dashboard.

Mean Time to Acknowledge (MTTA) Critical Alerts
How quickly you pick up and start working on the most serious security alerts.
Target · Under 15 minutes for critical alerts (P1/P2)

If a critical alert comes in at 10:00 AM, you should have it acknowledged and be actively investigating by 10:14 AM at the latest. We're talking 'drop everything' speed here.

Security Incident Resolution Rate within SLA
The percentage of routine security incidents you resolve within the agreed-upon service level agreement.
Target · Greater than 90% of L2 incidents resolved within SLA

If we have 100 L2 incidents in a month, you're expected to close at least 90 of them within their specified resolution window (e.g., 24-48 hours, depending on severity).

Phishing Report Analysis & Remediation
How thoroughly and quickly you analyse user-reported phishing emails and take appropriate action (e.g., blocking sender, removing from inboxes).
Target · 100% of user-reported emails analysed within 1 hour; malicious ones remediated within 2 hours

A user flags a suspicious email at 11:00 AM. By 11:59 AM, you've checked it out. If it's malicious, by 1:00 PM, that email (and similar ones) should be gone from everyone's inbox.

Vulnerability Scan Remediation Tracking
The accuracy and completeness of your tracking for vulnerabilities identified by scans, ensuring they're assigned and followed up.
Target · Less than 5% backlog of unassigned or untracked critical vulnerabilities

After a scan, if 50 critical vulnerabilities pop up, you'll make sure no more than 2-3 are sitting unassigned or haven't been followed up with the relevant team by the next review.

Quality of Incident Documentation
How clear, comprehensive, and accurate your incident reports and post-mortem notes are.
  • Your incident reports consistently include a clear timeline, all relevant Indicators of Compromise (IoCs), detailed containment and eradication steps, and lessons learned. Other analysts can easily pick up your notes and understand the full story. Frankly, if someone can't understand what happened from your write-up, it's not good enough.
Proactive Threat Identification
Your ability to spot unusual patterns or potential threats before they trigger a formal alert.
  • You're regularly bringing 'interesting' log entries or suspicious behaviours to your manager's attention, even if they haven't tripped an alert yet. This means you're not just reacting, you're looking for trouble – the good kind of looking for trouble, that is. Think 'threat hunting' on a smaller scale.
Effective Collaboration with IT Teams
How well you work with other IT teams (like Ops or Network) to get security issues fixed.
  • Feedback from IT Ops or Network teams indicates you provide clear, actionable information and work constructively to resolve issues, rather than just throwing tickets over the fence. They'll actually answer your calls and emails quickly because they know you're not just pointing fingers.
Contribution to Security Playbooks
Your input and improvements to our standard operating procedures and incident response playbooks.
  • You're not just following the playbook
  • you're suggesting improvements based on what you've learned from incidents. You'll spot gaps or inefficiencies and propose concrete changes that make our response better next time. This shows you're thinking beyond just the immediate task.

5Would you like it

The honest version. What people enjoy, and what grinds them down.

What people enjoy
Solving Complex Puzzles

You get a real kick out of taking a jumble of seemingly unrelated logs and alerts, piecing them together, and figuring out exactly what happened during an incident. It's like being a digital detective, and finding the culprit is a genuine win.

Spending an hour deep-diving into SIEM logs to trace an attacker's lateral movement, eventually pinpointing the compromised account and stopping them dead in their tracks.

Protecting the Organisation

There's a deep sense of satisfaction knowing your work directly contributes to keeping the company safe from real-world threats. You're the one standing between the bad guys and our valuable assets.

Successfully containing a malware outbreak before it spreads to critical systems, knowing you've prevented significant downtime and data loss.

Continuous Learning and Improvement

The cyber threat landscape changes constantly, and you genuinely enjoy the challenge of keeping up. You're always looking for new techniques, tools, and ways to make our security better.

Taking the initiative to research a new attack technique, then proposing a new detection rule for our SIEM to protect against it.

What frustrates people
  • The 'Department of No': You'll constantly fight the perception that your team's only purpose is to block business initiatives and add friction to development cycles. It's exhausting.
  • User Apathy: Watching users click on obvious phishing links minutes after completing their mandatory security awareness training for the fifth time. It's infuriating, frankly.
  • Shadow IT Risk: Discovering a critical business unit has been running on an unvetted, insecure SaaS platform for six months, exposing sensitive company data. You'll feel like you're constantly playing catch-up.
  • Alert Storms: Waking up at 3 AM to a flood of 5,000 alerts from the SIEM, knowing that 4,999 are likely false positives, but you have to investigate until you find the one that isn't. It's mentally draining.
What this role does not give you
  • A predictable 9-to-5 schedule: Incidents don't care about your plans. Expect occasional out-of-hours work.
  • Constant praise: Much of your best work is preventing bad things from happening, which often goes unnoticed.
  • Complete control: You'll often rely on other teams to implement your recommendations, which means you can't always dictate the pace.

6Who you work with

Your work directly reduces our exposure to cyber threats. You're the one stopping the small issues from becoming big problems, protecting our data, our systems, and ultimately, our customers' trust. A solid security analyst keeps the lights on, frankly.

Inside the business
  • IT Operations Team (they're often the ones implementing your fixes)
  • Helpdesk (first point of contact for user security issues)
  • Network Engineering (for firewall changes and network segmentation)
  • Application Development Teams (when an incident points to an application flaw)
  • Compliance & Risk Team (they'll want to know what happened and how we're improving)
Outside the business
  • Security Vendors (for tool support and updates)
  • Industry peers (for threat intelligence sharing, though less frequent at this level)

7What you need before you start

Not a wish list. The things you would be expected to already have.

  • Solid understanding of networking concepts (TCP/IP, DNS, firewalls).
  • Experience with Windows and Linux operating systems, including command-line tools.
  • Familiarity with common security concepts like encryption, hashing, and authentication.
  • Experience working in an IT support or operations role, or as a junior security analyst, for at least 2 years.
  • A genuine curiosity about how systems work and how they can be broken (ethically, of course!).

8What to practise next

Where the job is going, and what to do about it starting this week.

Advanced SIEM Querying & Rule Writing

Critical within 12 months – as threats get more sophisticated, our detection needs to keep pace. You'll move beyond pre-built queries to writing complex, multi-source correlation rules that spot subtle attack patterns.

Complex SPL/KQL for threat hunting · Machine learning capabilities in SIEM · Custom parser development

  • This week: Identify one complex threat scenario and try to build a custom query to detect it in our SIEM.
  • This month: Complete an advanced SIEM query language course (e.g., Splunk Power User or Microsoft Sentinel KQL Masterclass).
  • Month 2: Propose and implement two new, high-fidelity detection rules based on recent threat intelligence.
  • Month 3: Lead a small workshop for junior analysts on advanced SIEM querying techniques.

Quick win: Challenge yourself to solve every alert investigation using only custom queries, avoiding the pre-built dashboards where possible. It's great practice.

Endpoint Detection & Response (EDR) Scripting & Automation

Important within 12-18 months – to respond faster and more effectively, you'll need to automate common EDR tasks and build custom detection logic within the platform.

EDR API integration · Custom detection rule creation · Forensic data collection automation

  • This week: Explore the API documentation for our EDR platform.
  • This month: Write a simple script (e.g., in Python) to pull EDR alerts into a custom report.
  • Month 2: Develop a custom detection rule for a specific threat observed in our environment.
  • Month 3: Work with the Security Engineering team to integrate one of your scripts into a SOAR playbook.

Quick win: Start learning Python if you haven't already. It's the lingua franca for security automation and will unlock so many possibilities.

9Staying current once you are in

What people here do to keep up
  • Regularly participate in security conferences and webinars (e.g., Black Hat, DEF CON, local BSides events).
  • Contribute to open-source security projects or participate in Capture The Flag (CTF) competitions.
  • Maintain a home lab for experimenting with new security tools and attack techniques.
  • Follow leading security researchers and threat intelligence feeds on platforms like X (formerly Twitter) or LinkedIn.

10How the AI economy is changing work like this

Before we ask anything of you, here's what we can already say about AI and work of this kind:

The new skill this role is being asked for: Advanced Prompt Engineering for Security Tools

Critical within 6 months – LLMs are already integrated into many security tools (SIEMs, EDRs). Analysts who can effectively 'talk' to these AIs will be significantly more productive, automating tasks and getting deeper insights faster.

We'll only ever tell you what we can actually back up. No hype, no scare tactics.

Your PlanIllustration

Built for Security Analyst

5 units that map to this job, from the qualifications that cover it.

  1. Incident Response, Investigations and ForensicsQualifi Ltd · covers 5 of 10 standardsLevel 4
  2. Incident response and disaster recoveryNCFE · covers 5 of 10 standardsLevel 3
  3. Investigations and Incident ResponseQualifi Ltd · covers 4 of 10 standardsLevel 3
  4. Incident Response and ManagementSFJ Awards · covers 3 of 10 standardsLevel 4
  5. Carrying out Information Security Incident Management activitiesPearson Education Ltd · covers 2 of 10 standardsLevel 3
These are the real units behind this job, in the order they rank for it. Nothing here is marked done, because this plan has not been started by anyone yet. Yours would fill in as you go.

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

Advanced Prompt Engineering for Security Tools

Critical within 6 months – LLMs are already integrated into many security tools (SIEMs, EDRs). Analysts who can effectively 'talk' to these AIs will be significantly more productive, automating tasks and getting deeper insights faster.

  • Context windows and token limits
  • Temperature settings for different tasks
  • Output validation and hallucination detection
  • Prompt chaining for complex analysis

DevSecOps Principles & Security-as-Code

Important within 12-18 months – as development moves faster, security needs to be baked in from the start, not bolted on at the end. Understanding how security integrates into CI/CD pipelines will be essential.

  • Shift-left security
  • Infrastructure-as-Code (IaC) security scanning
  • Container security best practices
  • Automated security testing (SAST/DAST)

What you’ll use

Skills this role draws on

Technical

  • NIST Cybersecurity Framework (CSF) Application
  • ISO 27001/27002 Control Understanding
  • Incident Response Lifecycle Execution (PICERL)
  • Basic Threat Modelling Concepts
  • Zero Trust Architecture Principles

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

  1. 1

    IT Support Specialist / Helpdesk Analyst

    2-3 years in IT support, then 1-2 years as a Junior Security Analyst.

    Skills to master

    • Strong troubleshooting skills, understanding of user behaviour, basic networking, and a keen interest in security incidents beyond just 'fixing' the immediate problem.

    You're ready to move on when

    • Proactively identifying and escalating suspicious user activities (e.g., repeated password resets, unusual login times).
    • Taking initiative to learn about phishing techniques and malware.
    • Demonstrating an understanding of basic security principles in your daily work.
  2. 2

    Junior Security Analyst

    1-2 years in a junior security role.

    Skills to master

    • Mastering L1 alert triage, basic vulnerability scanning, understanding of security playbooks, and clear incident documentation under supervision.

    You're ready to move on when

    • Consistently closing L1 tickets within SLA with minimal errors.
    • Demonstrating a desire to understand the 'why' behind security incidents, not just the 'how'.
    • Taking on more complex tasks and showing initiative to learn new tools.
  3. 3

    Network Engineer / System Administrator

    3-4 years in network or systems administration, then a dedicated move into security.

    Skills to master

    • Deep understanding of network architecture, operating system internals, server hardening, and a shift in mindset from 'keeping systems running' to 'keeping systems secure'.

    You're ready to move on when

    • Actively implementing security best practices in your admin work (e.g., least privilege, secure configurations).
    • Proactively identifying network vulnerabilities and proposing solutions.
    • Showing a strong interest in threat detection and incident response.

11Where this role leads

The long view:Your journey here as a Security Analyst is just the beginning. We're committed to helping you grow, whether that's becoming a technical guru, a team leader, or even shaping the future of security for the entire organisation. The opportunities are genuinely vast, and we'll support you every step of the way.

Pay & demand

Typical pay £54,647 a year Source: ONS Annual Survey of Hours and Earnings, 2025 (provisional), under the Open Government Licence v3.0

The figure is the median for full-time employees in the ONS occupation this job title codes to (Cyber security professionals), from the April 2025 survey — about six months old when published, as ASHE always is. It is that occupation's middle, not this role's. Half earn more.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how Security Analyst is actually changing. In about two minutes, the free confidence check asks where you stand on each of the ten. That's the whole check, and it's what makes the plan yours rather than generic.

Where it leads

Roles this leads to

The record names a next step, but the catalogue has no page for it yet:

  • Senior Security Engineer (Level 003)

12The team that's yours

No two people are taught the same way. This is one-to-one, not one-to-many.

Zavmo is a hyper-personalised AI learning platform. Twelve virtual tutors, each with a different way of teaching, and one orchestration agent that picks the right one for the moment. So every single lesson is shaped around you, your role, and the way you learn. Not a course everyone sits through. A conversation built for you, and no one else.

…and nine more, matched to you after your first chat. Meet all twelve

Start free and meet yours

13What it feels like

A conversation, not a course

Because your tutor knows your role, your projects and your last session, learning sounds like this. And it's different for every single person:

Incident Response, Investigations and ForensicsLevel 4

Applied to your work in Security Analyst

This unit aims to equip learners with an understanding of incident response as a business function, including the operation of Computer Emergency Response Teams (CERTs) and aligned task forces for business continuity, disaster recovery, and crisis management. Learners will also understand how major computer incidents are formally investigated, including evidence gathering and analysis, and the relevant legal and ethical considerations.

How the thinking builds
  1. Remember
  2. Understand
  3. Apply
  4. Analyse
  5. Evaluate
  6. Create
An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

One to one, not one to many

No two people run this the same way

A course is written once and handed to everyone. This is assembled around you, and keeps changing as it learns you. Five things it reads, and what each one changes.

  1. Your actual work Every lesson is taught against a live piece of your own work, not a worked example from a textbook.
  2. What you already know The first conversation finds your starting point, so you skip what you can already do and spend the time on what you cannot.
  3. The conditions you learn under Not a learning-styles quiz. The evidence does not support those. The dimensions the research does back, read once and used to shape the plan.
  4. How far you got last time It picks up mid-thought. The tutor knows what you said, what you struggled with, and what it asked you to try.
  5. Which tutor suits the moment Twelve of them, each for a different kind of thinking. The one who walks you through a first idea is not the one who stress-tests it.

See how you learn, free. Eight questions, no sign-up. A directional taster; the diagnostic inside Zavmo goes deeper and keeps adapting.

DemonstrateIllustration

Evidenced on your work in Security Analyst

You do not finish by watching something. You finish by showing it on the work you already do, against the measures this job is judged on.

  • Mean Time to Acknowledge (MTTA) Critical AlertsHow quickly you pick up and start working on the most serious security alerts.If a critical alert comes in at 10:00 AM, you should have it acknowledged and be actively investigating by 10:14 AM at the latest. We're talking 'drop everything' speed here.Under 15 minutes for critical alerts (P1/P2)
  • Security Incident Resolution Rate within SLAThe percentage of routine security incidents you resolve within the agreed-upon service level agreement.If we have 100 L2 incidents in a month, you're expected to close at least 90 of them within their specified resolution window (e.g., 24-48 hours, depending on severity).Greater than 90% of L2 incidents resolved within SLA
  • Phishing Report Analysis & RemediationHow thoroughly and quickly you analyse user-reported phishing emails and take appropriate action (e.g., blocking sender, removing from inboxes).A user flags a suspicious email at 11:00 AM. By 11:59 AM, you've checked it out. If it's malicious, by 1:00 PM, that email (and similar ones) should be gone from everyone's inbox.100% of user-reported emails analysed within 1 hour; malicious ones remediated within 2 hours
  • Vulnerability Scan Remediation TrackingThe accuracy and completeness of your tracking for vulnerabilities identified by scans, ensuring they're assigned and followed up.After a scan, if 50 critical vulnerabilities pop up, you'll make sure no more than 2-3 are sitting unassigned or haven't been followed up with the relevant team by the next review.Less than 5% backlog of unassigned or untracked critical vulnerabilities
These are this job's own measures, with its own targets. Nothing is marked evidenced, because nobody has started this yet. Yours would fill in from the work you bring.

Your passport

This isn't a certificate you file away. It's a passport to the life you're designing.

Every credit you earn and every fluency you build adds up: evidence where it counts, carried with you. Zavmo keeps the map: where you are, where you're heading, and the next step, at your pace, around your life. From Security Analyst to Senior Security Engineer (Level 003), and whatever you decide comes after.

Level 3 · in progressAI Fluency→ Senior Security Engineer (Level 003)→ your design
Where this takes you

Your journey here as a Security Analyst is just the beginning. We're committed to helping you grow, whether that's becoming a technical guru, a team leader, or even shaping the future of security for the entire organisation. The opportunities are genuinely vast, and we'll support you every step of the way.

See Your Progress GrowIllustration
Security Analyst
  • NIST Cybersecurity Framework (CSF) Application
  • ISO 27001/27002 Control Understanding
  • Incident Response Lifecycle Execution (PICERL)
  • Basic Threat Modelling Concepts
  • Zero Trust Architecture Principles
This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

14The detail, folded away

Everything else the record holds

The career branches in full, how AI is already showing up in the day-to-day, and the questions people ask about this job. Here when you want them, out of the way while you decide.

Where it leads next, rung by rung

Where it leads

The career path, and where it branches

Security Analyst is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Senior Security Engineer (Level 003)

    Roughly 3-5 years as a Security Analyst.

    You'll move from independently resolving routine incidents to leading projects, deploying and tuning security tools, and mentoring junior analysts. You'll own complete workstreams within larger security projects.

    • Expertise in SIEM rule development and advanced threat hunting.
    • Deep understanding of cloud security architectures and security-as-code.
    • Leading incident response efforts for medium-to-high severity incidents.
    • Designing and implementing security controls for new systems.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be honest, a security analyst's job can be a bit like finding a needle in a haystack – a really, really big haystack. We're talking millions of logs, thousands of alerts, and a constant stream of new threats. That's where AI comes in. It's not here to replace you; it's here to make you incredibly good at your job, faster and more effective than ever before.

In this role, you'll be using AI-powered tools daily to cut through the noise, automate the tedious bits, and focus your brilliant human brain on the real threats. Think of it as having a super-smart assistant who never sleeps and can process data at lightning speed. It's about working smarter, not just harder.

AI-Powered Alert Triage

Imagine a SOAR (Security Orchestration, Automation, and Response) platform with AI that automatically investigates, enriches, and even closes low-level alerts – things like brute force attempts from known bad IP addresses. This frees you up from the mundane, letting you focus on the genuine, complex threats that need your expertise.

Anomaly Detection Acceleration

You'll use User and Entity Behaviour Analytics (UEBA) to automatically surface suspicious patterns that would take hours of manual log review to find. For example, an admin logging in from a brand new country at 3 AM, or a user accessing an unusual volume of sensitive files. AI spots these outliers in a flash.

Threat Intelligence Synthesis

Instead of sifting through dozens of threat intelligence reports daily, an AI assistant can summarise the latest CVE disclosures, dark web chatter, and industry news. You'll get a concise brief on relevant threats, saving you hours of reading and helping you stay ahead of the curve.

Instant Incident Report Drafting

After a major incident, writing the post-mortem report can be a multi-hour slog. With AI, you can feed it the incident timeline, Indicators of Compromise (IoCs), and containment steps, and it'll generate a solid first draft. This turns a long writing task into a 30-minute editing and refinement job.

Common questions

Common questions

How do you become a Security Analyst?

Common routes in include IT Support Specialist / Helpdesk Analyst (2-3 years in IT support, then 1-2 years as a Junior Security Analyst.), Junior Security Analyst (1-2 years in a junior security role.) and Network Engineer / System Administrator (3-4 years in network or systems administration, then a dedicated move into security.). Times vary with prior experience.

Where can a Security Analyst progress to?

This role can lead on to Senior Security Engineer (Level 003) (Roughly 3-5 years as a Security Analyst.), depending on the skills you build.

What level is a Security Analyst in the UK?

This role aligns to RQF Level 3 on the UK framework, a guide to the depth of qualification it maps to, not a hard entry bar.

What new skills matter most for a Security Analyst?

Increasingly, Advanced Prompt Engineering for Security Tools and DevSecOps Principles & Security-as-Code. These are the areas where the higher-paid, future-proof work is heading.

The honest bit

You’ve started things before

Most of them were built for a room full of people who aren’t you. A cohort moves on whether or not your week allowed it, and by the third week the thing you’re behind on becomes the reason you stop opening it.

There’s no cohort here, and no timetable to fall behind. Before anything starts, Zavmo asks when you’re sharpest and how long you can realistically sit down for, then builds the sessions around those answers. A bad fortnight changes your pace. It doesn’t put you behind.

And you only pay once you start learning. Searching and planning are free, and you can cancel any time — so the cost of finding out is an afternoon, not a year.

What it costs

Less than one coaching session. Every month.

A single career-coaching hour costs more than a month of this, and it ends when the hour does. Zavmo doesn't. It's £70 a month, about £2.30 a day, for a companion that knows a Security Analyst, works on the job you actually do, and keeps going at your pace rather than a timetable's.

  • Searching and planning stay free. You only pay when you start learning.
  • Your credits are yours. Regulated, and they don't vanish when a subscription ends.
  • Cancel any time and billing stops. No notice period, no minimum term.

Your path, personalised

You have the map. Walking it is the part we do together.

This route runs to 10 national skill standards. That is a real journey.

Zavmo shapes a learning experience as unique as you are. It fits how you learn, your pace and the work you already do. Every step stays benchmarked to recognised national standards. That’s the plan for becoming a Security Analyst: personal to you, and it still counts. The first steps are free.

Independent research finds well-designed intelligent tutoring performs nearly as well as one-to-one human tutoring: VanLehn (2011), Educational Psychologist.

A private tutor in the UK averages £35–40 an hour . Zavmo is £70/month.

A real plan on learn.zavmo.ai: Ofqual-regulated units, credits, and a three-month run at your own pace.
Start free No commitment. See your first steps free.

15Where to go from here

Other roles at Level 3

Same depth of qualification, different job. Useful if the work appeals but this particular role does not.

Other roles in Technical roles

Stay in the field you know and move sideways rather than up.

If you leave this industry

The skills you'll gain here are highly transferable across almost any industry. Every company needs strong cyber security, so you'll find opportunities in finance, healthcare, retail, government – you name it. Your expertise will always be in demand.

Not sure this is the right direction?

Work out what you actually want from work first, then come back and see which roles fit it. Takes about ten minutes.

This role profile is © 2026Growth Engineering Technologies Ltd. Built from UK occupational standards and regulated qualification data, and written for Zavmo.

You're not behind. You're right on time. The shift is only just beginning. Your role won't look the same in two years. Be the one who leads the change, not the one it happens to. Build my plan, free Here's the first ten minutes: a 2-minute confidence check → your personalised roadmap → meet the tutors matched to you. No card, cancel any time. No card. Build your plan, see your roadmap and meet the twelve tutors matched to you. All free. When you're ready to start learning, it's £70 a month, billed monthly. Cancel any time and billing stops.