<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>☼</title>
  <subtitle></subtitle>
  <link href="https://breakwellsbaseline.net/feed.xml" rel="self"/>
  <link href="https://breakwellsbaseline.net/"/>
  <updated>2026-06-03T00:00:00Z</updated>
  <id>https://breakwellsbaseline.net/</id>
  <author>
    <name></name>
  </author>
  
    <entry>
      <title>Packaging without a domain</title>
      <link href="https://breakwellsbaseline.net/cases/teamviewer-intune-msi-assumptions/"/>
      <updated>2026-06-03T00:00:00Z</updated>
      <id>https://breakwellsbaseline.net/cases/teamviewer-intune-msi-assumptions/</id>
      <summary>A TeamViewer Host packaging project exposed hidden assumptions in an MSI transform about stale domain infrastructure, leading to implementation of an Intune-ready package and detection model that restored visibility across multiple cloud native tenants.</summary>
    </entry>
  
    <entry>
      <title>Autopilot as state orchestration</title>
      <link href="https://breakwellsbaseline.net/writing/autopilot-state-orchestration/"/>
      <updated>2026-06-03T00:00:00Z</updated>
      <id>https://breakwellsbaseline.net/writing/autopilot-state-orchestration/</id>
      <summary>A practical model for thinking about Intune and Autopilot in hybrid environments: not as a step-by-step script runner, but as an asynchronous system that needs readiness gates where strict sequencing is non-negotiable.</summary>
    </entry>
  
    <entry>
      <title>Building a File Server by Subtraction</title>
      <link href="https://breakwellsbaseline.net/sandbox/building-a-file-server-by-subtraction/"/>
      <updated>2026-05-12T00:00:00Z</updated>
      <id>https://breakwellsbaseline.net/sandbox/building-a-file-server-by-subtraction/</id>
      <summary>A rough record of reducing a default Ubuntu server into a more limited machine for file serving and log collection, guided by security-brutalist ideas about purpose, subtraction, and survivability.</summary>
    </entry>
  
    <entry>
      <title>Secure Boot CA 2023 and BitLocker Recovery</title>
      <link href="https://breakwellsbaseline.net/cases/secure-boot-ca2023-bitlocker-recovery/"/>
      <updated>2026-04-23T00:00:00Z</updated>
      <id>https://breakwellsbaseline.net/cases/secure-boot-ca2023-bitlocker-recovery/</id>
      <summary>A planned Secure Boot CA 2023 rollout expanded cleanly at first, then surfaced repeated BitLocker recovery prompts on a narrow hardware subset after KB5083769. This case records the operational handling, root-cause investigation, and field remediation path.</summary>
    </entry>
  
    <entry>
      <title>A BitLocker false front</title>
      <link href="https://breakwellsbaseline.net/cases/false-bitlocker-deployment-intune/"/>
      <updated>2026-04-13T00:00:00Z</updated>
      <id>https://breakwellsbaseline.net/cases/false-bitlocker-deployment-intune/</id>
      <summary>A case record on a BitLocker deployment that appeared compliant but had not established meaningful OS-drive encryption.</summary>
    </entry>
  
    <entry>
      <title>Policy Scope Drift in Device Controls</title>
      <link href="https://breakwellsbaseline.net/cases/policy-scope-drift-device-controls/"/>
      <updated>2026-04-08T00:00:00Z</updated>
      <id>https://breakwellsbaseline.net/cases/policy-scope-drift-device-controls/</id>
      <summary>Device-oriented security controls had been attached to a broad dynamic user group, creating conflict state and unreliable testing. This record traces the scope problem and the low-risk migration path used to correct it.</summary>
    </entry>
  
</feed>
