<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cloud-Security on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/cloud-security/</link>
    <description>Recent content in Cloud-Security on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 06 Nov 2026 08:57:34 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/cloud-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Locking Down Service Accounts with Azure AD Conditional Access and Managed Identities</title>
      <link>https://linuxeries.org/post/2026-11-06-locking-down-service-accounts-with-azure-ad-c/</link>
      <pubDate>Fri, 06 Nov 2026 08:57:34 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-11-06-locking-down-service-accounts-with-azure-ad-c/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Locking Down Service Accounts with Azure AD Conditional Access and Managed Identities&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Service accounts are the backbone of most cloud workloads. They give apps the permissions to read secrets, write logs, or call APIs. When an attacker breaks into one of those accounts the fallout can be huge. Azure AD Conditional Access (CA) and Managed Identities (MI) let you shrink that attack surface without breaking the automation you depend on. Below is a practical walk‑through of the most common patterns, the trade‑offs, and the troubleshooting steps you’ll hit in production.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
