<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Change Management on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/change-management/</link><description>Recent content in Change Management on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/change-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Security, Access Control, and Change Management for Configurations</title><link>https://ai-blog.noorshomelab.dev/meta-trust-but-canary-config-safety-2026/security-access-control-config/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/meta-trust-but-canary-config-safety-2026/security-access-control-config/</guid><description>&lt;p&gt;Configuration changes are a silent killer in large-scale systems, often leading to outages more frequently than code deployments. At a company like Meta, where thousands of engineers make millions of changes across an infrastructure spanning millions of servers, ensuring the safety of configuration updates is paramount. This chapter dives into how Meta, based on industry best practices and its known engineering culture, likely approaches the critical areas of security, access control, and change management for configurations, all underpinned by the &amp;ldquo;Trust But Canary&amp;rdquo; philosophy.&lt;/p&gt;</description></item></channel></rss>