<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Seenu Bhupala on Medium]]></title>
        <description><![CDATA[Stories by Seenu Bhupala on Medium]]></description>
        <link>https://medium.com/@Seenu-Bhupala?source=rss-909b5003c61a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vdPUtqnB5OFAlzucQqyAbg.jpeg</url>
            <title>Stories by Seenu Bhupala on Medium</title>
            <link>https://medium.com/@Seenu-Bhupala?source=rss-909b5003c61a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:07:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Seenu-Bhupala/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building a grounded, secure AI assistant: the why, and the honest how]]></title>
            <link>https://medium.com/seenu-on-agentic-ai/building-a-grounded-secure-ai-assistant-the-why-and-the-honest-how-a1c4fb1b2058?source=rss-909b5003c61a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1c4fb1b2058</guid>
            <dc:creator><![CDATA[Seenu Bhupala]]></dc:creator>
            <pubDate>Sat, 04 Jul 2026 06:49:35 GMT</pubDate>
            <atom:updated>2026-10-17T01:29:01.959Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7DyeQY0d_yfiKD_UXSbCPw.png" /><figcaption>Defender for Servers Expert. My grounded, secure agentic AI assistant.</figcaption></figure><h4><strong><em>A personal project, and the security thinking behind it.</em></strong></h4><p><strong>Try it live</strong>: <a href="https://ai.cyberfixpro.com/">ai.cyberfixpro.com</a></p><p>I have spent a fair bit of time watching AI assistants answer with complete confidence and, often, complete fiction. As a security engineer, that sits badly with me. A confident wrong answer is not a small thing. In security work it can send someone down the wrong path, and it quietly erodes trust in the tool, and in the person who stood it up.</p><p>I will keep the deep mechanics to myself. Not to be precious about it, but because the value in this kind of work is in the judgement, not the recipe. What follows is the shape of the approach, which is the part actually worth sharing.</p><p><strong>Why I built it</strong></p><p>I learn best by building the whole thing, end to end, and breaking it a few times along the way. I wanted to understand agentic AI properly, not as a demo but as something that had to stand up in the open, on my own domain.</p><p>I also wanted to see whether my day job instincts carried across. I spend my time onboarding customers to security platforms and thinking about how systems fail. An AI assistant is just another system that can fail, so I treated it like one.</p><p><strong>What it actually is</strong></p><p>It is a narrow, grounded assistant. It answers questions within one defined subject area and politely declines everything else. Every factual claim it makes is tied back to a real, current source, with a link you can click and verify. If it cannot find grounding for something, it says so rather than filling the gap with something that sounds right.</p><p>That last behaviour is the whole point. Most of the trouble with these systems comes from their willingness to be helpful past the limit of what they actually know.</p><p><strong>Grounding was the entire idea</strong></p><p>There are two ways an assistant can answer. It can reach into what the model absorbed during training, which is broad but frozen in time and impossible to verify, or it can retrieve from a trusted, current source and answer only from what it just read. The first feels magical and occasionally invents things with great conviction. The second is slower to build and far more honest.</p><p>I built for the second. The assistant retrieves first, reasons over what it found, and then answers with citations attached. The rule underneath it is simple to say and surprisingly hard to enforce: if you cannot cite it, do not assert it.</p><p>The failure mode I was most worried about is the well dressed fabrication, where the model produces a tidy, structured, confident answer with a citation that looks perfect and points at nothing real. That one is dangerous precisely because it looks correct. A good chunk of the work went into making that outcome difficult.</p><p><strong>How it works, from a distance</strong></p><p>Without going into the plumbing, there are a handful of moving parts. A language model does the reasoning. A retrieval layer gives it access to trusted, current material rather than relying on memory. A tool connection lets it reach official documentation live, so its answers track the source of truth instead of a snapshot. An orchestration layer, the agent itself, ties the instructions, the tools and the knowledge together and decides what to do with a given question. A small web front end sits on top so people can actually use it, on a real domain.</p><p>The order matters more than the pieces. Retrieve, then reason, then answer, then cite. Get that sequence right and a lot of the bad behaviour simply has fewer places to hide.</p><p><strong>The infrastructure, at a glance</strong></p><p>I kept it deliberately lean and cloud hosted. There is a managed service running the model and the agent, a retrieval and knowledge layer feeding it grounded material, a lightweight web application, and a domain with an edge in front of it. Nothing exotic.</p><p>One habit from the day job carried straight over. Once something was no longer earning its keep, I removed it. At one point I realised part of the grounding setup was costing me money for capability the design no longer needed, so I decommissioned it cleanly and the assistant carried on without missing a beat. Knowing what to take out is as much a part of architecture as knowing what to put in.</p><p><strong>Securing it, which is really the point</strong></p><p>I approached the assistant the way I would approach any system that will be probed by strangers. Assume hostile input, assume someone will try to make it misbehave, and design so that no single failure is catastrophic. Defence in depth, in other words, applied to a slightly unusual system.</p><p>A few of the layers, described in principle rather than in detail:</p><p>Scope, as least privilege for topics. It answers what it is meant to and declines the rest. A narrow, well defined remit is a security control, not just a product decision, because it removes a huge amount of surface area.</p><p>Grounding as a safety mechanism. Because it will not assert without a source, an entire class of confident nonsense is closed off by design rather than patched after the fact.</p><p>Resistance to prompt injection and jailbreaks. All incoming text, and all retrieved text, is treated as untrusted data rather than as instructions. Attempts to smuggle in new orders, to trigger a persona change, or to talk it into ignoring its rules are recognised and refused, quietly and consistently.</p><p>Confidentiality of its own workings. It will not recite its instructions or describe its internals, no matter how the question is framed. Reconnaissance is the first step of most attacks, so I gave it nothing to hand over.</p><p>Output discipline. It answers in plain, readable language and will not be coaxed into odd encodings that could be used to sneak content past a filter.</p><p>Content safety at the platform edge, paired with a single, uniform refusal. Whichever layer catches a bad request, the person on the other end gets the same calm, consistent response. The experience should never leak which defence just fired.</p><p>Citation integrity. It cites only real, verbatim source links. It does not tidy up, shorten or reconstruct a link from memory, because a link that looks right but leads nowhere is its own small breach of trust.</p><p>Evaluation and regression testing. I keep a fixed set of questions, including deliberately adversarial ones, and re-run the lot after every change. If a future tweak quietly weakens a guardrail, that battery is meant to catch it before anyone else does.</p><p>None of these is clever on its own. Together they mean that getting the assistant to do something it should not requires defeating several independent controls at once, which is exactly the position you want an attacker to be in.</p><p><strong>Choosing a model, and knowing when to change it</strong></p><p>I started on a small, inexpensive model and it mostly worked. What it did not do reliably was hold a nuanced boundary. It would occasionally refuse a perfectly valid question, then, on another run, let through something it should have declined. That inconsistency is not just annoying, it is a reliability and security problem, because a guardrail that only works most of the time is not really a guardrail.</p><p>Moving to a stronger model fixed the wobble. It followed the same instructions far more consistently, in both directions. The lesson I took from it is that model choice is an engineering and security decision, not only a quality one.</p><p>If you take one thing from this, take the mindset rather than the settings. Ground everything. Assume the input is hostile. Test relentlessly. The specifics will follow from those three.</p><p><strong>Where it is now</strong></p><p>It is live, and it holds up. It answers within its remit, grounded and cited, and it stays composed when people try to break it. It is a personal proof of concept, not a product, and that is exactly what I wanted. It let me learn the whole stack, from the model down to the last guardrail, and it gave my security instincts somewhere new to be useful.</p><p>Much of what I know came from people who shared their thinking openly, and asked for nothing in return. This is a small attempt to do the same, minus the parts that are better learnt by doing.</p><p>A longer, more detailed write up may follow. For now, if you are building in this space, I hope the shape of it is useful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1c4fb1b2058" width="1" height="1" alt=""><hr><p><a href="https://medium.com/seenu-on-agentic-ai/building-a-grounded-secure-ai-assistant-the-why-and-the-honest-how-a1c4fb1b2058">Building a grounded, secure AI assistant: the why, and the honest how</a> was originally published in <a href="https://medium.com/seenu-on-agentic-ai">Seenu on Agentic AI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Writing Your First Analytics Rules in Microsoft Sentinel]]></title>
            <link>https://medium.com/architecting-and-engineering-microsoft-sentinel/writing-your-first-analytics-rules-in-microsoft-sentinel-6d10a5be73e6?source=rss-909b5003c61a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d10a5be73e6</guid>
            <category><![CDATA[microsoft-sentinel]]></category>
            <category><![CDATA[kql]]></category>
            <category><![CDATA[information-security]]></category>
            <dc:creator><![CDATA[Seenu Bhupala]]></dc:creator>
            <pubDate>Sun, 07 Sep 2025 07:23:32 GMT</pubDate>
            <atom:updated>2025-09-07T07:55:38.365Z</atom:updated>
            <content:encoded><![CDATA[<p>In this blog, we’ll look at the next steps after you’ve started ingesting logs into Microsoft Sentinel.</p><p>Following the example from my <a href="https://medium.com/architecting-and-engineering-microsoft-sentinel/building-the-right-foundation-choosing-data-connectors-in-microsoft-sentinel-1fdddb1427df">previous blog</a>, let’s continue with <em>sign-in</em> and <em>audit logs</em> ingested using the ‘Microsoft Entra ID’ data connector.</p><p>So, you now have logs flowing into Sentinel — what’s next?</p><p><strong>Why Analytics Rules Matter<br></strong>To detect suspicious events in the ingested logs, Microsoft Sentinel provides threat detection rules. These rules help identify potential security threats in your environment.</p><p>There are different types of rules, which you can read more about in <a href="https://learn.microsoft.com/en-us/azure/sentinel/threat-detection">Microsoft’s documentation</a>, but here we’ll focus on custom analytics rules.</p><p>These rules are written in KQL (Kusto Query Language), which is simple to learn and powerful to use. They run against your ingested logs, helping detect suspicious behaviour. Alerts generated from these rules are triaged by your SOC team, who decide whether to investigate further.</p><p><strong>Example Use Case<br></strong>Imagine your organization has a sensitive application, where access is controlled via an Entra security group called <em>SensitiveApp</em>.</p><p>Your SOC team wants to be alerted whenever a new member is added to this group. This alert should show:</p><ul><li>Who was added</li><li>Who added them</li><li>When the change happened</li></ul><p>Why is this useful?</p><ul><li>If legitimate, the alert can be closed as a false positive</li><li>If suspicious, the SOC can escalate to ensure the user is removed from the group and, relevant teams/managers are notified of this event</li></ul><p>This helps maintain strong security posture for <em>SensitiveApp</em>, ensuring only authorized users gain access.</p><p><strong>Getting Started with KQL<br></strong>Step 1: Confirm log ingestion</p><p>First, check that your logs are flowing into the Log Analytics Workspace (LAW).</p><p>In Sentinel, navigate to your data connector configuration to confirm the logs are reaching the correct table (for Entra ID audit logs, this is usually AuditLogs table):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/442/1*XUMqrkzacqmvLBHMkYKwDQ.png" /><figcaption>Microsoft Entra ID data connector &gt; AuditLogs table</figcaption></figure><p>Step 2: Open the Logs blade — In the Sentinel portal:</p><ol><li>Go to General &gt; Logs.</li><li>In the query editor, start typing the table name (e.g., AuditLogs). [IntelliSense can also help you to auto complete the name]</li></ol><p>Set the time range to something small (like the last 60 minutes) when testing, to make queries easier to run:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/297/1*D9P1BZzYZrPjesCZRvNVFg.png" /><figcaption>AuditLogs table &amp; Time range scoping</figcaption></figure><p>Step 3: Find the right operation</p><p>Next, you’ll want to filter on the correct OperationName. In this example, we’re looking for “Add member to group”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/211/1*r4cN841ZE9DdAN3Isvj73w.png" /><figcaption>OperationName column</figcaption></figure><p>You can right-click on the OperationName and select Filter for “Add member to group” and Sentinel will add this filter to your KQL query, as below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/342/1*s567iB4Y-6675M_JYAIQig.png" /><figcaption>Filtering / narrowing down our query</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/421/1*8a6ysyADfIa2HkwE2Cl6LA.png" /><figcaption>Filtering KQL for OperationName</figcaption></figure><p>Step 4: Explore the data</p><p>Click into a record and expand the JSON fields until you find the data you care about. For group additions, useful fields include:</p><ul><li>OperationName — the action taken</li><li>InitiatedBy — who performed the action</li><li>TargetResources — which object (group, user) was modified</li></ul><p>As mentioned earlier, you can always right-click a field in the Logs blade and choose <strong>Extend</strong> to have Sentinel insert the correct KQL syntax automatically:</p><p>Step 5: Build your first query</p><p>For this scenario, you might extend fields like <strong>OperationName</strong>, <strong>InitiatedBy</strong>, and <strong>TargetResources</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/229/1*aBYQLeK6c4V7oGjztsmapg.png" /><figcaption>Log results fields</figcaption></figure><p>A simple output could look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*35dTcPdZnUQ-YgF3B2LqZQ.png" /><figcaption>Initial KQL query — using extend operator from JSON fields</figcaption></figure><p>In my query I have renamed the fields below for clarity:</p><ul><li>userPrincipalName_ (from InitiatedBy) → InitiatedBy</li><li>newValue_ (from TargetResources) → GroupName</li><li>userPrincipalName_ (from TargetResources) → MemberAdded</li></ul><p>Below is the full KQL query — first in its original form(again!), then after renaming the fields. In the final version, I also used the <strong>project</strong> operator to display only the relevant columns:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*TDEbSb9we8qG_CoB_VKJzQ.png" /><figcaption>Original query</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mOqDW6ZwoCgAbeC4gGGBuA.png" /><figcaption>Refined final KQL query</figcaption></figure><p>Here is the full KQL query:</p><p>AuditLogs<br>| where OperationName == “Add member to group”<br>| extend InitiatedBy = tostring(parse_json(tostring(InitiatedBy.user)).userPrincipalName)<br>| extend GroupName = tostring(parse_json(tostring(parse_json(tostring(TargetResources[0].modifiedProperties))[1].newValue)))<br>| extend AddedUser = tostring(TargetResources[0].userPrincipalName)<br>| project TimeGenerated, InitiatedBy, GroupName, AddedUser</p><p>Using <strong>project</strong><em>:</em><br>To refine your query and display only the results you care about, you can use the <strong>project</strong> operator. For example:<br>| project Field1, Field2, Field3</p><p>This makes your output cleaner and easier to interpret, especially when reviewing results during investigations or when an alert is raised:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y9dJFGSCI92bWZj4pjVeBQ.png" /><figcaption>Final KQL query output</figcaption></figure><p><strong>That’s it — </strong>you’ve just written your first KQL query in Microsoft Sentinel! This simple example can serve as the foundation for building analytics rules that detect real threats in your environment</p><p><strong>Learning More KQL<br></strong>If you’re just starting out, the fastest way to learn is to:</p><ol><li>Use the Logs blade to explore data.</li><li>Extend fields you need.</li><li>Iterate your queries until you see meaningful results.</li></ol><p>Over time, you’ll build more complex detections, but the key is getting comfortable with the data first.</p><p>For structured learning, I recommend Microsoft’s official KQL resources: <a href="https://learn.microsoft.com/en-us/kusto/query/kql-learning-resources?view=microsoft-fabric">https://learn.microsoft.com/en-us/kusto/query/kql-learning-resources?view=microsoft-fabric</a></p><p>In my next blog, I’ll walk you through how to take this KQL query and turn it into an <strong>analytics rule</strong> in Microsoft Sentinel — so you can start detecting real alerts in your environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d10a5be73e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/architecting-and-engineering-microsoft-sentinel/writing-your-first-analytics-rules-in-microsoft-sentinel-6d10a5be73e6">Writing Your First Analytics Rules in Microsoft Sentinel</a> was originally published in <a href="https://medium.com/architecting-and-engineering-microsoft-sentinel">Architecting Microsoft Sentinel</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building the right foundation: Choosing data connectors in Microsoft Sentinel]]></title>
            <link>https://medium.com/architecting-and-engineering-microsoft-sentinel/building-the-right-foundation-choosing-data-connectors-in-microsoft-sentinel-1fdddb1427df?source=rss-909b5003c61a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fdddb1427df</guid>
            <category><![CDATA[data-ingestion]]></category>
            <category><![CDATA[microsoft-sentinel]]></category>
            <category><![CDATA[siem]]></category>
            <dc:creator><![CDATA[Seenu Bhupala]]></dc:creator>
            <pubDate>Sat, 28 Jun 2025 12:55:49 GMT</pubDate>
            <atom:updated>2025-06-28T13:14:08.109Z</atom:updated>
            <content:encoded><![CDATA[<p>Now that your Microsoft Sentinel environment is up and running and users have been assigned the correct permissions, the next step is ingesting logs.</p><p>Once these logs are flowing into Sentinel, you can start creating KQL-based analytics rules to detect suspicious activity. You’ll also begin receiving alerts directly from integrated security platforms like Microsoft Defender XDR, Purview, and others, enabling your SOC to respond from a single console.</p><p>Think of Sentinel as your central “eyes on glass” platform, providing a unified view across your organization. For example, relying solely on Defender XDR for alert triage might seem sufficient at first — but it can quickly lead to alert fatigue. Getting security alerts via email may sound convenient, but in practice, it often results in flooded inboxes, missed high-fidelity alerts, and inefficient investigations.</p><p>How do you separate false positives from real threats? How do you tune noisy alerts across multiple tools? And if you want to ingest logs from non-Microsoft platforms like a Fortinet FortiGate firewall, how would you go about doing that?</p><p>This is where centralizing your logs in Sentinel truly shines: it enables event correlation across systems. For example, when an alert is triggered, you can instantly correlate it with the user’s sign-ins across Entra ID, recent process activity from Defender for Endpoint, or even network traffic from your firewall. Having all relevant telemetry in one place drastically improves your ability to investigate quickly and respond confidently.</p><p><strong>How to start ingesting logs, and which ones to choose first<br></strong>To begin ingesting logs in Microsoft Sentinel, navigate to the Content hub, located under the Content Management section in the left-hand menu.</p><p>The Content hub serves as a centralized location for discovering, deploying, and enabling out-of-the-box solutions within Sentinel. These solutions include data connectors, workbooks, analytics rules, automation playbooks, and API integrations — grouped by use case, domain, or industry vertical. Think of it as your one-stop shop for enabling visibility across Microsoft and third-party security platforms.</p><p><strong>Start with core data connectors (for Microsoft environments)<br></strong>If your organization is running the Microsoft Defender XDR suite (formerly Defender for Endpoint, Office 365, Identity, and Cloud Apps), and your infrastructure is primarily in Azure, then these four data connectors are essential:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*nVR4rAVb7CZwcDYzp1k3uA.png" /><figcaption>Microsoft Sentinel — Core data connectors</figcaption></figure><p><strong>Remember:</strong> Most of the logs ingested into Sentinel costs money. Be deliberate about what you enable. It’s completely fine to start small — ingest only what you need for initial visibility and expand gradually based on your detection needs. Prioritize the log sources that provide the most high-value security telemetry.</p><p><strong>One tip I recommend is this:</strong> if you’re using Microsoft Defender XDR and have Microsoft Defender for Endpoint (MDE) deployed on your endpoints, you’re already sitting on a goldmine of telemetry.</p><p>MDE doesn’t just raise alerts when suspicious activity is detected — it also collects a rich stream of raw telemetry, including device events, file operations, image loads, process creation, and more. This data is accessible via advanced hunting in Defender XDR, and many of these tables can also be ingested into Sentinel.</p><p><strong>Why does this matter?</strong> Reviewing these tables will help you identify high-value security use cases — such as custom threat hunting, correlating alerts with endpoint behaviour, or creating tailored analytics rules in Sentinel. Based on your objectives, you can choose to selectively ingest only the data that adds meaningful value to your detection and response capabilities.</p><p><strong>Connecting Microsoft Entra ID to ingest Sign-in and Audit Logs<br></strong>Before you begin, check that you have the right permissions — each data connector lists the required roles on its setup page.</p><p>For example, here are the permissions required by the Microsoft Entra ID data connector:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*PAceZlEPSdpUiHd4praOCA.png" /><figcaption>Microsoft Entra ID — Data Connector prerequisites</figcaption></figure><p><strong>Steps:</strong></p><ul><li>Go to <strong>Microsoft Sentinel</strong> in the Azure portal and select your workspace</li><li>From the left menu click <strong>Content hub</strong> under <strong>Content Management</strong></li><li>Search for <strong>Microsoft Entra ID</strong> and install the solution if it isn’t already installed</li><li>From the left menu under <em>Configuration </em>click <strong>Data connectors</strong>, search for <strong>Microsoft Entra ID</strong>, and click <em>Open connector page</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fRoEn69OVvewbuHY2fGs3g.png" /><figcaption>Microsoft Entra ID - Data connector</figcaption></figure><ul><li>Tick the boxes to enable:</li></ul><p><strong>Sign-in logs</strong> (SignInLogs)</p><p><strong>Audit logs</strong> (AuditLogs)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*0mpDUjIwE9lg4xPtWC68Eg.png" /><figcaption>Configuring sign-in and audit logs</figcaption></figure><ul><li>Click <strong>Apply Changes</strong> to complete the setup</li></ul><p>Once you’ve connected all the core data connectors and logs are flowing into Microsoft Sentinel, the next step is to turn that data into action. In the next blog, I’ll walk you through how to write KQL queries and create custom analytics rules to detect threats and generate alerts based on your ingested data.</p><p>In future posts, I’ll also cover more advanced topics — such as ingesting logs from network appliances like Fortinet FortiGate firewalls, as well as custom logs from endpoints like Sysmon, tailored to your organization’s specific business and security needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fdddb1427df" width="1" height="1" alt=""><hr><p><a href="https://medium.com/architecting-and-engineering-microsoft-sentinel/building-the-right-foundation-choosing-data-connectors-in-microsoft-sentinel-1fdddb1427df">Building the right foundation: Choosing data connectors in Microsoft Sentinel</a> was originally published in <a href="https://medium.com/architecting-and-engineering-microsoft-sentinel">Architecting Microsoft Sentinel</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Structuring Microsoft Sentinel for Cost and Compliance]]></title>
            <link>https://medium.com/architecting-and-engineering-microsoft-sentinel/start-smart-structuring-microsoft-sentinel-for-cost-compliance-and-scale-f11e42e8238d?source=rss-909b5003c61a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f11e42e8238d</guid>
            <category><![CDATA[microsoft-sentinel]]></category>
            <category><![CDATA[azure-security]]></category>
            <category><![CDATA[security-operation-center]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cloud-security]]></category>
            <dc:creator><![CDATA[Seenu Bhupala]]></dc:creator>
            <pubDate>Wed, 30 Apr 2025 11:31:01 GMT</pubDate>
            <atom:updated>2025-06-29T11:46:44.853Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*02lqfagFNpv7kOrh" /><figcaption>Photo by <a href="https://unsplash.com/@alterego_swiss?utm_source=medium&amp;utm_medium=referral">AbsolutVision</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Deploying Microsoft Sentinel is about building a scalable, cost-effective, and compliant security operations platform from day one.</p><p>While Microsoft provides extensive documentation for each step, this post distills the key considerations you should focus on early in the process. I strongly recommend reviewing the official documents for full prerequisites, architectural guidance, and supported configurations.</p><p><strong>Define the purpose and scope of your Sentinel deployment<br></strong>Before enabling anything, be clear about what Microsoft Sentinel is expected to achieve. Purpose drives design decisions — from data connector selection to RBAC, workspace region, and retention strategy.</p><p><strong>Common scope examples</strong>:<br>Internal Visibility: Monitor Microsoft 365, Entra ID, Azure PaaS/IaaS resources, and internal workloads.</p><p>Hybrid Monitoring: Extend visibility to on-premises infrastructure and multi-cloud environments.</p><p>Multi-Tenant Management: Centralize monitoring across customer environments or business units using Azure Lighthouse.</p><p>SOC Enablement: Full security operations use including detection engineering, incident triage, threat hunting, and automated response via playbooks.</p><p><strong>Clarifying questions to guide scope</strong>:<br>Will you monitor only Azure-native workloads, or also hybrid/on-premises and multi-cloud assets?</p><p>Will Sentinel serve as your primary incident response platform, or integrate with third-party SOAR or ITSM tools?</p><p>Are there compliance requirements (e.g., ISO 27001, Essential Eight, IRAP) that impact log retention or monitoring?</p><p>Will this environment need to scale across tenants, regions, or business units?</p><p><strong>Start with a dedicated Resource Group and Log Analytics Workspace<br></strong>Before attaching Microsoft Sentinel, create a dedicated resource group for all related components. This provides logical separation from infrastructure and application resources, supporting cleaner role-based access and lifecycle management.</p><p>Next, create a Log Analytics Workspace (LAW) within that resource group. The workspace’s region selection is permanent and determines where your logs are physically stored — a decision with operational impact.</p><p><strong>Why region selection matters</strong>:<br>Compliance: Data residency requirements (e.g., IRAP in Australia, GDPR in the EU) may mandate that security logs remain within specific geographies.</p><p>Cost: While ingestion pricing is generally fixed, data retention costs and availability of commitment tiers can vary slightly by region, especially for large-scale environments.</p><p><strong>Choose the right Azure region:<br></strong>Once the Log Analytics Workspace (LAW) is created, its region cannot be changed — making region selection a critical up-front decision during Microsoft Sentinel deployment.</p><p><strong>Best practices</strong>:<br>Align the workspace region with your Entra ID tenant and most of your Azure workloads to minimize latency and simplify integration.</p><p>Ensure compliance with regional data protection regulations (e.g., GDPR, IRAP).</p><p>Validate pricing using the Azure Pricing Calculator, particularly for data retention and commitment tiers.</p><p>Also consider latency and automation efficiency — workflows like playbooks and API calls often perform better when deployed in the same region as the workspace and connected services.</p><p><strong>Permissions Required to Enable and Use Microsoft Sentinel<br></strong>Role-Based Access Control (RBAC) is critical to ensuring secure, delegated, and least-privilege access to Microsoft Sentinel.</p><p><strong>To enable Microsoft Sentinel</strong>: You need Contributor permission on the subscription where the Log Analytics Workspace (LAW) resides. This is required to deploy Microsoft Sentinel to a workspace.</p><p><strong>To use Microsoft Sentinel features</strong>: Assign either the Microsoft Sentinel Contributor or Microsoft Sentinel Reader role at the resource group level that contains the workspace. These roles control access to analytics rules, incidents, workbooks, playbooks, and hunting queries.</p><p><strong>To install and manage solutions from the Content Hub</strong>: The Microsoft Sentinel Contributor role is required on the resource group that contains the workspace.</p><p>For best results, assign these roles at the resource group level that contains the Microsoft Sentinel workspace. This ensures access is consistently applied across all Sentinel-related resources — including analytics rules, playbooks, workbooks, and data connectors — which should also reside in the same resource group for clean management and security boundaries.</p><p><strong>After understanding how Microsoft Sentinel roles work, you can apply the following best practices when assigning roles to users</strong><br> <br><strong>Security Analysts</strong> → Assign the Microsoft Sentinel Responder role at the resource group level.</p><p>This allows users to view data, incidents, workbooks, and other Sentinel resources. They can also manage incidents, such as assigning, tagging, or dismissing them.<br> <br><strong>Security Engineers</strong> → Assign the Microsoft Sentinel Contributor role at the resource group level.</p><p>This includes all Responder permissions, and additionally allows users to create and edit analytics rules, workbooks, hunting queries, and other Sentinel resources. They can also install and manage solutions from the Content Hub.</p><p><strong>Avoid assigning roles directly to individual users</strong>. Instead, create Entra ID groups that reflect operational responsibilities, and assign those groups to the appropriate roles at the resource group level. Then, add users to these groups based on their role in the security team. This approach simplifies access management, supports least privilege, and integrates cleanly with Privileged Identity Management (PIM) if used.</p><p><strong>Note: </strong>Some data connectors require additional permissions beyond Microsoft Sentinel roles. Always review the specific permissions listed on each connector’s documentation page to ensure successful onboarding.</p><p><strong>Final Thoughts: Think Strategically, Deploy Intentionally</strong></p><ul><li>When setting up Microsoft Sentinel, don’t just “turn it on.”</li><li>Start with: A dedicated resource group and workspace</li><li>Group-based RBAC aligned to operational responsibilities</li><li>High-value connector onboarding based on your detection priorities</li><li>Region planning for compliance, performance, and long-term cost control</li></ul><p>These foundational decisions ensure that Microsoft Sentinel is not only secure — but also scalable, well-governed, and operationally effective from day one.</p><p>In the next blog, I’ll walk through how to choose, prioritize, and configure Microsoft Sentinel data connectors — including how to avoid unnecessary ingestion costs, ensure proper permissions, and align each connector to your detection objectives.</p><p><strong>Useful Microsoft Resources</strong>:</p><p><a href="https://azure.microsoft.com/en-us/pricing/calculator/">https://azure.microsoft.com/en-us/pricing/calculator/</a></p><p><a href="https://learn.microsoft.com/en-us/azure/sentinel/deploy-overview">https://learn.microsoft.com/en-us/azure/sentinel/deploy-overview</a></p><p><a href="https://learn.microsoft.com/en-us/azure/sentinel/roles">https://learn.microsoft.com/en-us/azure/sentinel/roles</a></p><p><a href="https://learn.microsoft.com/en-us/azure/reliability/regions-list">https://learn.microsoft.com/en-us/azure/reliability/regions-list</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f11e42e8238d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/architecting-and-engineering-microsoft-sentinel/start-smart-structuring-microsoft-sentinel-for-cost-compliance-and-scale-f11e42e8238d">Structuring Microsoft Sentinel for Cost and Compliance</a> was originally published in <a href="https://medium.com/architecting-and-engineering-microsoft-sentinel">Architecting Microsoft Sentinel</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Think before you deploy: Microsoft Sentinel planning that works]]></title>
            <link>https://medium.com/architecting-and-engineering-microsoft-sentinel/think-before-you-deploy-microsoft-sentinel-planning-that-works-dc988756cac7?source=rss-909b5003c61a------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc988756cac7</guid>
            <category><![CDATA[siem]]></category>
            <category><![CDATA[microsoft-sentinel]]></category>
            <dc:creator><![CDATA[Seenu Bhupala]]></dc:creator>
            <pubDate>Sat, 29 Mar 2025 08:17:59 GMT</pubDate>
            <atom:updated>2025-03-29T08:17:59.510Z</atom:updated>
            <content:encoded><![CDATA[<p>Whether I’m deploying Microsoft Sentinel in a personal lab for hands-on learning or rolling it out in a real-world production environment, I always follow the same structured approach.</p><p>Over time, I’ve developed a checklist that ensures every Sentinel deployment I work on is thoughtfully planned, cost-aware, and operationally sound from day one.</p><p>This blog isn’t about clicking through the portal — it’s about thinking like an architect. Strategic planning ensures that Sentinel doesn’t just ingest data, but becomes a scalable, automated, and efficient security platform tailored to the environment it supports.</p><p><strong>Why planning ahead makes a difference</strong></p><p>Microsoft Sentinel is powerful, but it’s easy to lose sight of the bigger picture when the focus is just on getting it up and running.</p><p>Taking time to plan helps with:</p><ul><li>Avoiding unnecessary log ingestion and unexpected cost</li><li>Ensuring the right roles and permissions are in place</li><li>Reducing alert noise through focused, high-value detections</li><li>Designing for automation and efficient incident response</li><li>Supporting multi-tenant or hybrid scenarios with less friction</li></ul><p><strong>What this blog is (and isn’t)</strong></p><p>This isn’t a deep technical walk-through, and it’s not a “getting started” guide. It’s about the thinking that comes before any deployment begins.</p><p>The goal is simple: to ensure you’re ready to deploy Microsoft Sentinel with purpose — not guesswork.</p><p><strong>Microsoft Sentinel checklist</strong></p><p>Here’s the checklist I rely on across all Sentinel deployments — whether I’m delivering a production rollout, preparing for a certification, or testing features in a lab environment. These are the core areas I make sure are covered right from the start.</p><p><strong>Define the purpose and scope</strong>:<br>Clarify what the Sentinel deployment is intended to support — such as internal visibility, hybrid monitoring, multi-tenant operations, or full SOC enablement.</p><p><strong>Plan for ingestion costs early</strong>:<br>Estimate expected data volume, retention requirements, and connector usage up front to align with budget and avoid unexpected Log Analytics charges.</p><p><strong>Assign the right permissions</strong>:<br>Ensure the appropriate roles are assigned at both the tenant and subscription levels to enable Sentinel setup and management. Use built-in roles or Privileged Identity Management (PIM) to enforce least privilege and scoped administrative access.</p><p><strong>Set up the resource group and Log Analytics workspace</strong>:<br>Design the resource group and Log Analytics workspace based on the environment type, data residency requirements, and operational lifecycle planning.</p><p><strong>Deploy Microsoft Sentinel manually</strong>:<br>Attach Microsoft Sentinel to the Log Analytics workspace intentionally. Avoiding automation at this stage helps validate each configuration step and ensures the environment is structured cleanly from the start.</p><p><strong>Apply RBAC for Sentinel operations</strong>:<br>Define role-based access using built-in Sentinel roles such as Microsoft Sentinel Contributor, Reader, and Logic App Contributor, and align them with each team member’s operational responsibilities.</p><p><strong>Configure data connectors strategically</strong>:<br>Start with high-value native sources such as Microsoft Entra ID (formerly Azure AD), Microsoft Defender XDR (which includes logs from Defender for Endpoint, Identity, Office 365, and more), and Azure Activity. Prioritize connectors based on log fidelity, coverage, and relevance to your detection use cases.</p><p><strong>Consider hybrid ingestion using Azure Arc (optional)</strong>:<br>Use Azure Arc to onboard non-Azure servers and enable them for monitoring in Microsoft Sentinel via the Azure Monitor Agent (AMA) and Data Collection Rules (DCR).</p><p><strong>Plan your analytics rule approach</strong>:<br>Decide where built-in rule templates are suitable, where custom KQL-based rules are required, and how to align detections to the MITRE ATT&amp;CK framework for consistent threat coverage.</p><p><strong>Define automation use cases up front</strong>:<br>Identify which alerts require triage, enrichment, or auto-response, and design supporting logic using automation rules to trigger playbooks or apply tagging.</p><p><strong>Build playbooks for response and enrichment</strong>:<br>Start with foundational playbooks such as email notifications, user or IP enrichment, and incident tagging, then expand into more advanced response actions as needed.</p><p><strong>Create watchlists for use in detections</strong>:<br>Define and upload contextual lists — such as VIP users, critical assets, or known bad hosts — that can be referenced in analytics rules, hunting queries, and investigations.</p><p><strong>Implement GitHub CI/CD for rule management</strong>:<br>Establish a version-controlled deployment process using GitHub to manage analytics rules, workbooks, playbooks, and KQL queries as code via ARM or Bicep templates.</p><p><strong>Plan for multi-tenant management via Azure Lighthouse</strong>:<br>If you manage Microsoft Sentinel across multiple tenants, use Azure Lighthouse to onboard them for delegated access, unified visibility, and centralized operations.</p><p><strong>Tune retention and monitor ingestion over time</strong>:<br>Adjust Log Analytics workspace retention settings, monitor data ingestion patterns regularly, and onboard additional connectors as your detection needs evolve.</p><p><strong>What’s Next<br></strong>In upcoming posts, I’ll dive deeper into each of these checklist areas — sharing how I approach permissions, connector planning, automation, GitHub integration, and more.</p><p>Whether you’re preparing for a Microsoft Sentinel deployment or looking to get more out of an existing setup, this series will walk through each step with practical examples and real-world context.</p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc988756cac7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/architecting-and-engineering-microsoft-sentinel/think-before-you-deploy-microsoft-sentinel-planning-that-works-dc988756cac7">Think before you deploy: Microsoft Sentinel planning that works</a> was originally published in <a href="https://medium.com/architecting-and-engineering-microsoft-sentinel">Architecting Microsoft Sentinel</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Phishing Incident Analysis: A Cyber Threat Intelligence Report with Proactive Detection Strategies]]></title>
            <link>https://medium.com/cyber-threat-intelligence-cti/phishing-incident-analysis-a-cyber-threat-intelligence-report-with-proactive-detection-strategies-d32f00e07b3c?source=rss-909b5003c61a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d32f00e07b3c</guid>
            <category><![CDATA[cyber-defense]]></category>
            <category><![CDATA[soc]]></category>
            <category><![CDATA[cyber-threat-intelligence]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[phishing]]></category>
            <dc:creator><![CDATA[Seenu Bhupala]]></dc:creator>
            <pubDate>Sun, 16 Feb 2025 05:49:59 GMT</pubDate>
            <atom:updated>2025-05-02T11:46:33.229Z</atom:updated>
            <content:encoded><![CDATA[<p>The following CTI report format was inspired by Adam Goss in his blog, <a href="https://adamgoss.medium.com/cyber-threat-intelligence-report-template-free-download-1cb0839c3938"><em>Cyber Threat Intelligence Report Template (+FREE Download)</em></a>. The content, analysis, and customization presented below are entirely my own work.</p><p>This sample CTI report is based on the phishing incident discussed in my <a href="https://medium.com/cyber-threat-intelligence-cti/phishing-analysis-how-to-map-ttps-with-mitre-att-ck-158e5627c2fd">previous blog</a>. It is designed to provide actionable insights for both executives and SOC teams.</p><p><strong>Table of Contents</strong></p><ol><li>Executive Summary</li><li>Key Takeaways</li><li>Intelligence Assessment</li><li>MITRE ATT&amp;CK® Techniques</li><li>Detection Opportunities<strong> </strong>for SOC Teams (with KQL Query)</li><li>Indicators of Compromise (IOCs)</li><li>Recommendations</li><li>Feedback Contacts</li></ol><p><strong>1. Executive Summary</strong></p><p>This report analyzes a recent phishing incident where a spear-phishing email targeted employees using a compromised legitimate domain and an obfuscated URL. The goal of the attack was to harvest user credentials by redirecting victims to a fake banking login page.</p><p><strong>Key Findings:</strong></p><ul><li>The phishing email bypassed standard email security defenses by leveraging a legitimate, compromised domain and obfuscated URL techniques.</li><li>If successful, this phishing attempt could have resulted in credential compromise and unauthorized access to sensitive systems or data.</li><li>Such attacks pose a significant financial and reputational risk to organizations, particularly if sensitive data is exfiltrated or critical systems are compromised</li></ul><p><strong>Impact:</strong></p><p>Credential theft from this phishing attack could enable adversaries to:</p><ul><li>Move laterally within the organization.</li><li>Access sensitive financial systems or other critical assets.</li><li>Launch subsequent attacks, such as ransomware deployment or data exfiltration.</li></ul><p><strong>Actionable Takeaway for Executives:</strong></p><p>To mitigate such threats, executives should prioritize:</p><ul><li>Investing in advanced email security solutions with URL inspection capabilities.</li><li>Enforcing multi-factor authentication (MFA) across all sensitive systems.</li><li>Supporting regular phishing awareness training programs to educate employees on identifying and avoiding phishing attempts.</li></ul><p><strong>2. Key Takeaways</strong></p><ul><li>The phishing email leveraged a legitimate but compromised domain to bypass security defenses.</li><li>The malicious URL employed obfuscation techniques, including Base64 encoding and an @ symbol, to make the link appear legitimate and evade detection.</li><li>Mapping the attack to the MITRE ATT&amp;CK framework identified key TTPs used by the adversary, providing a foundation for actionable mitigations.</li><li>A custom detection query has been developed to enable SOC teams to proactively identify similar phishing attempts in the future</li></ul><p><strong>3. Intelligence Assessment</strong></p><p>The phishing attack demonstrates a moderate level of sophistication, leveraging:</p><ul><li>A legitimate, compromised domain to evade basic email filtering.</li><li>Obfuscation of the URL to mask the malicious intent and destination.</li><li>A realistic fake banking login page designed to harvest credentials from unsuspecting users.</li></ul><p><strong>Adversary Goals:</strong></p><ul><li>Harvest valid user credentials to gain unauthorized access.</li><li>Target potentially high-value accounts for financial fraud or lateral movement.</li></ul><p><strong>Likelihood and Priority:</strong></p><p>Given the use of common obfuscation tactics and phishing techniques, similar attacks are likely to recur. This threat should be treated as a medium-high priority due to its potential to compromise credentials and enable secondary attacks, such as lateral movement or financial fraud.</p><p><strong>4. MITRE ATT&amp;CK Techniques</strong></p><p><strong>Tactic: Initial Access (TA0001)<br>Technique: Phishing<br>Sub-Technique: Spearphishing Link (T1566.002)</strong><br>Description: The adversary sent a spear-phishing email containing a malicious link to gain initial access.</p><p><strong>Tactic: Defense Evasion (TA0005)<br>Technique: Obfuscated Files or Information (T1027)</strong><br>Description: The URL used an @ symbol to include a legitimate domain name before the malicious link, which helped mask its true destination. Additionally, the URL contained a Base64-encoded string representing the recipient’s email address, further obfuscating the malicious intent, and making it harder for automated security tools to detect.</p><p><strong>Tactic: Credential Access (TA0006)<br>Technique: Input Capture (T1056)</strong><br>Description: The fake banking login page was designed to capture user credentials as they were entered.</p><p><strong>Tactic: Command and Control (TA0011)<br>Technique: Application Layer Protocol<br>Sub-Technique: Web Protocols (T1071.001)</strong><br>Description: The harvested credentials were transmitted over HTTPS, an application layer protocol, to the adversary’s server.</p><p><strong>5. Detection Opportunities for SOC Teams </strong>(with KQL Query)</p><p>To aid SOC teams, a custom detection query has been developed to proactively identify URLs with suspicious patterns, including obfuscation techniques.</p><p><strong>KQL Detection Query:</strong></p><p>EmailUrlInfo<br>| where Url matches regex “@[A-Za-z0–9.-]+/[A-Za-z0–9%+/=]*”<br>| project Timestamp, NetworkMessageId, Url, UrlDomain</p><p>(<strong>Please note:</strong> This is a foundational KQL query and one of many possible approaches. It can be further refined based on your environment’s specific configurations and filtering needs. Since this blog focuses on the CTI report, I have kept it minimal as a proof of concept)</p><p><strong>How It Works:</strong></p><ul><li>Detects URLs containing an @ symbol, followed by a domain-like structure and an obfuscated string (e.g., Base64-encoded email address).</li><li>Targets phishing attempts leveraging obfuscated URLs to evade detection.</li></ul><p><strong>SOC Actions:</strong></p><ul><li>Use this query in Microsoft Defender XDR - Advanced Hunting to identify phishing emails with obfuscated URLs.</li><li>Set up custom alerts for URLs that match this pattern to proactively detect similar phishing attempts.</li></ul><p>Integrate these detection results into email filtering solutions to block malicious links proactively.</p><p><strong>6. Indicators of Compromise (IOCs)</strong></p><p><strong>Observed IOCs:</strong></p><p><strong>Domains</strong>:</p><ul><li>example[.]com (intermediary domain)</li><li>destination[.]com (malicious final site)</li></ul><p><strong>URL Patterns</strong>:</p><ul><li>URLs with @ symbols preceding malicious domains.</li><li>Base64-encoded strings (e.g., dXNlckBleGFtcGxlLmNvbQ==) within URL paths.</li></ul><p><strong>7. Recommendations</strong></p><p><strong>For Executives:</strong></p><p><strong>Invest in Email Security</strong>:</p><ul><li>Deploy advanced solutions like Defender for Office 365 and ensure they are configured with enhanced URL filtering, Safe Links, and dynamic scanning capabilities.</li><li>Support your teams in identifying and addressing detection gaps by allocating resources for updating custom rules to counter emerging obfuscation techniques, such as Base64 encoding and @ symbols in URLs.</li><li>Supplement DFO365 with additional threat intelligence feeds to expand detection coverage and adapt to evolving tactics.</li></ul><p><strong>Support Multi-Factor Authentication (MFA)</strong>:</p><ul><li>Mandate MFA across all sensitive systems to minimize the risk of credential-based attacks. MFA ensures accounts remain protected even if credentials are compromised, significantly reducing the likelihood of unauthorized access.</li></ul><p><strong>Support User Awareness Training</strong>:</p><ul><li>Invest in phishing awareness programs across the organization. Provide resources and support for conducting regular phishing simulations and delivering tailored training to employees to reduce their susceptibility to phishing attacks. Executive sponsorship of these initiatives ensures organization-wide adoption and fosters a proactive security culture.</li></ul><p><strong>For SOC Teams:</strong></p><p><strong>Implement Detection Queries:</strong></p><ul><li>Use KQL queries — like the sample included in this post — alongside custom queries tailored to your environment in <strong>Microsoft Defender XDR — Advanced Hunting</strong> to proactively detect phishing emails containing <strong>obfuscated URLs</strong>.</li><li>Because the @ symbol can appear in URLs — both legitimately and maliciously — detection logic must be precisely scoped. Use multiple indicators, such as unexpected domain structures, encoded strings, and contextual signals, to improve accuracy and minimize false positives before turning queries into production rules.</li></ul><p><strong>Monitor Email Threats:</strong></p><ul><li>Regularly analyze email traffic for unusual patterns, including URLs that misuse the @ symbol or contain encoded user information.</li><li>Investigate flagged URLs to identify potential phishing attempts and recurring attack patterns.</li></ul><p><strong>Enhance Incident Response:</strong></p><ul><li>Configure automatic blocking of domains associated with similar phishing campaigns to reduce future risks.</li><li>Maintain up-to-date threat intelligence feeds to ensure real-time insights into emerging threats and continuously adapt detection rules.</li></ul><p><strong>8. Feedback Contacts (Hypothetical)</strong></p><p>For questions or feedback about this report, please contact:</p><p><strong>Cyber Threat Intelligence Team</strong><br>Email: <a href="/service/mailto:cti-team@example.com">cti-team@example.com</a><br>Phone: +1 (800) 123–4567</p><h3><strong>Conclusion</strong></h3><p>This CTI report, based on the <a href="https://medium.com/cyber-threat-intelligence-cti/phishing-analysis-how-to-map-ttps-with-mitre-att-ck-158e5627c2fd">phishing incident discussed earlier</a>, underscores the critical need for organizations to remain vigilant against advanced obfuscation techniques. Leveraging the MITRE ATT&amp;CK framework, along with tailored detection strategies, empowers organizations to strengthen their defenses and minimize the risk of credential theft.</p><p>The MITRE ATT&amp;CK framework provides a comprehensive foundation for understanding adversary behavior and guiding defensive strategies. However, SOC teams must use their experience to adapt detection efforts to the unique context and threats relevant to their organization. While not all adversary techniques are explicitly detailed within the framework, it remains a vital tool for structuring and enhancing detection capabilities. By combining the guidance of MITRE ATT&amp;CK with expert judgment and organizational relevance, SOC teams can proactively address evolving challenges.</p><p>This report delivers actionable insights for both executives and SOC teams, bridging the gap between strategic decision-making and operational security measures. Together, these efforts create a stronger and more proactive cybersecurity posture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d32f00e07b3c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cyber-threat-intelligence-cti/phishing-incident-analysis-a-cyber-threat-intelligence-report-with-proactive-detection-strategies-d32f00e07b3c">Phishing Incident Analysis: A Cyber Threat Intelligence Report with Proactive Detection Strategies</a> was originally published in <a href="https://medium.com/cyber-threat-intelligence-cti">Cyber Threat Intelligence (CTI)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Phishing Analysis: How to Map TTPs with MITRE ATT&CK®]]></title>
            <link>https://medium.com/cyber-threat-intelligence-cti/phishing-analysis-how-to-map-ttps-with-mitre-att-ck-158e5627c2fd?source=rss-909b5003c61a------2</link>
            <guid isPermaLink="false">https://medium.com/p/158e5627c2fd</guid>
            <category><![CDATA[mitre-attack]]></category>
            <category><![CDATA[phishing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[phishing-awareness]]></category>
            <category><![CDATA[cyber-threat-intelligence]]></category>
            <dc:creator><![CDATA[Seenu Bhupala]]></dc:creator>
            <pubDate>Sat, 08 Feb 2025 07:00:56 GMT</pubDate>
            <atom:updated>2025-03-13T07:20:14.102Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction</strong>:<br>In this blog I want to demonstrate how to map an analyzed phishing incident to the MITRE ATT&amp;CK framework. Let’s dive in!</p><p><strong>Phishing incident analysis</strong>:<br>A user received a spear-phishing email containing a malicious link. The email originated from a legitimate domain that had been compromised, allowing it to bypass standard email defenses.</p><p>The body of the email contained a link to a malicious site disguised as a banking login page. The URL was designed to appear legitimate and reduce suspicion, making it more likely for users to click.</p><p>The phishing link included an @ symbol, with a trusted banking domain name appearing before it to make the link look legitimate. After the @ symbol, the true malicious domain followed, along with a Base64-encoded string representing the recipient’s email address.</p><p>This carefully crafted link redirected users to a fake site closely resembling the legitimate one. The fake site aimed to deceive users into entering their credentials, which would have been captured by the attacker.</p><p>Both the intermediary and destination sites were specifically designed to trick users into entering their credentials. These sites have since been taken offline.</p><p><strong>Mapping to MITRE ATT&amp;CK</strong>:<br>Using the observations from the phishing incident, we can map the tactics and techniques employed by the adversary to the ATT&amp;CK framework. This process involves aligning observed adversary behaviors with the framework’s predefined tactics and techniques.</p><p>It is important to note that mapping intelligence to ATT&amp;CK can be approached in various ways, with no single ‘right’ or ‘wrong’ method. The goal of mapping is to better understand the adversary’s behavior and tailor it to your organization’s context, priorities, and objectives.</p><p>To keep this example simple and focused, I have selected a few key TTPs from the framework that are most relevant to the observed attack.</p><p><strong>Tactics and Techniques Identified:</strong></p><p><strong><em>Tactic: Initial Access (TA0001)<br>Technique: Phishing<br>Sub-Technique: Spearphishing Link (T1566.002)</em></strong><br>Description: The adversary sent a spear-phishing email containing a malicious link to gain initial access.</p><p><strong><em>Tactic: Defense Evasion (TA0005)<br>Technique: Obfuscated Files or Information (T1027)</em></strong><br>Description: The URL used an @ symbol to include a legitimate domain name before the malicious link, which helped mask its true destination. Additionally, the URL contained a Base64-encoded string representing the recipient’s email address, further obfuscating the malicious intent and making it harder for automated security tools to detect.</p><p><strong><em>Tactic: Credential Access (TA0006)<br>Technique: Input Capture (T1056)</em></strong><br>Description: The fake banking login page was designed to capture user credentials as they were entered.</p><p><strong><em>Tactic: Command and Control (TA0011)<br>Technique: Application Layer Protocol<br>Sub-Technique: Web Protocols (T1071.001)</em></strong><br>Description: The harvested credentials were transmitted over HTTPS, an application layer protocol, to the adversary’s server.</p><p>Here are the TTPs mapped in the <a href="https://mitre-attack.github.io/attack-navigator/">ATT&amp;CK Navigator</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n1klkloDZ9po6G7v-Pz8Qg.png" /><figcaption>Phishing incident mapped to ATT&amp;CK</figcaption></figure><p>In my <a href="https://medium.com/cyber-threat-intelligence-cti/phishing-incident-analysis-a-cyber-threat-intelligence-report-with-proactive-detection-strategies-d32f00e07b3c">next blog</a>, I will demonstrate how this analysis can be transformed into a Cyber Threat Intelligence (CTI) report tailored for both executives and SOC teams. The report will provide executives with actionable insights to support informed business decisions and guide SOC teams on enhancing detection engineering and strengthening defenses. I look forward to sharing these practical takeaways with you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=158e5627c2fd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cyber-threat-intelligence-cti/phishing-analysis-how-to-map-ttps-with-mitre-att-ck-158e5627c2fd">Phishing Analysis: How to Map TTPs with MITRE ATT&amp;CK®</a> was originally published in <a href="https://medium.com/cyber-threat-intelligence-cti">Cyber Threat Intelligence (CTI)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to practically use the MITRE ATT&CK® framework]]></title>
            <link>https://medium.com/cyber-threat-intelligence-cti/how-to-practically-use-the-mitre-att-ck-framework-3fa8edcc5bd0?source=rss-909b5003c61a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fa8edcc5bd0</guid>
            <category><![CDATA[practical-guides]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[mitre-attack]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[mitre-attack-framework]]></category>
            <dc:creator><![CDATA[Seenu Bhupala]]></dc:creator>
            <pubDate>Sun, 02 Feb 2025 10:02:59 GMT</pubDate>
            <atom:updated>2025-02-02T10:02:59.555Z</atom:updated>
            <content:encoded><![CDATA[<p>In this blog, I will cover two key aspects of the practical application of MITRE ATT&amp;CK:</p><ul><li>How to get started with the ATT&amp;CK framework and different approaches to begin using it</li><li>An introduction to mapping an attack to the framework — and how that mapping can be leveraged to create detections and mitigations</li></ul><p><strong>Getting Started: Approaches to Using MITRE ATT&amp;CK</strong></p><p>When starting with the MITRE ATT&amp;CK framework, there are several approaches to help you become familiar with its structure and use cases.</p><p>Some useful starting points are:</p><ul><li>Choosing a specific technique to analyze and understand</li><li>Basing your research on a known threat actor group or campaign that is relevant to your industry</li><li>Using the framework to analyze specific adversary software (e.g., malware, tools like Mimikatz, or Cobalt Strike)</li><li>Focusing on the industry your organization operates in to determine which adversaries and techniques are most relevant</li><li>Mapping a recent security alert from your SOC team to ATT&amp;CK for real-world analysis</li></ul><p>Since ATT&amp;CK is vast and covers multiple attack vectors, narrowing your focus to what’s most relevant to your organization is essential.</p><p>For example, if you work in the finance sector, you can use ATT&amp;CK to identify threat groups that typically target financial organizations. From there, you can analyze their TTPs and begin applying ATT&amp;CK to your security operations.</p><p><strong>A Practical Approach: Using a Real-World Security Alert</strong></p><p>Even with a narrowed focus, diving into ATT&amp;CK can still feel overwhelming. To simplify this, I recommend starting with a real-world alert from your SOC team.</p><p>Here’s how you can do this:</p><ul><li>Take a recent security alert your organization has responded to (e.g., an attempt at intrusion, a phishing attack, or malware infection)</li><li>Analyze the alert to determine the tactics and techniques used in the attack</li><li>Map the observed activity to the MITRE ATT&amp;CK framework using the <a href="https://mitre-attack.github.io/attack-navigator/"><strong>ATT&amp;CK Navigator</strong></a> for visualization and analysis</li><li>Use ATT&amp;CK’s detection and mitigation sections on each technique page to strengthen your defenses</li></ul><p><strong>Why This Approach is Effective</strong></p><p>By mapping real-world alerts to the ATT&amp;CK framework, you gain several advantages:</p><ul><li>Better visibility into your security posture — Assess how well your current defenses detect and mitigate known attack techniques</li><li>Identify security gaps — If certain techniques are being used against you but your detections are weak, you now have clear areas for improvement</li><li>Strengthen defenses — By using ATT&amp;CK’s recommended mitigations, you can enhance your security controls and reduce the risk of future attacks</li></ul><p>This approach ensures that MITRE ATT&amp;CK is applied in a way that directly benefits your organization, helping you proactively strengthen your security posture against real threats.</p><p>As you become more comfortable with mapping incidents to ATT&amp;CK, you can expand your analysis to other scenarios. The key is to start small, define a clear scope, and refine your research and mappings as you gain deeper insights.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fa8edcc5bd0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cyber-threat-intelligence-cti/how-to-practically-use-the-mitre-att-ck-framework-3fa8edcc5bd0">How to practically use the MITRE ATT&amp;CK® framework</a> was originally published in <a href="https://medium.com/cyber-threat-intelligence-cti">Cyber Threat Intelligence (CTI)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MITRE ATT&CK® framework simplified: Understanding the Matrix, Tactics, and Techniques]]></title>
            <link>https://medium.com/cyber-threat-intelligence-cti/mitre-att-ck-framework-simplified-understanding-the-matrix-tactics-and-techniques-43ff511f875b?source=rss-909b5003c61a------2</link>
            <guid isPermaLink="false">https://medium.com/p/43ff511f875b</guid>
            <category><![CDATA[mitre-attack]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Seenu Bhupala]]></dc:creator>
            <pubDate>Wed, 29 Jan 2025 13:57:46 GMT</pubDate>
            <atom:updated>2025-01-31T11:32:55.612Z</atom:updated>
            <content:encoded><![CDATA[<h3>MITRE ATT&amp;CK® basics: Understanding the Matrix, Tactics, and Techniques</h3><p>In this blog, I aim to simplify the MITRE ATT&amp;CK framework, making it easier to understand. Let’s dive right in!</p><p><strong>What is the MITRE ATT&amp;CK framework?<br></strong>The MITRE ATT&amp;CK framework is a publicly available knowledge base that documents cyber adversary tactics, techniques, and procedures (TTPs) based on real-world observations. It helps cybersecurity professionals understand, detect, and defend against cyber threats effectively.</p><p><strong>Who benefits from using this framework?</strong></p><ul><li><strong>Incident Responders</strong> — Helps analyze and map attack behaviors during investigations</li><li><strong>Threat Hunters </strong>— Guides proactive threat hunting by identifying known adversary techniques</li><li><strong>Red Team Members</strong> — Assists in adversary emulation by simulating real-world attacks</li><li><strong>Security Operations Centers (SOCs)</strong> — Improves detection, response, and defensive strategies based on attacker TTPs</li></ul><p><strong>What are the benefits of using this framework?<br></strong>The framework offers several benefits, with some of the most common being:</p><ul><li><strong>Mapping real-world adversary tactics and techniques</strong> — Helps organizations take a proactive approach to defense by understanding how attackers operate</li><li><strong>Improving detection rules</strong> — Assists SOC teams in developing more effective detection rules based on actual attacker behaviors</li><li><strong>Enhancing collaboration</strong> — Provides a standardized model that allows security teams to work together more efficiently</li><li><strong>Identifying security gaps</strong> — Helps security teams assess their defensive coverage and prioritize improvements</li><li><strong>Supporting threat modeling</strong> — Assists in identifying which attack techniques are most relevant to an organization’s environment</li><li><strong>Continuous updates</strong> — The framework evolves regularly, enabling security teams to keep their defenses aligned with emerging threats</li></ul><p><strong>What are Tactics, Techniques and Procedures (TTPs)?</strong></p><p><strong>Tactics</strong>:<br>Tactics define what the adversary is trying to achieve. They represent the high-level objectives of an attacker.</p><p>For example, an adversary may aim to gain credential access to steal usernames and passwords for further exploitation.</p><p><strong>Techniques</strong>:<br>Techniques explain how an adversary achieves their tactical goal. They describe the specific methods or actions attackers use to accomplish their objectives.<br> <br>For example, an adversary attempting to gain credential access might use credential dumping to extract passwords from memory.</p><p><strong>Sub-Techniques:<br></strong>Sub-techniques provide a more specific breakdown of how an adversary executes a technique to achieve their goal.</p><p>For example, an adversary attempting credential dumping may target Local Security Authority (LSA) secrets to extract stored credentials.</p><p><strong>Procedures</strong>:<br>Procedures describe the specific implementation an adversary uses to conduct a technique or sub-technique. These are real-world examples of how attackers execute their tactics.<br> <br>For example, an adversary may use PowerShell-based Mimikatz to dump credentials from a victim machine.</p><p><strong>What technologies can MITRE ATT&amp;CK apply to?<br></strong>This framework is designed to cover a wide range of technologies and environments where cyber threats exist. Some of the key technologies it applies to include:</p><ul><li>Windows</li><li>macOS</li><li>Linux</li><li>Network Infrastructure</li><li>Container Technologies</li><li>Infrastructure-as-a-Service (IaaS)</li><li>Software-as-a-Service (SaaS)</li><li>Android</li><li>iOS</li><li>ICS (Industrial Control Systems)</li></ul><p>MITRE ATT&amp;CK continuously evolves to include new technologies and attack surfaces, making it a versatile tool for cybersecurity defense.</p><p><strong>Understanding the MITRE ATT&amp;CK Matrix Layout<br></strong>Here are some key tips to help you easily navigate the MITRE ATT&amp;CK matrix layout and its structure.</p><ul><li>Each Tactic, Technique, and Procedure (TTP) in the MITRE ATT&amp;CK matrix is assigned a unique ID number. This makes it easier to locate specific items and reference them when collaborating with others</li><li>Tactics consist of multiple techniques, and some techniques may have one or more sub-techniques that provide a more detailed breakdown.</li></ul><p><strong>Example</strong>:<br><strong>Tactic</strong>: Command and Control <strong>[ID: TA0011]</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*1S9X70NCmh5-Vbdmf3NiWw.png" /><figcaption>Tactic ID assignment example</figcaption></figure><p><strong>Technique</strong>: Application Layer Protocol <strong>[ID: T1071]</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J5gSrtF7fC3la9nhzD05Eg.png" /><figcaption>Technique ID assignment example</figcaption></figure><p><strong>Sub-Technique</strong>: Web Protocols <strong>[ID: T1071.001]</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BiCmYj9-o3SrjDtSa-5GKA.png" /><figcaption>Sub-technique ID assignment example</figcaption></figure><p>Each technique or sub-technique contains details on Procedure Examples, Mitigations, and Detection methods, which help enhance understanding.</p><p>Procedure examples are classified with IDs starting with:</p><ul><li><strong>S</strong> (Software)</li><li><strong>G</strong> (Group)</li><li><strong>C</strong> (Campaigns)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/393/1*wrKsqDN7fbnBKCtiENddZQ.png" /><figcaption>Procedure examples classification</figcaption></figure><p>Mitigations are classified with IDs starting with:</p><ul><li><strong>M</strong> (e.g., M1031)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/1*D6Y-xL6koUq2CKPkmVkHig.png" /><figcaption>Mitigations classification</figcaption></figure><p>Detection methods are classified with IDs starting with:</p><ul><li><strong>DS</strong> (e.g., DS0029)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/405/1*33w8vyB6hkeZfn9cUii2lw.png" /><figcaption>Detection methods classification</figcaption></figure><p>At the bottom of individual technique and sub-technique pages, you will find <strong>References </strong>section that provide links to original data sources used for documenting specific adversary behaviors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/1*O3G8-8XLS68GoKYo7532VA.png" /><figcaption>References citing original data sources</figcaption></figure><p>I hope this blog helps break down the MITRE ATT&amp;CK framework in a way that makes it easier to understand and navigate. By simplifying its structure and terminology, my goal is to help you feel more confident when exploring the ATT&amp;CK matrix.</p><p>In a future blog, I will dive deeper into the MITRE ATT&amp;CK framework and explore various ways to operationalize it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43ff511f875b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cyber-threat-intelligence-cti/mitre-att-ck-framework-simplified-understanding-the-matrix-tactics-and-techniques-43ff511f875b">MITRE ATT&amp;CK® framework simplified: Understanding the Matrix, Tactics, and Techniques</a> was originally published in <a href="https://medium.com/cyber-threat-intelligence-cti">Cyber Threat Intelligence (CTI)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Pyramid of Pain: Why TTPs matter in cyber threat intelligence]]></title>
            <link>https://medium.com/cyber-threat-intelligence-cti/the-pyramid-of-pain-why-ttps-matter-in-cyber-threat-intelligence-af6be24011ba?source=rss-909b5003c61a------2</link>
            <guid isPermaLink="false">https://medium.com/p/af6be24011ba</guid>
            <category><![CDATA[pyramid-of-pain]]></category>
            <category><![CDATA[cyber-threat-intelligence]]></category>
            <dc:creator><![CDATA[Seenu Bhupala]]></dc:creator>
            <pubDate>Mon, 27 Jan 2025 06:48:50 GMT</pubDate>
            <atom:updated>2025-03-13T07:12:44.469Z</atom:updated>
            <content:encoded><![CDATA[<p>In my <a href="https://medium.com/@Seenu-Bhupala/demystifying-cyber-threat-intelligence-what-it-is-and-why-it-matters-b7c3f8c523b0">recent blog post</a> I talked about what cyber threat intelligence is and its importance to any cybersecurity program.</p><p>Following on from that topic, I want to discuss next what pyramid of pain concept is and how it helps us focus our efforts on disrupting adversaries’ actions.</p><p><strong>What is the pyramid of pain?<br></strong>The Pyramid of Pain is a concept originally created by David J. Bianco, and you can find the article <a href="https://detect-respond.blogspot.com/2013/03/the-pyramid-of-pain.html">here</a>.</p><p>This framework, illustrated below, categorizes the types of indicators used to detect attacker activities and shows how challenging it is for attackers to adapt or change them, with easier changes like hash values at the bottom and significantly tougher changes like TTPs at the top.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*i-WXglKlI_1hzuPvIR1w0g.png" /><figcaption><a href="https://detect-respond.blogspot.com/2013/03/the-pyramid-of-pain.html">Pyramid of pain</a></figcaption></figure><p>Since changing TTPs is the most challenging task for adversaries, it is worth prioritizing our efforts on disrupting this type of indicator. By doing so, we shift our focus to adversaries’ behaviors rather than just the tools they use.</p><p>Focusing on TTPs, as highlighted at the top of the Pyramid of Pain, requires a deep understanding of how adversaries operate. This is where the <strong><em>MITRE ATT&amp;CK®</em> framework</strong> becomes invaluable. It provides a comprehensive and structured approach to mapping and understanding TTPs, enabling defenders to analyze and effectively counter adversary behaviors.</p><p>In my <a href="https://medium.com/cyber-threat-intelligence-cti/mitre-att-ck-framework-simplified-understanding-the-matrix-tactics-and-techniques-43ff511f875b">next post</a>, I will delve deeper into the <em>ATT&amp;CK</em> framework and provide practical guidance on how to get started using it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af6be24011ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cyber-threat-intelligence-cti/the-pyramid-of-pain-why-ttps-matter-in-cyber-threat-intelligence-af6be24011ba">The Pyramid of Pain: Why TTPs matter in cyber threat intelligence</a> was originally published in <a href="https://medium.com/cyber-threat-intelligence-cti">Cyber Threat Intelligence (CTI)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>