<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>HTTP on Policy to Packets</title>
    <link>https://www.policytopackets.com/tags/http/</link>
    <description>Recent content in HTTP on Policy to Packets</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>reedveggleston@gmail.com (Reed Eggleston)</managingEditor>
    <webMaster>reedveggleston@gmail.com (Reed Eggleston)</webMaster>
    <copyright>© 2026 Reed Eggleston</copyright>
    <lastBuildDate>Fri, 27 Feb 2026 14:45:00 +0000</lastBuildDate><atom:link href="https://www.policytopackets.com/tags/http/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>(Writeup) LetsDefend Challenge - Brute Force Attacks</title>
      <link>https://www.policytopackets.com/writeups/letsdefend/challenges/brute-force-attacks/</link>
      <pubDate>Fri, 27 Feb 2026 14:45:00 +0000</pubDate>
      <author>reedveggleston@gmail.com (Reed Eggleston)</author>
      <guid>https://www.policytopackets.com/writeups/letsdefend/challenges/brute-force-attacks/</guid>
      <description>Analyzing a PCAP and Linux auth.log to investigate HTTP, RDP, and SSH brute-force activity, identifying successful credential compromise, and quantifying failed login attempts.</description>
      
    </item>
    
    <item>
      <title>(Writeup) LetsDefend Challenge - Investigate Web Attack</title>
      <link>https://www.policytopackets.com/writeups/letsdefend/challenges/investigate_web_attack/</link>
      <pubDate>Mon, 23 Feb 2026 12:14:00 +0000</pubDate>
      <author>reedveggleston@gmail.com (Reed Eggleston)</author>
      <guid>https://www.policytopackets.com/writeups/letsdefend/challenges/investigate_web_attack/</guid>
      <description>Analyzing raw Apache access logs with Bash tools to identify reconnaissance with Nikto, forced browsing, successful login brute force activity, and command injection leading to account creation on the target system.</description>
      
    </item>
    
    <item>
      <title>(Writeup) LetsDefend Challenge - Http Basic Auth.</title>
      <link>https://www.policytopackets.com/writeups/letsdefend/challenges/http_basic_auth./</link>
      <pubDate>Mon, 23 Feb 2026 11:41:00 +0000</pubDate>
      <author>reedveggleston@gmail.com (Reed Eggleston)</author>
      <guid>https://www.policytopackets.com/writeups/letsdefend/challenges/http_basic_auth./</guid>
      <description>Analyzing a PCAP file to identify HTTP GET requests, enumerate server and client details from HTTP headers, and decode Basic Authentication credentials using Wireshark and CyberChef.</description>
      
    </item>
    
    <item>
      <title>(Writeup) LetsDefend EventID: 120 - [SOC170 - Passwd Found in Requested URL - Possible LFI Attack]</title>
      <link>https://www.policytopackets.com/writeups/letsdefend/soc/170_120/</link>
      <pubDate>Mon, 23 Feb 2026 11:10:00 +0000</pubDate>
      <author>reedveggleston@gmail.com (Reed Eggleston)</author>
      <guid>https://www.policytopackets.com/writeups/letsdefend/soc/170_120/</guid>
      <description>Investigating a suspected local file inclusion alert after a directory traversal attempt targeted /etc/passwd, reviewing SIEM HTTP logs, and confirming the attack failed based on a 500 server response with no returned content.</description>
      
    </item>
    
    <item>
      <title>(Writeup) LetsDefend EventID: 119 - [SOC169 - Possible IDOR Attack Detected]</title>
      <link>https://www.policytopackets.com/writeups/letsdefend/soc/169_119/</link>
      <pubDate>Sun, 22 Feb 2026 21:48:00 +0000</pubDate>
      <author>reedveggleston@gmail.com (Reed Eggleston)</author>
      <guid>https://www.policytopackets.com/writeups/letsdefend/soc/169_119/</guid>
      <description>Investigating an IDOR alert after repeated POST requests incremented a user ID parameter, reviewing HTTP logs and response behavior, and confirming successful data exposure based on varying response sizes and consistent 200 status codes before escalating the case.</description>
      
    </item>
    
    <item>
      <title>(Writeup) LetsDefend EventID: 118 - [SOC168 - Whoami Command Detected in Request Body]</title>
      <link>https://www.policytopackets.com/writeups/letsdefend/soc/168_118/</link>
      <pubDate>Sat, 21 Feb 2026 23:46:00 +0000</pubDate>
      <author>reedveggleston@gmail.com (Reed Eggleston)</author>
      <guid>https://www.policytopackets.com/writeups/letsdefend/soc/168_118/</guid>
      <description>Investigating a command injection alert after POST requests containing system commands targeted a web endpoint, validating attacker IP reputation and analyzing HTTP response behavior, confirming successful command execution through response size variation, and initiating containment and escalation due to a confirmed web shell.</description>
      
    </item>
    
    <item>
      <title>(Writeup) LetsDefend EventID: 117 - [SOC167 - LS Command Detected in Requested URL]</title>
      <link>https://www.policytopackets.com/writeups/letsdefend/soc/167_117/</link>
      <pubDate>Sat, 21 Feb 2026 23:01:00 +0000</pubDate>
      <author>reedveggleston@gmail.com (Reed Eggleston)</author>
      <guid>https://www.policytopackets.com/writeups/letsdefend/soc/167_117/</guid>
      <description>Investigating a command-injection alert after a URL triggered on the string “ls,” reviewing SIEM logs and threat intelligence data, and determining the activity was normal user browsing traffic that resulted in a false positive.</description>
      
    </item>
    
    <item>
      <title>(Writeup) LetsDefend EventID: 116 - [SOC166 - Javascript Code Detected in Requested URL]</title>
      <link>https://www.policytopackets.com/writeups/letsdefend/soc/166_116/</link>
      <pubDate>Sat, 21 Feb 2026 21:18:00 +0000</pubDate>
      <author>reedveggleston@gmail.com (Reed Eggleston)</author>
      <guid>https://www.policytopackets.com/writeups/letsdefend/soc/166_116/</guid>
      <description>Investigating an XSS alert after multiple JavaScript payloads were sent to a web application, validating the attacker IP reputation and reviewing HTTP response behavior, and confirming the attempts failed based on consistent 302 redirects and clean endpoint verification.</description>
      
    </item>
    
    <item>
      <title>(Writeup) LetsDefend EventID: 115 - [SOC165 - Possible SQL Injection Payload Detected]</title>
      <link>https://www.policytopackets.com/writeups/letsdefend/soc/165_115/</link>
      <pubDate>Sat, 21 Feb 2026 18:15:00 +0000</pubDate>
      <author>reedveggleston@gmail.com (Reed Eggleston)</author>
      <guid>https://www.policytopackets.com/writeups/letsdefend/soc/165_115/</guid>
      <description>Investigating a SQL injection alert after repeated crafted payloads targeted a web server, decoding and validating the requests through log analysis, reviewing source IP reputation across multiple threat intelligence sources, and confirming the attack was unsuccessful based on server responses and endpoint verification.</description>
      
    </item>
    
  </channel>
</rss>
