Cybersecurity Foundations
BeginnerLearn the fundamentals every other CTI Academy path assumes you already have: what a threat, an asset and a vulnerability actually are, how the CIA triad and defense-in-depth hold together, how attackers actually get in through malware and social engineering, and how Linux becomes a daily analysis tool rather than a list of commands to memorise. You will work through core information security concepts, then spend three sections on grep, awk, sed, log analysis, process and network investigation, and bash automation using real-looking incident data. Four sections, 58 lessons, and four case-based missions.
Curriculum
9 more steps behind a free account
Free account
Ready to start Cybersecurity Foundations?
Create a free account to open the remaining 9 steps, track every one you finish and earn your certificate.
- Free to start
- Progress saved on every step
- Certificate on completion
Already have an account? Sign in
About this path
Most people who try to start in cybersecurity do not fail because the material is too hard. They fail because they start in the middle, with a tool, a certification syllabus, or a list of Linux commands, without ever building the small set of ideas everything else in the field assumes you already have. This path starts at the actual beginning: what a threat is, why the CIA triad is worth defending, and why an attacker rarely needs to be clever when a person or a misconfiguration will do the work for them.
The first section builds the concepts every later CTI Academy path leans on: risk, assets and vulnerabilities, the CIA triad, how the threat landscape has actually changed, malware anatomy, social engineering, and the defensive side of the picture: authentication beyond passwords, encoding versus encryption, hashing, digital signatures, firewalls, IDS/IPS/EDR and network architecture, closing with a practical map of where you might fit in the field and how to build a home lab.
The next three sections turn Linux from a set of commands into a working analysis environment. You chain grep, awk and sed on real log and text data, read systemd logs and monitor them live, examine a file system for hidden files and timestamp inconsistencies, investigate suspicious processes and connections, read a packet capture with tcpdump and Zeek, and write enough bash to automate a repeated hunt instead of retyping it every time.
This path assumes nothing beyond basic computer literacy. You do not need to know what a SOC, a CVE or a shell is before you start. Every concept is introduced before it is used, and by the end you should be able to read a log file, a process list or a packet capture and say something specific about what happened, which is the actual prerequisite every other path in the academy, Cyber Threat Intelligence, OSINT, HUMINT and Attack Surface Management, quietly assumes you already cleared.
What you will learn
- Name what you are actually protecting. Tell a threat, a vulnerability and a risk apart, and use the CIA triad to say what "secure" is supposed to mean for a given system.
- Recognise how attackers actually get in. Break down malware by what it does rather than its name, and explain why social engineering beats a technical exploit far more often than headlines suggest.
- Explain the defensive stack you keep hearing about. Tell encoding, encryption and hashing apart, explain what a digital signature actually proves, and place firewalls, IDS, IPS and EDR in the layer each one defends.
- Turn Linux into an analysis tool, not a memory test. Navigate the file system, chain pipes and redirection, and use grep, awk and sed together to pull a specific answer out of a large log file.
- Read a log the way an analyst does. Use journalctl and live monitoring to reconstruct what happened on a system, and tell a routine entry from a suspicious one.
- Investigate a live or captured system. Spot hidden files and timestamp inconsistencies, identify a suspicious process through /proc and lsof, and read a packet capture with tcpdump, BPF filters and TShark.
- Automate a repeated investigation. Write a bash script that runs a hunting routine on a schedule instead of retyping the same commands every time.
Who this path is for
- Complete beginners who want a real foundation before choosing a specialisation, not a buzzword tour of the field.
- Career changers moving into IT or security from an unrelated background who need the vocabulary and the Linux comfort other paths assume.
- Students preparing for an entry-level security or SOC role who want to arrive already comfortable reading a log, a process list and a packet capture.
- Anyone about to start Cyber Threat Intelligence, OSINT, HUMINT or Attack Surface Management who is not yet sure they recognise phishing, malware, a SOC or a hash on sight.
Guides for this path
- Introduction to Information SecurityEvery organization, from global enterprises to small startups, depends on digital infrastructure. With that dependence comes risk. Cyberattacks are growing in frequency, sophistication, and impact, making information security one of the most critical disciplines of the modern era. Whether you are a student exploring career options, an IT professional looking to pivot, or a business leader trying to understand the threat landscape, this guide will give you a solid foundation in the principles, pr
Frequently asked questions
No. This is the one CTI Academy path that assumes nothing beyond basic computer literacy. Every other path, Cyber Threat Intelligence, OSINT, HUMINT, Attack Surface Management, assumes you already cleared this one, or already know its content some other way.
No previous setup is required. The path teaches you how to build one in the "Your Future" module, and every exercise can be worked through the reader itself. A disposable Linux environment helps but is not required to complete the lessons.
No. It does not track a specific certification syllabus. It builds the concepts and Linux fluency that certification study, and every later path in the academy, assumes you already have.
A generic tutorial teaches commands. This path teaches investigation, reading a log, a process list or a packet capture to answer a specific question, which is the actual skill, not the command syntax underneath it.
Cases built around a real-looking artifact, an access log, a memory image, a process listing, a packet capture, where you have to reach a specific conclusion using the grep/awk/sed and Linux investigation skills the preceding lessons taught, not multiple-choice recall.