Registered non-governmental non-profit organisation certificate No. 1052p

Articles

A career in cybersecurity: roles, skills and a learning path

10 min read
A laptop with a terminal window open, a shield and a key

What SOC analysts, pentesters, security engineers and GRC specialists do, which skills you need and how to learn the field legally and safely.

Cybersecurity is the work of protecting computers, networks, software and the data inside them from unauthorised access, theft and damage. Banks, hospitals, schools, shops and public services all depend on the internet today, so the need for people who protect them keeps growing. Many people picture this career from films: a black screen and code scrolling fast. In reality, cybersecurity is about patience, order, constant learning and, above all, respect for the law. In this guide we look at the main roles in the field, what they do day to day, the skills you need, legal ways to practise and a realistic learning plan.

What cybersecurity is and why it matters

Let us start with a simple example. Your front door has a lock, your windows close, and you do not hand your key to strangers. Computer systems work the same way: passwords are keys, network protection is the walls, and updates replace an old, worn-out lock. A cybersecurity specialist finds the weak spots in this “house”, helps fix them and notices in time when someone tries to get in.

The field is built around three core goals:

  • Confidentiality — only people with permission can see the information.
  • Integrity — data is not changed without permission.
  • Availability — the system works and is open to users when they need it.

Every role protects one or more of these goals.

The main roles: who does what

Cybersecurity is not a single job but a family of directions. Here are the four roles beginners hear about most often, explained in plain language.

SOC analyst

A SOC is a security operations centre. The analyst there watches alerts coming in from systems: who logged in and when, which computer started a strange process, whether something on the network looks unusual. The daily work is reading event logs, telling a real threat from a false alarm, documenting the incident and escalating it when needed. Many people enter the field through this role, because it teaches quickly how systems really work.

Pentester (penetration tester)

A pentester is hired by an organisation and, with written permission, looks at its systems through an attacker’s eyes to find weaknesses. The goal is not to break in for its own sake, but to find the problem before a real criminal does and to write a clear report so it can be fixed. A large part of the job is the report: what was found, how dangerous it is and how to fix it. A good pentester is also a good writer.

Security engineer

This specialist builds and configures the defences: firewalls, access rights, encryption, backups and monitoring tools. They work alongside developers and system administrators and make sure new systems are designed securely. People often move into this role after working as system administrators or programmers.

GRC specialist

GRC stands for governance, risk and compliance. This direction is closer to rules and processes than to technology: writing security policies, assessing risks, checking that the organisation meets legal and standard requirements and training staff. It is a good way into the field for people with a background in law, economics or management.

What a day looks like: an illustrative example

Imagine a young SOC analyst called Aziz starting his working day. The example is made up and only meant to explain the job.

  1. In the morning he reviews the list of alerts that came in overnight.
  2. One shows that an employee’s account had many wrong passwords entered in a short time. Aziz checks the logs and finds that the employee simply forgot the password — a false alarm.
  3. Another alert reports a suspicious email from an unknown address. Aziz analyses the email, confirms it is phishing and hands a colleague the task of blocking such messages for other staff.
  4. At the end of the day he writes a short report on what he saw and what he did.

As you can see, the work is mostly careful reading, logical thinking and clear writing.

Ethics and the law: the most important rule

This is the most important section of the article.

Never test a system without permission. Work only on systems you own, in dedicated training labs or with the owner’s written consent.

In Uzbekistan, as in other countries, unauthorised access to computer data, changing it or disrupting a system is a crime punishable by law. Excuses such as “I was just curious” or “I didn’t break anything” do not remove responsibility. You can read the exact rules in the official legislation database, lex.uz.

Practical rules:

  • your neighbour’s Wi-Fi, your school’s website, a friend’s account — do not “test” any of them;
  • even when a pentest is part of your job, permission must be in writing and must clearly state which systems may be tested and for how long;
  • if you stumble on a vulnerability by accident, do not use it — report it to the owner politely and through official channels;
  • never collect or share other people’s personal data.

In cybersecurity, trust is your most valuable asset. An employer hands you their most sensitive systems, so honesty matters even more than skill.

Which skills you need

Networks

Without understanding how data travels across the internet and what an IP address, a port, DNS or a router is, you cannot understand either attacks or defence. Exploring your home router’s settings is a good place to begin.

Linux and operating systems

Many servers and security tools run on Linux. Working with files on the command line, managing users and permissions and viewing processes are core skills. You also need to understand how Windows works, especially its accounts and permissions.

Scripting

Instead of repeating the same task by hand every day, you will need to automate it. Being able to write a simple Python or Bash script — for example, to pull the relevant lines out of a log file — is very useful. You do not have to become a professional programmer, but you should be able to read code and automate a simple task.

English

Documentation, reports about new vulnerabilities, tool manuals and professional communities are mostly in English. Being able to read and understand technical text is a must.

Soft skills

Writing clearly, explaining complex things simply, staying calm under pressure and working as part of a team. Someone who does not panic during an incident is highly valued.

The good news: you do not need to touch anyone else’s systems to practise.

  • CTF competitions. In “capture the flag” competitions, participants solve specially prepared challenges. Many are online, free and have beginner levels.
  • Online labs. Dedicated training platforms provide deliberately vulnerable virtual machines. Practising on them is legal because they were built for exactly that purpose.
  • A home lab. Using virtualisation software, you can install several virtual machines on your own computer and build a small network. It is yours — experiment as much as you like.
  • Open learning materials. Many universities and communities publish free courses, videos and guides.

Before using any platform, read its rules: even on a training site you may only work on the targets you are allowed to.

A realistic learning roadmap

This plan assumes about 6–10 hours of study a week. Everyone’s pace is different — what matters is consistency.

  1. Months 1–2: computer basics. Operating systems, files, users and simple networking ideas. Install Linux in a virtual machine and use it every day.
  2. Months 3–4: networks. Network models, protocols, IP addresses and ports. Observe your own home network with a traffic analysis tool.
  3. Months 5–6: scripting and programming basics. Small Python tasks: reading a file, searching text, producing a simple report.
  4. Months 7–8: security fundamentals. Common types of attack, password security, the idea of encryption and the signs of phishing. Your first challenges in online labs.
  5. Months 9–12: choosing a direction. If you enjoy monitoring, focus on log analysis; if the attacking side interests you, web application security; if you prefer rules and processes, risk assessment. Take part in CTFs.

Keep notes on everything you learn: short summaries and write-ups of lab challenges (where the training platform’s rules allow it). Later these will serve as your portfolio.

Getting ready for your first job: a checklist

Many people come into cybersecurity not directly but through related jobs: IT support, system or network administration, or junior development. In these roles you see in real life how systems work and what mistakes users make, and that experience pays off later. Before you start job hunting, check yourself against this list:

  • I can do basic tasks on the Linux command line.
  • I can draw a diagram of my home network and explain what each device does.
  • I can write a simple script that finds the information I need in a log file.
  • I can explain how a phishing email differs from a normal one.
  • I have solved several lab or CTF challenges and written up my solutions.
  • I can understand a technical article in English, even if I need a dictionary.
  • I know the legal boundaries and follow them strictly.

If you can say “yes” to most of these, you can start applying for entry-level roles.

About certifications

The field has international certifications at entry and professional levels. They help you organise your knowledge and show it to employers, but they do not replace practical skills. Learn the basics first, then pick a certification that fits your goal and check its requirements on its official website.

Myths and beginners’ mistakes

Common myths

  • “You have to be a genius.” No. Patience, curiosity and regular practice matter more.
  • “Cybersecurity means hacking.” Most of the field is about defence, monitoring, documentation and processes.
  • “You need a university degree first.” A degree helps, but many specialists entered the field through self-study and practice.
  • “I’ll learn it in a couple of months.” Even the basics take several months, and learning continues throughout your career.
  • “It’s fine to test someone’s website out of curiosity.” It is not — it breaks the law.

Beginners’ mistakes

  • Skipping the basics and jumping straight to complex tools.
  • Watching videos without repeating the steps by hand.
  • Putting English off “until later”.
  • Relying on one tool without understanding how it works.
  • Not taking notes — after a month everything is forgotten.
  • Not taking legal boundaries seriously.

Conclusion

Cybersecurity is an interesting, responsible and constantly evolving field. To get in, you do not need a special talent; you need computer basics, networking, Linux, simple scripting, English and, most of all, honesty. Start with small steps, practise only in permitted environments and write down what you learn.

If you would like to start this path in a structured way, take a look at our association’s free training programmes: they include cybersecurity, network administration, programming, computer literacy and English. When you are ready, submit an application and take your first step today.

Back to articles

More articles

14 min read

Using AI tools responsibly at work

What AI chat assistants are good for at work, how to write a good prompt, how to check the output and which data never to type in.

15 min read

Algorithmic thinking: the step before coding

Breaking problems down, patterns and abstraction, conditions and loops, pseudocode and flowcharts, simple tasks and tracing by hand, plus practical exercises.

Start learning today

Enrollment is open. Leave an application — our specialists will contact you and help you choose the right field.

Message us on Telegram