<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>IDOR on Policy to Packets</title>
    <link>https://www.policytopackets.com/tags/idor/</link>
    <description>Recent content in IDOR 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>Sun, 22 Feb 2026 21:48:00 +0000</lastBuildDate><atom:link href="https://www.policytopackets.com/tags/idor/index.xml" rel="self" type="application/rss+xml" />
    
    <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>
    
  </channel>
</rss>
