<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Latacora</title><link>https://www.latacora.com/categories/architecture/</link><description>Recent content in Architecture on Latacora</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 04 Nov 2025 10:00:00 -0500</lastBuildDate><atom:link href="https://www.latacora.com/categories/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>OIDC workload identity on AWS</title><link>https://www.latacora.com/blog/2025/11/04/aws-oidc-workload-identity/</link><pubDate>Tue, 04 Nov 2025 10:00:00 -0500</pubDate><guid>https://www.latacora.com/blog/2025/11/04/aws-oidc-workload-identity/</guid><description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt;: after years of being on the wish list of a ton of top AWS teams, AWS
released &lt;a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_outbound.html" target="_blank" rel="noopener noreferrer"&gt;a built-in version of this feature&lt;/a&gt; about two weeks
after we published this. Never let it be said gentle ribbing doesn&amp;rsquo;t work.
Also, thanks AWS! We meant it when we said that the only thing better than
having something easy to deploy was not needing to deploy anything at all.
Everything in this post about workload identity is still relevant but you
should probably use upstream&amp;rsquo;s implementation unless you have a good reason not
to (for example, private validators for whom you need a VPC endpoint).&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>Lessons in logging, part 2: mapping your path to a mature security program with logs and audit trails</title><link>https://www.latacora.com/blog/2024/10/23/mapping-your-path-to-a-more-mature-security-program-with-logs-and-audit-trails/</link><pubDate>Wed, 23 Oct 2024 11:00:00 -0400</pubDate><guid>https://www.latacora.com/blog/2024/10/23/mapping-your-path-to-a-more-mature-security-program-with-logs-and-audit-trails/</guid><description>&lt;p&gt;&lt;em&gt;This post is the second in a series about logging and audit trails from a security perspective. For the first post in the series, see &lt;a href="https://www.latacora.com/blog/2023/11/28/lessons-in-logging-chopping-down-security-risks-using-audit-trails/" target="_self" rel=""&gt;Lessons in Logging: Chopping Down Security Risks Using Audit Trails&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;If you’re looking to level up your security practices, logging is a good place to focus your attention. Just as logging is a core pillar of observability, comprehensive audit trails are a core pillar of a strong security program. Logs and audit trails are separate but overlapping concepts, and most companies can improve their security posture by investing in this area.&lt;/p&gt;</description></item><item><title>Lessons in logging: chopping down security risks using audit trails</title><link>https://www.latacora.com/blog/2023/11/28/lessons-in-logging-chopping-down-security-risks-using-audit-trails/</link><pubDate>Tue, 28 Nov 2023 10:30:00 -0500</pubDate><guid>https://www.latacora.com/blog/2023/11/28/lessons-in-logging-chopping-down-security-risks-using-audit-trails/</guid><description>&lt;p&gt;&lt;em&gt;This post is the first in a series about logging and audit trails from a security perspective. For the next post in the series, see &lt;a href="https://www.latacora.com/blog/2024/10/23/mapping-your-path-to-a-more-mature-security-program-with-logs-and-audit-trails/" target="_self" rel=""&gt;Lessons in Logging, Part 2: Mapping Your Path to a Mature Security Program with Logs and Audit Trails&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;At Latacora, we bootstrap security practices. We partner with companies that frequently have minimally developed security programs, work with them to figure out the right security practices for their current size, and then help them evolve and scale those practices as their business matures.&lt;/p&gt;</description></item><item><title>A Child's Garden of Inter-Service Authentication Schemes</title><link>https://www.latacora.com/blog/2018/06/12/inter-service-authentication-schemes/</link><pubDate>Tue, 12 Jun 2018 16:27:00 -0400</pubDate><guid>https://www.latacora.com/blog/2018/06/12/inter-service-authentication-schemes/</guid><description>&lt;p&gt;Modern applications tend to be composed from relationships between smaller
applications. Secure modern applications thus need a way to express and enforce
security policies that span multiple services. This is the “server-to-server”
(S2S) authentication and authorization problem (for simplicity, I’ll mash both
concepts into the term “auth” for most of this post).&lt;/p&gt;
&lt;p&gt;Designers today have a lot of options for S2S auth, but there isn’t much
clarity about what the options are or why you’d select any of them. Bad
decisions sometimes result. What follows is a stab at clearing the question up.&lt;/p&gt;</description></item></channel></rss>