<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Seams &amp; Dependencies on URE</title><link>https://ure.us/pillars/seams--dependencies/</link><description>Recent content in Seams &amp; Dependencies on URE</description><generator>Hugo -- 0.164.0</generator><language>en-us</language><lastBuildDate>Wed, 08 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ure.us/pillars/seams--dependencies/index.xml" rel="self" type="application/rss+xml"/><item><title>Who Holds the Keys to Confidential Computing</title><link>https://ure.us/articles/who-holds-the-keys-to-confidential-computing/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/who-holds-the-keys-to-confidential-computing/</guid><description>Nitro, GCP, and Azure hold the keys to your confidential computing. Own attestation with a SPIFFE root of trust across any cloud and self-owned metal.</description></item><item><title>The Call Is Coming From Your Update Server</title><link>https://ure.us/articles/friendly-fire-when-trusted-updates-break-you/</link><pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/friendly-fire-when-trusted-updates-break-you/</guid><description>Everyone hunts the zero-day. The outage that takes your fleet down arrives signed, scheduled, and fully audited. Why the trusted update is the attack surface.</description></item><item><title>Kudos to Anthropic - Governments Bury Ecosystems</title><link>https://ure.us/articles/kudos-to-anthropic/</link><pubDate>Sat, 28 Feb 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/kudos-to-anthropic/</guid><description>Anthropic held two safety red lines. The Pentagon blacklisted them. Brazil tried government control over tech once - it destroyed the industry forever.</description></item><item><title>Everybody Spies: Sovereignty and the AI Land Grab</title><link>https://ure.us/articles/everybody-spies/</link><pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/everybody-spies/</guid><description>Anthropic claims foreign distillation attacks. Europe races for AI sovereignty. The question hasn&amp;#39;t changed in thirty years: who do you want watching?</description></item><item><title>Building Trust in Security: Part 3</title><link>https://ure.us/articles/building-trust-in-security-part-3/</link><pubDate>Tue, 17 Feb 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/building-trust-in-security-part-3/</guid><description>Security as chromium in steel: a once-in-a-lifetime market window, technical debt, and what earned trust at the M&amp;amp;A table. Part 3 - real CISO story.</description></item><item><title>Building Trust in Security: Part 2</title><link>https://ure.us/articles/building-trust-in-security-part-2/</link><pubDate>Mon, 09 Feb 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/building-trust-in-security-part-2/</guid><description>From DDoS mitigation to CDN improvisation: how crossing domains and showing up under fire turns a security advisor into a trusted partner. Real CISO story.</description></item><item><title>Building Trust in Security: Part 1</title><link>https://ure.us/articles/building-trust-in-security-part-1/</link><pubDate>Thu, 05 Feb 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/building-trust-in-security-part-1/</guid><description>Earning credibility before authority: build a security program during hyper-growth by starting with the pain, not the framework. Part 1 - real CISO story.</description></item><item><title>Cold Aisle Trenches: When Theory Hits the Asphalt</title><link>https://ure.us/articles/cold-aisle-trenches-when-theory-hits-the-asphalt/</link><pubDate>Fri, 30 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/cold-aisle-trenches-when-theory-hits-the-asphalt/</guid><description>A bricked storage array, a 2+4 SLA that technically performed, and a technician asking about lunch while executives circled.</description></item><item><title>The Entropy of Sovereign AI: Map vs. Territory</title><link>https://ure.us/articles/the-entropy-of-sovereign-ai-why-the-map-is-not-the-territory/</link><pubDate>Mon, 26 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/the-entropy-of-sovereign-ai-why-the-map-is-not-the-territory/</guid><description>Sovereign AI isn&amp;#39;t a policy memo - it&amp;#39;s a moving contest of leverage, export controls, incentives, and real infrastructure built under shifting rules.</description></item><item><title>It Took a Pandemic to Learn Why Standards Failed</title><link>https://ure.us/articles/it-took-a-pandemic-to-learn-why-standards-failed/</link><pubDate>Fri, 23 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/it-took-a-pandemic-to-learn-why-standards-failed/</guid><description>Outside-in SOPs drift, create friction, and weaken shared fate. Resilient standards are generated in workflow by the people who operate them.</description></item><item><title>From Security to Resilience: Defense in Depth</title><link>https://ure.us/articles/from-security-to-resilience-defense-in-depth/</link><pubDate>Thu, 22 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/from-security-to-resilience-defense-in-depth/</guid><description>Multi-tenant cloud security is resilience: detect, contain, and recover faster than adversaries can escalate, without violating tenant privacy.</description></item><item><title>When Lack of Guardrails Hurt the Business</title><link>https://ure.us/articles/when-lack-of-guardrails-hurt-the-business/</link><pubDate>Wed, 21 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/when-lack-of-guardrails-hurt-the-business/</guid><description>A $400M Series D company leaked 2M+ user records because the system allowed it. The lesson: security is guardrails, not slogans.</description></item><item><title>When the Constraint Isn’t Capacity</title><link>https://ure.us/articles/when-the-constraint-isnt-capacity/</link><pubDate>Tue, 20 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/when-the-constraint-isnt-capacity/</guid><description>A bootstorm incident that looked like capacity pressure, until instrumentation revealed a non-existent SQL dependency stalling every request path.</description></item><item><title>Security Assurance - URE Case - 1/5 - The Inception</title><link>https://ure.us/articles/security-assurance-engineering-practical-example-ure-chapter-1/</link><pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/security-assurance-engineering-practical-example-ure-chapter-1/</guid><description>URE Case 1/5. Separating security intent from proof, showing what assurance looks like when you treat a system as real, owned, changing, and measurable.</description></item><item><title>Security Assurance - URE Case - 2/5 - Trust Boundaries</title><link>https://ure.us/articles/security-assurance-engineering-practical-example-ure-chapter-2/</link><pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/security-assurance-engineering-practical-example-ure-chapter-2/</guid><description>URE Case 2/5. Making boundaries and ownership explicit before implementation, preventing common failure modes through intentional security design.</description></item><item><title>Security Assurance - URE Case - 3/5 - The Design</title><link>https://ure.us/articles/security-assurance-engineering-practical-example-ure-chapter-3/</link><pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/security-assurance-engineering-practical-example-ure-chapter-3/</guid><description>URE Case 3/5 - The Design. Making the system legible before making it powerful, and defining an architecture baseline that fits on one page.</description></item><item><title>Security Assurance - URE Case - 4/5 - Enabler</title><link>https://ure.us/articles/security-assurance-engineering-practical-example-ure-chapter-4/</link><pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/security-assurance-engineering-practical-example-ure-chapter-4/</guid><description>URE Case 4/5. How security enables business by arriving early with solutions, not vetoes, and reshaping systems to preserve the mission.</description></item><item><title>Security Assurance - URE Case - 5/5 - Conclusion</title><link>https://ure.us/articles/security-assurance-engineering-practical-example-ure-conclusion/</link><pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/security-assurance-engineering-practical-example-ure-conclusion/</guid><description>URE Case 5/5. How security assurance turns intent into proof, delivers clarity and confidence, and makes the safe path the easiest path.</description></item><item><title>Business Resiliency Through Security Assurance</title><link>https://ure.us/articles/improving-business-resiliency-through-security-assurance/</link><pubDate>Tue, 13 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/improving-business-resiliency-through-security-assurance/</guid><description>Resiliency isn&amp;#39;t more security - it&amp;#39;s operating through failures. Security assurance turns belief into evidence, stopping incidents from becoming outages.</description></item><item><title>MEP Providers Are Never in the Postmortem</title><link>https://ure.us/articles/mep-providers-are-never-in-the-postmortem/</link><pubDate>Wed, 07 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/mep-providers-are-never-in-the-postmortem/</guid><description>Why AI-era data center reliability fails between &amp;#39;designed&amp;#39; and &amp;#39;installed&amp;#39; -and how contract chains erase ownership of MEP details when incidents happen.</description></item><item><title>Why GPU Fleet Control Starts with a Map</title><link>https://ure.us/articles/why-gpu-fleet-control-starts-with-a-map/</link><pubDate>Wed, 07 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/why-gpu-fleet-control-starts-with-a-map/</guid><description>GPU operations starts with footprint truth: a living map of where compute really is, across sites, standards, and drift.</description></item><item><title>Tail Latency Killed My Beowulf Cluster in 2006</title><link>https://ure.us/articles/tail-latency-killed-beowulf-cluster-2006/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ure.us/articles/tail-latency-killed-beowulf-cluster-2006/</guid><description>In 2006, I learned that scaling out doesn&amp;#39;t work when the interconnect is the bottleneck. Twenty years later, the same physics governs GPU infrastructure.</description></item></channel></rss>