United Kingdom · Technology and data · Mid-Level (2-5 years)

Cloud Security Analyst

As a Cloud Security Analyst, you become the vigilant guardian of our digital sky, ensuring every alert is a call to action, not just noise.

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.

Start my Cloud Security Analyst plan, free

Free to start: a plan built for this role, and a Future Fluency module to try first. No card.

Keep this job description

Where should we send it?

One email: what AI is changing in this job, and where to start free. With a link back here. Nothing else follows unless you confirm your address.

Upskilling a team in this role? Talk to us

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

Also advertised as Security Operations Analyst · Mid-level Cloud Defender · Cyber Security Analyst (Cloud Focus)

Built on 43,079 real UK job descriptions we analysed · grounded in qualifications employers recognise

Two short quizzes about you

1From this job to a course

The qualifications matched to this job

Pearson BTEC Level 4 Higher National Certificate in Cloud Computing Pearson Education Ltd · Level 4 · covers 3 of 12 standards

City & Guilds Level 3 Diploma in ICT Systems and Principles for IT Professionals City & Guilds Limited · Level 3 · covers 1 of 12 standards

City & Guilds Level 3 Certificate in ICT Systems and Principles City & Guilds Limited · Level 3 · covers 1 of 12 standards

Pearson BTEC Level 5 Higher National Diploma in Cloud Computing Pearson Education Ltd · Level 5 · covers 4 of 12 standards

Pearson BTEC Level 5 Higher National Diploma in Digital Technologies Pearson Education Ltd · Level 5 · covers 3 of 12 standards

NCFE Level 5 Diploma: Cloud Systems and Secure Networking NCFE · Level 5 · covers 2 of 12 standards

Matched from the standards this job is measured against: a suggestion, not an official ruling.

The units you would start with

Security in the Cloud Pearson BTEC Level 4 Higher National Certificate in Cloud Computing

Implementing and maintaining Cloud technologies and infrastructure City & Guilds Level 3 Diploma in ICT Systems and Principles for IT Professionals

Applied Security in the Cloud Pearson BTEC Level 5 Higher National Diploma in Cloud Computing

Security compliance and legislation NCFE Level 5 Diploma: Cloud Systems and Secure Networking

The future skills this job leans on

AI Fluency working with AI as a thinking partner

Data Fluency turning numbers into a decision

Trust Fluency keeping the digital world safe

Start my Cloud Security Analyst plan, free

Your Plan Illustration

Built for Cloud Security Analyst

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

Security in the Cloud Pearson Education Ltd · covers 3 of 12 standards Level 4
Implementing and maintaining Cloud technologies and infrastructure City & Guilds Limited · covers 1 of 12 standards Level 3
Applied Security in the Cloud Pearson Education Ltd · covers 4 of 12 standards Level 5
Security compliance and legislation NCFE · covers 2 of 12 standards Level 5

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.

2AI and this work

Will AI change your work as a Cloud Security Analyst?

Nobody can say exactly how. Here is what this job is being asked for next, and where to start.

How the AI economy is changing work like this

A broad read on this kind of work, not an analysis of this job on its own. Roles that share a pattern get the same answer here.

Fading: AI does more of this

AI is taking over the routine triage of alerts, freeing you from the repetitive busywork.

→

Rising: worth more because of AI

Your ability to discern nuanced threats and prioritise vulnerabilities becomes even more valuable in the AI-enhanced landscape.

The new skills this role is being asked for

Prompt Engineering for Security Tasks
Cloud Native Security Tooling Beyond CSPM

Why each one is rising

The future skills this job leans on

AI Fluencyworking with AI as a thinking partner
Data Fluencyturning numbers into a decision
Trust Fluencykeeping the digital world safe

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

What happens when you start

Next, a free account. We build your Cloud Security Analyst plan as you set up, starting with a Future Fluency module on using AI in your job. No card.

Your first Future Fluency module is free. After that, your AI tutor is £70 a month.

Start my Cloud Security Analyst plan, free Ready to pay? Subscribe for £70 a month

3What this role really is

We see you

You sometimes wonder if AI might eventually replace the grunt work you do, but you know it lacks the human intuition that keeps our systems truly safe. While AI can handle the routine, it’s your keen eye that spots the real threats.

A cloud security analyst monitors cloud systems for threats and works to keep data and infrastructure secure. The work involves handling alerts, checking configurations and finding weak points before they cause harm. Protecting customer data and keeping systems running sits at the centre of the job. It calls for close attention to detail and a habit of digging into what's actually happening.

4A day in the life

Not a job advert. A real day, built from what this role actually holds.

08:45

You start by diving into the security alert queue, separating the real risks from the false alarms with a discerning eye.

11:00

A genuine incident arises, and you spring into action, following the playbook to contain the threat and gather evidence.

14:30

You spend time fine-tuning security configurations, collaborating with senior colleagues to enhance detection accuracy.

16:15

The day winds down with a review of security documentation, ensuring the playbooks reflect the latest insights and practices.

5What you'd actually use

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

AWS (Security Hub, GuardDuty, IAM Access Analyzer) Intermediate

Navigating dashboards, investigating pre-configured alerts, running basic compliance checks, and applying simple IAM role fixes with a playbook.

Azure (Defender for Cloud, Sentinel) Intermediate

Monitoring security posture, triaging alerts, and executing basic KQL queries to investigate suspicious activity.

Splunk Enterprise Security or Azure Sentinel Basic

Executing saved searches, monitoring real-time dashboards for anomalies, and escalating alerts based on documented procedures.

Tenable.io (Nessus) or Qualys Cloud Platform Intermediate

Scheduling and running routine vulnerability scans, validating findings to eliminate false positives, and creating remediation tickets.

Okta or Azure AD (Entra ID) Intermediate

Provisioning/de-provisioning user access, resetting MFA, and auditing permissions against a 'least privilege' checklist.

Jira & Confluence Intermediate

Managing your personal ticket queue, providing clear updates on incidents, and documenting findings according to templates.

6What 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 choice	Coming in	Where you are now	The step above
Incident Response Actions (e.g., blocking an IP, suspending a user)	Requires immediate supervisor approval; executes under direct instruction.	Executes independently if covered by a documented playbook; escalates for novel situations or significant business impact.	Makes independent decisions for most incidents, including novel ones; consults leadership for enterprise-wide impact.
Vulnerability Prioritisation and Remediation	Identifies vulnerabilities; supervisor prioritises and assigns remediation.	Prioritises vulnerabilities based on risk and business context; creates detailed remediation tickets for engineering teams.	Defines vulnerability prioritisation criteria; negotiates remediation timelines with engineering leadership.
Security Tool Configuration Changes (e.g., alert tuning, new rules)	Suggests potential tuning improvements; changes implemented by senior staff.	Proposes and helps implement minor tuning changes under supervision; contributes to new rule development.	Designs and implements complex detection rules and tuning strategies; owns tool configuration for a specific domain.
Documentation Updates	Updates existing documentation following templates; requires review.	Independently updates and creates new documentation for routine processes; peer review for critical documents.	Defines documentation standards; reviews and approves documentation from junior team members.

7How you'll be judged

The scoreboard, and what is not on it. The hard targets, how often each is actually looked at, and the quiet signals that never reach a dashboard.

Mean Time to Acknowledge (MTTA) Critical Alerts

How quickly you pick up and start investigating a high-priority security alert.

Target · Under 15 minutes for critical alerts, 30 minutes for high-priority.

If a critical alert comes in at 10:00 AM, you should be actively looking into it by 10:10 AM, at the latest.

Vulnerability Remediation Ticket Accuracy

The quality and completeness of the vulnerability tickets you raise for engineering teams.

Target · Greater than 95% of tickets include clear reproduction steps, affected assets, and recommended fixes.

You create a Jira ticket for a vulnerable S3 bucket. It clearly states the bucket name, the specific misconfiguration, and the exact IAM policy change needed, with no back-and-forth for clarification.

Playbook Adherence for Standard Incidents

How closely you follow our documented procedures for common security incidents and alerts.

Target · 100% adherence to documented playbooks for all routine incidents.

When a 'Suspicious Login' alert fires, you follow every step in the 'Suspicious Login Playbook' – checking logs, isolating the user, notifying HR, etc., without skipping anything.

False Positive Reduction Contribution

Your input and actions to help tune our security tools to reduce the number of irrelevant alerts.

Target · Contribute to a 5-10% reduction in false positives from one key system (e.g., GuardDuty) per quarter.

You identify a recurring 'unauthorised API call' alert that's actually our legitimate backup service. You propose and help implement an exclusion rule to stop it firing needlessly.

Proactive Issue Identification

You don't just wait for alerts; you actively look for potential problems before they become critical.

You're regularly flagging potential misconfigurations you spot during routine checks, suggesting improvements to existing security controls, or bringing up 'what if' scenarios in team meetings. People come to you with questions before things break.

Clear Incident Communication

During an incident, you keep everyone who needs to know in the loop, clearly and calmly, without causing panic.

Your incident updates are concise and factual. Stakeholders understand the situation and next steps without needing to ask follow-up questions. You know when to escalate and who needs to be told what, and you do it without being prompted.

Contribution to Documentation & Knowledge Sharing

You help make our collective knowledge better, whether it's updating a playbook or sharing a new trick you've learned.

You're regularly updating Confluence pages, adding notes to incident tickets that help the next person, or running quick 'lunch and learn' sessions for new team members. You don't hoard knowledge
you share it.

Collaborative Problem Solving

You work well with other teams, especially engineering, to resolve security issues without being seen as a blocker.

Engineering teams don't dread getting a ticket from you
they see you as a partner. You're able to explain technical risks in a way they understand and work with them to find practical solutions, not just dictate them.

8Would you like it

Both sides. What people enjoy, and what grinds them down.

What people enjoy

Solving Complex Puzzles

You love the challenge of piecing together clues from logs and alerts to understand what's really happening. It's like being a detective, but for code and cloud infrastructure.

An alert fires about unusual activity from a service account. You don't just block it; you dig through CloudTrail logs, network flow data, and asset inventories to figure out the root cause and how it happened.

Protecting the Organisation

You get a real buzz from knowing your work directly contributes to keeping our systems and data safe from threats. It's about being a guardian.

Successfully containing a potential incident and knowing you prevented a major breach, or finding a critical vulnerability before anyone else did.

Continuous Learning and Growth

The cloud security landscape changes constantly, and you're excited by the idea of always learning new tools, techniques, and threats. Stagnation isn't for you.

Spending your lunch break reading up on a new AWS security service or experimenting with a new open-source security tool you've heard about.

What frustrates people

Alert Fatigue: Drowning in thousands of low-priority alerts from an untuned SIEM, making it easy to miss the one that actually matters. It's like looking for a needle in a haystack, every single day.
Developer Pushback: Hearing 'It works on my machine' or 'We'll fix it later' in response to a critical vulnerability you've just found in their code. It can feel like an uphill battle.
Explaining the 'Why': Having to repeatedly justify basic security controls (like multi-factor authentication) to senior stakeholders who see them as an inconvenience. It gets tiring.
Inheriting a Mess: Starting a new role and discovering the cloud environment is a chaotic free-for-all with no documentation, no tagging standards, and hundreds of 'admin' level IAM users. It's a lot of cleanup.

What this role does not give you

A quiet, predictable routine with no surprises. Cloud security is anything but.
Guaranteed immediate resolution for every issue you find. Sometimes, fixes take time and negotiation.
A role where you only ever build new things. There's a lot of maintenance and investigation involved.
A job where you don't have to explain complex technical concepts to non-technical people. Communication is key.

9Who you work with

Your work directly impacts our ability to protect sensitive data, maintain operational uptime, and comply with regulations. Basically, you're helping us avoid costly breaches and reputational damage. When you do your job well, our engineering teams can build faster and safer, knowing you've got their back.

Inside the business

Your Manager (for guidance and prioritisation)
DevOps and Site Reliability Engineering (SRE) teams (you'll work closely to fix issues)
Product teams (when security issues affect their applications)
Internal Audit (they'll check your work sometimes)
Other Security team members (for incident collaboration and knowledge sharing)

Outside the business

Cloud Providers (AWS, Azure, GCP support, if you need to raise tickets)
Security Tool Vendors (for technical support or feature requests)

10What you need before you start

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

At least 2 years of hands-on experience in a security operations centre (SOC), IT support role with significant security exposure, or a junior cloud engineering role with a security focus.
A solid grasp of fundamental cloud computing concepts, ideally with practical experience in AWS, Azure, or GCP.
Demonstrable experience with incident triage, vulnerability management, or identity and access management.
A genuine curiosity about security and a drive to constantly learn and improve your skills.

11What to practise next

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

Advanced Threat Hunting Techniques

Attackers are getting stealthier. Relying solely on automated alerts isn't enough. You'll need to develop the skills to actively search for hidden threats in our cloud environments, using hypotheses and data analysis.

Hypothesis-Driven Hunting · Anomaly Detection (Manual & Automated) · Log Aggregation & Correlation (Advanced) · Threat Intelligence Integration

This month: Read up on common cloud attack patterns (e.g., MITRE ATT&CK for Cloud) and identify 2-3 specific hunting hypotheses.
Next month: Practice writing complex SIEM queries (KQL, Splunk SPL) to test those hypotheses against our existing log data.
Month 3: Participate in a 'purple teaming' exercise if we run one, or try to simulate one with a colleague to test your hunting skills.
Month 4: Present a 'threat hunt' finding (even if it's benign) to the team, explaining your process and conclusions.

Quick win: Start by regularly reviewing your SIEM's 'unusual activity' alerts, even the low-priority ones. See if you can spot patterns or connections that the automated rules missed.

Security Automation & Orchestration (SOAR basics)

To keep up with the volume of alerts and the speed of cloud changes, we need to automate more. You'll move from manually responding to alerts to helping build automated playbooks that handle routine tasks.

Playbook Development (Simple) · API Integration (Basic) · Conditional Logic in Automation · Error Handling in Automation

This month: Get familiar with our SOAR platform (if we have one) or explore a free/open-source automation tool like Shuffle.
Next month: Try to automate a very simple, repetitive task you do daily, like enriching an IP address from a threat intelligence feed.
Month 3: Work with a senior analyst to contribute to a small part of an existing automation playbook.
Month 4: Document your automated workflow and the time savings it brings.

Quick win: Identify one task you do at least 3 times a week that takes more than 5 minutes. Think about how you could use a simple script or a no-code automation tool to do it faster.

12Staying current once you are in

What people here do to keep up

Regularly participate in security conferences, webinars, and local meetups (like OWASP chapters). It's a great way to stay current and network.
Dedicate time each week to 'play' in a lab environment—spin up some cloud resources, try to break them, and then secure them. Hands-on learning is invaluable.
Contribute to open-source security projects or write blog posts about your security findings. It shows initiative and helps build your personal brand.
Take online courses (e.g., from Coursera, A Cloud Guru, Pluralsight) on new cloud security services or advanced threat hunting techniques.

13The rising capability

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.

Prompt Engineering for Security Tasks

AI is changing how we work, fast. Competitors are already using tools like ChatGPT and Claude to draft incident summaries, analyse logs, and even suggest secure code snippets in minutes, tasks that used to take hours. Analysts who master this will be significantly more productive.

Effective Prompt Construction
Context Windows & Token Limits
Output Validation & Hallucination Detection
Security-Specific LLM Fine-tuning (basic awareness)

Cloud Native Security Tooling Beyond CSPM

While CSPM tools are great, the cloud providers are constantly releasing new, more specialised security services (e.g., AWS Macie for data discovery, Azure DDoS Protection, GCP Binary Authorisation). Understanding these will be key to building truly robust cloud defences.

Data Security Services (e.g., AWS Macie, Azure Purview)
Network Security Services (e.g., AWS WAF, Azure Firewall)
Container Security (e.g., ECR/ACR scanning, Kubernetes security policies)
Serverless Security (e.g., Lambda permissions, API Gateway security)

14What you’ll use

What you’ll use

Skills this role draws on

Technical

Incident Response Lifecycle (Identification & Containment)
Least Privilege Principle Application
Defence in Depth Concepts
Compliance Framework Application (CIS, NIST CSF basics)
Basic Scripting (Python or PowerShell)

15The pathway

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
Junior Cloud Security Analyst / Associate Cloud Security Analyst
1-2 years
Skills to master
- Foundational cloud concepts, basic security principles, alert monitoring and escalation, following incident response playbooks, basic scripting.
You're ready to move on when
- Consistently and accurately triaging L1 alerts without constant supervision.
- Successfully completing basic vulnerability scans and reporting findings.
- Demonstrating a proactive attitude towards learning new security tools and techniques.
- Clear and concise communication of security issues to the team.
2
IT Support Engineer with Security Focus
2-3 years
Skills to master
- User access management, basic network troubleshooting, understanding of common security threats (phishing, malware), experience with security tools (antivirus, firewalls).
You're ready to move on when
- Successfully resolving user access issues related to IAM or SSO.
- Identifying and escalating security incidents that come through the helpdesk.
- Proactively suggesting security improvements for internal IT systems.
- Demonstrating a strong interest in moving into a dedicated security role.
3
Cloud Operations Engineer / DevOps Engineer (Security-minded)
2-4 years
Skills to master
- Cloud infrastructure management (AWS, Azure, GCP), IaC (Terraform, CloudFormation), CI/CD pipelines, basic scripting, an understanding of operational security challenges.
You're ready to move on when
- Successfully deploying and managing cloud resources securely.
- Integrating security checks into CI/CD pipelines.
- Proactively identifying and remediating security misconfigurations in cloud environments.
- A clear desire to specialise in cloud security rather than general operations.

16How people get here · where they go next

Came from

Junior Cloud Security Analyst / Associate Cloud Security Analyst

1-2 years

You mastered the art of triaging alerts and conducting basic vulnerability assessments, setting the stage for more complex responsibilities.

You are here

Cloud Security Analyst

Mid-Level (2-5 years)

Goes to

Senior Cloud Security Analyst (L3)

3-5 years

You move into a role where leading incident responses and mentoring junior analysts become central to your work.

The long view: This role can lead into broader cyber security work, such as security architecture or a lead cloud security engineer position.

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 Cloud Security Analyst is actually changing.

How you would learn this

One to one, on the work you already do

A tutor sets the task against your own job and marks the reasoning, at your pace. There is no cohort to fall behind.

A lesson from Security in the Cloud, worked against Cloud Security Analyst.

Security in the Cloud Level 4

Applied to your work in Cloud Security Analyst

The objective of this unit is to enable learners to understand and apply security principles in a cloud infrastructure. Learners will design and configure secure cloud solutions based on corporate requirements, implement security measures to protect against threats, and develop test plans to improve cloud security and identify vulnerabilities.

The Coach Last time, we looked at how you handled that tricky incident with the AWS GuardDuty alert. Let's build on that today.

You I remember, it was a bit challenging but rewarding.

The Coach Great! Let's simulate a similar scenario, but this time, focus on refining your initial triage steps to improve efficiency.

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.

It is £70 a month, billed monthly. Your free first module is Future Fluency, and you can cancel any time.

Start my Cloud Security Analyst plan, free

A year from now

A year from now, you are a confident security analyst who not only handles incidents with precision but also contributes to shaping the security posture of the organisation.

See Your Progress Grow Illustration

Cloud Security Analyst

Incident Response Lifecycle (Identification & Containment)
Least Privilege Principle Application
Defence in Depth Concepts
Compliance Framework Application (CIS, NIST CSF basics)
Basic Scripting (Python or PowerShell)

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.

17The 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

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

Senior Cloud Security Analyst (L3)
3-5 years in this role

You'll move from primarily executing tasks to leading workstreams and mentoring others. Think of it as owning entire security processes, not just parts of them.
- **Leading Incident Response ** Taking charge of major security incidents from start to finish.
- **Advanced SIEM Tuning & Rule Creation ** Designing and implementing complex detection rules to reduce false positives and improve threat coverage.
- **Security Architecture Review (Basic) ** Providing security input on new system designs and architectures.
- **Security Automation Scripting ** Writing more complex scripts to automate security tasks and build custom tools.

Working with AI on the job

Working with AI

Where AI is starting to help

Let's be honest, cloud security can feel like a never-ending game of whack-a-mole. But what if you could offload some of the grunt work to AI? We're not talking about replacing you, but giving you a seriously powerful co-pilot. Our team uses AI to cut down on the tedious, repetitive tasks, freeing you up for the real detective work and problem-solving.

As a Cloud Security Analyst, you're constantly sifting through logs, triaging alerts, and drafting reports. AI can step in to automate the initial investigation, summarise massive amounts of data, and even help you write more secure code. It means less time on the mundane, more time on the meaningful stuff.

Alert Triage Automation

Imagine an AI-powered SOAR platform automatically investigating, enriching, and even closing low-level, high-volume alerts. It can query threat intel, check asset databases, and only escalate to you if it spots multiple red flags. This cuts down on the noise, letting you focus on the real threats.

Threat Intelligence Synthesis

Instead of manually trawling through thousands of threat intelligence articles and CVE reports, AI can analyse and summarise them for you. It'll highlight TTPs (Tactics, Techniques, and Procedures) relevant to our specific cloud setup (AWS, Azure) and even suggest new detection rules before an attack even happens.

IaC Code Review Assistant

Use an AI code assistant, like GitHub Copilot with security plugins, to review Terraform or CloudFormation templates. It can suggest more secure configurations in real-time, explain the risk of a certain setting, and even provide the corrected code snippet. It's like having a security expert looking over your shoulder as you code.

Incident Report Generation

After an incident, you can feed the timeline of events, logs, and actions taken into an LLM. Ask it to generate a draft executive summary and a detailed technical post-mortem report. This transforms raw data into a structured narrative for review, saving you hours of documentation time.

Common questions

How do you become a Cloud Security Analyst?

Common routes in include Junior Cloud Security Analyst / Associate Cloud Security Analyst (1-2 years), IT Support Engineer with Security Focus (2-3 years) and Cloud Operations Engineer / DevOps Engineer (Security-minded) (2-4 years). Times vary with prior experience.

Where can a Cloud Security Analyst progress to?

This role can lead on to Senior Cloud Security Analyst (3-5 years in this role), depending on the skills you build.

What new skills matter most for a Cloud Security Analyst?

Increasingly, Prompt Engineering for Security Tasks and Cloud Native Security Tooling Beyond CSPM. These are the skills our record of this role lists as growing.

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. Start my Cloud Security Analyst plan, free What happens next: a free account, then we build your plan as you set up. 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.

Cloud Security Analyst

Where should we send it?

Two short quizzes about you

Will AI change your work as a Cloud Security Analyst?

What's rising in its place

Prompt Engineering for Security Tasks

Cloud Native Security Tooling Beyond CSPM

Skills this role draws on

Technical

How you actually get there, here

Junior Cloud Security Analyst / Associate Cloud Security Analyst

IT Support Engineer with Security Focus

Cloud Operations Engineer / DevOps Engineer (Security-minded)

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

Roles this leads to

One to one, on the work you already do

A year from now, you are a confident security analyst who not only handles incidents with precision but also contributes to shaping the security posture of the organisation.

Everything else the record holds

The career path, and where it branches

Senior Cloud Security Analyst (L3)

Where AI is starting to help

Alert Triage Automation

Threat Intelligence Synthesis

IaC Code Review Assistant

Incident Report Generation

Common questions

Want a read on where you stand?