<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tooling on Latacora</title><link>https://www.latacora.com/categories/tooling/</link><description>Recent content in Tooling on Latacora</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 22 Sep 2025 12:00:00 -0400</lastBuildDate><atom:link href="https://www.latacora.com/categories/tooling/index.xml" rel="self" type="application/rss+xml"/><item><title>Introducing Replik8s, a Modern Security Tool for Kubernetes</title><link>https://www.latacora.com/blog/2025/09/22/introducing-replik8s/</link><pubDate>Mon, 22 Sep 2025 12:00:00 -0400</pubDate><guid>https://www.latacora.com/blog/2025/09/22/introducing-replik8s/</guid><description>&lt;h2 id="introduction" class="heading-with-anchor"&gt;
&lt;a href="#introduction" class="heading-anchor-link" aria-label="Link to Introduction"&gt;
Introduction
&lt;span class="heading-anchor-icon" aria-hidden="true"&gt;#&lt;/span&gt;
&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Security tools are often designed to highlight specific issues by consuming
APIs and applying predefined logic. Each tool implements its own data
structures, storage formats, and evaluation logic. While effective in narrow
contexts, this approach creates challenges for teams managing a diverse
toolset. Moreover, most tools are optimized to fetch only the data needed for
specific findings, limiting their utility in broader contexts such as incident
response or historical analysis.&lt;/p&gt;</description></item><item><title>Bit by bit: how Latacora helped Notion build security that scales</title><link>https://www.latacora.com/blog/2025/08/29/bit-by-bit-latacora-notion/</link><pubDate>Fri, 29 Aug 2025 11:55:00 -0500</pubDate><guid>https://www.latacora.com/blog/2025/08/29/bit-by-bit-latacora-notion/</guid><description>&lt;p&gt;&lt;strong&gt;Security rarely tops the priority list for startups - but that doesn&amp;rsquo;t make
it optional.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Running a startup is no small feat. Facing enormous pressure to address a
never-ending list of priorities (finding market fit, fundraising, launching new
features, scaling infrastructure, etc.) security often becomes a “later”
issue……until it can’t be. Even when companies know they need help, the breadth
of the problem can be intimidating. Application security, cloud infrastructure,
third-party vendors, compliance, cryptography: any resource-constrained startup
will be hard-pressed to find a unicorn hire who can own all these
responsibilities equally well.&lt;/p&gt;</description></item><item><title>Datomic and Content Addressable Techniques: An Ultimate Data Wonderland</title><link>https://www.latacora.com/blog/2024/09/13/datomic-and-content-addressable-techniques/</link><pubDate>Fri, 13 Sep 2024 12:00:00 -0500</pubDate><guid>https://www.latacora.com/blog/2024/09/13/datomic-and-content-addressable-techniques/</guid><description>&lt;p&gt;Latacora collects and analyzes data about services our clients use. You may
have read about &lt;a href="https://www.latacora.com/blog/2023/11/01/our-approach-to-building-security-tooling/" target="_self" rel=""&gt;our approach to building security
tooling&lt;/a&gt;, but the tl;dr
is we make requests to all the (configuration metadata) read-only APIs available
to us and store the results in S3. We leverage the data to understand our clients'
infrastructure and identify security issues and misconfigurations. We retain the
files (&amp;ldquo;snapshots&amp;rdquo;) to support future IR/forensics efforts.&lt;/p&gt;
&lt;p&gt;This approach has served us well, but the limited scope of a snapshot meant
there was always a problem of first needing to figure out which files to look
at. We love &lt;code&gt;aws s3 sync&lt;/code&gt; and &lt;code&gt;grep&lt;/code&gt; as much as anyone but security analysis
requires looking for complex relationships between resources; text search is,
at best, only a Bloom filter. What we really wanted was a performant way to ask
any question across all the data we have for a client that would support
complex queries using logic programming.&lt;/p&gt;</description></item><item><title>Our Approach to Building Security Tooling</title><link>https://www.latacora.com/blog/2023/11/01/our-approach-to-building-security-tooling/</link><pubDate>Wed, 01 Nov 2023 12:00:00 -0400</pubDate><guid>https://www.latacora.com/blog/2023/11/01/our-approach-to-building-security-tooling/</guid><description>&lt;h2 id="introduction" class="heading-with-anchor"&gt;
&lt;a href="#introduction" class="heading-anchor-link" aria-label="Link to Introduction"&gt;
Introduction
&lt;span class="heading-anchor-icon" aria-hidden="true"&gt;#&lt;/span&gt;
&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Most &amp;ldquo;security tools&amp;rdquo; today are typically composed by code that consumes an API
and applies predefined logic to identify issues. This is generally accomplished
by:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Fetching a subset of the endpoints exposed by the service / API being
audited (that is, the information required for the evaluation logic, such as
a list of the EC2 instances deployed in an AWS account, as well as their
configuration)&lt;/li&gt;
&lt;li&gt;Storing the data retrieved&lt;/li&gt;
&lt;li&gt;Evaluating this data to produce &amp;ldquo;findings&amp;rdquo; (this is the added value provided
by the tool)&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Integrating third party tools into our monitoring platform isn&amp;rsquo;t always
straightforward, as each tool:&lt;/p&gt;</description></item></channel></rss>