DEV Community: CyberVulnx

Linux For Beginners : Part 1

Ajitesh — Thu, 02 Jul 2026 09:29:56 +0000

Introduction:

Linux is one of the most important operating systems in modern computing. It is used in servers, cloud systems, DevOps, and cybersecurity environments.

This series is made for beginners. It is also useful for students and aspiring SOC or cybersecurity learners who want to build a strong foundation in Linux.

In this first article, you will learn:

What Linux is ?
Where it came from.
Why is it open source?
The basic Linux philosophy.
A simple view of Linux architecture.
The Linux file system.
A few basic commands.
How to start practicing Linux safely.

Linux matters because it is used widely in real-world IT. Many production servers, cloud platforms, and security tools run on Linux.

For cybersecurity learners, Linux is especially useful because many logs, commands, and investigation tasks are done in the terminal. Learning Linux gives you a strong base for blue teaming, SOC operations, and forensics.

Red teamers need Linux because many attack, reconnaissance, and post-exploitation tools run on it, and understanding the system helps them work more effectively in real environments.

Origin of Linux and Why It Was Created

Linux has an interesting history that begins with a simple idea: giving people the freedom to use, study, modify, and improve an operating system. To understand Linux, it is helpful to know why it was created and how it evolved into one of the world's most widely used operating systems.

Origin of Linux:
Before Linux, Unix was one of the most popular operating systems used in universities, research institutions, and large organizations.

Although Unix was powerful and reliable, many versions were commercial, expensive, and not easily accessible to students and hobbyists.

In 1991, Linus Torvalds, a computer science student at the University of Helsinki, Finland, started developing a new operating system kernel as a personal project.

His goal was to create a free, Unix-like kernel that anyone could use, learn from, and improve.

On August 25, 1991, Linus announced his project on the Usenet newsgroup comp.os.minix, inviting others to contribute. This collaborative approach marked the beginning of what would become the Linux community.

As developers around the world joined the project, Linux rapidly evolved through community collaboration and continuous improvement.

It is important to remember that Linux is a kernel, not a complete operating system. A complete Linux operating system is created by combining the Linux kernel with software from the GNU Project and other open-source applications. These complete systems are known as Linux distributions (distros), such as Ubuntu, Debian, Fedora, Arch Linux, and openSUSE.

Why Was Linux Created?:
Linux was created to overcome several limitations that existed at the time.

Existing Unix systems were often proprietary, expensive, and difficult for individuals to access or modify.

Linus Torvalds wanted a flexible and Unix-like operating system that he could use and customize on his own computer.

He believed that software development could benefit from collaboration, where developers worldwide could contribute ideas, fix bugs, and improve the system together.

Linux was designed to be portable, stable, efficient, and adaptable for different hardware platforms (Like x86 based, ARM, RISCV, etc).

Because the source code was openly available, users could learn how the operating system worked, customize it to their needs, and contribute improvements back to the community.

This open development model helped Linux evolve rapidly and gain widespread adoption in education, research, enterprise computing, cloud platforms, embedded systems, and cybersecurity.

Why Linux Is Open Source:

Linux is open source because its source code is publicly available. This means people can view it, study how it works, modify it, and share improvements with others.redhat.

This openness is one of the main reasons Linux grew so quickly. It allows developers, companies, and communities to work together, fix problems faster, and improve the system over time.opensource.

For beginners, the simple idea is this: Linux is open source because it gives users more freedom, more transparency, and more control over the software they use.

Linux Philosophy:
Linux is more than just an operating system - it follows a set of design principles that make it simple, flexible, and efficient. These principles, often referred to as the Linux philosophy , encourage building software that is easy to understand, reusable, and capable of working well with other tools.

Some of the key principles of the Linux philosophy are:

Do one thing and do it well: Most Linux commands are designed to perform a single task efficiently. Complex tasks can be completed by combining multiple simple commands.
Everything is a file: In Linux, many system resources such as hardware devices, configuration files, and processes are represented as files, making them easier to access and manage.
Build small & reusable tools: Instead of creating one large program for every task, Linux provides many small utilities that can be combined to solve complex problems.
Combine commands using pipes and redirection: The output of one command can be used as the input for another, allowing users to create powerful command sequences without writing complex programs.
Prefer text-based configuration: Many Linux applications store their settings in plain text files, making them easy to read, edit, back up, and automate.
Automate repetitive tasks: Linux encourages automation through shell scripts and command-line tools, helping administrators and developers save time and reduce manual effort.
Keep the system modular: Different parts of the operating system are designed to work independently while cooperating with one another. This makes Linux easier to maintain, customize, and troubleshoot.

By learning the Linux philosophy early, beginners can better understand why Linux works the way it does and develop good habits for system administration and automation.

Linux Architecture:

Source : https://www.scaler.com/topics/linux-kernel-architecture/

Linux follows a layered architecture, which means each part of the system has a specific role. The diagram shows how user applications communicate with the operating system through the GNU C Library, the system call interface, and then the kernel.

User applications: These are the programs people use directly, such as browsers, editors, terminal tools, and file managers. They run in user space and do not access hardware directly.

GNU C Library (glibc): acts as a bridge between applications and the kernel. It provides common functions that programs use to interact with the operating system in a standard way. This makes software development easier because applications do not need to deal with low-level hardware details

System call interface: This is where a program asks Linux to perform a task such as opening a file, creating a process, or sending data over the network. In simple words, system calls are the requests applications make to the kernel.

Kernel: is the core of Linux. It manages processes, memory, files, devices, and networking. It is the most important part of the operating system because it controls how system resources are used and shared.

Architecture-dependent kernel code : This part helps Linux work with different hardware platforms, such as x86 or ARM systems. That is one reason Linux can run on such a wide range of devices.

Hardware platform: which includes the CPU, RAM, storage, and other devices. Linux sits between the applications and the hardware, making sure both sides communicate properly.

This separation between user space and kernel space is important for stability and security. User programs stay in user space, while the kernel handles sensitive operations in kernel space. This reduces direct hardware access and helps protect the system from errors in applications.

Linux File System:

One of the first concepts every Linux user should understand is the Linux file system. Whether you are a system administrator, developer, or cybersecurity professional, knowing how files and directories are organized is essential for navigating and managing a Linux system.

Unlike Windows, which organizes storage using multiple drive letters such as C: or D:, Linux uses a single hierarchical directory structure that begins at the root directory (/). Every file, directory, storage device, and mounted filesystem exists somewhere under this root, forming a tree-like structure.

Source : https://www.devopsschool.com/blog/linux-tutorials-root-file-systems-in-linux/

Learning how the Linux file system is organized is one of the first practical skills introduced in many cybersecurity training platforms, including TryHackMe, because almost every task - from locating configuration files to analyzing logs - requires efficient navigation through directories.

Files:
A file is a collection of data stored on the system. Files may contain text, images, videos, source code, configuration settings, executable programs, or system logs.

Examples include:

notes.txt : Text document
photo.jpg : Image file
script.sh : Shell script
config.conf : Configuration file
access.log ; System or application log

One unique characteristic of Linux is that many resources, including devices and configuration information, are represented as files.

Directories:
A directory (also called a folder) is used to organize files and other directories into a structured hierarchy.

Understanding Paths:

A path tells Linux where a file or directory is located.

There are two types of paths:

1. Absolute Path:

An absolute path always starts from the root directory (/) and specifies the complete location.

Example: “/home/student/Documents/report.txt”

No matter where you are currently working, this path always points to the same file.

2. Relative Path:

A relative path starts from your current working directory instead of the root.

If your current directory is: “/home/student”

then the relative path: “Documents/report.txt”

points to the same file as: “/home/student/Documents/report.txt”

Relative paths are shorter and commonly used while navigating within the current directory structure.

Basic Commands:

Here are some basic Linux commands. These are enough for to get in touch with Linux, try to execute those commands on any Linux distro. There are many video resources which will help be much helpful for downloading and running Linux.

pwd : shows your current location in the file system.
ls : lists files and folders in the current directory.
cd : changes the directory.
mkdir : creates a new directory.
touch : creates an empty file.
cp : copies files or folders.
mv : moves or renames files and folders.
rm : removes files.
cat : displays the content of a file.
clear : clears the terminal screen.
man : shows the manual page for a command.
whoami : shows the current logged-in user.

Explanation: These commands are the starting point for using Linux from the terminal. They help you navigate folders, create files, manage content, and understand what is happening in the system. Once a beginner gets comfortable with these, it becomes much easier to learn permissions, processes, networking, and scripting later in the series.

Short example:
If you want to create a folder and enter it, you can use:

mkdir practice
cd practice

(Reference: self VM)

Getting Started with Practice:

The best way to learn Linux is by using it regularly in a safe environment. Beginners do not need to start on a real server right away, because there are many free and simple options for practice.

Good places to begin:

Kali in a virtual machine: Install VirtualBox and run Kali inside it. This gives you a safe practice space.
TryHackMe linux fundamental rooms: Good for learning terminal basics in a guided way. ( https://tryhackme.com/module/linux-fundamentals)
Linux Survival: Free — browser-based practice. (https://linuxsurvival.com/)
Labex.io linux Journey: Linux Journey is free, browser-based, and requires zero setup (https://labex.io/linuxjourney/)

What to practice first ?

Navigating folders with pwd, ls, and cd.
Creating and deleting files with touch and rm.
Making folders with mkdir.
Reading files with cat and man.
Moving and renaming files with mv.
Copying files with cp.

The Roadmap for the series:

After Article 1, the series can continue like this:

Linux Commands for Beginners

Linux File System in Detail

Users and Groups

Permissions and Ownership

Processes and Services

Package Management

Networking Basics in Linux

Shell Basics and Shell Scripting

Logs and Troubleshooting

Linux for Cybersecurity and SOC Operations

References:

TryHackMe – Linux Fundamentals Module: https://tryhackme.com/module/linux-fundamentals
Linux Kernel Documentation: https://docs.kernel.orgdocs.kernel
The Art of Unix Programming (Eric S. Raymond): http://www.catb.org/~esr/writings/taoup/
Ubuntu tutorial on the Linux command line for beginners: https://ubuntu.com/tutorials/command-line-for-beginners
Holland Computing Center Linux commands reference: https://hcc.unl.edu/docs/connecting/basic_linux_commands/
Basic Linux commands overview: https://www.geeksforgeeks.org/linux-unix/basic-linux-commands/
Red Hat, What is open source?: https://www.redhat.com/en/topics/open-source/what-is-open-source
Linux Official Course (Free) - https://trainingportal.linuxfoundation.org/courses/introduction-to-linux-lfs101
TryHackMe – Linux Fundamentals Module: https://tryhackme.com/module/linux-fundamentals
Linux Kernel Documentation: https://docs.kernel.orgdocs.kernel
The Art of Unix Programming (Eric S. Raymond): http://www.catb.org/~esr/writings/taoup/
Ubuntu tutorial on the Linux command line for beginners: https://ubuntu.com/tutorials/command-line-for-beginners
Holland Computing Center Linux commands reference: https://hcc.unl.edu/docs/connecting/basic_linux_commands/
Basic Linux commands overview: https://www.geeksforgeeks.org/linux-unix/basic-linux-commands/
Red Hat, What is open source?: https://www.redhat.com/en/topics/open-source/what-is-open-source
Linux Official Course (Free) - https://trainingportal.linuxfoundation.org/courses/introduction-to-linux-lfs101

Cybersecurity Roadmap

Ajitesh — Fri, 26 Jun 2026 06:39:22 +0000

Introduction:
Cybersecurity is one of the most in-demand fields on the planet - and also one of the most confusing to break into. This roadmap cuts through the noise. No fluff, no overwhelming jargon. Just a clear, step-by-step path from zero knowledge to job-ready skills.

Who this is for:
▸ Complete beginners.
▸ Students who want practical skills, not just theory
The Big Picture

Phase Focus Goal
Phase 1 Foundations : Understand how computers & internet actually work
Phase 2 Networking : Read network traffic, understand protocols
Phase 3 Linux & Windows : Navigate both OS like a professional
Phase 4 Programming : Read & write basic scripts
Phase 5 Core Security : Learn how attacks & defense work
Phase 6 Specialize : Pick a lane: Red, Blue, or Cloud

Phase 1 - Foundations:
Before learning how to hack or defend anything, you need to understand how computers and the internet actually work. Skip this and you'll be blindly running tools with no idea why they do what they do.

What to learn:
▸ How computers store and process data (bits, bytes, binary)
▸ What an operating system does
▸ How the internet works at a basic level (client, server, request, response)
▸ What IP addresses, ports, and protocols are

Free resources:
▸ CS50's Introduction to Computer Science : https://pll.harvard.edu/course/cs50-introduction-computer-science
▸ Professor Messer's CompTIA A+ : https://www.professormesser.com/get-a-plus-core-1-certified/

Phase 2 - Networking:
Networking is the bloodline of cybersecurity. Every attack and every defense happens over a network. You cannot protect what you don't understand.

What to learn:
▸ OSI Model - 7 layers, what each one does
▸ TCP/IP - how data actually travels across the internet
▸ Key protocols: DNS, DHCP, HTTP/HTTPS, FTP, SSH, SMTP
▸ Subnetting - how IP ranges work
▸ How firewalls, routers, and switches fit together

Hands-on tools:
▸ Wireshark - capture and read real network traffic
▸ Cisco Packet Tracer - simulate networks for free

Free resources:
▸ Professor Messer's Network+ : https://www.professormesser.com/network-plus/n10-009/n10-009-video/n10-009-training-course/
▸ TryHackMe Pre-Security Path : TryHackMe | Pre Security Training

Phase 3 - Linux & Windows:
In a real job, you won't be clicking icons. You'll be working in terminals and command lines. Get comfortable here before moving on.

Linux - what to learn:
▸ Navigating directories: cd, ls, pwd, find
▸ File permissions: chmod, chown
▸ Processes: ps, kill, top
▸ Networking commands: ifconfig, netstat, ping, curl
▸ Text editing: nano or vim basics

Windows - what to learn:
▸ Command Prompt and PowerShell basics
▸ User and group management
▸ File permissions and registry basics
▸ Windows Event Logs - where everything is recorded

Free resources:
▸ Linux Journey - Linux Journey Official Site | Learn Linux for Free
▸ TryHackMe - Linux Fundamentals (Parts 1, 2, 3) (TryHackMe | Linux Fundamentals Training)
▸ TryHackMe - Windows Fundamentals (Parts 1, 2, 3) ( TryHackMe | Windows Fundamentals Training)

Phase 4 - Programming
You are not trying to become a software developer. But if you can't read code, you can't understand how attacks happen, how tools work, or how to automate your own tasks.

Start with Python - it's the standard in security. Focus only on:
▸ Variables, strings, and data types
▸ Lists, dictionaries (storing collections of data)
▸ If/else logic and loops
▸ Reading and writing files
▸ Basic network scripts using the socket library

Also worth knowing:
▸ Bash scripting - automate repetitive Linux tasks
▸ Basic HTML/JavaScript - helps with web security later

Free resources:
▸ Code with Harry - Python course : https://www.codewithharry.com/tutorial/python
▸ Code with Harry - javascript: https://www.codewithharry.com/tutorial/js
Phase 5 - Core Security Concepts & Tools
Now you have the foundation. Time to learn how attackers think and how defenders respond.

Core concepts to understand:
▸ CIA Triad - Confidentiality, Integrity, Availability
▸ Authentication vs Authorisation
▸ Common attack types: phishing, MITM, SQL injection, XSS, brute force
▸ Malware types: virus, worm, ransomware, trojan, spyware
▸ Vulnerability vs Exploit vs Payload
▸ Defence in depth - layered security approach

Essential tools to get hands-on with:
▸ Nmap - network scanner, find open ports and services
▸ Burp Suite - intercept and analyse web traffic
▸ Metasploit - learn how exploits are structured (legal lab use only)
▸ Wireshark - analyse packet captures
▸ John the Ripper / Hashcat - password cracking basics

Free resources:
▸ TryHackMe - Cybersecurity 101 (TryHackMe | Cyber Security 101 Training)
▸ TryHackMe - Jr Penetration Tester path (TryHackMe | Jr Penetration Tester Training)
▸ PortSwigger Web Security Academy (https://portswigger.net/web-security)

Certifications:
Certs don't replace skill. But they signal to employers that you understand the basics. Here's the recommended order for beginners:

Beginner (start here):
▸ CompTIA Security+ - Most widely recognised entry-level cert. Covers everything broadly.
▸ Google Cybersecurity Certificate (Coursera) - Free with financial aid. Good intro.

Intermediate :
▸ CompTIA CySA+ - Defensive/analyst focused
▸ CEH Practical (Certified Ethical Hacker Practical) - hands-on exam, not multiple choice. Avoid the theory-only version or combine both practical and theory.
▸ eJPT by INE - Practical, beginner penetration testing cert

Reality check: Certificates don’t matter as much as practical skills do. A certificate tells employers you studied. Your lab work, CTF writeups, and GitHub tell them you can actually do the job. Build the skills first, the cert is just the stamp on top.

Phase 6 - Pick Your Specialization
Once you have the foundations, it's time to go deep in one direction. Here are the three main paths:

Red Team (Offensive)
You simulate real attacks to find weaknesses before the bad guys do. This is penetration testing, red teaming, and ethical hacking.

What you'll do:
▸ Scan networks for open ports and vulnerabilities
▸ Exploit misconfigurations and software flaws
▸ Break into systems (legally, in a controlled scope)
▸ Write reports showing what you found and how to fix it

Where to learn:
▸ TryHackMe - Jr Penetration Tester path(TryHackMe | Jr Penetration Tester Training)
▸ TryHackMe - Web Application Pen testing (TryHackMe | Web Application Pentesting Training)

Blue Team (Defensive)
You monitor, detect, and respond to real attacks. This is SOC analysis, incident response, and digital forensics.

What you'll do:
▸ Analyse security logs and alerts
▸ Investigate suspicious activity and incidents
▸ Hunt for threats hiding in the network
▸ Write detection rules and playbooks

Where to learn:
▸ TryHackMe - SOC Level 1 path (TryHackMe | SOC Level 1 Training)
▸ Blue Team Labs Online - (Blue Team Labs Online - Cyber Range)

Cloud Security
As companies move everything to AWS, Azure, and GCP, cloud security skills are exploding in demand. This is one of the highest-paying niches.

What you'll do:
▸ Secure cloud infrastructure and configurations
▸ Manage IAM (Identity & Access Management) policies
▸ Monitor cloud environments for threats
▸ Ensure compliance with frameworks like CIS Benchmarks

Where to learn:
▸ AWS free training (600+ courses) (https://aws.amazon.com/training/)

▸ CloudGoat by Rhino Security Labs (https://github.com/RhinoSecurityLabs/cloudgoat)
Build a Home Lab
A home lab is where you go from student to practitioner. Before setting up software, make sure your system can handle running multiple virtual machines simultaneously.

Minimum system requirements:
▸ RAM: 8GB minimum, 16GB recommended - running 2-3 VMs at once eats memory fast
▸ Processor: Intel Core i5 9th Gen+ or AMD Ryzen 5 5000 series+ — you need virtualisation support (VT-x/AMD-V)
▸ Storage (Preferrable - SSD): 100GB+ free space — VMs take up 20-40GB each

Essential setup:
▸ VirtualBox or VMware (free) - run multiple virtual machines
▸ Kali Linux VM - the standard attacker machine, free download
▸ Windows 10/11 VM - for practicing Windows attacks and defense
▸ Metasploitable - deliberately vulnerable Linux machine to attack
▸ DVWA (Damn Vulnerable Web App) - vulnerable web app for web security practice
▸ Splunk - To detect the attacks

What to do in your lab:
▸ Practice Nmap scanning on your own VMs
▸ Set up a basic SIEM (like Splunk free tier) and generate logs
▸ Try attacking Metasploitable, then defend it
▸ Capture traffic in Wireshark and analyze what you see

Daily Learning Routine
Consistency beats intensity. 1 hour every day beats 7 hours on Sunday.

Suggested daily split (1–2 hours):
▸ 30 min - One TryHackMe room or lab
▸ 20 min - Read one cybersecurity article or news update
▸ 10 min - Write down what you learned (notes = retention)

Weekly goals:
▸ Complete at least 3 hands-on labs
▸ Solve one CTF challenge
▸ Post one thing you learned on LinkedIn or a blog

Resources & Communities:
You will get stuck. That's normal. These communities and resources will help.

Must-follow YouTube channels:
▸ NetworkChuck - great for networking and general intro content (https://www.youtube.com/@NetworkChuck)
▸ John Hammond - CTF walkthroughs and malware analysis ( https://www.youtube.com/@_JohnHammond)
▸ The Cyber Mentor (TCM Security) - practical hacking tutorials( https://www.youtube.com/@TCMSecurityAcademy)
▸ David Bombal - networking and ethical hacking ( https://www.youtube.com/@davidbombal)
▸ Indian Cyber Club - Bug Bounty and ethical hacking (https://www.youtube.com/@AbhishekParashar-ICC)

Resources to use:
▸ TryHackMe ( TryHackMe | Cyber Security Training) - Best for beginners
▸ HacktheBox ( Best Online Cybersecurity Courses & Certifications | HTB Academy) - for intermediate level
▸ PortSwigger Web Academy - Dedicated web application security labs. Completely free. ( https://portswigger.net/web-security)
▸ Overthewire ( Bandit) - Best platform to practise linux for beginners. ( https://overthewire.org/wargames/bandit/)
▸ Blue Team Labs Online - (Blue Team Labs Online - Cyber Range)

Must-bookmark websites:
▸ OWASP Top 10 : the standard list of web vulnerabilities (https://owasp.org/www-project-top-ten/)
▸ MITRE ATT&CK : how real attackers operate ( https://attack.mitre.org/)
▸ CVE Detail : track real vulnerabilities (https://www.cvedetails.com/)
▸ Krebs on Security : real-world security news ( https://krebsonsecurity.com/)
▸ CyberVulnx : CyberVulnX is a student-driven cybersecurity club focused on capture the flag, digital forensics, cyber awareness, and practical cybersecurity learning (https://cybervulnx.in/)

Conclusion:
The cybersecurity industry has a massive skills gap. Companies are desperate for people who can actually do the work - not just talk about it.

Here's what separates candidates who get hired from those who don't:
▸ They have a GitHub with real projects
▸ They've done hundreds of hands-on labs, not just watched tutorials
▸ They can explain what they did and why - in plain English
▸ They keep learning even when nobody is watching

Your degree (or lack of one) matters far less than your demonstrated skill. Build things. Break things. Document everything. Share it publicly.