<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Om Gohil on Medium]]></title>
        <description><![CDATA[Stories by Om Gohil on Medium]]></description>
        <link>https://medium.com/@ogohel53?source=rss-fbcd6c713b16------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Nk_ufn9pfNYiRvbVaeMPjg.png</url>
            <title>Stories by Om Gohil on Medium</title>
            <link>https://medium.com/@ogohel53?source=rss-fbcd6c713b16------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 21:03:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ogohel53/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[OverTheWire Bandit Walkthrough (Part 3): Levels 16 to 21 Explained for Beginners]]></title>
            <link>https://medium.com/@ogohel53/overthewire-bandit-walkthrough-part-3-levels-16-to-21-explained-for-beginners-4f72429b8b97?source=rss-fbcd6c713b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f72429b8b97</guid>
            <category><![CDATA[overthewire]]></category>
            <category><![CDATA[overthewire-writeup]]></category>
            <category><![CDATA[bandit-overthewire]]></category>
            <category><![CDATA[bandit-level-17]]></category>
            <dc:creator><![CDATA[Om Gohil]]></dc:creator>
            <pubDate>Fri, 20 Nov 2026 18:11:50 GMT</pubDate>
            <atom:updated>2026-11-20T18:11:50.218Z</atom:updated>
            <content:encoded><![CDATA[<p>Nov 20, 2026 · @om</p><p>Port scanning, file comparison, setuid binaries and network tricks: the last Bandit levels, explained step by step in simple English.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yFzenS_cOAy9Wv6gU4HqBQ.png" /><figcaption>level 17–20</figcaption></figure><h3>Level 16 → Level 17: Port Scanning with Nmap</h3><p><strong>Goal:</strong> One port between 31000 and 32000 on localhost has a service that speaks SSL and gives you the next credentials. You do not know which port it is.</p><p><strong>Concept:</strong> Port scanning means checking which ports are open on a machine and what is running on them. The most popular tool for this is nmap. In this level, many ports are open, but only one of them gives you a useful reply.</p><p><strong>Step 1: Find the open ports</strong></p><pre>nmap -p 31000-32000 localhost</pre><ul><li>nmap: the port scanner.</li><li>-p 31000-32000: scan only this range of ports.</li><li>localhost: the machine to scan, which is the one we are on.</li></ul><p><strong>Step 2: Find which ones use SSL</strong></p><pre>nmap -sV -p 31000-32000 localhost</pre><ul><li>-sV: tries to detect the service and its version on each open port. Look for ports marked as ssl.</li></ul><p><strong>Step 3: Try each SSL port</strong></p><p>Send the current password to each SSL port using the command from Level 15. Replace PORT with the port number you found:</p><pre>cat /etc/bandit_pass/bandit16 | openssl s_client -connect localhost:PORT -quiet</pre><p>Some ports simply echo your message back to you. Only one port answers with Correct! and a private SSH key.</p><p><strong>Step 4: Save the key and log in</strong></p><p>Copy the whole key, including the BEGIN and END lines. Save it in a new file inside a folder in /tmp:</p><pre>mkdir /tmp/mykey456<br>cd /tmp/mykey456<br>nano key.private<br>chmod 600 key.private<br>ssh -i key.private bandit17@localhost -p 2220</pre><ul><li>nano key.private: opens a text editor. Paste the key, then press Ctrl + X, then Y, then Enter to save.</li><li>chmod 600: makes the key private. SSH refuses to use a key that other users can read.</li><li>ssh -i: logs in with the key, just like in Level 13.</li></ul><p>Once you are in as bandit17, run cat /etc/bandit_pass/bandit17 to get the password.</p><p><strong>Key takeaway:</strong> nmap shows you what is running on a machine. Scanning first, then testing, is how real security work starts.</p><h3>Level 17 → Level 18: Finding the Difference Between Two Files</h3><p><strong>Goal:</strong> The home directory has two files: passwords.old and passwords.new. The password is the only line that was changed between them.</p><p><strong>Concept:</strong> Each file has many lines, and almost all of them are the same. Comparing them by eye would take forever. The diff command compares two files and shows only the lines that are different.</p><p><strong>Commands:</strong></p><pre>diff passwords.old passwords.new</pre><ul><li>diff: compares two files line by line.</li><li>The first file is passwords.old, the second is passwords.new.</li></ul><p>The output shows two lines:</p><ul><li>A line starting with &lt; comes from the first file (passwords.old).</li><li>A line starting with &gt; comes from the second file (passwords.new).</li></ul><p>The password is the line that starts with &gt;, because the level says the password is the changed line in passwords.new.</p><p><strong>Key takeaway:</strong> diff is a quick way to find what changed between two versions of a file.</p><h3>Level 18 → Level 19: When the Server Logs You Out</h3><p><strong>Goal:</strong> The password is in a file called readme in the home directory. But someone edited .bashrc so you are logged out right after you connect.</p><p><strong>Concept:</strong> .bashrc is a script that runs when your shell starts. The level creator added a line to it that closes your session immediately, so you can never type commands inside the normal shell. But SSH has a useful feature: instead of opening a shell, you can give it one command to run on the server, and it sends back the result.</p><p><strong>Commands:</strong></p><pre>ssh bandit18@bandit.labs.overthewire.org -p 2220 cat readme</pre><p>Run this from your own computer or from any other Bandit level, not from inside Level 18.</p><ul><li>ssh bandit18@bandit.labs.overthewire.org -p 2220: the same login as always.</li><li>cat readme: the command that is sent to the server and run right away. Its output comes back to your screen.</li></ul><p>Enter the password of bandit18 when asked, and the password for the next level is printed.</p><p><strong>Key takeaway:</strong> SSH can run a single remote command. This is very handy when an interactive shell is blocked or broken.</p><h3>Level 19 → Level 20: Using a Setuid Program</h3><p><strong>Goal:</strong> To get the password, use the special program bandit20-do in the home directory.</p><p><strong>Concept:</strong> Normally a program runs with the permissions of the user who starts it. A <strong>setuid</strong> program is different: it runs with the permissions of the user who <strong>owns</strong> the file. Here bandit20-do is owned by bandit20, so when you run it, it can do things as bandit20. That includes reading the file /etc/bandit_pass/bandit20, which only bandit20 can read.</p><p>You can spot a setuid program with ls -l. Look for an s in the permissions, like -rwsr-x---.</p><p><strong>Commands:</strong></p><pre>ls -l<br>./bandit20-do<br>./bandit20-do cat /etc/bandit_pass/bandit20</pre><ul><li>ls -l: the -l flag shows the long format with permissions and owner. The s tells you it is a setuid file.</li><li>./bandit20-do: running it without anything shows how to use it. It runs another command for you.</li><li>./bandit20-do cat /etc/bandit_pass/bandit20: runs cat with bandit20 permissions and prints the password.</li><li>./: tells Linux to run the program from the current directory.</li></ul><p><strong>Key takeaway:</strong> Setuid is useful but dangerous. If a setuid program is not written carefully, attackers can misuse it to gain higher privileges. This is a very common topic in privilege escalation.</p><h3>Level 20 → Level 21: Making the Program Connect to You</h3><p><strong>Goal:</strong> The home directory has a setuid program called suconnect. It connects to a port on localhost that you choose, reads one line, and compares it with the password of the current level (bandit20). If it matches, it sends back the password for the next level.</p><p><strong>Concept:</strong> Here you play both roles. You create your own small server that listens on a port and sends the current password to anyone who connects. Then you run suconnect and tell it to connect to your server. It receives the right password, is happy, and replies with the next password.</p><pre>your netcat listener  &lt;-- suconnect connects here<br>   sends the bandit20 password --&gt;  suconnect checks it<br>   &lt;-- receives the bandit21 password</pre><p><strong>Commands:</strong></p><pre>cat /etc/bandit_pass/bandit20 | nc -l -p 4444 &amp;<br>./suconnect 4444</pre><ul><li>cat /etc/bandit_pass/bandit20: prints the password of the current level.</li><li>nc -l -p 4444: -l means &quot;listen&quot; and -p 4444 sets the port. This starts your own mini server on port 4444. You can use any free port number above 1024.</li><li>&amp;: puts the listener in the background, so you can keep using the same terminal.</li><li>./suconnect 4444: runs the program and tells it to connect to port 4444.</li></ul><p>If everything works, suconnect prints that the password matches. The password of the next level then appears on your screen from the listener.</p><blockquote><em>Tip: If you prefer, open two terminals. Run the listener in the first one and </em><em>./suconnect 4444 in the second one. Do not forget that both terminals must be logged in as </em><em>bandit20.</em></blockquote><p><strong>Key takeaway:</strong> A listener (nc -l) lets your machine act like a server. This idea is the base of many real tools, such as reverse shells, which you will meet later in your security journey.</p><h3>What You Learned in Part 3</h3><p>Congratulations, you have now finished every level in this series up to the password for Level 21. In these last 5 levels you moved from basic file tricks to scanning, SSH tricks and privilege-related ideas:</p><p>Command</p><p>What it does</p><p>Used in</p><p>nmap -p / nmap -sV</p><p>Scan ports and detect services</p><p>Level 16</p><p>diff</p><p>Show the difference between two files</p><p>Level 17</p><p>ssh user@host command</p><p>Run one command on a remote server</p><p>Level 18</p><p>Setuid programs (ls -l, s bit)</p><p>Run a file with its owner’s permissions</p><p>Level 19</p><p>nc -l -p</p><p>Open a listener on a port</p><p>Level 20</p><p>&amp;</p><p>Run a command in the background</p><p>Level 20</p><p>The skills from all three parts (searching, decoding, SSH, ports and permissions) are the same ones used daily by SOC analysts and penetration testers. The next levels of Bandit build on them with cron jobs, scripting and Git.</p><p>If you liked this guide, watch the full video series on my YouTube channel: <a href="https://www.youtube.com/@TOmSec-OG">TOmSec-OG</a>. Follow me here on Medium for more cybersecurity walkthroughs.</p><p>Happy hacking!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f72429b8b97" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OverTheWire Bandit Walkthrough (Part 2): Levels 10 to 16 Explained for Beginners]]></title>
            <link>https://medium.com/@ogohel53/overthewire-bandit-walkthrough-part-2-levels-10-to-16-explained-for-beginners-cd424b6a2d6c?source=rss-fbcd6c713b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd424b6a2d6c</guid>
            <category><![CDATA[bandit-overthewire]]></category>
            <category><![CDATA[bandit-level-10]]></category>
            <category><![CDATA[overthewire]]></category>
            <category><![CDATA[overthewire-writeup]]></category>
            <category><![CDATA[bandit-level]]></category>
            <dc:creator><![CDATA[Om Gohil]]></dc:creator>
            <pubDate>Fri, 20 Nov 2026 18:08:55 GMT</pubDate>
            <atom:updated>2026-11-20T18:08:55.353Z</atom:updated>
            <content:encoded><![CDATA[<p>Nov 20, 2026 · @om</p><p>Encoding, compression, SSH keys and network ports: the next 6 Bandit levels, explained step by step in simple English.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yFzenS_cOAy9Wv6gU4HqBQ.png" /></figure><h3>Level 10 → Level 11: Decoding Base64</h3><p><strong>Goal:</strong> The password is stored in data.txt, but the content is encoded with Base64.</p><p><strong>Concept:</strong> Base64 is a way to turn data into plain letters and numbers so it can travel safely in text. It looks like random text, often ending with = signs. Important: Base64 is <strong>encoding</strong>, not encryption. Anyone can decode it, and no key is needed.</p><p><strong>Commands:</strong></p><pre>cat data.txt<br>base64 -d data.txt</pre><ul><li>cat data.txt: shows the encoded text so you can see what it looks like.</li><li>base64: the tool that encodes and decodes Base64 data.</li><li>-d: the &quot;decode&quot; flag. Without it, the tool would encode the text instead.</li></ul><p>The decoded text tells you the password.</p><p><strong>Key takeaway:</strong> If text looks like random letters ending with =, it is probably Base64. Decode it with base64 -d.</p><h3>Level 11 → Level 12: ROT13 Cipher</h3><p><strong>Goal:</strong> The password is in data.txt, where all lowercase and uppercase letters were rotated by 13 positions.</p><p><strong>Concept:</strong> This is called ROT13, a very old and simple cipher. Each letter moves 13 places forward in the alphabet, so A becomes N, B becomes O, and so on. The alphabet has 26 letters, so applying ROT13 a second time brings you back to the original text. That means the same operation both hides and reveals the message.</p><p><strong>Commands:</strong></p><pre>cat data.txt | tr &#39;A-Za-z&#39; &#39;N-ZA-Mn-za-m&#39;</pre><ul><li>tr: short for &quot;translate&quot;. It replaces characters one by one.</li><li>&#39;A-Za-z&#39;: the original letters (all uppercase, then all lowercase).</li><li>&#39;N-ZA-Mn-za-m&#39;: the letters to replace them with. It starts at N and wraps around to A-M, and the same for lowercase.</li><li>|: sends the file content into tr.</li></ul><p><strong>Key takeaway:</strong> tr can swap characters in text. ROT13 is easy to break, so never use it to protect real secrets.</p><h3>Level 12 → Level 13: Hexdump and Layers of Compression</h3><p><strong>Goal:</strong> The password is in data.txt, which is a hexdump of a file that was compressed many times.</p><p><strong>Concept:</strong> A hexdump shows the bytes of a file as hexadecimal text. Here someone took a compressed file, turned it into a hexdump, and then compressed it again and again, like a box inside a box inside a box. Your job is to turn the hexdump back into a real file and then open each layer one by one until you see readable text.</p><p>We do not have permission to write files in our home directory, so first we make our own working folder in /tmp.</p><p><strong>Step 1: Set up a working folder</strong></p><pre>mkdir /tmp/mywork123<br>cp data.txt /tmp/mywork123<br>cd /tmp/mywork123</pre><ul><li>mkdir: creates a new directory. Use any unique name instead of mywork123.</li><li>cp: copies a file to another place.</li></ul><p><strong>Step 2: Turn the hexdump back into a file</strong></p><pre>xxd -r data.txt &gt; data<br>file data</pre><ul><li>xxd -r: the -r flag means &quot;reverse&quot;. It converts the hexdump back into the original binary data.</li><li>&gt;: saves the output into a new file called data.</li><li>file data: tells you what type of file it is now.</li></ul><p><strong>Step 3: Open each layer</strong></p><p>The file command will say what kind of compression is used. Use the table below, then run file again on the new result. Repeat until file says ASCII text.</p><p>If file says</p><p>Rename it</p><p>Then run</p><p>gzip compressed data</p><p>mv data data.gz</p><p>gzip -d data.gz</p><p>bzip2 compressed data</p><p>mv data data.bz2</p><p>bzip2 -d data.bz2</p><p>POSIX tar archive</p><p>mv data data.tar</p><p>tar -xf data.tar</p><ul><li>mv: renames a file. Tools like gzip and bzip2 need the right extension (.gz, .bz2) to work.</li><li>gzip -d and bzip2 -d: the -d flag means &quot;decompress&quot;.</li><li>tar -xf: -x means extract and -f means &quot;use this file&quot;. A tar archive can create a new file with a different name, so run ls to see it.</li></ul><p>When the last result is ASCII text, read it with cat.</p><blockquote><em>Tip: Always run </em><em>file after every step. It is like a map that tells you what to do next.</em></blockquote><p><strong>Key takeaway:</strong> Compressed files can be nested many times. Identify the type with file, then use the right tool to open it.</p><h3>Level 13 → Level 14: Logging In with an SSH Key</h3><p><strong>Goal:</strong> There is no password this time. Instead the home directory has a private SSH key called sshkey.private. You use it to log in as bandit14.</p><p><strong>Concept:</strong> SSH can verify who you are in two ways: with a password, or with a key pair. A key pair has a public key (kept on the server) and a private key (kept by you). If your private key matches, the server lets you in without asking for a password. Treat a private key like a house key and never share it.</p><p>The password of bandit14 is stored in /etc/bandit_pass/bandit14. Only bandit14 can read it, so we first log in as that user.</p><p><strong>Commands:</strong></p><pre>ls<br>ssh -i sshkey.private bandit14@localhost -p 2220<br>cat /etc/bandit_pass/bandit14</pre><ul><li>ssh -i sshkey.private: the -i flag means &quot;identity file&quot;. It tells SSH to use this key to log in.</li><li>bandit14@localhost: log in as user bandit14. localhost means &quot;this same machine&quot;, because we are already inside the Bandit server.</li><li>-p 2220: the same Bandit port as before.</li><li>cat /etc/bandit_pass/bandit14: after login, this prints the password for bandit14.</li></ul><p>The first time you connect, SSH asks if you trust the server. Type yes and press Enter.</p><blockquote><em>Tip: If SSH says the key permissions are too open, run </em><em>chmod 600 sshkey.private first. The number </em><em>600 means only the owner can read and write the file.</em></blockquote><p><strong>Key takeaway:</strong> SSH keys are a safer and more common way to log in than passwords. The -i flag lets you choose which key to use.</p><h3>Level 14 → Level 15: Talking to a Port with Netcat</h3><p><strong>Goal:</strong> Send the current level’s password (bandit14) to port 30000 on localhost. The service replies with the next password.</p><p><strong>Concept:</strong> A computer can run many network services at the same time. A <strong>port</strong> is like a numbered door that a service listens on. To get the password, you connect to port 30000 and send the right message. The tool for raw connections like this is nc, short for <strong>netcat</strong>.</p><p><strong>Commands:</strong></p><pre>cat /etc/bandit_pass/bandit14 | nc localhost 30000</pre><ul><li>cat /etc/bandit_pass/bandit14: prints the password of the current level.</li><li>|: sends that password into the next command.</li><li>nc localhost 30000: opens a connection to port 30000 on this machine and sends the password through it.</li></ul><p>The service checks the password and replies with Correct! and the next password.</p><p>You can also do it by hand: run nc localhost 30000, then type or paste the password and press Enter.</p><p><strong>Key takeaway:</strong> nc is like a simple chat tool for network ports. It is very useful for testing services.</p><h3>Level 15 → Level 16: Talking to an SSL Port</h3><p><strong>Goal:</strong> Send the current level’s password to port 30001 on localhost, but this time using SSL/TLS encryption.</p><p><strong>Concept:</strong> In the last level the connection was plain text, so anyone watching the network could read it. SSL/TLS encrypts the connection. This is the same technology behind the padlock you see in your browser (HTTPS). A normal nc cannot speak SSL, so we use openssl, which can.</p><p><strong>Commands:</strong></p><pre>openssl s_client -connect localhost:30001</pre><p>After it connects, paste the password of the current level and press Enter.</p><ul><li>openssl: a toolkit for working with encryption.</li><li>s_client: runs OpenSSL as a client that connects to an SSL server.</li><li>-connect localhost:30001: the address and port to connect to, written as host:port.</li></ul><p>The connection prints a lot of certificate details. You can ignore them and look for the Correct! message near the end.</p><p>A cleaner one-line version:</p><pre>cat /etc/bandit_pass/bandit15 | openssl s_client -connect localhost:30001 -quiet</pre><ul><li>-quiet: hides the certificate details and shows only the server reply.</li></ul><blockquote><em>Tip: If the output says </em><em>KEYUPDATE or </em><em>RENEGOTIATING instead of the password, use the </em><em>-quiet version. It avoids this problem.</em></blockquote><p><strong>Key takeaway:</strong> Use openssl s_client to talk to any service that uses SSL/TLS.</p><h3>What You Learned in Part 2</h3><p>These 6 levels moved us from reading files to working with encoding, archives, keys and the network:</p><p>Command</p><p>What it does</p><p>Used in</p><p>base64 -d</p><p>Decodes Base64 text</p><p>Level 10</p><p>tr</p><p>Replaces characters (used for ROT13)</p><p>Level 11</p><p>xxd -r</p><p>Turns a hexdump back into a binary file</p><p>Level 12</p><p>gzip, bzip2, tar</p><p>Open compressed files and archives</p><p>Level 12</p><p>ssh -i</p><p>Log in with a private key</p><p>Level 13</p><p>nc</p><p>Connect to a network port</p><p>Level 14</p><p>openssl s_client</p><p>Connect to a port that uses SSL/TLS</p><p>Level 15</p><p>In Part 3 we scan for open ports with nmap, compare files with diff, and learn how to use setuid programs.</p><p>If you liked this guide, watch the full video series on my YouTube channel: <a href="https://www.youtube.com/@TOmSec-OG">TOmSec-OG</a>. Follow me here on Medium for the next part.</p><p>👾👾 Happy hacking!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd424b6a2d6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OverTheWire Bandit Walkthrough (Part 1): Levels 0 to 10 Explained for Beginners]]></title>
            <link>https://medium.com/@ogohel53/overthewire-bandit-walkthrough-part-1-levels-0-to-10-explained-for-beginners-dee8e43e4b44?source=rss-fbcd6c713b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/dee8e43e4b44</guid>
            <category><![CDATA[bandit-overthewire]]></category>
            <category><![CDATA[bandit-walkthrough]]></category>
            <category><![CDATA[overthewire]]></category>
            <dc:creator><![CDATA[Om Gohil]]></dc:creator>
            <pubDate>Fri, 20 Nov 2026 15:49:40 GMT</pubDate>
            <atom:updated>2026-11-20T19:31:18.486Z</atom:updated>
            <content:encoded><![CDATA[<p>Nov 20, 2026 · @om</p><p>A beginner-friendly guide to the first 10 Bandit levels, with every command, flag and concept explained in simple English.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yFzenS_cOAy9Wv6gU4HqBQ.png" /></figure><h3>What Is OverTheWire Bandit?</h3><p>Bandit is a free wargame from OverTheWire, made for people who are new to Linux and cybersecurity. Every level hides a password for the next level. You find it using basic Linux commands, then use it to log in to the next level.</p><p>Think of it like a game of locked doors. Each door teaches you one new skill, and the password is the key to the next door.</p><p>In this series I explain every command and every flag, so even a complete beginner can follow along.</p><blockquote><em>Note: In this article I write passwords as </em><em>&lt;password&gt;. Use the real password you find on your own screen.</em></blockquote><h3>Before You Start: How to Connect</h3><p>Every Bandit level uses the same server and the same port. You connect with SSH from your terminal:</p><pre>ssh bandit0@bandit.labs.overthewire.org -p 2220</pre><p>Here is what each part means:</p><ul><li>ssh: the tool that lets you log in to another computer safely over the network.</li><li>bandit0: the username. For Level 0 it is bandit0, for Level 1 it is bandit1, and so on.</li><li>bandit.labs.overthewire.org: the address of the Bandit server.</li><li>-p 2220: the port number. Normal SSH uses port 22, but Bandit uses 2220.</li></ul><p>The password for Level 0 is also bandit0. When you type a password in Linux, nothing appears on the screen. This is normal, so just type it and press Enter.</p><p>To move to the next level, type exit to leave the current level. Then connect again with the next username (for example bandit1) and the password you just found.</p><blockquote><em>Tip: Keep a notes file on your own computer with each level’s password. You will need them if you log out.</em></blockquote><h3>Level 0 → Level 1: Reading Your First File</h3><p><strong>Goal:</strong> The password for the next level is stored in a file called readme in the home directory.</p><p><strong>Concept:</strong> When you log in, you start in your home directory. Two commands are enough here: one to look around and one to read a file.</p><p><strong>Commands:</strong></p><pre>ls<br>cat readme</pre><ul><li>ls: lists the files and folders in the current directory.</li><li>cat: prints the content of a file on the screen.</li></ul><p><strong>Key takeaway:</strong> Use ls to look and cat to read. Many Bandit levels start with this simple pair.</p><h3>Level 1 → Level 2: A File Named Dash</h3><p><strong>Goal:</strong> The password is in a file called - in the home directory.</p><p><strong>Concept:</strong> A single dash - has a special meaning in Linux. Many commands treat it as &quot;read from the keyboard&quot; instead of a file name. So if you type cat -, the terminal just waits for you to type something. To fix this, give the file a clear path so Linux knows it is a file.</p><p><strong>Commands:</strong></p><pre>ls<br>cat ./-</pre><ul><li>./: means &quot;the current directory&quot;. Writing ./- tells Linux that - is a file here, not a special symbol.</li></ul><p>Another way that also works:</p><pre>cat &lt; -</pre><ul><li>&lt;: sends the content of a file into the command as input.</li></ul><p><strong>Key takeaway:</strong> When a file name starts with a dash, add ./ before it.</p><h3>Level 2 → Level 3: Spaces in the File Name</h3><p><strong>Goal:</strong> The password is in a file called spaces in this filename.</p><p><strong>Concept:</strong> The terminal uses spaces to separate words. If you type cat spaces in this filename, Linux thinks you gave it four different files. You must tell the terminal that the spaces belong to one name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hn98iwyErijABGCh7BNeJA.png" /></figure><p><strong>Commands:</strong></p><pre>ls<br>cat ./&quot;--spaces in this filename--&quot;</pre><ul><li>&quot; &quot; (quotes): everything inside the quotes is treated as one single name.</li></ul><p>You can also put a backslash before each space:</p><pre>cat spaces\ in\ this\ filename</pre><ul><li>\ (backslash): means &quot;treat the next character as normal text&quot;, so the space is not a separator.</li></ul><blockquote><em>Tip: Press the Tab key after typing a few letters. The terminal completes the file name for you and adds the backslashes automatically.</em></blockquote><p><strong>Key takeaway:</strong> Use quotes or backslashes when a file name has spaces.</p><h3>Level 3 → Level 4: Finding a Hidden File</h3><p><strong>Goal:</strong> The password is in a hidden file inside the inhere directory.</p><p><strong>Concept:</strong> In Linux, any file whose name starts with a dot . is hidden. A normal ls does not show it. You need to ask ls to show all files, including hidden ones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o9TwaEUFOgHZ-83zRH0Hdg.png" /></figure><p><strong>Commands:</strong></p><pre>cd inhere<br>ls<br>ls -a<br>cat ...Hiding-From-You</pre><ul><li>cd inhere: moves you into the inhere directory.</li><li>ls: shows nothing, because the file is hidden.</li><li>ls -a: the -a flag means &quot;all&quot;. It shows hidden files too.</li><li>cat ...Hiding-From-You: reads the hidden file. Its name starts with three dots.</li></ul><p><strong>Key takeaway:</strong> Always try ls -a when a folder looks empty.</p><h3>Level 4 → Level 5: Which File Is Human-Readable?</h3><p><strong>Goal:</strong> The inhere directory has several files. Only one of them contains readable text, and that one has the password.</p><p><strong>Concept:</strong> Some files hold normal text, and others hold random binary data that looks like garbage on the screen. The file command checks what type of data a file contains, so you do not need to open each one by hand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-SM2U-n3w5CdZuq2HOL1pg.png" /></figure><p><strong>Commands:</strong></p><pre>cd inhere<br>ls<br>file ./*<br>cat ./-file07</pre><ul><li>file: tells you the type of each file, for example ASCII text or data.</li><li>./*: the * means &quot;every file in this folder&quot;. The ./ is needed because the file names start with a dash (same trick as Level 1).</li><li>cat ./-file07: reads the file marked as ASCII text. In this level it is -file07.</li></ul><p><strong>Key takeaway:</strong> Use file to check a file before you open it.</p><h3>Level 5 → Level 6: Searching with Filters</h3><p><strong>Goal:</strong> Somewhere inside the inhere directory there is a file that is human-readable, exactly 1033 bytes in size, and not executable.</p><p><strong>Concept:</strong> The inhere directory has many sub-folders with many files, so checking them one by one is slow. The find command can search through all folders at once and filter files by size, type and permissions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*joY_JqcKEl71IjR39aG2PA.png" /></figure><p><strong>Commands:</strong></p><pre>cd inhere<br>find . -type f -size 1033c ! -executable<br>cat ./maybehere07/.file2</pre><ul><li>find .: start searching from the current directory (. means &quot;here&quot;).</li><li>-type f: look only for normal files, not folders.</li><li>-size 1033c: the file size must be exactly 1033 bytes. The letter c means bytes.</li><li>! -executable: the ! means &quot;not&quot;. So this keeps only files that are not executable.</li></ul><p>The search gives you one file path. Read it with cat. In this level it is ./maybehere07/.file2.</p><p><strong>Key takeaway:</strong> find is like a smart search bar for your terminal. Combine its filters to narrow down results.</p><h3>Level 6 → Level 7: Searching the Whole Server</h3><p><strong>Goal:</strong> The password is stored somewhere on the server. The file is owned by user bandit7, owned by group bandit6, and is 33 bytes in size.</p><p><strong>Concept:</strong> Every file in Linux has an owner (a user) and a group. You can use find to search by these details. This time we search the whole system, starting from the root directory /.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E4AHXJPnbF_3Y5WtuVTchw.png" /></figure><p><strong>Commands:</strong></p><pre>find / -user bandit7 -group bandit6 -size 33c 2&gt;/dev/null<br>cat /var/lib/dpkg/info/bandit7.password</pre><ul><li>find /: start the search from the root of the whole system.</li><li>-user bandit7: the file must be owned by the user bandit7.</li><li>-group bandit6: the file must belong to the group bandit6.</li><li>-size 33c: the file must be exactly 33 bytes.</li><li>2&gt;/dev/null: hides all the &quot;Permission denied&quot; errors. The number 2 means the error output, and /dev/null is like a trash bin that throws away anything sent to it.</li></ul><p>Without 2&gt;/dev/null your screen fills with hundreds of error lines. With it, you see only the real result: /var/lib/dpkg/info/bandit7.password.</p><p><strong>Key takeaway:</strong> Use 2&gt;/dev/null to keep your results clean when you search the whole system.</p><h3>Level 7 → Level 8: Finding a Word Inside a File</h3><p><strong>Goal:</strong> The password is stored in data.txt, on the same line next to the word millionth.</p><p><strong>Concept:</strong> data.txt is a huge file with thousands of lines. Reading it by eye is not possible. The grep command searches for a word inside a file and prints only the lines that contain it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BvDP-st_ejLADGWN5QyxPQ.png" /></figure><p><strong>Commands:</strong></p><pre>grep millionth data.txt</pre><ul><li>grep: searches for text inside a file.</li><li>millionth: the word we are looking for.</li><li>data.txt: the file to search in.</li></ul><p>The output is one line. The word after millionth is the password.</p><p><strong>Key takeaway:</strong> grep is one of the most useful commands for finding information fast.</p><h3>Level 8 → Level 9: The One Line That Appears Only Once</h3><p><strong>Goal:</strong> The password is the only line in data.txt that appears exactly once. All other lines are repeated.</p><p><strong>Concept:</strong> The uniq command can filter repeated lines, but it only compares lines that are next to each other. So first you must sort the file, which puts identical lines side by side. Then uniq can find the single line.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mQfsZF5iTs4rsTAfmq0x1Q.png" /></figure><p><strong>Commands:</strong></p><pre>sort data.txt | uniq -u</pre><ul><li>sort data.txt: arranges all lines in order, so repeated lines come together.</li><li>| (pipe): takes the output of the first command and sends it as input to the second command.</li><li>uniq -u: the -u flag means &quot;unique&quot;. It prints only the lines that appear one time.</li></ul><p><strong>Key takeaway:</strong> The pipe | lets you chain small commands together to solve bigger problems. Remember that uniq always needs sorted input.</p><h3>Level 9 → Level 10: Readable Text Inside a Binary File</h3><p><strong>Goal:</strong> The password is in data.txt, in one of the few human-readable strings. It comes after several = characters.</p><p><strong>Concept:</strong> data.txt is a binary file, so it is mostly unreadable symbols. If you use cat, your terminal shows garbage. The strings command pulls out only the readable text from a binary file. Then grep can pick the line we need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lOEESZyiL80JrG1Fx-9Udw.png" /></figure><p><strong>Commands:</strong></p><pre>strings data.txt | grep &quot;==&quot;</pre><ul><li>strings: extracts printable (readable) text from a file.</li><li>|: sends that text into the next command.</li><li>grep &quot;==&quot;: keeps only the lines that contain two or more equal signs.</li></ul><p>Look for the line that has a row of = characters followed by the password.</p><p><strong>Key takeaway:</strong> Never use cat on an unknown binary file. Use strings to safely see the readable parts.</p><h3>What You Learned in Part 1</h3><p>In just 10 levels you learned the basic toolkit that every Linux user and security analyst needs:</p><p>Command</p><p>What it does</p><p>Used in</p><p>ls / ls -a</p><p>List files, with or without hidden ones</p><p>Levels 0, 3</p><p>cat</p><p>Print a file on the screen</p><p>Levels 0 to 5</p><p>cd</p><p>Move into a directory</p><p>Levels 3 to 5</p><p>file</p><p>Check what type a file is</p><p>Level 4</p><p>find</p><p>Search files by size, owner, group and type</p><p>Levels 5, 6</p><p>grep</p><p>Search for text inside a file</p><p>Levels 7, 9</p><p>sort and uniq</p><p>Order lines and remove repeats</p><p>Level 8</p><p>strings</p><p>Pull readable text out of a binary file</p><p>Level 9</p><p>| (pipe)</p><p>Connect two commands together</p><p>Levels 8, 9</p><p>In Part 2 we move to encoding, compression, SSH keys and our first network commands.</p><p>If you liked this guide, watch the full video series on my YouTube channel: <a href="https://www.youtube.com/@TOmSec-OG">TOmSec-OG</a>. Follow me here on Medium for the next parts.</p><p>Happy hacking!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dee8e43e4b44" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[️ How I Built an Enterprise-Style SOC Detection & Response Lab Using Wazuh SIEM]]></title>
            <link>https://medium.com/@ogohel53/%EF%B8%8F-how-i-built-an-enterprise-style-soc-detection-response-lab-using-wazuh-siem-d42081e5fc92?source=rss-fbcd6c713b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/d42081e5fc92</guid>
            <category><![CDATA[threat-detection]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security-operation-center]]></category>
            <category><![CDATA[wazuh]]></category>
            <dc:creator><![CDATA[Om Gohil]]></dc:creator>
            <pubDate>Tue, 27 Jan 2026 06:09:59 GMT</pubDate>
            <atom:updated>2026-01-27T06:09:59.498Z</atom:updated>
            <content:encoded><![CDATA[<p>#CyberSecurity #SOC #Wazuh #SIEM #BlueTeam #MITREATTACK #IncidentResponse #ThreatDetection #SecurityOperations</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-UpY50KhLiY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-UpY50KhLiY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-UpY50KhLiY%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/12fe9171fa5ee8718787b017a45f810f/href">https://medium.com/media/12fe9171fa5ee8718787b017a45f810f/href</a></iframe><h3>Introduction: Why SOC Skills Matter More Than Ever</h3><p>In today’s evolving cyber threat landscape, organizations don’t just need security tools — they need <strong>skilled Security Operations Center (SOC) analysts</strong> who can detect, investigate, and respond to attacks in real time.</p><p>While many beginners learn SIEM tools through tutorials, <strong>real SOC work is very different</strong>. It involves:</p><ul><li>Understanding attacker behavior</li><li>Correlating logs from multiple systems</li><li>Mapping detections to threat frameworks</li><li>Documenting evidence for investigation and audits</li></ul><p>To gain hands-on, real-world SOC experience, I built an <strong>enterprise-style SOC Detection &amp; Response lab using Wazuh SIEM</strong>, focused on <strong>realistic attack simulations and evidence-driven analysis</strong>.</p><p>This article explains <strong>how the lab was built, what attacks were simulated, and how detections were performed like a real SOC analyst</strong>.</p><h3>Why I Built This SOC Lab (Beyond Tutorials)</h3><p>Most SIEM labs stop at:</p><ul><li>Installing the SIEM</li><li>Generating logs</li><li>Viewing dashboards</li></ul><p>But a real SOC analyst must answer deeper questions:</p><ul><li>What exactly happened?</li><li>Which endpoint was affected?</li><li>Is this activity malicious or benign?</li><li>What evidence supports the alert?</li><li>What should be the response?</li></ul><h3>Project Goals</h3><ul><li>Build an <strong>enterprise-style SOC environment</strong></li><li>Simulate <strong>real-world cyber attacks</strong></li><li>Detect threats using <strong>Wazuh SIEM</strong></li><li>Map detections to <strong>MITRE ATT&amp;CK</strong></li><li>Maintain <strong>SOC-standard documentation and evidence</strong></li></ul><p>This project was designed as <strong>proof-of-work</strong>, not a demo lab.<br>Real SOC Lab Setup (Physical Environment)</p><h3>Real SOC Lab Setup (Physical Environment)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JccBzHvRZNWpfAc-poF37g.jpeg" /></figure><p>Unlike single-VM labs, this project used a <strong>real physical lab setup</strong> with multiple systems running simultaneously.</p><h3>Why This Matters</h3><ul><li>Real-time attack execution</li><li>Concurrent alert generation</li><li>Analyst-style investigation under realistic workload conditions</li></ul><p>This setup closely resembles <strong>real SOC operational environments</strong>.</p><h3>SOC Lab Architecture (Enterprise Design)</h3><p>The lab follows a <strong>centralized SOC architecture</strong>, commonly used in enterprises.</p><h3>Architecture Components</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*8F-mSAR1taoPT9xYRN2Ffw.png" /></figure><ul><li><strong>Wazuh Manager &amp; Dashboard</strong> — Central SIEM for log analysis and alerting</li><li><strong>Windows Endpoints</strong> — Aditya &amp; Jamod</li><li><strong>Ubuntu Linux Endpoint</strong> — Devang</li><li><strong>Kali Linux</strong> — Attacker machine for simulations</li><li><strong>Slack Integration</strong> — Real-time alert notifications</li></ul><p>All systems operated inside a <strong>controlled internal network</strong>, ensuring ethical and safe testing.</p><h3>SOC Workflow Implemented in the Lab</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YLk_PXGUCwWNRmMV0X396w.png" /></figure><p>The lab follows a standard <strong>SOC operational workflow</strong>:</p><ol><li>Security events generated on endpoints</li><li>Log collection using Wazuh agents</li><li>Event correlation and detection rules</li><li>Alert generation in Wazuh</li><li>Analyst triage and investigation</li><li>Evidence documentation</li></ol><p>This workflow mirrors how <strong>SOC L1 and SOC L2 analysts</strong> operate in real environments.</p><h3>Attack Simulations &amp; Detection Use Cases</h3><h3>Linux Endpoint (Ubuntu — Devang)</h3><h4>SSH Brute Force Detection</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GwxcbLXe8ud9Xsk7Ur06nQ.png" /><figcaption>ubuntu devang ssh bruteforce</figcaption></figure><p>SSH brute-force attacks are one of the most common attacks against Linux servers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nirge19XwzxR9Lp1Fymrpg.png" /><figcaption>Techniques Performed on this end point</figcaption></figure><p><strong>Detection approach:</strong></p><ul><li>Monitored /var/log/auth.log</li><li>Detected repeated authentication failures</li><li>Correlated events within a defined time window</li></ul><p><strong>MITRE ATT&amp;CK Mapping:</strong></p><ul><li>T1110 — Brute Force</li></ul><p>This detection helps identify credential access attempts before successful compromise.</p><h4>Nmap Network Scan Detection</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Ot2E2FGIgpY0QGGsj1itQ.png" /><figcaption>Nmap Scan Performed On Ub</figcaption></figure><p>Attackers often begin with <strong>network reconnaissance</strong> to discover open ports and services.</p><p><strong>Detection approach:</strong></p><ul><li>Identified abnormal network activity</li><li>Analyzed vulnerability and threat detection telemetry</li><li>Correlated scanning behavior using Wazuh dashboards</li></ul><p><strong>MITRE ATT&amp;CK Mapping:</strong></p><ul><li>T1046 — Network Service Scanning</li><li>T1595 — Active Scanning</li></ul><p>Early detection of reconnaissance significantly reduces attack surface risk.</p><h3>Windows Endpoint (Aditya)</h3><h4>Failed Login Attempt Detection</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0D69yBVUHwkosGFCFVs1FA.png" /><figcaption>Before login Attempts</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y1E4ODEeAYN7p26h9yy52g.png" /><figcaption>After Login Attempts</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ycLtIGjgpizXKPjAdHMaIg.png" /><figcaption>Slack Norified</figcaption></figure><p>Repeated failed login attempts may indicate brute-force or password spraying attacks.</p><p><strong>Detection approach:</strong></p><ul><li>Windows Security Event ID <strong>4625</strong></li><li>Threshold-based alerting</li><li>Timeline analysis</li></ul><p><strong>MITRE ATT&amp;CK Mapping:</strong></p><ul><li>T1110 — Brute Force</li></ul><h4>RDP Brute Force Detection</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RVEd8QeJryBa_TaIADbozw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-DUa4bqBB3Ri6pRDoPXLIw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vmX4JVb5jKzoATsbDyDrJA.png" /></figure><p>RDP brute-force attacks are high-risk and often linked to ransomware incidents.</p><p><strong>Detection approach:</strong></p><ul><li>Event ID <strong>4625</strong></li><li>Logon Type <strong>10 (RemoteInteractive)</strong></li><li>High-severity alerts for repeated failures</li></ul><p><strong>MITRE ATT&amp;CK Mapping:</strong></p><ul><li>T1110 — Brute Force</li><li>T1021.001 — Remote Services: RDP</li></ul><h3>Windows Endpoint (Jamod)</h3><h4>RDP Brute Force Detection</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WYjCdNu_RVfNdgzRlqKHwQ.png" /><figcaption>Mittre ATTAck frame work on Windows VM</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dSj5MkpLKLX00tUmg-UP4Q.png" /></figure><p>This endpoint was used to validate <strong>detection consistency across multiple systems</strong>, ensuring scalability and reliability of detection logic.</p><h3>Evidence-Driven SOC Documentation (What Makes This Project Different)</h3><p>A key focus of this project was <strong>evidence-based SOC documentation</strong>.</p><p>Each detection includes:</p><ul><li>Alert and dashboard screenshots</li><li>OS-level logs</li><li>Attack simulation videos</li><li>MITRE ATT&amp;CK mapping</li><li>Analyst investigation notes</li></ul><p>A centralized <strong>evidence index</strong> was maintained to track:</p><ul><li>Attack type</li><li>Affected endpoint</li><li>Supporting evidence</li></ul><p>This approach closely mirrors <strong>enterprise SOC case management</strong>.</p><h3>Dashboards &amp; Threat Visibility in Wazuh</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MpgcNUGYOxFVgZ0Ar83kdw.png" /></figure><p>Dashboards used:</p><ul><li>MITRE ATT&amp;CK coverage</li><li>Threat Hunting</li><li>Vulnerability Detection</li><li>Authentication Monitoring</li><li>Agent Health</li></ul><p>Dashboards provide <strong>situational awareness</strong>, not just alerts.<br>Frameworks &amp; Standards Alignment</p><h3>Frameworks &amp; Standards Alignment</h3><p>This SOC lab aligns with:</p><ul><li><strong>MITRE ATT&amp;CK</strong> — Threat classification and reporting</li><li><strong>NIST 800-series concepts</strong> — Continuous monitoring &amp; detection</li><li><strong>SOC best practices</strong> — Triage, escalation, and documentation</li></ul><h3>Key Learnings from Building This SOC Lab</h3><ul><li>Detection without evidence is incomplete</li><li>Correlation improves alert accuracy</li><li>Early detection minimizes impact</li><li>Documentation is a core SOC skill</li></ul><blockquote><strong><em>Thinking like a SOC analyst is more important than just knowing tools.</em></strong></blockquote><h3>Conclusion: Real SOC Proof-of-Work</h3><p>This project represents <strong>hands-on SOC proof-of-work</strong>, not a tutorial exercise.</p><p>By combining:</p><ul><li>Realistic attack simulations</li><li>Wazuh SIEM detections</li><li>MITRE ATT&amp;CK alignment</li><li>Evidence-driven SOC workflows</li></ul><p>I built a lab that closely reflects <strong>enterprise SOC detection and response operations</strong>.</p><p>For anyone learning cybersecurity or SOC roles, focus on <strong>how alerts are investigated and documented</strong>, not just how they are generated.</p><h3>Ethical Disclaimer</h3><p>All activities were performed in a controlled lab environment owned by the author.<br> No production systems, real users, or unauthorized networks were involved.</p><h3>Thank You My CYBER SECURUITY LERNER Brother’s &amp; Sister’s 🥰🥰🥰😎😎😎</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d42081e5fc92" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beginner to Advanced Networking — Complete Practical Guide]]></title>
            <link>https://medium.com/@ogohel53/beginner-to-advanced-networking-complete-practical-guide-d66f2dbac6a2?source=rss-fbcd6c713b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/d66f2dbac6a2</guid>
            <category><![CDATA[computer-networking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[network-security]]></category>
            <dc:creator><![CDATA[Om Gohil]]></dc:creator>
            <pubDate>Sun, 16 Nov 2025 07:27:01 GMT</pubDate>
            <atom:updated>2025-11-16T07:27:01.198Z</atom:updated>
            <content:encoded><![CDATA[<h3>🌐<strong>Beginner to Advanced Networking — Complete Practical Guide</strong>🚀</h3><p>By Om Gohil — Cybersecurity &amp; Ethical Hacking Learner</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VWLeNvuqj9LxFa9d5tLLeQ.png" /></figure><h3>📌Content covered</h3><ol><li><strong><em>Introduction to Networking</em></strong></li><li><strong><em>How Networks Work (Beginner Friendly)</em></strong></li><li><strong><em>OSI &amp; TCP/IP Models (Essential Concepts)</em></strong></li><li><strong><em>Common Networking Devices</em></strong></li><li><strong><em>IP Addresses &amp; Subnetting (Made Easy)</em></strong></li><li><strong><em>DNS, DHCP, NAT — Everyday Network Services</em></strong></li><li><strong><em>TCP vs UDP — Reliable vs Fast</em></strong></li><li><strong><em>Wi-Fi Basics — Radio, Channels &amp; Security</em></strong></li><li><strong><em>Common Network Attacks (Explained Simply)</em></strong></li><li><strong><em>Practical Networking &amp; Security Tools</em></strong></li><li><strong><em>Hands-On Lab Ideas (Safe &amp; Legal)</em></strong></li><li><strong><em>Network Hardening Checklist</em></strong></li><li><strong><em>Final Notes for Learners (What to Do Next)</em></strong></li></ol><h3>🧩 1. Introduction to Networking</h3><p><strong>Networking</strong> is the foundation of modern communication. It allows computers, smartphones, servers, and IoT devices to exchange data across the world.</p><h4>Networking is the backbone of:</h4><ul><li>The Internet</li><li>Cloud environments</li><li>Cybersecurity</li><li>Ethical hacking</li><li>Enterprise IT</li><li>Remote work &amp; collaboration</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*rriq0Qtbt2FUYtYN.png" /></figure><h3>🏗️ 2. How Networks Work (Beginner Friendly)</h3><blockquote><strong>A network works through a simple process:</strong></blockquote><ol><li><strong>Device creates data</strong></li><li>Data is broken into <strong>packets</strong></li><li>Packets travel through <strong>network devices</strong></li><li>Packets reach their <strong>destination</strong></li><li>The receiving device reconstructs the data</li></ol><p><strong>Example:</strong> Opening YouTube → request goes through router → DNS resolves → server responds → video plays.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JhkYC9BmxenzleDo.png" /></figure><h3>📚 3. OSI &amp; TCP/IP Models (Essential Concepts)</h3><p><strong>Understanding protocols starts here.</strong></p><h4>OSI Model — 7 Layers</h4><ul><li><strong>Physical (1):</strong> cables, radio signals — e.g., bad cable = physical layer failure.</li><li><strong>Data Link (2):</strong> MAC addresses, switches, ARP — local network talk.</li><li><strong>Network (3):</strong> IP, routing — how packets move across networks.</li><li><strong>Transport (4):</strong> TCP/UDP — reliable vs fast delivery.</li><li><strong>Application (5–7 / App layer):</strong> HTTP, DNS, SMTP — what apps use.</li></ul><blockquote><strong>Practical note:</strong> A web request failure might be DNS (app), routing (network), or firewall (link/transport) — diagnosing means testing at each layer.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*AZasoBvTG_0fczQE2aUYAw.jpeg" /></figure><h4>TCP/IP Model — 4 Layers</h4><ul><li>Application</li><li>Transport</li><li>Internet</li><li>Network Access</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/0*bpsorOhNzvmx92Hh.jpeg" /></figure><p><strong>Why it’s important:</strong><br> Every attack, defense, protocol, and network tool operates on one of these layers.</p><h3>🛰️ 4. Common Networking Devices</h3><h4>Router</h4><p>Connects LAN to Internet &amp; forwards packets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rbdqs-ftZOV2qHwM.jpg" /><figcaption>Router of Asus</figcaption></figure><h4>Switch</h4><p>Connects devices inside the same network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*xuBmuo9V4GR8olaS.jpg" /><figcaption>D-link port router switch</figcaption></figure><h4>Access Point</h4><p>Provides Wi-Fi connectivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/0*RAGN48NwOS-R83mx" /><figcaption>access point of TP-link</figcaption></figure><h4>Firewall</h4><p>Filters and blocks malicious traffic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/764/0*TppU8RVob7Ctsqq3" /></figure><h4>IDS/IPS</h4><p>Monitors &amp; stops suspicious activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FwFgm2PWakFmyZt2.png" /></figure><h3>📡 5. IP Addresses &amp; Subnetting — made easy</h3><p><strong>IPv4 address:</strong> 192.168.1.10<br> <strong>Subnet mask /24</strong> means hosts share 192.168.1.x (254 usable hosts).</p><p><strong>Analogy:</strong> Subnet = a neighborhood. /24 ≈ one neighborhood with many houses.</p><p><strong>Mini-lab: show your IP</strong></p><pre># Linux/macOS<br> ip addr show<br># Windows<br> ipconfig</pre><p><strong>Small exercise:</strong> Convert /24 to number of hosts:</p><ul><li>/24 → 32-24 = 8 bits for hosts → 2^8 − 2 = 254 usable hosts.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/0*OLtTM29_YRfo2N61.png" /></figure><h3>🖧 6. DNS, DHCP, NAT — everyday services (and why they matter)</h3><ul><li><strong>DNS:</strong> Name → IP (human-friendly).</li><li><strong>DHCP:</strong> Automatically assigns IPs to devices.</li><li><strong>NAT:</strong> Hides internal (private) IPs from Internet — your whole home uses one public IP.</li></ul><p><strong>Mini-lab — DNS check</strong></p><pre>nslookup google.com<br>dig google.com</pre><blockquote><strong>Defensive tip:</strong> DNS logs are gold for detecting suspicious activity (e.g., data exfil via DNS).</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iAdB0fvoimxNJwkc.png" /></figure><h3>🧩 8. TCP vs UDP — reliable vs fast</h3><ul><li><strong>TCP:</strong> Connection-oriented, ensures delivery (like a phone call). Examples: HTTP, SSH.</li><li><strong>UDP:</strong> Connectionless, fast, no guarantee (like shouting across a stadium). Examples: DNS queries, video streaming.</li></ul><p><strong>Why it matters:</strong> Attackers exploit UDP (reflection DDoS) and rely on TCP for session hijacking.</p><h3>🖧🛰️7. Wi-Fi basics — radio, channels, and security</h3><p>Wi-Fi uses radio frequencies: 2.4 GHz (more range, more interference) &amp; 5 GHz (less interference, higher speed).</p><p><strong>Security:</strong></p><ul><li><strong>WEP:</strong> broken — avoid.</li><li><strong>WPA2:</strong> common — secure if strong password.</li><li><strong>WPA3:</strong> modern, better.</li><li><strong>WPS:</strong> often vulnerable — disable it.</li></ul><p><strong>Mini-lab (safely on your own AP):</strong> Use iwconfig / iw to view interfaces and nmcli dev wifi list (Linux).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BZRe48gDc3eROEv8.png" /></figure><h3>💥 8. Common Network Attacks — explained simply + how to detect/prevent</h3><p>I’ll list each attack with a short explanation, how to test (lab), and defenses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6X7-9c55ZDMV1eSE.png" /></figure><h4>8.1 ARP Spoofing / Poisoning</h4><ul><li><strong>What:</strong> Attacker tells network “I am the gateway” by sending fake ARP replies.</li><li><strong>Result:</strong> MITM (Man-in-the-Middle) to sniff traffic.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*8wR0I6gBlKrYlpyt.jpg" /></figure><ul><li><strong>Test (lab):</strong> Use arpspoof on an isolated lab.</li><li><strong>Defend:</strong> Use static ARP (rare), use DHCP snooping, enable Dynamic ARP Inspection (on managed switches), use HTTPS.</li><li><strong>Detection:</strong> Unexpected ARP table changes; alert on ARP anomalies in network logs.</li></ul><h4>8.2 DNS Spoofing</h4><p><strong>— What:</strong> Return fake IP for a domain (e.g., google.com → attacker IP).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WGT0qtJbNQ4XE_3n.png" /></figure><p>— <strong>Test:</strong> Set up a local DNS server and respond with wrong IP (lab only).<br> — <strong>Defend:</strong> DNSSEC, monitor DNS logs, use secure DNS resolvers.</p><h4>8.3 Man-in-the-Middle (MITM)</h4><p><strong>— What:</strong> Intercept, read, or modify traffic between two endpoints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DhIF2Ys8N_qVB261.png" /></figure><p>— <strong>How:</strong> ARP spoofing, rogue AP, or proxy.<br> — <strong>Defend:</strong> TLS everywhere (HTTPS), certificate pinning, HSTS, monitor for TLS interception.</p><h4>8.4 Port Scanning</h4><p><strong>— What:</strong> Scanning for open ports (Nmap).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*XfFn-UWEvTkNckr_.png" /></figure><p>— <strong>Use:</strong> Attackers &amp; defenders both use it.<br> — <strong>Defend:</strong> Close unused ports, firewall rules, IDS signatures to alert on scanning bursts.</p><h4>8.5 Deauthentication (Wi-Fi)</h4><p><strong>— What:</strong> Send deauth frames to clients to disconnect them — used to capture handshakes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/841/0*AnOyZgtROzgPoLx9.png" /></figure><p>— <strong>Defend:</strong> WPA3 (protected management frames), use 802.11w if supported, monitor unusual deauth rates.</p><h4>8.6 DDoS</h4><p><strong>— What:</strong> Flood resources (bandwidth/CPU) to make services unavailable.<br> — <strong>Defend:</strong> Rate limits, scrubbing services, CDNs, scalable infra.</p><h4>8.7 BGP Hijacking (advanced)</h4><p><strong>— What:</strong> Bad actor advertises IP prefixes they don’t own — Internet routing tables get poisoned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Z10ztz9Ga8GK8bBc.png" /></figure><h3>🛠️ 9. Practical Tools (what to learn, and practice commands)</h3><p>Group tools by purpose and include one-liner usage.</p><h4>Scanning &amp; Recon</h4><ul><li><strong>Nmap</strong> — network scanner</li><li>nmap -sC -sV -oN nmap_scan.txt 10.10.10.1/24</li><li><strong>Masscan</strong> — very fast port scanner</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*TFmwDeBGb-mmKMvm.png" /><figcaption>massscan</figcaption></figure><h4>Packet Capture &amp; Analysis</h4><ul><li><strong>Wireshark</strong> — GUI deep packet inspection</li><li><strong>tcpdump</strong> — CLI packet capture</li><li>sudo tcpdump -i eth0 -w capture.pcap</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*twlpeZsQkQco2pqP.png" /><figcaption>wireshark</figcaption></figure><h4>Wi-Fi Tools</h4><ul><li><strong>aircrack-ng</strong>, <strong>airodump-ng</strong>, <strong>aireplay-ng</strong></li><li><strong>hcxdumptool + hcxpcapngtool</strong> for PMKID capture and modern hash formats</li></ul><h4>MITM &amp; Credential Capture</h4><ul><li><strong>Bettercap</strong>, <strong>Responder</strong>, <strong>mitmproxy</strong></li></ul><h4>IDS/Monitoring</h4><ul><li><strong>Suricata</strong>, <strong>Zeek (Bro)</strong>, <strong>Snort</strong>, <strong>Wazuh</strong>, <strong>Splunk</strong></li></ul><h4>Password Cracking (offline)</h4><ul><li><strong>Hashcat</strong> — GPU cracking</li><li>hashcat -m 22000 capture.hc22000 wordlist.txt</li></ul><h3>💻 10. Hands-On Lab Ideas (step by step, safe &amp; legal)</h3><p>Set up a small home lab (virtual machines + one AP you own). Always practice only on systems you own or are authorized to test.</p><h4>Lab A — Local Network Recon</h4><ol><li>Run nmap -sP 192.168.1.0/24 to discover devices.</li><li>Run nmap -sV -p- &lt;target_ip&gt; to find services and versions.</li><li>Use wget or curl to fetch web services the scan reveals.</li></ol><p><strong>Learning outcome:</strong> You’ll learn how to map a network and identify attack surface.</p><h4>Lab B — Packet Capture &amp; HTTP Analysis</h4><ol><li>Capture traffic with tcpdump -i any -w lab.pcap while you browse a simple site (HTTP).</li><li>Open lab.pcap in Wireshark and filter http or tcp.port==80.</li><li>Observe requests, responses, and session flows.</li></ol><p><strong>Learning outcome:</strong> Understand how requests and responses look on the wire.</p><h4>Lab C — Safe Wi-Fi Practice (on your AP)</h4><ol><li>Use airodump-ng to view SSIDs (monitor mode required).</li><li>Use aireplay-ng --deauth only on APs you own to force reconnect and observe handshake capture.</li><li>Use aircrack-ng with rockyou.txt to practice cracking weak passwords (your own AP).</li></ol><p><strong>Learning outcome:</strong> Learn Wi-Fi handshake flow and how WPA2 can be cracked with weak passwords.</p><h3>🛡️ 11. How to Detect Attacks — Practical Signals</h3><ul><li>Sudden increase in failed connections or authentication failures → brute force.</li><li>New, unexpected hosts advertising as default gateway → ARP spoofing.</li><li>Large volumes of DNS queries to unusual domains → data exfiltration via DNS.</li><li>Repeated SYN scans or port sweeps → scanning attack.</li><li>Unusual outgoing traffic on non-standard ports → compromised host.</li></ul><p><strong>Tools for detection:</strong> SIEM (Splunk/ELK), Zeek, Suricata, Wazuh — correlate logs and set alerts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/0*5ZMgodzRMpLfUeRN.png" /></figure><h3>📝 12. Network Hardening Checklist (easy, action-oriented)</h3><ol><li>Change default passwords on devices</li><li>Apply least privilege and network segmentation (VLANs)</li><li>Disable unused services &amp; ports</li><li>Use strong Wi-Fi encryption (WPA3 if possible)</li><li>Enable logging and centralize logs to SIEM</li><li>Patch regularly (routers, switches, servers)</li><li>Use MFA for remote access &amp; admin accounts</li><li>Use VPN / Zero Trust for remote workers</li><li>Implement IDS/IPS and tune signatures</li><li>Run regular vulnerability scans and penetration tests</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*x7NYliV1y70V-p-L.jpg" /></figure><h3>💡 13. Final Tips for Readers (practical roadmap)</h3><ol><li>Master Linux command line &amp; basic tools (nmap, tcpdump, wireshark).</li><li>Build a small home lab (2 VMs + one router/AP).</li><li>Document every lab — screenshots, commands, lessons.</li><li>Do TryHackMe rooms (networking &amp; Wi-Fi labs).</li><li>Publish write-ups: your portfolio is proof-of-work for recruiters.</li></ol><h3>🙏 Thank You for Reading</h3><blockquote>Thank you so much for taking the time to go through this beginner-to-advanced networking guide. 🌐<br> I hope it helped you understand how networks work, what threats exist today, and how you can grow your skills in cybersecurity. 🛡️💡</blockquote><blockquote>If you found this helpful, feel free to share it, drop a comment, or connect with me.<br> Your support motivates me to create more practical, easy-to-understand content for learners and aspiring cybersecurity professionals. 🚀</blockquote><blockquote>Stay curious, stay ethical, and keep learning! 💻✨</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d66f2dbac6a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tryhackme: Identity and Access Management — By TOM]]></title>
            <link>https://medium.com/@ogohel53/tryhackme-identity-and-access-management-by-tom-21c089bbac4e?source=rss-fbcd6c713b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/21c089bbac4e</guid>
            <category><![CDATA[tryhackme-writeup]]></category>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <dc:creator><![CDATA[Om Gohil]]></dc:creator>
            <pubDate>Sun, 09 Nov 2025 19:45:06 GMT</pubDate>
            <atom:updated>2025-11-09T19:45:06.100Z</atom:updated>
            <content:encoded><![CDATA[<h3>Tryhackme: Identity and Access Management — By TOM</h3><h3>🧩 Task 1: <strong>Introduction</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*JHsD4Mij4I4WvHU0.png" /></figure><ol><li>What is the name of the room recommended to finish before this one?</li></ol><p>Answer: <strong>Security Principles</strong></p><h3>🧩 Task 2: <strong>IAAA Model</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*Ye02CshkkN_U8MHb.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*DmTu5_HHBODLQKJi.png" /></figure><ol><li>You are granted access to read and send an email. What is the name of this process?</li></ol><p>Answer: <strong>Authorisation</strong></p><p>2. Which process would require you to enter your username?</p><p>Answer: <strong>Identification</strong></p><p>3. Although you have write access, you should only make changes if necessary for the task. Which process is required to enforce this policy?</p><p>Answer: <strong>Accountability</strong></p><h3>🧩Task 3: <strong>Identification</strong></h3><p>I am just providing THM info FOr your use if you read this then you can easily understand what are going on understand bro</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*hHGop4uVCYXyiTK1.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*AJy0cBLLFObqdjQp.png" /></figure><h4>1. Which of the following <strong>cannot</strong> be used for identification?</h4><ol><li><strong><em>Email address</em></strong></li><li><strong><em>Mobile number with international code</em></strong></li><li><strong><em>Year of birth</em></strong></li><li><strong><em>Passport number</em></strong></li></ol><blockquote><strong>Answer: 3</strong></blockquote><h4>2. Which of the following <strong>cannot</strong> be used for identification?</h4><ol><li><strong><em>Landline phone number</em></strong></li><li><strong><em>Street number</em></strong></li><li><strong><em>Health insurance card number</em></strong></li><li><strong><em>Student ID number</em></strong></li></ol><blockquote><strong>Answer: 2</strong></blockquote><h3>🧩 Task 4: <strong>Authentication</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*MVoJvTxe9H6kT5r6.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*DuXodJsp8LDeAMYi.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*dDl9RL5q_yaNyhau.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*8UnuFpEla2wfDbl8.png" /></figure><blockquote>1. When you want to check your email, you enter your username and password. What kind of authentication is your email provider using?</blockquote><p>Answer: <strong>1</strong></p><blockquote>2. Your bank lets you finish most of your banking operations using its app. You can log in to your banking app by providing a username and a password and then entering the code received via SMS. What kind of authentication is the banking app using?</blockquote><p>Answer: <strong>4</strong></p><blockquote>3. Your new landline phone system at home allows callers to leave you a message when the call is not picked up. You can call your home number and enter a secret number to listen to recorded messages. What kind of authentication is being used here?</blockquote><p>Answer: <strong>1</strong></p><blockquote>4. You have just started working at an advanced research centre. You learned that you need to swipe your card and enter a four-digit PIN whenever you want to use the elevator. Under which group does this authentication fall?</blockquote><p>Answer: <strong>4</strong></p><h3>🧩Task 5: <strong>Authorisation and Access Control</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*7XcpHjx7sBIZ5ffR.png" /></figure><p>The new policy states that the secretary should be able to send an email on the manager’s behalf. What is this policy dictating?</p><p>Answer: <strong>1</strong></p><p>You shared a document with your colleague and gave them view permissions so they could read without making changes. What would ensure that your file won’t be modified?</p><p>Answer: <strong>2</strong></p><p>The hotel management decided that the cleaning staff needed access to all the hotel rooms to do their work. What phase is this decision part of?</p><p>Answer: <strong>1`</strong></p><h3>🧩Task 6: <strong>Accountability and Logging</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*chjp2ReOvYxPj3on.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*unQ6WCpoC2NL5wWM.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*SlzYTfa8r9kJO4_x.png" /></figure><h3>🧩Task 7: <strong>Identity Management</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*4cF1eoykIf3jdUcG.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*dHXEOt4ox4w6atK4.png" /></figure><ol><li>What does IdM stand for?</li></ol><p>Answer: <strong>Identity Management</strong></p><p>2. What does IAM stand for?</p><p>Answer: <strong>Identity and Access Management</strong></p><h3>🧩Task 8: <strong>Attacks Against Authentication</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*QPNNGFDLcy-RYbsX.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*QkG12Ls0i8psd73y.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*hB4MEEwb8LvsaFp6.png" /></figure><ol><li>The attacker could authenticate using the user’s response when the authentication protocol required a password encrypted with a shared key. What is the name of the attack?</li></ol><p>Answer: <strong>Replay Attack</strong></p><h3>🧩 Task 9: <strong>Access Control Models</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*vvul-YV6sXlMoSgz.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*FF84qBlkagqT88_Z.png" /></figure><ol><li>You are sharing a document via a network share and giving edit permission only to the accounting department. What example of access control is this?</li></ol><p>Answer: <strong>2</strong></p><p>2. You published a post on a social media platform and made it only visible to three out of your two hundred friends. What kind of access control did you use?</p><p>Answer: <strong>1</strong></p><h3>🧩Task 10: <strong>Single Sign-On</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*QTfaKp2mJERznFF6.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*Kl-F_HEsOQVDdxmG.png" /></figure><ol><li>What does SSO stand for?</li></ol><p>Answer: <strong>Single Sign-On</strong></p><p>2. Does SSO simplify MFA use as it needs to be set up once? (Yea/Nay)</p><p>Answer: <strong>Yea</strong></p><p>3. Is it true that SSO can be cumbersome as it requires the user to remember and input different passwords for the various services? (Yea/Nay)</p><p>Answer: <strong>Nay</strong></p><p>4. Does SSO allow users to access various services after signing in once? (Yea/Nay)</p><p>Answer: <strong>Yea</strong></p><p>5. Does the user need to create and remember a single password when using SSO? (Yea/Nay)</p><p>Answer: <strong>Yea</strong></p><h3>🧩Task 11: <strong>Scenarios</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*4P3fT02tIkEjAD6r.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*V72JywiX-ThK0dj4.png" /></figure><p>Answer: <strong>{THM_ACCESS_CONTROL}</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*Tls6RueFZKp9Zerz.png" /></figure><h3>🙏 Thank You for Reading!</h3><p>Thank you so much for taking the time to explore this walkthrough 💻✨<br> I truly appreciate your interest and support! Your time and curiosity motivate me to keep sharing more cybersecurity insights, labs, and hands-on experiences 🔐🚀</p><p>If you found this helpful, don’t forget to leave a comment, share your thoughts, or connect with me for more upcoming write-ups and security projects 💬🤝</p><p>Stay curious, stay secure, and keep learning! 🧠⚡</p><p><strong>– Om Gohil | TheOldMan 🕶️</strong><br> <em>Cybersecurity Enthusiast | Ethical Hacker | IAM Specialist</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*QHn1r4h_5Ohr1BWQj7nDyA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21c089bbac4e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tryhackme : Secure Network Architecture — by TOM ( +Hindi )]]></title>
            <link>https://medium.com/@ogohel53/tryhackme-secure-network-architecture-by-tom-hindi-c5de9614a025?source=rss-fbcd6c713b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5de9614a025</guid>
            <category><![CDATA[securenetworkarch]]></category>
            <category><![CDATA[tryhackme-room]]></category>
            <category><![CDATA[room]]></category>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <category><![CDATA[hindi-walkthrough]]></category>
            <dc:creator><![CDATA[Om Gohil]]></dc:creator>
            <pubDate>Sun, 09 Nov 2025 19:02:42 GMT</pubDate>
            <atom:updated>2025-11-09T19:02:42.108Z</atom:updated>
            <content:encoded><![CDATA[<h3>Tryhackme : Secure Network Architecture — by TOM ( +Hindi )</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/159/1*2ra51w4M_U58KeHvMOww6w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o-tdJRVAKAKe5nocMlT0Mg.png" /></figure><h3>🧩 Task 2 — Network Segmentation</h3><p><strong>Concept Summary (English):</strong><br> Network segmentation divides a network into smaller subnetworks (segments) to limit access, reduce attack surfaces, and contain threats. It ensures that even if an attacker compromises one area, they can’t easily move laterally across the organization.</p><p><strong>Hindi Explanation (हिंदी में):</strong><br> Network segmentation का मतलब है network को छोटे हिस्सों में बाँटना ताकि attacker अगर एक हिस्से में घुस भी जाए तो बाकी system सुरक्षित रहे। इससे security बढ़ती है और control आसान हो जाता है।</p><p><strong>Key Learning:</strong></p><ul><li>Use VLANs, firewalls, and ACLs for segmentation.</li><li>Apply least privilege access across segments.</li></ul><h4><strong>Questions :</strong></h4><blockquote>1. How many trunks are present in this configuration?</blockquote><blockquote>Ans: 4</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*drVGm5q9_DlvjC4THvC3vQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xhWHm2FaUD73PGIhM_W4-g.png" /></figure><blockquote>2. What is the VLAN tag ID for interface eth12?</blockquote><blockquote>Ans: 30</blockquote><ul><li>VyOS uses bridges as trunks.</li><li>Interface eth12 is located under the br0 bridge.</li></ul><h3>🧩 Task 3 — Common Secure Network Architecture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*LqEspJtlpV5JpjGAoq2NGA.png" /></figure><p><strong><em>Concept Summary (English):</em></strong></p><p>A <strong>DMZ (Demilitarized Zone)</strong> is a controlled subnetwork that acts as a buffer between an organization’s internal network and the external internet. Public-facing services like web servers, DNS, and mail servers are hosted here to isolate them from sensitive internal systems. This design reduces the risk of attackers directly accessing critical assets even if public systems are compromised.</p><p><strong><em>Hindi Explanation (हिंदी में):</em></strong><br> DMZ एक ऐसा network zone होता है जो internal network और internet के बीच सुरक्षा की दीवार बनाता है। इस zone में public-facing servers (जैसे web server, mail server) रखे जाते हैं ताकि अगर कोई attacker इन servers तक पहुँच भी जाए तो internal systems safe रहें।</p><p><strong>Key Learning Points:</strong></p><ul><li>Always place public servers (web, mail, DNS) inside a DMZ, not directly on internal LAN.</li><li>Restrict traffic flow between DMZ and internal network using strict firewall rules.</li><li>Monitor DMZ traffic separately for any anomalies.</li></ul><h4>Questions :</h4><blockquote>1. From the above table, what zone would a user connecting to a public web server be in?</blockquote><blockquote>Ans : <strong>External</strong></blockquote><blockquote>2. From the above table, what zone would a public web server be in?</blockquote><blockquote>Ans: <strong>DMZ</strong></blockquote><blockquote>3. From the above table, what zone would a core domain controller be placed in?</blockquote><blockquote>Ans: <strong>Restricted</strong></blockquote><h3>🧩 Task 4— Network Security Policies and Controls</h3><p><strong>Concept Summary (English):</strong><br> Network Security Policies define the rules, guidelines, and configurations that govern how data and resources are protected within a network. Security controls (like firewalls, IDS/IPS, NAC, and VPNs) enforce these policies in practice. Together, they ensure consistent protection, compliance, and response to threats.</p><p><strong>Hindi Explanation (हिंदी में):</strong><br> Network Security Policies वो नियम और दिशानिर्देश हैं जो बताते हैं कि data और network resources को कैसे सुरक्षित रखना है। Security controls (जैसे firewall, IDS, VPN, NAC) इन policies को लागू करने के काम आते हैं ताकि पूरे network में एक समान security बनी रहे।</p><p><strong>Key Learning Points:</strong></p><ul><li><strong>Administrative Controls:</strong> Security policies, user access rules, and change management.</li><li><strong>Technical Controls:</strong> Firewalls, antivirus, IDS/IPS, VPNs, and encryption.</li><li><strong>Physical Controls:</strong> Restricted server rooms, CCTV, and access badges.</li><li>Policies must be reviewed regularly to align with new threats and organizational changes.</li></ul><h4>Questaion:</h4><ol><li><strong>According to the corresponding ACL policy, will the first packet result in a drop or accept?</strong></li></ol><p><strong>Ans : accept</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k1CJ1I96wIlemxdtDGuVcw.png" /></figure><blockquote><strong>why ?</strong></blockquote><blockquote>“ The packet will be accepted. The source IP (10.10.212.209) matches the destination IP, and the destination port (22) is commonly used for SSH, suggesting that there is likely an ACL rule allowing this traffic. Therefore, it is permitted as it meets the conditions defined in the ACL policy.”</blockquote><p><strong>2. According to the corresponding ACL policy, will the second packet result in a drop or accept?</strong></p><p><strong>Ans : Drop</strong></p><blockquote><strong>why?</strong></blockquote><blockquote>“The first packet (with Src: 10.10.212.209, Dst: 10.10.212.209) is accepted by the ACL because it matches the rule allowing traffic from the source IP range 10.10.212.0/24. This rule permits any traffic originating from that subnet. The second packet (with Src: 10.10.212.200, Dst: 10.10.212.209) is also accepted as it originates from a valid source within the allowed range, targeting the destination IP 10.10.212.209. However, if there is a conflicting deny rule for destination 10.10.212.209, it would be denied. Since the provided rules suggest allowing traffic from the subnet, the overall outcome for both packets would be acceptance under the current policy context.”</blockquote><h3>🧩 Task 5— Zone-Pair Policies and Filtering</h3><p><strong>Concept Summary (English):</strong><br> <strong>Zone-based security</strong> is a method of grouping network interfaces into zones based on trust levels (e.g., internal, external, DMZ).<br> <strong>Zone-pair policies</strong> define how traffic can flow between these zones — for example, allowing web traffic from the external zone to the DMZ but blocking it from directly reaching the internal network.<br> <strong>Filtering</strong> ensures that only legitimate, authorized communication passes between zones, reducing attack surfaces and preventing lateral movement.</p><p><strong>Hindi Explanation (हिंदी में):</strong><br> Zone-based security का मतलब है network interfaces को उनकी trust level के अनुसार अलग-अलग zones में बाँटना — जैसे internal, external, और DMZ।<br> Zone-pair policies यह तय करती हैं कि कौन सा zone दूसरे zone से communicate कर सकता है और किसे block करना है।<br> Filtering यह सुनिश्चित करता है कि केवल valid और authorized traffic ही zones के बीच जाए, जिससे attacker का lateral movement रोका जा सके।</p><p><strong>Key Learning Points:</strong></p><ul><li>Create <strong>zones</strong> like Internal, External, DMZ — assign interfaces accordingly.</li><li>Define <strong>zone pairs</strong> (e.g., External → DMZ) and specify allowed traffic types (HTTP, HTTPS).</li><li><strong>Drop all unspecified traffic</strong> by default (“deny all” rule).</li><li>Use <strong>stateful inspection</strong> to allow only established connections.</li><li>Regularly review zone-pair configurations to prevent misconfigurations and policy drift.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/0*A62qFYZafOaMws0d.png" /></figure><p>Nothing in the site just have to see the below table and understand that which network connects with which’s and then do certain tasks that provided that’s it…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P3lata23msOywKHOSwavyg.png" /></figure><p>This is the completed Task :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*gxFctiiBE7bP9w89.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qonCjmvQOvbmuDEgpGDtNg.png" /></figure><blockquote>Flag is : <strong>THM{M05tly_53cure}</strong></blockquote><h3>🧩 Task 6 — Validating Network Traffic</h3><p><strong>Concept Summary (English):</strong><br> <strong>Validating network traffic</strong> means continuously inspecting and analyzing data packets to ensure they follow legitimate and secure communication patterns.<br> This validation helps identify malicious traffic, unauthorized access attempts, and abnormal data transfers. Tools like firewalls, IDS/IPS, and SIEM solutions are often used to perform deep packet inspection and traffic correlation.</p><p><strong>Hindi Explanation (हिंदी में):</strong><br> Network traffic validation का मतलब है network से गुजरने वाले data packets को ध्यान से check करना ताकि यह पता चले कि वो valid और secure हैं या नहीं।<br> अगर कोई malicious या suspicious traffic मिलता है तो उसे तुरंत block या alert किया जा सके। यह काम firewalls, IDS/IPS और SIEM जैसे tools करते हैं।</p><p><strong>Key Learning Points:</strong></p><ul><li>Validate both <strong>inbound</strong> and <strong>outbound</strong> traffic to prevent data exfiltration.</li><li>Use <strong>deep packet inspection (DPI)</strong> to detect hidden payloads or anomalies.</li><li>Regularly analyze logs using <strong>SIEM</strong> to correlate unusual traffic patterns.</li><li>Ensure <strong>only whitelisted protocols and ports</strong> are allowed for communication.</li></ul><h4>Questaion :</h4><ol><li><strong>Does SSL inspection require a man-in-the-middle proxy? (Y/N)</strong></li></ol><p><strong>Ans : Y</strong></p><p><strong>2. What platform processes data sent from an SSL proxy?</strong></p><p><strong>Ans: Unified Threat Management</strong></p><h3>🧩 Task 7 — Addressing Common Attacks</h3><p><strong>Concept Summary (English):</strong><br> Understanding and mitigating <strong>common network attacks</strong> like <strong>DDoS, Man-in-the-Middle (MitM), ARP spoofing, DNS poisoning, and port scanning</strong> is essential for maintaining network integrity.<br> Each of these attacks targets specific layers of the network stack, and a combination of preventive controls like firewalls, intrusion detection, encryption, and segmentation helps defend against them.</p><p><strong>Hindi Explanation (हिंदी में):</strong><br> Common network attacks (जैसे DDoS, Man-in-the-Middle, ARP spoofing, DNS poisoning) network की सुरक्षा को नुकसान पहुँचाने के लिए की जाती हैं।<br> इनसे बचने के लिए layered defense की जरूरत होती है — मतलब firewall, IDS/IPS, encryption और network segmentation का सही उपयोग।</p><p><strong>Key Learning Points:</strong></p><ul><li><strong>DDoS (Distributed Denial of Service):</strong> Use rate limiting, load balancing, and cloud-based DDoS protection.</li><li><strong>Man-in-the-Middle (MitM):</strong> Enforce TLS encryption and certificate pinning.</li><li><strong>ARP/DNS Spoofing:</strong> Use static ARP entries, DNSSEC, and network monitoring.</li><li><strong>Port Scanning:</strong> Restrict unnecessary open ports using firewalls and continuous vulnerability scanning.</li><li>Regularly patch and update systems to close known attack vectors.</li></ul><h3>DHCP Snooping</h3><ul><li>Any DHCP packet is received from outside of the network.</li><li>The source MAC address and DHCP client hardware address do not match.</li><li>A DHCPRELEASE or DHCPDECLINE packet is received on an untrusted interface that does not match an interface that the source address already has registered.</li><li>A DHCP packet that includes a relay agent address that is not 0.0.0.0</li></ul><h3>Dynamic ARP Inspection</h3><p>Right output is : show ip dhcp snoop bind</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_P14FOnWvymm47-AuoYk_g.png" /></figure><p>Below is a diagram showing an invalid ARP request that does not match the binding database and requests information (note the Sender MAC address has been spoofed).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UzT3MPeq21hHsjxM3MoJzQ.png" /></figure><h4>Questions:</h4><ol><li>Where does DHCP snooping store leased IP addresses from untrusted hosts?</li></ol><p><strong>Ans : DHCP Binding Database</strong></p><p>2. Will a switch drop or accept a DHCPRELEASE packet?</p><p><strong>Ans :Drop</strong></p><p>3. Does dynamic ARP inspection use the DHCP binding database? (Y/N)</p><p><strong>Ans : Y</strong></p><p>4. Dynamic ARP inspection will match an IP address and what other packet detail?</p><p><strong>Ans : MAC Address</strong></p><blockquote><strong>In this room, we have expanded the common requirements of a well-designed network to include security standards.</strong></blockquote><blockquote><strong>We have discussed approaches and solutions for problems commonly encountered at layers two and three of the OSI model. It may be apparent that this does not solve all issues, and each environment may have different requirements for what it should monitor and block.</strong></blockquote><h3>🙏 Thank You for Reading!</h3><p>Thank you so much for taking the time to explore this walkthrough 💻✨<br> I truly appreciate your interest and support! Your time and curiosity motivate me to keep sharing more cybersecurity insights, labs, and hands-on experiences 🔐🚀</p><p>If you found this helpful, don’t forget to leave a comment, share your thoughts, or connect with me for more upcoming write-ups and security projects 💬🤝</p><p>Stay curious, stay secure, and keep learning! 🧠⚡</p><p><strong>– Om Gohil | TheOldMan 🕶️</strong><br> <em>Cybersecurity Enthusiast | Ethical Hacker | IAM Specialist</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5de9614a025" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tryhackme Room : Linux Fundamentals Part 1 — The Core of Every Hacker’s Toolkit]]></title>
            <link>https://medium.com/@ogohel53/tryhackme-room-linux-fundamentals-part-1-the-core-of-every-hackers-toolkit-14ebbc04676c?source=rss-fbcd6c713b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/14ebbc04676c</guid>
            <dc:creator><![CDATA[Om Gohil]]></dc:creator>
            <pubDate>Fri, 07 Nov 2025 14:48:37 GMT</pubDate>
            <atom:updated>2025-11-07T14:48:37.348Z</atom:updated>
            <content:encoded><![CDATA[<h3>Tryhackme Room : Linux Fundamentals Part 1 — The Core of Every Hacker’s Toolkit</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fg0KtP2TBMRfDBnyuBKCkg.png" /></figure><p><strong>Type:</strong> Walkthrough | <strong>Level:</strong> Easy | <strong>Category:</strong> OS Basics / Command Line Essentials</p><h3>Task : 1</h3><p><strong>Introduction :</strong> Welcome to the first part of the “Linux Fundamentals” room series. You’re most likely using a Windows or Mac machine, both are different in visual design and how they operate. Just like Windows, iOS and MacOS, Linux is just another operating system and one of the most popular in the world powering smart cars, android devices, supercomputers, home appliances, enterprise servers, and more.</p><h3>Task : 2 (A Bit of Background on Linux)</h3><blockquote>Q-1 : Research: What year was the first release of a Linux operating system?<strong>Ans : <em>1991</em></strong></blockquote><h3>Task : 4 (Running Your First few Commands)</h3><p><strong>Objective:</strong> Learn basic command usage in Linux — echo and whoami.</p><p>In this task, we learned two basic Linux commands — echo and whoami.<br>The echo command prints text to the screen, and whoami shows the current logged-in user.<br>We tried echo &quot;TryHackMe&quot; to print text and whoami to display the username.<br>These are the first steps to interact with the Linux terminal.</p><blockquote>Q-1: If we wanted to output the text “<strong>TryHackMe</strong>”, what would our command be?</blockquote><blockquote>Ans: <strong>echo TryHackMe</strong></blockquote><blockquote>Q-2: What is the username of who you’re logged in as on your deployed Linux machine?</blockquote><blockquote>Ans: <strong>tryhackme</strong></blockquote><h3>Task : 5(Interacting With the Filesystem!)</h3><p>This section covers the basic Linux commands used to navigate and interact with the filesystem:</p><ul><li><strong>ls (list)</strong> — View the contents of the current or specified directory.</li><li><strong>cd (change directory)</strong> — Move between directories in the filesystem.</li><li><strong>cat (concatenate)</strong> — Display the contents of files directly in the terminal.</li><li><strong>pwd (print working directory)</strong> — Show the full path of the current directory.</li></ul><p>These commands help users explore, locate, and read files or folders without a graphical interface, forming the foundation of Linux navigation and file management.</p><blockquote>Q-1: On the Linux machine that you deploy, how many folders are there?</blockquote><blockquote><strong>Ans: 4</strong></blockquote><blockquote>Q-2: Which directory contains a file?</blockquote><blockquote><strong>Ans: folder4</strong></blockquote><blockquote>Q-3: On the Linux machine that you deploy, how many folders are there?</blockquote><blockquote><strong>Ans: Hello World!</strong></blockquote><blockquote>Q-4: Use the cd command to navigate to this file and find out the new current working directory. What is the path?</blockquote><blockquote><strong>Ans: /home/tryhackme/folder4</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-mBHiq2TLnmQUesdO4RAhw.png" /></figure><h3>Task : 6 (Searching for Files)</h3><p>This section introduces efficient ways to locate files and specific data using:</p><ul><li><strong>find</strong> — Search for files and directories by name or pattern (e.g., find -name passwords.txt, find -name *.txt).</li><li><strong>grep</strong> — Search inside files for specific text or patterns (e.g., finding an IP or keyword in logs).</li></ul><p>These tools make it easy to locate files or extract relevant information without manually browsing through directories or reading long files, improving command-line efficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nnBHn09hQEU7CO6MeS49Jg.png" /></figure><p>ANS : <strong>THM{ACCESS}</strong></p><h3>Task : 7(Searching for Files)</h3><p>This section explains key Linux shell operators that enhance command efficiency:</p><ul><li><strong>&amp;</strong> — Runs a command in the background.</li><li><strong>&amp;&amp;</strong> — Chains multiple commands; the next runs only if the previous succeeds.</li><li><strong>&gt;</strong> — Redirects output to a file (overwrites existing content).</li><li><strong>&gt;&gt;</strong> — Appends output to a file without overwriting existing data.</li></ul><p>These operators help automate, multitask, and control output flow effectively in Linux.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8hmaGWoFuSWanvbmVEVDMQ.png" /></figure><h3>Task : 8 Conclusions &amp; Summaries</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rrQaZ3hzREv50NgFMisw9Q.png" /></figure><p><strong>This room helped me understand the basics of Linux and terminal usage.<br> I learned how to navigate the file system, create and edit files, and use common commands like </strong><strong>ls, </strong><strong>cd, </strong><strong>cat, </strong><strong>echo, and </strong><strong>whoami.<br> These fundamentals build the foundation for using Linux in cybersecurity, scripting, and system administration.</strong></p><h3>🙏 Thank You</h3><blockquote>Thank you for reading my write-up on <em>Linux Fundamentals Part 1</em>.<br> This was my first step toward mastering Linux for cybersecurity and ethical hacking.<br> If you found this helpful, stay tuned for my next write-up on <strong>Windows Fundamentals Part 2</strong> and more TryHackMe rooms!<br> 💻 Follow me for more practical cybersecurity learning and walkthroughs.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14ebbc04676c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Story Behind “TheOldMan”]]></title>
            <link>https://medium.com/@ogohel53/the-story-behind-theoldman-ef37a353fcfd?source=rss-fbcd6c713b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef37a353fcfd</guid>
            <dc:creator><![CDATA[Om Gohil]]></dc:creator>
            <pubDate>Fri, 07 Nov 2025 13:50:29 GMT</pubDate>
            <atom:updated>2025-11-07T13:51:25.339Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VWLeNvuqj9LxFa9d5tLLeQ.png" /><figcaption>Our Youtube Chanel : <a href="http://www.youtube.com/@TOmSec-OG"><strong>www.youtube.com/@TOmSec-OG</strong></a></figcaption></figure><h3>🔥 My Journey from Curiosity to Cybersecurity</h3><p>Like Every journey starts with curiosity.<br>Mine started with a simple question — <em>“How does this system really work?”</em><br>That curiosity slowly turned into passion, and today, it drives me every single day as I walk deeper into the world of <strong>Cybersecurity</strong> and <strong>Ethical Hacking</strong>.</p><h3>🧠 The Beginning — Curiosity, Mistakes &amp; Learning</h3><p>Like most security enthusiasts, I started by breaking things — not to harm, but to understand.<br> Exploring <strong>Linux</strong>, running tools on <strong>Kali</strong>, experimenting with <strong>Python scripts</strong> — every small success or failure taught me something new about how systems truly behave under the hood.</p><p>That’s when I realized: hacking isn’t just about commands.<br> It’s about <strong>thinking differently</strong> — like an attacker, but acting responsibly like a defender.</p><h3>🧩 Building the Foundation</h3><p>To build strong skills, I took the structured route too — diving into <strong>TryHackMe</strong> labs and real-world challenges.<br> From <strong>Windows &amp; Linux Fundamentals</strong>, <strong>Networking</strong>, and <strong>Active Directory</strong>, to <strong>Privilege Escalation</strong> and <strong>SOC analysis</strong>, each room built a small piece of my understanding of how security works in layers.</p><p>Tools like <strong>Burp Suite</strong>, <strong>Nmap</strong>, <strong>OpenVAS</strong>, <strong>MobSF</strong>, <strong>ZAP</strong>, and <strong>Hydra</strong> became my everyday companions.</p><h3>⚙️ From Learning to Designing</h3><p>Curiosity soon led to design.<br> While working on <strong>IAM (Identity &amp; Access Management)</strong> solutions at <em>TechCorp</em>, I explored how real organizations manage access, authentication, and automation securely.<br> Implementing <strong>RBAC</strong>, <strong>Least Privilege</strong>, <strong>MFA</strong>, and <strong>Lifecycle Automation</strong> gave me a broader view — security isn’t just about hacking; it’s about <strong>protecting at scale</strong>.</p><h3>💡 Side Projects &amp; Proof of Work</h3><p>Projects like my <strong>Emotion-Based Song Recommendation System</strong> helped me mix AI and security thinking — connecting <strong>Machine Learning, APIs, and automation</strong> into real products.</p><p>In the <strong>Shields Up Challenge</strong>, I faced a simulated <strong>Log4j zero-day</strong> and cracked a ransomware-encrypted ZIP file using <strong>Python automation</strong> — a reminder that creativity and persistence always win.</p><h3>🔐 The Mission</h3><p>Today, I continue this journey — learning, breaking, building, and sharing.<br> My mission is simple:</p><blockquote><em>To master the art of securing systems, while inspiring others to explore this field fearlessly.</em></blockquote><p>I’m still “<strong>TheOldMan</strong>” online — not because I’m old, but because I’ve learned that wisdom in cybersecurity doesn’t come from age; it comes from <em>experience, patience,</em> and <em>curiosity.</em></p><p><strong>Next Up:</strong> I’ll be sharing walkthroughs, project write-ups, and lessons from my TryHackMe rooms — from fundamentals to offensive tactics and IAM design.<br> Stay tuned, and let’s grow together. 💻🔥</p><p>💡 <strong>Thanks for reading!</strong><br> Follow me (<strong>@TheOldMan</strong>) for more write-ups on my<br> 🧠 <em>Cybersecurity Learning Roadmap</em><br> 💻 <em>Ethical Hacking Journey</em><br> 🕵️ <em>TryHackMe Write-ups</em><br> 🔐 <em>IAM Security Design</em><br> ⚔️ <em>Red Team vs Blue Team Analysis</em><br> and my ongoing <em>Cybersecurity Portfolio for Recruiters</em> series.</p><p>Let’s learn, hack, and grow together. 🚀<br> #TryHackMe #Cybersecurity #EthicalHacking #TechCareer</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef37a353fcfd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>