<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>C2 on Daniyal Ahmed | Red Team &amp; Cloud Security</title><link>https://daniyalahmed.dev/tags/c2/</link><description>Recent content in C2 on Daniyal Ahmed | Red Team &amp; Cloud Security</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>daniyal.ahmed@microtechx.com (Daniyal Ahmed)</managingEditor><webMaster>daniyal.ahmed@microtechx.com (Daniyal Ahmed)</webMaster><lastBuildDate>Sun, 03 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://daniyalahmed.dev/tags/c2/index.xml" rel="self" type="application/rss+xml"/><item><title>Living-Off-the-Cloud: Logic Apps as Covert C2 and Persistence</title><link>https://daniyalahmed.dev/posts/living-off-the-cloud---logic-apps-as-covert-c2-and-persistence/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><author>daniyal.ahmed@microtechx.com (Daniyal Ahmed)</author><guid>https://daniyalahmed.dev/posts/living-off-the-cloud---logic-apps-as-covert-c2-and-persistence/</guid><description>The attacker did not deploy malware. They did not use a custom C2 framework. They used Azure Logic Apps — the same service your HR team uses for onboarding automation. The traffic was indistinguishable from a legitimate business workflow. The managed identity had Key Vault access. The persistence survived the incident response team&amp;rsquo;s VM wipe. And it ran for 11 days before anyone looked at Logic Apps.
This article is about what that attack looks like, why it is so hard to detect, and how to build the detection framework that most organizations have never configured.</description></item></channel></rss>