<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Muhammad Subhan</title>
    <description>The latest articles on DEV Community by Muhammad Subhan (@muhammadsubhan007).</description>
    <link>https://dev.to/muhammadsubhan007</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4016543%2F44a2ef3b-bc9b-4753-8936-06f7c19b20e7.png</url>
      <title>DEV Community: Muhammad Subhan</title>
      <link>https://dev.to/muhammadsubhan007</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/muhammadsubhan007"/>
    <language>en</language>
    <item>
      <title>Defensive Security Intro</title>
      <dc:creator>Muhammad Subhan</dc:creator>
      <pubDate>Sun, 05 Jul 2026 22:31:56 +0000</pubDate>
      <link>https://dev.to/muhammadsubhan007/defensive-security-intro-25hd</link>
      <guid>https://dev.to/muhammadsubhan007/defensive-security-intro-25hd</guid>
      <description>&lt;p&gt;Now over hear instead of us being the attacker, we are the defender, an SOC analyst. We were given a monitoring system which detects suspicious attempts and reports them to us. It reported that FakeBank.com was accessed on the admin endpoint so I had to block the source of the traffic. Joe (the SOC analyst) added rate limiting. Rate limiting helps as it caps the amount of requests a user can send to the server. Dirb works by sending hundreds or thousands of requests per second. which means rate limiting throttles or blocks it. and Web Application Firewall (WAF). The firewall allowed me to block the traffics Ip so that source could not access the website again.&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>analyst</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Offensive Security Intro</title>
      <dc:creator>Muhammad Subhan</dc:creator>
      <pubDate>Sun, 05 Jul 2026 18:37:38 +0000</pubDate>
      <link>https://dev.to/muhammadsubhan007/offensive-security-intro-37kn</link>
      <guid>https://dev.to/muhammadsubhan007/offensive-security-intro-37kn</guid>
      <description>&lt;p&gt;This is the starting of my journey. The first path I cross is TryHackMe. This is the first room from PreSecurity. Dirb,  a tool that discovers hidden/unlinked pages on a website by rapidly guessing common folder and file names from a wordlist. A &lt;code&gt;CODE:200&lt;/code&gt; response means the page exists. Example: &lt;code&gt;dirb https://example.com/&lt;/code&gt; might reveal &lt;code&gt;https://example.com/admin/&lt;/code&gt;, &lt;code&gt;https://example.com/config.php&lt;/code&gt;, &lt;code&gt;https://example.com/backup/&lt;/code&gt;, etc. In the room (a fake bank), this exposed an admin dashboard and a &lt;code&gt;users.db&lt;/code&gt; file that were reachable by anyone with the URL. &lt;strong&gt;Why it's a vulnerability:&lt;/strong&gt; those pages should have been behind a login or blocked — leaving them accessible lets an attacker reach sensitive data directly. &lt;strong&gt;Remediation:&lt;/strong&gt; require authentication on admin areas, keep database/backup files out of web-accessible folders, return 403/404 for sensitive paths. &lt;/p&gt;

</description>
      <category>security</category>
      <category>firstpost</category>
      <category>cybersecurity</category>
      <category>tryhackme</category>
    </item>
  </channel>
</rss>
