<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>hugs4bugs</title>
    <description>Practical deep dives into cloud security, Microsoft Sentinel, Docker, and DevSecOps by Shubhendu Shubham. Updated weekly.</description>
    <link>https://hugs4bugs.me/</link>
    <atom:link href="https://hugs4bugs.me/feed.xml" rel="self" type="application/rss+xml"/>
    <pubDate>Mon, 12 Oct 2026 04:53:41 +0000</pubDate>
    <lastBuildDate>Mon, 12 Oct 2026 04:53:41 +0000</lastBuildDate>
    <generator>Jekyll v3.10.0</generator>
    
      <item>
        <title>How microVM Isolation Actually Secures your Autonomous Agents</title>
        <description>&lt;p&gt;Let me start with simple question, why do we actually need isolated environment for our agent? It’s already belongs to my secure infra, or it’s local on my system? If I ask same question differently&lt;/p&gt; &lt;h1 id=&quot;docker-ai-sandboxes-architecture-how-microvm-isolation-actually-works-for-autonomous-agents&quot;&gt;Docker AI Sandboxes Architecture: How microVM Isolation Actually Works for Autonomous Agents&lt;/h1&gt; &lt;p&gt;When someone hands an AI coding agent the keys to your repository and says “go fix the CI pipeline,” the question that should follow immediately is: what exactly can that agent touch on your host? Docker Sandboxes gives you an answer to that question backed by hypervisor-level isolation rather than namespace tricks....</description>
        <pubDate>Wed, 02 Sep 2026 05:24:39 +0000</pubDate>
        <link>https://hugs4bugs.me/how-microvm-isolation-actually-secures-your-autonomous-agents/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/how-microvm-isolation-actually-secures-your-autonomous-agents/</guid>
        
        <category>docker</category>
        
        <category>security</category>
        
        <category>ai</category>
        
        <category>docker</category>
      </item>
    
      <item>
        <title>Why your Microsoft sentinel logic apps are leaking sensitive credentials during automation?</title>
        <description>&lt;h2 id=&quot;what-credential-leakage-in-sentinel-playbooks-actually-means&quot;&gt;What credential leakage in Sentinel playbooks actually means&lt;/h2&gt; &lt;p&gt;Here’s the thing nobody tells you when you build your first Microsoft Sentinel playbook: the automation that’s supposed to make your SOC faster is, by default, writing every API key, bearer token, and Key Vault secret it touches straight into a run history that half your Azure AD tenant can probably read.&lt;/p&gt; &lt;p&gt;I’ve reviewed enough Logic Apps-based SOAR implementations now to know this isn’t an edge case. It’s the default behavior. Azure Logic Apps was built as an integration platform first and a security automation engine second, and that heritage shows...</description>
        <pubDate>Sat, 04 Jul 2026 20:04:25 +0000</pubDate>
        <link>https://hugs4bugs.me/why-your-microsoft-sentinel-logic-apps-are-leaking-sensitive-credentials-during-automation/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/why-your-microsoft-sentinel-logic-apps-are-leaking-sensitive-credentials-during-automation/</guid>
        
        <category>microsoft sentinel</category>
        
        <category>credential exposure</category>
        
        <category>security</category>
      </item>
    
      <item>
        <title>Why Ephemeral Docker Sandbox Environments Are Essential For Secure Incident Response Analysis?</title>
        <description>&lt;p&gt;Somewhere in most SOCs there’s a Windows analysis VM nobody fully trusts anymore. Analysts open suspicious attachments in it, snapshot, revert, snapshot, revert — for months. Nobody remembers exactly what ran on it last Tuesday. That VM is the opposite of what a detonation environment is supposed to be, and it’s the reason a lot of IR teams end up reinfecting their own lab.&lt;/p&gt; &lt;p&gt;The fix isn’t a better VM. It’s treating every analysis environment as throwaway infrastructure — built fresh for one sample, used once, and destroyed completely before the next one touches it. Docker makes that pattern cheap...</description>
        <pubDate>Sun, 28 Jun 2026 17:56:26 +0000</pubDate>
        <link>https://hugs4bugs.me/why-ephemeral-docker-sandbox-environments-are-essential-for-secure-incident-response-analysis/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/why-ephemeral-docker-sandbox-environments-are-essential-for-secure-incident-response-analysis/</guid>
        
        <category>docker sandboxes</category>
        
        <category>malware analysis</category>
        
        <category>container security</category>
        
        <category>devsecops</category>
      </item>
    
      <item>
        <title>Why AI Agent Poisoning Is The Biggest Threat To SOC Teams In 2026</title>
        <description>&lt;h2 id=&quot;what-is-ai-agent-poisoning-and-why-does-it-land-on-the-socs-desk-in-2026&quot;&gt;What is AI agent poisoning, and why does it land on the SOC’s desk in 2026&lt;/h2&gt; &lt;p&gt;Prompt injection got all the headlines in 2023 and 2024. It’s still around, but it’s the easy problem now — it resets when the session ends, and most XPIA-style classifiers catch the obvious cases. Agent poisoning doesn’t reset. An attacker writes something once, into your agent’s memory, its tool catalog, or its RAG index, and the corruption sits there until something retrieves it. Days later. Months later. In a session that has nothing to do with the original interaction.&lt;/p&gt; &lt;p&gt;OWASP made this distinction...</description>
        <pubDate>Fri, 26 Jun 2026 19:11:22 +0000</pubDate>
        <link>https://hugs4bugs.me/why-ai-agent-poisoning-is-the-biggest-threat-to-soc-teams-in-2026/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/why-ai-agent-poisoning-is-the-biggest-threat-to-soc-teams-in-2026/</guid>
        
        <category>MCP security</category>
        
        <category>agentic AI</category>
        
        <category>OWASP ASI06</category>
        
        <category>security</category>
      </item>
    
      <item>
        <title>Why You Still Need a SIEM</title>
        <description>&lt;p&gt;I get this question almost every quarter, usually from someone who just signed off on a &lt;a href=&quot;https://newrelic.com/&quot;&gt;New Relic&lt;/a&gt; or Datadog renewal: “We have full observability now, dashboards, traces, alerts on everything, do we really need to buy a SIEM on top of this?” The honest answer is yes, and it has nothing to do with how good Grafana or New Relic is at its job. It’s because neither of them was built to answer the question a SIEM exists for.&lt;/p&gt; &lt;p&gt;Observability answers “is my system healthy.” A SIEM answers “is someone doing something to my system they shouldn’t be.”...</description>
        <pubDate>Fri, 26 Jun 2026 07:15:50 +0000</pubDate>
        <link>https://hugs4bugs.me/why-you-still-need-a-siem/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/why-you-still-need-a-siem/</guid>
        
        <category>SIEM</category>
        
        <category>Microsoft Sentinel</category>
        
        <category>Observability</category>
        
        <category>security</category>
      </item>
    
      <item>
        <title>Letting Gordon migrate your Dockerfile to DHI: </title>
        <description>&lt;p&gt;&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;docker ai&lt;/code&gt;, then &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;&quot;Migrate my dockerfile to DHI&quot;&lt;/code&gt;, then a minute or two of back-and-forth, and you get a working multi-stage Dockerfile back. That part isn’t the interesting bit — it works about as well as you’d expect for a well-documented, pattern-based migration. The interesting bit is what you just approved while you were looking at the diff instead of the permission prompt.&lt;/p&gt; &lt;p&gt;I covered the &lt;a href=&quot;https://docs.docker.com/dhi/migration/migrate-from-doi/&quot;&gt;manual DHI migration&lt;/a&gt; for Verclaim Health’s claims-validation API in the last post. This time I pointed &lt;a href=&quot;https://docs.docker.com/ai/gordon/&quot;&gt;Gordon&lt;/a&gt; at the same Dockerfile to see what it does differently, and...</description>
        <pubDate>Thu, 25 Jun 2026 20:33:16 +0000</pubDate>
        <link>https://hugs4bugs.me/letting-gordon-migrate-your-dockerfile-to-dhi/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/letting-gordon-migrate-your-dockerfile-to-dhi/</guid>
        
        <category>docker hardened images</category>
        
        <category>docker ai</category>
        
        <category>devsecops</category>
      </item>
    
      <item>
        <title>Docker Hardened Images migration</title>
        <description>&lt;p&gt;You change one line in your Dockerfile — swap &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;FROM python:3.11-slim&lt;/code&gt; for &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;FROM dhi.io/python:3.11-debian12&lt;/code&gt; — kick off the build, and watch it fall over. &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;apt-get: command not found&lt;/code&gt;. Fix that, rebuild, and now it’s &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;Permission denied&lt;/code&gt; writing to a log directory. Fix that too, and your container won’t bind to port 80 anymore. None of this is broken tooling. It’s &lt;a href=&quot;https://docs.docker.com/dhi/&quot;&gt;Docker Hardened Images&lt;/a&gt; (DHI) doing exactly what they’re designed to do, and the official migration guide assumes you already know why before you start.&lt;/p&gt; &lt;p&gt;I ran this migration for a Flask...</description>
        <pubDate>Thu, 25 Jun 2026 20:16:10 +0000</pubDate>
        <link>https://hugs4bugs.me/docker-hardened-images-migration/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/docker-hardened-images-migration/</guid>
        
        <category>docker hardened images</category>
        
        <category>dockerfile</category>
        
        <category>container security</category>
        
        <category>Devsecops</category>
      </item>
    
      <item>
        <title>The FIFA World Cup Bug Wasn&apos;t About FIFA </title>
        <description>&lt;p&gt;On June 14, a researcher going by BobDaHacker registered as a football agent on FIFA’s public site. Within a few hours they had standing access to FIFA’s live World Cup streaming controls, match management system, and commentator dashboard. Not read access to a leaked file — live, write-capable access to the production systems running the tournament.&lt;/p&gt; &lt;p&gt;No exploit chain, no zero-day, no clever bypass. They filled out a form.&lt;/p&gt; &lt;p&gt;The root cause is one sentence, and it’s the kind of thing that should make every architect uncomfortable: &lt;strong&gt;the frontend checked permissions, the backend didn’t.&lt;/strong&gt;&lt;/p&gt; &lt;h2 id=&quot;what-actually-happened&quot;&gt;What actually happened&lt;/h2&gt; &lt;p&gt;FIFA runs...</description>
        <pubDate>Thu, 18 Jun 2026 11:56:18 +0000</pubDate>
        <link>https://hugs4bugs.me/the-fifa-world-cup-bug-wasn-t-about-fifa/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/the-fifa-world-cup-bug-wasn-t-about-fifa/</guid>
        
        <category>client-side authorization</category>
        
        <category>broken access control</category>
        
        <category>microsoft entra</category>
        
        <category>api security</category>
        
        <category>owasp</category>
        
        <category>security</category>
      </item>
    
      <item>
        <title>How a Single Photo Can Silently Own Your Mac via ExifTool</title>
        <description>&lt;p&gt;Let me start with a question most people get wrong.&lt;/p&gt; &lt;p&gt;You receive a photo from a client. A photographer sends you their portfolio. A contractor drops an image into Slack. You open it, nothing happens — no weird pop-up, no warning, nothing. Safe, right?&lt;/p&gt; &lt;p&gt;Not necessarily. If the software processing that image is a tool called ExifTool and it’s running an unpatched version on a Mac, that image could have already run commands on your machine before you even saw the picture. That’s CVE-2026-3102. Let’s break down exactly how. &lt;img src=&quot;https://res.cloudinary.com/hugs4bugs/image/upload/v1781716724/hugs4bugs/extra/2_kyvtzw.png&quot; alt=&quot;image&quot; /&gt;&lt;/p&gt; &lt;h2 id=&quot;what-is-exiftool-and-who-actually-uses-it&quot;&gt;What is ExifTool and who actually...</description>
        <pubDate>Wed, 17 Jun 2026 15:40:11 +0000</pubDate>
        <link>https://hugs4bugs.me/how-a-single-photo-can-silently-own-your-mac-via-exiftool/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/how-a-single-photo-can-silently-own-your-mac-via-exiftool/</guid>
        
        <category>CVE-2026-3102</category>
        
        <category>ommand-injection</category>
        
        <category>supply-chain</category>
        
        <category>security</category>
      </item>
    
      <item>
        <title>Take Care of Your Agent</title>
        <description>&lt;p&gt;&lt;strong&gt;What Agentic AI Security Actually Looks Like in 2026”&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;There’s a joke going around red team reddit channels right now: &lt;em&gt;the fastest way to get domain admin in 2026 is to write a prompt, not an exploit&lt;/em&gt;. It’s not far off.&lt;/p&gt; &lt;p&gt;AI agents are in production. They’re reading your emails, querying your databases, executing code, and calling APIs on behalf of your users. What most organizations haven’t done is figure out what security controls apply to something that isn’t a user but also isn’t quite software.&lt;/p&gt; &lt;p&gt;That’s the gap. And it’s being actively exploited.&lt;/p&gt; &lt;p&gt;This post is for security architects...</description>
        <pubDate>Thu, 04 Jun 2026 04:02:15 +0000</pubDate>
        <link>https://hugs4bugs.me/take-care-of-your-agent/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/take-care-of-your-agent/</guid>
        
        <category>agentic-ai-security</category>
        
        <category>model-context-protocol</category>
        
        <category>owasp-agentic-top10</category>
        
        <category>LLM-security</category>
        
        <category>non-human-identity</category>
        
        <category>security</category>
      </item>
    
      <item>
        <title>Your IDE Just Got Pwned: The Nx Console Supply Chain Attack</title>
        <description>&lt;p&gt;Your IDE is now part of your attack surface. The Nx Console breach on May 18, 2026 proves it.&lt;/p&gt; &lt;h2 id=&quot;what-happened--and-why-its-worse-than-a-typical-extension-compromise&quot;&gt;What Happened — and Why It’s Worse Than a Typical Extension Compromise&lt;/h2&gt; &lt;p&gt;Most extension compromises are sloppy — a typosquat, a stolen package name, a rogue maintainer who pushes a coin miner. This wasn’t that.&lt;/p&gt; &lt;p&gt;On May 18, 2026, version &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;18.95.0&lt;/code&gt; of the Nx Console VS Code extension (&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;nrwl.angular-console&lt;/code&gt;) was published to the Visual Studio Code Marketplace with malicious code baked in. The extension has over &lt;strong&gt;2.2 million installs&lt;/strong&gt;. The compromised version was live for exactly...</description>
        <pubDate>Fri, 22 May 2026 05:26:18 +0000</pubDate>
        <link>https://hugs4bugs.me/your-ide-just-got-pwned-the-nx-console-supply-chain-attack/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/your-ide-just-got-pwned-the-nx-console-supply-chain-attack/</guid>
        
        <category>supply-chain-attack</category>
        
        <category>vscode-extension</category>
        
        <category>nx-console</category>
        
        <category>github-security</category>
        
        <category>GHSA</category>
        
        <category>devsecops</category>
      </item>
    
      <item>
        <title>Locking Down VS Code Extensions in the Enterprise — Lessons from the GitHub Breach</title>
        <description>&lt;p&gt;&lt;strong&gt;By a Security Architect who’s tired of being surprised by developer endpoints&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;&lt;strong&gt;May 20, 2026.&lt;/strong&gt; GitHub confirms that approximately 3,800 of its internal repositories were exfiltrated after a threat actor embedded malware inside a VS Code extension and a GitHub employee installed it. Critical secrets were rotated within hours.&lt;/p&gt; &lt;p&gt;&lt;img src=&quot;https://res.cloudinary.com/hugs4bugs/image/upload/v1779268674/hugs4bugs/hacking-news/twitter-gh_jlkg9o.png&quot; alt=&quot;image&quot; /&gt; &lt;a href=&quot;https://x.com/github/status/2056949168208552080&quot;&gt;official GitHub Tweet&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;em&gt;This is not a vulnerability in GitHub’s platform. This is a developer endpoint with unchecked tooling. And that is a far scarier problem.&lt;/em&gt;&lt;/p&gt; &lt;h2 id=&quot;why-this-hit-different&quot;&gt;Why This Hit Different&lt;/h2&gt; &lt;p&gt;Every time I see a supply chain incident, I run a quick mental exercise: “Could...</description>
        <pubDate>Wed, 20 May 2026 09:03:37 +0000</pubDate>
        <link>https://hugs4bugs.me/locking-down-vs-code-extensions-in-the-enterprise-lessons-from-the-github-breach/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/locking-down-vs-code-extensions-in-the-enterprise-lessons-from-the-github-breach/</guid>
        
        <category>security</category>
        
        <category>threatintel</category>
        
        <category>security</category>
      </item>
    
      <item>
        <title>TLS Automation Isn&apos;t Optional Anymore. Here&apos;s What That Means for Your Stack.</title>
        <description>&lt;p&gt;&lt;em&gt;Why manual TLS management is quietly breaking the web — and what the industry is doing about it.&lt;/em&gt;&lt;/p&gt; &lt;h2 id=&quot;before-we-start-what-problem-are-we-actually-solving&quot;&gt;Before We Start: What Problem Are We Actually Solving?&lt;/h2&gt; &lt;p&gt;Picture this: it’s 2 AM. Your company’s e-commerce site starts throwing &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;NET::ERR_CERT_DATE_INVALID&lt;/code&gt; errors in every browser. Customer support is flooded. Revenue is bleeding per minute. Your on-call engineer digs in, only to realize that the TLS certificate — the thing that keeps your site on HTTPS — quietly expired at midnight, and nobody set up an alert for it.&lt;/p&gt; &lt;p&gt;&lt;img src=&quot;https://res.cloudinary.com/hugs4bugs/image/upload/v1779199368/hugs4bugs/extra/Gemini_Generated_Image_1n8nyp1n8nyp1n8n_tfcdfd.png&quot; alt=&quot;image&quot; /&gt;&lt;/p&gt; &lt;p&gt;This isn’t a hypothetical. It happens to...</description>
        <pubDate>Tue, 19 May 2026 17:53:24 +0000</pubDate>
        <link>https://hugs4bugs.me/tls-automation-isn-t-optional-anymore-here-s-what-that-means-for-your-stack/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/tls-automation-isn-t-optional-anymore-here-s-what-that-means-for-your-stack/</guid>
        
        <category>security</category>
        
        <category>dns</category>
        
        <category>certificate</category>
        
        <category>security</category>
      </item>
    
      <item>
        <title>Docker Agent: Building Your Own AI Agent Teams from the Terminal</title>
        <description>&lt;h1 id=&quot;docker-agent-building-your-own-ai-agent-teams-from-the-terminal&quot;&gt;Docker Agent: Building Your Own AI Agent Teams from the Terminal&lt;/h1&gt; &lt;p&gt;You’ve probably used GitHub Copilot to autocomplete a line of code, or maybe you’ve typed something into ChatGPT and copy-pasted the result into your editor. That workflow is… fine. But what if you could have a team of AI agents sitting in your terminal, each one with a specific job, passing work between each other, running your tests, reading your files, and actually finishing tasks end to end?&lt;/p&gt; &lt;p&gt;That’s what Docker Agent is. It’s an open-source framework for defining and running teams of specialized AI agents. Not one...</description>
        <pubDate>Tue, 12 May 2026 12:22:39 +0000</pubDate>
        <link>https://hugs4bugs.me/docker-agent-building-your-own-ai-agent-teams-from-the-terminal/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/docker-agent-building-your-own-ai-agent-teams-from-the-terminal/</guid>
        
        <category>docker</category>
        
        <category>ai</category>
        
        <category>agents</category>
        
        <category>docker</category>
      </item>
    
      <item>
        <title>Docker Scout Security Policy: A Technical  Deep Dive</title>
        <description>&lt;p&gt;Most teams treat container security as a one-time scan — push the image, check the CVE report, feel good, move on. That worked when you had a handful of services. It doesn’t scale when you’re running 40 microservices across three environments and someone quietly bumped a base image from &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;node:18-alpine&lt;/code&gt; to &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;node:18&lt;/code&gt; last Tuesday.&lt;/p&gt; &lt;p&gt;Docker Scout’s Policy Evaluation is the answer to that problem. It takes the raw image analysis that Scout already does and puts a governance layer on top — letting you define what “good” looks like for your organization, track how far your...</description>
        <pubDate>Fri, 08 May 2026 19:13:52 +0000</pubDate>
        <link>https://hugs4bugs.me/docker-scout-security-policy-a-technical-deep-dive/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/docker-scout-security-policy-a-technical-deep-dive/</guid>
        
        <category>docker</category>
        
        <category>container-security</category>
        
        <category>policy-as-code</category>
        
        <category>docker</category>
      </item>
    
      <item>
        <title>NDR vs. EDR vs. XDR: A Deep Technical Breakdown for Security Engineers</title>
        <description>&lt;p&gt;Modern enterprise security stacks are crowded with acronyms. NDR, EDR, and XDR each occupy a distinct position in the detection and response landscapeâand conflating them leads to coverage gaps, redundant tooling, and wasted budget. This post breaks down each technology at a technical level, maps them to the SOC Visibility Triad, and helps you reason about how they should fit together in a mature security architecture.&lt;/p&gt; &lt;h2 id=&quot;the-core-problem-fragmented-visibility&quot;&gt;The Core Problem: Fragmented Visibility&lt;/h2&gt; &lt;p&gt;Enterprise environments are sprawling. An attacker compromising a single endpoint can move laterally across the network, exfiltrate data through encrypted channels, pivot into cloud workloads, and persist for...</description>
        <pubDate>Fri, 08 May 2026 18:51:37 +0000</pubDate>
        <link>https://hugs4bugs.me/ndr-vs-edr-vs-xdr-a-deep-technical-breakdown-for-security-engineers/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/ndr-vs-edr-vs-xdr-a-deep-technical-breakdown-for-security-engineers/</guid>
        
        <category>security</category>
        
        <category>soc</category>
        
        <category>Security</category>
      </item>
    
      <item>
        <title>Your AI Agent Just Exfiltrated Your SSH Keys. You Approved It.</title>
        <description>&lt;p&gt;.&lt;/p&gt; &lt;blockquote&gt; &lt;p&gt;&lt;strong&gt;Source&lt;/strong&gt;: All technical content sourced from the &lt;a href=&quot;https://docs.docker.com/ai/sandboxes/&quot;&gt;official Docker Sandboxes documentation&lt;/a&gt; and &lt;a href=&quot;https://docs.docker.com/engine/security/&quot;&gt;Docker Engine Security docs&lt;/a&gt;.&lt;/p&gt; &lt;/blockquote&gt; &lt;hr /&gt; &lt;h2 id=&quot;the-new-problem-sitting-in-every-engineering-teams-lap&quot;&gt;The New Problem Sitting in Every Engineering Team’s Lap&lt;/h2&gt; &lt;p&gt;AI coding agents changed how software gets written. Claude Code, GitHub Copilot CLI, Codex, Gemini CLI — these tools don’t just suggest code anymore, they execute it. They install packages, run builds, modify config files, call APIs, and spin up services. And by default, they do all of that on your machine, with your credentials, against your filesystem.&lt;/p&gt; &lt;p&gt;That’s fine until it isn’t. The moment an agent...</description>
        <pubDate>Thu, 30 Apr 2026 12:00:00 +0000</pubDate>
        <link>https://hugs4bugs.me/your-ai-agent-exfiltrated-your-ssh-keys/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/your-ai-agent-exfiltrated-your-ssh-keys/</guid>
        
        <category>docker</category>
        
        <category>sandbox</category>
        
        <category>ai-agents</category>
        
        <category>security</category>
        
        <category>security</category>
      </item>
    
      <item>
        <title>Logic App vs Security Copilot </title>
        <description>&lt;p&gt;Introduction: The Automation Dilemma&lt;/p&gt; &lt;p&gt;Today I do judge any organisation having mature SOC (Security Operation Center) not on the basis of Cybersecurity frameworks and Industry standards, I do see what extent they do have SOAR or automation placed, how much is MTTD and MTTR? and till what levels manual intervion is involved?&lt;/p&gt; &lt;p&gt;Since organisations should not have an option when it comes to SOAR , it should be mandatory considering emerging sophiticated threat landscape. They’re constantly asking which tool is right for the job. Should you use a battle-tested orchestrator like Logic Apps? Or embrace the new paradigm of AI-powered...</description>
        <pubDate>Wed, 17 Dec 2025 00:00:00 +0000</pubDate>
        <link>https://hugs4bugs.me/logicapps-vs-securitycopilot/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/logicapps-vs-securitycopilot/</guid>
        
        <category>soc</category>
        
        <category>Cybersecurity</category>
        
        <category>sentinel</category>
        
        <category>cybersecurity</category>
      </item>
    
      <item>
        <title>Sentinel Authentication:you&apos;re probably doing it wrong?</title>
        <description>&lt;p&gt;When your Security Operations Center starts automating incident response with Microsoft Sentinel playbooks or SOAR features (via Logic Apps), one question consistently surfaces during architecture reviews: “Which authentication method should we use?” I’ve seen teams default to &lt;strong&gt;OAuth&lt;/strong&gt; because it’s familiar, only to face credential sprawl nightmares six months later. Others jump straight to &lt;strong&gt;managed identities&lt;/strong&gt; without understanding when a &lt;em&gt;service principal&lt;/em&gt; actually makes more sense.&lt;/p&gt; &lt;p&gt;Let’s directly jump to the point and talk about three authentication methods available for the Microsoft sentinel Logic Apps connector, when each one fits your security architecture and the operational realities that often get...</description>
        <pubDate>Wed, 15 Oct 2025 00:00:00 +0000</pubDate>
        <link>https://hugs4bugs.me/best-ms-sentinel-authentication-method/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/best-ms-sentinel-authentication-method/</guid>
        
        <category>soc</category>
        
        <category>Cybersecurity</category>
        
        <category>sentinel</category>
        
        <category>cybersecurity</category>
      </item>
    
      <item>
        <title>Email Security is broken?</title>
        <description>&lt;p&gt;Email security has become a cat-and-mouse game where attackers consistently outpace traditional defenses. While we’ve spent years perfecting signature-based detection and sandboxing, threat actors have moved to more sophisticated tactics: compromised accounts, domain spoofing, and slow-burn social engineering campaigns that span weeks or months.&lt;/p&gt; &lt;p&gt;The fundamental issue is that most email security solutions treat each message in isolation. They scan for malware, check against reputation databases, and apply content filters—but they miss the behavioral patterns that reveal the real threats. A CEO fraud email from a trusted domain with clean content will sail right through these defenses.&lt;/p&gt; &lt;p&gt;This is where...</description>
        <pubDate>Sun, 31 Aug 2025 00:00:00 +0000</pubDate>
        <link>https://hugs4bugs.me/email-security-is-broken/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/email-security-is-broken/</guid>
        
        <category>emailsecurity</category>
        
        <category>Cybersecurity</category>
        
        <category>cybersecurity</category>
      </item>
    
      <item>
        <title>MadeYouReset&apos; HTTP/2 Vulnerability (CVE-2025-8671) Explained</title>
        <description>&lt;p&gt;&lt;strong&gt;Introduction&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;The internet carries much of its vital traffic over the HTTP protocol. With the evolution from HTTP/1.1 to HTTP/2, websites and web apps became dramatically faster, more responsive, and capable of handling heavier loads. But with these leaps forward come new, sometimes quietly lurking, risks. In 2023, the world’s top cloud providers faced the &lt;em&gt;“Rapid Reset”&lt;/em&gt; vulnerability, which allowed attackers to crash powerful services using HTTP/2’s own stream management features. While defenses for that attack were deployed quickly, 2025 saw the discovery of a new twist: “MadeYouReset” (CVE-2025-8671). This crafty vulnerability asks a chilling question—what if attackers didn’t flood...</description>
        <pubDate>Wed, 20 Aug 2025 00:00:00 +0000</pubDate>
        <link>https://hugs4bugs.me/made-your-reset-vulnerability/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/made-your-reset-vulnerability/</guid>
        
        <category>cve</category>
        
        <category>Cybersecurity</category>
        
        <category>cve</category>
      </item>
    
      <item>
        <title>SIEM Done Right:3stage RoadMap</title>
        <description>&lt;p&gt;Last week I got a situation that stuck me “Why does SIEM feel like it’s fighting against us instead of helping us”? It’s a fair question. Too many organisations jumps into SIEM implementation assuming they’ll flip a switch and suddenly have perfect visibility. I have been observing since my last 6 years in cybersecurity domain that most of the organisation approach towards SIEM deployment is completly wrong.They are simply adopting facing tools and doing partenership with fancy vendors. The reality?&lt;/p&gt; &lt;p&gt;We all knows or those who got chance to work within SOC might agree with me. Building an effective SIEM...</description>
        <pubDate>Fri, 15 Aug 2025 00:00:00 +0000</pubDate>
        <link>https://hugs4bugs.me/SIEM-doneright-3-stages-roadmap-that-actually-works/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/SIEM-doneright-3-stages-roadmap-that-actually-works/</guid>
        
        <category>SOC</category>
        
        <category>Cybersecurity</category>
        
        <category>Cyber Security</category>
      </item>
    
      <item>
        <title>Terraform&apos;s Secret Weapon: Write Only Arguments</title>
        <description>&lt;p&gt;If you’ve been working with Terraform for a while, you’ve probably run into this frustrating situation: you need to pass a password or API token to a resource, but you don’t want that sensitive data sitting in your state file for everyone to see. Maybe you’ve tried creative workarounds with external data sources or complex scripting, but let’s be honest – it always felt like a hack.&lt;/p&gt; &lt;p&gt;Well, good news! Terraform 1.11 introduces write-only arguments, and they’re about to change how we handle secrets in our infrastructure code. Think of them as a secure handoff mechanism – you can pass...</description>
        <pubDate>Thu, 17 Jul 2025 00:00:00 +0000</pubDate>
        <link>https://hugs4bugs.me/no-more-secrets-in-terraform-statefile-write-only-arguments/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/no-more-secrets-in-terraform-statefile-write-only-arguments/</guid>
        
        <category>IaaC</category>
        
        <category>Cybersecurity</category>
        
        <category>Cyber Security</category>
      </item>
    
      <item>
        <title>When Snyk Saved my Firebase Project</title>
        <description>&lt;iframe style=&quot;border-radius:12px&quot; src=&quot;https://open.spotify.com/embed/episode/5MSloKT0dP8PR4O7CW7qTW?utm_source=generator&quot; width=&quot;100%&quot; height=&quot;352&quot; frameborder=&quot;0&quot; allowfullscreen=&quot;&quot; allow=&quot;autoplay; clipboard-write; encrypted-media; fullscreen; picture-in-picture&quot; loading=&quot;lazy&quot;&gt;&lt;/iframe&gt; &lt;p&gt;Yesterday, I got an unexpected visitor to my GitHub repository. Not a human contributor, but Snyk’s automated security bot, flagging a critical vulnerability in my Firebase project. What started as a routine dependency check turned into a fascinating case study of how modern security tools can catch threats that even experienced developers might miss.&lt;/p&gt; &lt;p&gt;The culprit? An uncontrolled resource consumption vulnerability lurking in the @grpc/grpc-js library, buried deep within Firebase’s dependency chain. With a severity score of &lt;strong&gt;559&lt;/strong&gt; and the identifier &lt;strong&gt;SNYK-JS-GRPCGRPCJS-7242922&lt;/strong&gt;, this wasn’t just another minor...</description>
        <pubDate>Tue, 15 Jul 2025 00:00:00 +0000</pubDate>
        <link>https://hugs4bugs.me/snyk-saved-my-project-ft-uncontrolled-resource-consumption/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/snyk-saved-my-project-ft-uncontrolled-resource-consumption/</guid>
        
        <category>AppSec</category>
        
        <category>Cybersecurity</category>
        
        <category>Cyber Security</category>
      </item>
    
      <item>
        <title>How Snyk broker solves the Enterprise Integration Puzzle?</title>
        <description>&lt;p&gt;Recently I got interviewed with a company and there I being asked a scernairo based question somewhat regarding Snyk Broker connector 3rd party tool and integration seems fine, but artifact scans are getting failed. So this question forced me to think about as organizations mature their DevSecOps practices, one of the biggest challenges they face is integrating security tools with their existing infrastructure while maintaining strict security boundaries. This is particularly true for enterprises with air-gapped environments, strict network policies, or sensitive codebases that cannot be exposed to external services.&lt;/p&gt; &lt;p&gt;Being Snyk Ambassador, let’s see hwo &lt;strong&gt;Snyk Broker&lt;/strong&gt; solves the...</description>
        <pubDate>Tue, 08 Jul 2025 00:00:00 +0000</pubDate>
        <link>https://hugs4bugs.me/how-snyk-broker-solves-enterprise-integration-puzzle/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/how-snyk-broker-solves-enterprise-integration-puzzle/</guid>
        
        <category>AppSec</category>
        
        <category>Cybersecurity</category>
        
        <category>Cyber Security</category>
      </item>
    
      <item>
        <title>DNS4EU vs Cloudflare: Europe&apos;s Sovereign DNS Resolver — An Honest Security Review</title>
        <description>&lt;p&gt;Last month, something interesting happened in the DNS landscape that most security teams probably missed. &lt;a href=&quot;https://www.joindns4.eu/&quot;&gt;DNS4EU went live in June 2025&lt;/a&gt;, marking Europe’s first serious attempt at building DNS infrastructure that doesn’t route through Silicon Valley. After spending time analyzing the technical implementation and testing the resolvers, here’s what security professionals need to know about this development. If you can’t read text I have aleternative solution for you as audio book&lt;/p&gt; &lt;iframe src=&quot;https://creators.spotify.com/pod/show/shubhendushubham/embed/episodes/DNS4EU--How-Europe-built-DNS-Killer-e3438an/a-ac09800&quot; height=&quot;102px&quot; width=&quot;400px&quot; frameborder=&quot;0&quot; scrolling=&quot;no&quot;&gt;&lt;/iframe&gt; &lt;p&gt;&lt;strong&gt;What DNS4EU Is?&lt;/strong&gt; &lt;img src=&quot;https://res.cloudinary.com/hugs4bugs/image/upload/v1749618151/hugs4bugs/Smermaid.live_czsbce.jpg&quot; alt=&quot;Image&quot; /&gt;&lt;/p&gt; &lt;p&gt;DNS4EU represents more than just another public DNS resolver—it’s the EU’s strategic infrastructure play for...</description>
        <pubDate>Wed, 11 Jun 2025 00:00:00 +0000</pubDate>
        <link>https://hugs4bugs.me/DNS4EU-How-europe-just-built-a-dns-killer/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/DNS4EU-How-europe-just-built-a-dns-killer/</guid>
        
        <category>dns</category>
        
        <category>dns4eu</category>
        
        <category>cloudflare</category>
        
        <category>network-security</category>
        
        <category>gdpr</category>
        
        <category>europe</category>
        
        <category>security</category>
      </item>
    
      <item>
        <title>Be a Detective with AWS Detective</title>
        <description>&lt;p&gt;In the ever-evolving landscape of cloud security, identifying and responding to threats swiftly is paramount. Amazon detective makes its easy for soc analyst or security engineer to analyse, investigate, and do RCA. Before jumping to the tehnical side, let’s understand the landscape of security Incidents investigation phase :&lt;/p&gt; &lt;p&gt;&lt;img src=&quot;https://res.cloudinary.com/hugs4bugs/image/upload/v1748666399/hugs4bugs/aws/1_d9pzu7.jpg&quot; alt=&quot;image&quot; /&gt;&lt;/p&gt; &lt;p&gt;1.Triage – Figuring Out If There’s a Real Threat Imagine getting an alert that something suspicious might be happening in your system. Your first step is to check whether it’s a real problem or a false alarm.&lt;/p&gt; &lt;p&gt;Some alerts come from Amazon GuardDuty or Amazon Inspector, which help...</description>
        <pubDate>Sat, 31 May 2025 00:00:00 +0000</pubDate>
        <link>https://hugs4bugs.me/be-a-detective-with-aws-detective/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/be-a-detective-with-aws-detective/</guid>
        
        <category>aws</category>
        
        <category>Cybersecurity</category>
        
        <category>Cyber Security</category>
      </item>
    
      <item>
        <title>Stop Fighting Local LLMs:Docker Just fixed the Mess</title>
        <description>&lt;p&gt;If you’re like me and have been wrestling with running LLMs locally for development, Docker just dropped something that might change your workflow completely. &lt;img src=&quot;https://res.cloudinary.com/hugs4bugs/image/upload/v1748409418/hugs4bugs/dockermodelrunner/3_jhl3rl.png&quot; alt=&quot;image&quot; /&gt; The new “Models” tab you see in Docker Desktop isn’t just another UI addition—it’s part of Docker Model Runner, a beta feature that’s currently shaking up how we work with AI models locally.&lt;/p&gt; &lt;p&gt;&lt;strong&gt;What Exactly Is This Thing?&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;Docker Model Runner makes it easier for developers to run AI models locally. No extra setup, no jumping between tools, and no need to wrangle infrastructure. &lt;img src=&quot;https://res.cloudinary.com/hugs4bugs/image/upload/v1748406335/hugs4bugs/dockermodelrunner/1_k0cx3q.png&quot; alt=&quot;image&quot; /&gt;&lt;/p&gt; &lt;p&gt;Think of it as...</description>
        <pubDate>Wed, 28 May 2025 00:00:00 +0000</pubDate>
        <link>https://hugs4bugs.me/stop-fighting-local-llm-docker-just-fixed-mess-model-runnner/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/stop-fighting-local-llm-docker-just-fixed-mess-model-runnner/</guid>
        
        <category>Model Runner</category>
        
        <category>Docker</category>
        
        <category>Docker</category>
      </item>
    
      <item>
        <title>Ship AI Tools Like Apps with  Docker&apos;s MCP ToolKit</title>
        <description>&lt;h1 id=&quot;ship-ai-tools-like-apps-dockers-mcp-toolkit&quot;&gt;Ship AI Tools Like Apps: Docker’s MCP ToolKit&lt;/h1&gt; &lt;p&gt;The AI revolution is here, and every company wants their services to work seamlessly with large language models (LLMs). Wait a minute, I do recall a quote from “&lt;a href=&quot;https://www.linkedin.com/in/ajeetsraina/&quot;&gt;Ajeet’s&lt;/a&gt; talk “ is now every company an AI company?” and we all know the answer. Now the Model Context Protocol (MCP) – Anthropic’s open standard that’s rapidly becoming the bridge between LLMs and real-world applications. With Windows Copilot, Google Gemini, OpenAI’s ChatGPT, and Claude all embracing MCP, the message is clear: if you want LLMs to use your service, you need...</description>
        <pubDate>Sun, 25 May 2025 00:00:00 +0000</pubDate>
        <link>https://hugs4bugs.me/ship-ai-tools-like-app-with-docker-mcptoolkit/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/ship-ai-tools-like-app-with-docker-mcptoolkit/</guid>
        
        <category>MCP</category>
        
        <category>Docker</category>
        
        <category>Docker</category>
      </item>
    
      <item>
        <title>Build Your Own IOC Playground with ELastic SIEM</title>
        <description>&lt;p&gt;When it comes to proactive approach of security, threat Hunting comes to the picture. And being aware of IOC aka Indicators of Compromise gives an extra leverage to find malicious urls, hash, IP and block those and take proper action. In this lab, I’m gonna build homelab with Elastic Cloud and Elastic SIEM deployment and generate IOC with AbuseCH .&lt;/p&gt; &lt;p&gt;Basic HLD&lt;/p&gt; &lt;p&gt;&lt;img src=&quot;https://res.cloudinary.com/hugs4bugs/image/upload/v1747751796/hugs4bugs/Screenshot_20-5-2025_20540_excalidraw.com_rlsc0e.jpg&quot; alt=&quot;image&quot; /&gt;&lt;/p&gt; &lt;p&gt;&lt;strong&gt;Steps to create a hosted Deployment&lt;/strong&gt;&lt;/p&gt; &lt;ol&gt; &lt;li&gt;Signup to &lt;a href=&quot;https://cloud.elastic.co&quot;&gt;Elastic Cloud&lt;/a&gt;&lt;/li&gt; &lt;li&gt;Click on Add Deployment &lt;img src=&quot;https://res.cloudinary.com/hugs4bugs/image/upload/v1747754029/hugs4bugs/Elastics/hostedclouddeployment_ustvd2.jpg&quot; alt=&quot;image&quot; /&gt;&lt;/li&gt; &lt;li&gt;Launching Deployement &lt;img src=&quot;https://res.cloudinary.com/hugs4bugs/image/upload/v1747754101/hugs4bugs/Elastics/launching_deployement_ewcinj.jpg&quot; alt=&quot;image&quot; /&gt;&lt;/li&gt; &lt;li&gt;Incoming Data Confirmation &lt;img src=&quot;https://res.cloudinary.com/hugs4bugs/image/upload/v1747754167/hugs4bugs/Elastics/incomingdatapreview_vlz16q.jpg&quot; alt=&quot;image&quot; /&gt;&lt;/li&gt; &lt;/ol&gt;...</description>
        <pubDate>Sun, 09 Mar 2025 00:00:00 +0000</pubDate>
        <link>https://hugs4bugs.me/build-threat-hunting-IOC-with-elastic-siem/</link>
        <guid isPermaLink="true">https://hugs4bugs.me/build-threat-hunting-IOC-with-elastic-siem/</guid>
        
        <category>Cyber Security</category>
        
        <category>Elastic SIEM</category>
        
        <category>security</category>
      </item>
    
  </channel>
</rss>
