I Started Learning Cybersecurity 10 Articles Ago — Here’s What Finally Clicked

When I first decided to learn cybersecurity, I honestly didn't know where to begin.

I knew the word.

I knew it had something to do with protecting computers.

And, like many beginners, I probably associated it with hackers typing mysterious commands into black screens.

But the more I learned, the more I realized something important:

Cybersecurity isn't really about the tools. It's about understanding what you're protecting.

So I decided to start from the basics.

Not with advanced hacking tools.

Not with complicated labs.

Just with my own computer.

And that decision completely changed how I look at technology.

It Started With an IP Address

One of the first things I wanted to understand was something incredibly simple:

What is my IP address?

I opened Command Prompt and started experimenting.

At first, an IP address looked like nothing more than a bunch of numbers.

But then I started asking questions.

Why does my computer have an IP address?

Who gives it to my computer?

Is it the same as my public IP?

How does another computer know where to send information?

Suddenly, something I had seen hundreds of times became interesting.

I wasn't just looking at numbers anymore.

I was looking at an identity used inside a network.

That was my first real step into networking.

Then I Started Asking My Computer Questions

After learning about IP addresses, I started using simple network commands.

Commands like:

ipconfig

ping

nslookup

tracert

At first, they looked like random commands I had copied from somewhere.

But slowly, I started understanding what they were showing me.

ipconfig helped me see my network configuration.

ping showed me that my computer could test whether another destination was reachable.

nslookup showed me what happens when a domain name needs to be translated into an IP address.

And tracert gave me a glimpse of the path network traffic can take.

That was when networking stopped feeling like a chapter in a textbook.

It started feeling real.

Then I Discovered Ports

This was another moment that changed how I thought about computers.

I ran:

netstat -ano

And suddenly I was looking at connections and ports on my own machine.

Before this, I had heard people talk about things like:

"Open ports."

"Attack surface."

"Listening services."

They sounded like advanced cybersecurity vocabulary.

But after actually seeing ports on my own computer, the concepts became much easier to understand.

I learned something important:

An open port isn't automatically a vulnerability.

A port can simply be part of a service that needs to communicate.

The important questions are:

What is listening?

Why is it listening?

Should it be accessible?

And what software is behind it?

That was one of my first lessons in thinking like a security learner instead of just a computer user.

Then I Typed a Website Into My Browser

This might sound like the most ordinary thing in the world.

I typed a website address.

Pressed Enter.

The page appeared.

Done.

Except it isn't really done.

There is a lot happening behind that simple action.

My computer needs to communicate with a network.

The domain name needs to be resolved.

Requests need to travel through the network.

A server needs to receive the request.

The server needs to respond.

Then my browser needs to process everything and display the page.

And when HTTPS is involved, the communication is also protected through encryption.

Once I understood even a small part of this process, browsing the web felt different.

Every website became a system instead of just a page.

The Firewall Finally Made Sense

I had heard the word firewall many times before.

But knowing a definition and actually understanding an idea are two different things.

When I looked at Windows Firewall, I started thinking about rules.

What traffic should be allowed?

What traffic should be blocked?

What happens with inbound connections?

What about outbound connections?

And how does this connect with ports?

That last question was important.

I started seeing how different pieces of cybersecurity connect with each other.

A port isn't isolated.

A firewall isn't isolated.

A network connection isn't isolated.

They are all parts of the same system.

And that system is what I am trying to understand.

Developer Tools Changed How I See Websites

Then I opened my browser's Developer Tools.

And websites became even more interesting.

I could see HTML.

I could see CSS.

I could see JavaScript.

Then I opened the Network tab.

Suddenly I could watch requests and responses happening while a website loaded.

I saw status codes such as:

200

404

403

These weren't just numbers anymore.

They were clues about what was happening between my browser and a server.

That was another important realization:

Web security starts with understanding how the web works.

You can't properly understand how a website can be attacked if you don't understand how a normal website communicates in the first place.

Then I Asked a Simple Question:

How does a website know it's me?

This led me into authentication.

I started learning about:

Login forms
Passwords
Sessions
Cookies
Tokens
Password hashing
Authentication
Authorization

Before this, logging into a website felt like one simple action.

Enter username.

Enter password.

Click login.

But behind that button is an entire system.

The browser sends information.

The server processes it.

The server checks whether the credentials are valid.

Then the website needs some way to remember that the user has been authenticated.

That's where concepts like sessions, cookies, and tokens become important.

And then I discovered another important distinction:

Authentication asks, "Who are you?"

Authorization asks, "What are you allowed to do?"

That difference seems simple now.

But learning it made websites feel much more understandable.

And Finally, I Started Thinking About Vulnerabilities

This was probably the biggest change in my thinking.

Instead of asking:

"What hacking tool should I learn?"

I started asking:

"Where could a system make a mistake?"

That's a completely different question.

A website accepts input.

What happens if the input isn't properly handled?

A user logs in.

What happens if authentication is implemented incorrectly?

A user requests something.

What happens if authorization isn't checked properly?

A database receives information.

What happens if the application doesn't safely handle that input?

That's where the idea of a vulnerability started becoming real to me.

I learned about concepts such as SQL injection and cross-site scripting.

I didn't suddenly become a hacker.

I simply started understanding why mistakes in software can become security problems.

And honestly, that is much more valuable for me right now.

So What Does Cybersecurity Mean to Me Now?

After all of this, I don't think of cybersecurity as:

"learning how to hack."

At least not anymore.

To me, cybersecurity is about understanding systems deeply enough to recognize how they can fail, how they can be misused, and how they can be protected.

It involves computers.

Networks.

Operating systems.

Websites.

Applications.

Users.

Data.

Authentication.

Permissions.

Software.

And, most importantly, people.

Because even the strongest technical system can have problems if the person using it makes a mistake.

Cybersecurity is much bigger than I originally imagined.

And I'm still at the beginning.

What These 10 Articles Actually Taught Me

Looking back, I can see a path that I couldn't see when I started.

It looks something like this:

Computer basics

↓

IP addresses

↓

Networking

↓

DNS

↓

Network commands

↓

Ports

↓

Attack surface

↓

Websites

↓

HTTP and HTTPS

↓

Firewalls

↓

Developer Tools

↓

Authentication

↓

Vulnerabilities

↓

Cybersecurity

The interesting thing is that none of these topics exist completely by themselves.

They connect.

That's probably the biggest lesson I've learned.

When I was learning about IP addresses, I didn't know how important networking would become.

When I was learning about ports, I didn't yet understand attack surface.

When I was learning about websites, I didn't understand how much was happening behind one page load.

When I was learning about authentication, I didn't yet think about authorization.

And when I started learning about vulnerabilities, I finally began connecting everything together.

I'm Still a Beginner

I want to be honest about something.

Writing these ten articles doesn't mean I've mastered cybersecurity.

I haven't.

There are still huge areas I haven't properly explored.

Linux.

Python.

Web security testing.

Networking at a deeper level.

Security tools.

CTFs.

Security labs.

Operating systems.

Cryptography.

And countless other topics.

But I don't feel like I'm standing at the same starting point anymore.

Ten articles ago, cybersecurity looked like a giant wall.

Now I can at least see some of the doors.

And that's progress.

What's Next?

This is where my learning gets more serious.

My next goal isn't to collect random hacking tools.

I want to build stronger foundations.

I want to become comfortable with Linux.

I want to learn Python properly.

I want to practice networking more deeply.

I want to eventually work through legal cybersecurity labs and challenges.

I want to learn how security professionals actually investigate problems.

And most importantly, I want to practice only in environments where I have permission to test.

Because learning cybersecurity isn't about breaking into random systems.

It's about understanding systems responsibly.

Ten Articles Later, Something Finally Clicked

When I started this journey, I thought I was learning cybersecurity.

Now I realize I was actually learning how computers communicate, how websites work, how systems trust users, and how small mistakes can create security problems.

Cybersecurity was the bigger picture.

The individual concepts were the pieces.

And these ten articles helped me start putting those pieces together.

I started with an IP address.

Then I followed the connection.

I looked at ports.

I watched network traffic.

I explored websites.

I checked firewalls.

I opened Developer Tools.

I learned about authentication.

I started thinking about vulnerabilities.

And somewhere along the way, cybersecurity stopped looking like a mysterious world of hackers.

It started looking like a giant system that can actually be understood.

This Isn't the End

This is the end of my first ten articles about learning cybersecurity.

But it isn't the end of my cybersecurity journey.

Actually, I think this is where the interesting part begins.

The first chapter was about understanding the foundations.

The next chapter will be about getting my hands dirty.

More practice.

More experiments.

More mistakes.

Contents