<?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: else54</title>
    <description>The latest articles on DEV Community by else54 (@else54).</description>
    <link>https://dev.to/else54</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%2F4160038%2F5344d52b-2098-4d8a-847d-886db3413264.png</url>
      <title>DEV Community: else54</title>
      <link>https://dev.to/else54</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/else54"/>
    <language>en</language>
    <item>
      <title>Outwards - i build app that help you secure your company by finding exposed data</title>
      <dc:creator>else54</dc:creator>
      <pubDate>Sat, 03 Oct 2026 15:38:21 +0000</pubDate>
      <link>https://dev.to/else54/outwards-helping-you-secure-your-company-by-finding-exposed-data-5hdg</link>
      <guid>https://dev.to/else54/outwards-helping-you-secure-your-company-by-finding-exposed-data-5hdg</guid>
      <description>&lt;p&gt;Hey,&lt;/p&gt;

&lt;p&gt;AI has changed the way we work quite a lot. We’re more productive than ever, but at the same time it’s becoming harder to keep track of where company data actually ends up.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3xx97bmn7l0kgcuo3rqg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3xx97bmn7l0kgcuo3rqg.png" alt="Sources of leaks" width="800" height="408"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;I’ve personally come across situations like these:&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;someone prepares a &lt;strong&gt;client proposal and uploads internal files directly into an AI tool&lt;/strong&gt;,&lt;/li&gt;
&lt;li&gt;an internal PDF is left somewhere under &lt;strong&gt;wp-uploads&lt;/strong&gt; and eventually gets indexed by Google,&lt;/li&gt;
&lt;li&gt;working notes from &lt;strong&gt;NotebookLM&lt;/strong&gt; or files on &lt;strong&gt;Google Drive&lt;/strong&gt; turn out to be publicly accessible,&lt;/li&gt;
&lt;li&gt;an &lt;strong&gt;API key is hardcoded&lt;/strong&gt; in source code and ends up in a public repository.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;They’re just small mistakes that anyone can make.&lt;/p&gt;

&lt;p&gt;That’s why I’ve been working on a project called Outwards — a tool for monitoring publicly exposed confidential company data.&lt;/p&gt;

&lt;p&gt;The idea is that a company first verifies that it actually owns the domain. Then Outwards builds a map of its public assets: domains, repositories, accounts, documents and other related resources.&lt;/p&gt;

&lt;p&gt;After that, it looks at the company from the outside and checks things like:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;AI tools -&lt;/strong&gt; whether AI models or publicly shared AI conversations can surface information about the company that probably shouldn’t be easy to find.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Search engines&lt;/strong&gt; - whether Google or Bing are indexing internal documents, employee data, contracts, email addresses or other sensitive material.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Public repositories -&lt;/strong&gt; whether API keys, credentials, config files or other secrets were accidentally committed to public code.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cloud files -&lt;/strong&gt; whether Google Drive files, shared documents, boards or similar resources are publicly accessible.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F85ihfnn72zrvejv4cfwb.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F85ihfnn72zrvejv4cfwb.png" alt="App flow" width="799" height="353"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If something is found, the user gets an alert, an explanation of the risk, and guidance on how to remove or secure it.&lt;/p&gt;

&lt;p&gt;In practice, I think of it as continuous OSINT performed on your own company - trying to find the problem before someone else does.&lt;/p&gt;

&lt;p&gt;I’ve opened an early waitlist and I’m currently looking for feedback:&lt;/p&gt;


&lt;div class="crayons-card c-embed text-styles text-styles--secondary"&gt;
    &lt;div class="c-embed__content"&gt;
      &lt;div class="c-embed__body flex items-center justify-between"&gt;
        &lt;a href="https://getoutwards.com/en" rel="noopener noreferrer" class="c-link fw-bold flex items-center"&gt;
          &lt;span class="mr-2"&gt;getoutwards.com&lt;/span&gt;
          

        &lt;/a&gt;
      &lt;/div&gt;
    &lt;/div&gt;
&lt;/div&gt;


&lt;p&gt;&lt;strong&gt;What do you think about the idea? Would you see a real use case for something like this in software companies?&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>security</category>
      <category>saas</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
