<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>urlscan.io on Saksham Anand</title>
    <link>/tags/urlscan.io/</link>
    <description>Recent content in urlscan.io on Saksham Anand</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 15 Apr 2022 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/urlscan.io/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>urlscan.io Dorking</title>
      <link>/blog/urlscan-dorking/</link>
      <pubDate>Fri, 15 Apr 2022 00:00:00 +0000</pubDate>
      <guid>/blog/urlscan-dorking/</guid>
      <description>urlscan.io is a free and paid tool that is used to scan and analyse URLs. The tool is often used by Security Analysts and employees working in a SOC. It is also available as an integration add-on in several popular security toolings such as Splunk SOAR and Cortex XSOAR. This post will be focusing on the Search functionality in urlscan.io and how it can be abused to extract sensitive content due to tooling misconfigurations or accidental information leakage.</description>
    </item>
  </channel>
</rss>
