<?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 Venkatesh on Medium]]></title>
        <description><![CDATA[Stories by Venkatesh on Medium]]></description>
        <link>https://medium.com/@venkatesh0919?source=rss-57aaadeaddc6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9k4om0IBGRlZ_5eLBoa31w.jpeg</url>
            <title>Stories by Venkatesh on Medium</title>
            <link>https://medium.com/@venkatesh0919?source=rss-57aaadeaddc6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:40:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@venkatesh0919/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[What It Really Takes to Build a Sustainable SOC: Lessons From the Operational Side of Security]]></title>
            <link>https://medium.com/@venkatesh0919/what-it-really-takes-to-build-a-sustainable-soc-lessons-from-the-operational-side-of-security-d986dc465a7d?source=rss-57aaadeaddc6------2</link>
            <guid isPermaLink="false">https://medium.com/p/d986dc465a7d</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <dc:creator><![CDATA[Venkatesh]]></dc:creator>
            <pubDate>Mon, 07 Sep 2026 14:17:42 GMT</pubDate>
            <atom:updated>2026-09-07T14:17:42.915Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Why sustainable performance depends on how we design the work, not just the technology we deploy.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RzJ8zSPyURLuLPYrF6wQHA.png" /></figure><p>When we talk about building a Security Operations Center, the conversation usually starts with technology.</p><blockquote>Which SIEM should we use?</blockquote><blockquote>Which EDR should we deploy?</blockquote><blockquote>What use cases should we build?</blockquote><blockquote>How much should we automate?</blockquote><blockquote>How quickly can we reduce MTTR?</blockquote><p>All of these questions are important.</p><p>But after spending years working around SOC operations, I’ve learned that there is another question we don’t always ask early enough:</p><p><strong>Can the way we operate today continue to work six months or two years from now?</strong></p><p>Because building a SOC is not only about detecting threats.</p><p><strong>It’s also about building an operating model that people can sustain.</strong></p><p>That includes how we manage alerts, how investigations are handed over, how analysts deal with interruptions, how leaders handle pressure, and how much unnecessary complexity we allow into day-to-day operations.</p><p>And sometimes, the difference between a SOC that performs well and one that struggles isn’t another security tool.</p><p><strong>It’s how the work itself is designed.</strong></p><h3><strong>The SOC Is Always Moving</strong></h3><p>A SOC is rarely predictable.</p><p>One moment, the team is working through normal alert volumes.</p><p>Then a critical vulnerability is announced.</p><p>A suspicious login appears.</p><p>An endpoint triggers a high-severity detection.</p><p>An application owner asks for an investigation update.</p><p>Someone needs help with a phishing incident.</p><p>And while all of this is happening, the regular queue doesn’t stop.</p><p>The analyst still has alerts to review, investigations to document, tickets to update, and handovers to prepare.</p><p>This is the reality of security operations.</p><p>The challenge isn’t simply the amount of work.</p><p>It’s the <strong>constant switching between different types of work</strong>.</p><p>An analyst may move from investigating a PowerShell event to reviewing an identity alert, then join an incident call, respond to an escalation, and return to the original investigation.</p><p>Technically, they may have been busy for the entire hour.</p><p>But being busy doesn’t always mean being productive.</p><p>Security investigations require concentration.</p><p>You need to remember what happened, understand the context, connect events, challenge assumptions, and decide what to do next.</p><p>Every interruption breaks that chain.</p><p>Over time, that creates a level of mental fatigue that isn’t always visible on a dashboard.</p><h3><strong>Alert Volume Is Not the Same as Security Value</strong></h3><p>One of the common challenges in SOC operations is alert volume.</p><p>We often measure:</p><ul><li>How many alerts were generated?</li><li>How many were closed?</li><li>How many breached SLA?</li><li>What is the MTTR?</li><li>How many false positives do we have?</li></ul><p>These metrics are useful.</p><p>But I think there is another question worth asking:</p><p><strong>How many of those alerts actually helped the analyst make a security decision?</strong></p><p>If an analyst spends most of their shift closing alerts that repeatedly turn out to be expected activity, the problem isn’t only productivity.</p><blockquote><strong>It affects attention | It affects confidence.</strong></blockquote><p>And eventually, it affects how carefully the analyst approaches the next alert.</p><p>Imagine seeing the same type of alert dozens of times every day:</p><blockquote>“Expected administrative activity.”</blockquote><blockquote>“Known application.”</blockquote><blockquote>“Approved process.”</blockquote><blockquote>“False positive.”</blockquote><p>After enough repetition, the analyst naturally starts recognizing patterns.</p><p>That’s useful when the pattern is legitimate.</p><p>But it can become dangerous when a genuine threat appears inside the same noise.</p><p>This is why alert tuning is more than a SIEM engineering exercise.</p><p><strong>Every unnecessary alert consumes analyst attention.</strong></p><p>Reducing noise gives that attention back.</p><p>And that can directly improve investigation quality.</p><h3><strong>Context Switching Is a Bigger Problem Than We Think</strong></h3><p>A SOC analyst rarely works on one investigation from beginning to end without interruption.</p><p>A typical investigation might look something like this:</p><blockquote><strong>10:05 AM</strong> — Suspicious PowerShell alert arrives.</blockquote><blockquote><strong>10:10 AM</strong> — Analyst starts reviewing the process tree.</blockquote><blockquote><strong>10:15 AM</strong> — IT asks for an update on another incident.</blockquote><blockquote><strong>10:20 AM</strong> — Analyst joins a quick call.</blockquote><blockquote><strong>10:30 AM</strong> — Returns to the PowerShell investigation.</blockquote><blockquote><strong>10:35 AM</strong> — New critical alert arrives.</blockquote><blockquote><strong>10:40 AM</strong> — Manager asks for the status of an ongoing incident.</blockquote><blockquote><strong>10:50 AM</strong> — Analyst finally returns to the original investigation.</blockquote><p>Nothing unusual happened.</p><p>Everyone was simply doing their job.</p><p>But the analyst now has to mentally reconstruct where they were.</p><p>This is why small operational improvements can have a large impact.</p><p>Things like:</p><ul><li>Clear handover practices</li><li>Consistent investigation notes</li><li>Defined escalation paths</li><li>Clear priorities</li><li>Planned communication channels</li><li>Better shift transitions</li><li>Reduced unnecessary meetings</li><li>Defined interruption thresholds</li></ul><p>These may sound like basic operational practices.</p><p>But they reduce the amount of information analysts need to keep in their heads.</p><p>And that matters.</p><h3><strong>Don’t Build a SOC That Depends on Heroes</strong></h3><p>There is always someone in a SOC who seems to be able to handle everything.</p><p>They know the SIEM inside out.</p><p>They understand the EDR.</p><p>They know the environment.</p><p>They remember how a particular detection works.</p><p>They are usually the person everyone calls when something complicated happens.</p><p>Having experienced people is a strength.</p><p>But depending on one or two people for everything is a weakness.</p><p>If only one analyst knows how to investigate a particular detection, you have a knowledge gap.</p><p>If only one person can handle a certain incident, you have a resilience problem.</p><p>If one person is always staying late because they don’t want to leave an investigation unfinished, you may have an operational design problem.</p><p>A mature SOC should not depend on individual heroics.</p><p>It should depend on:</p><blockquote><strong>People + Process + Technology + Knowledge Sharing</strong></blockquote><p>The goal isn’t to eliminate high performers.</p><p>The goal is to make sure the operation can continue even when those people are unavailable.</p><h3><strong>A Good Handover Is a Sign of Good Operations</strong></h3><p>I have always believed that a good investigation should be capable of being handed over.</p><p>But sometimes, analysts see handover as losing ownership.</p><p>There can be an unspoken mindset:</p><p>“I started the investigation, so I should finish it.”</p><p>That sounds like ownership.</p><p>But sometimes it simply means someone is carrying unnecessary pressure.</p><p>A good SOC should make handover normal.</p><p>Another analyst should be able to pick up an investigation and understand:</p><p><strong>What do we know?</strong></p><p>The facts confirmed so far.</p><p><strong>What have we checked?</strong></p><p>The investigation already completed.</p><p><strong>What don’t we know?</strong></p><p>The unanswered questions.</p><p><strong>What are we waiting for?</strong></p><p>User confirmation, logs, IT feedback, or other information.</p><p><strong>What happens next?</strong></p><p>The recommended next action.</p><p>That’s enough to continue the investigation without starting from the beginning.</p><h3><strong>Good documentation allows ownership to move without losing context.</strong></h3><p>And that’s important in a 24×7 SOC.</p><p>Your investigation doesn’t belong to one person.</p><p>It belongs to the operation.</p><blockquote><strong>It’s Okay to Say, “We Don’t Know Yet”</strong></blockquote><p>This is another area where I think SOC culture matters.</p><p>Security investigations rarely start with complete information.</p><p>You may know that an account logged in from an unusual location.</p><p>But you may not know whether the account was compromised.</p><p>You may know that PowerShell executed.</p><p>But you may not know whether the command was malicious.</p><p>You may know that malware was detected.</p><p>But you may not yet know whether execution actually occurred.</p><p>That’s normal.</p><p>A good investigation doesn’t require immediate certainty.</p><p>It requires a structured way of dealing with uncertainty.</p><p>For example:</p><p><strong>What we know:</strong></p><p>A successful authentication occurred from a previously unseen location.</p><p><strong>What we don’t know:</strong></p><p>Whether the activity was performed by the legitimate user.</p><p><strong>What we checked:</strong></p><p>MFA status, source IP reputation, device information, and related authentication events.</p><p><strong>What we need next:</strong></p><p>User validation and additional session activity.</p><p>This is much more useful than simply writing:</p><p>“Possible account compromise. Investigation ongoing.”</p><p>The ability to say <strong>“we don’t know yet”</strong> is not a weakness.</p><p>It shows that the analyst understands the difference between evidence and assumption.</p><h3><strong>Protect Investigation Time</strong></h3><p>SOC metrics naturally focus on speed.</p><p>How quickly did we detect it?</p><p>How quickly did we respond?</p><p>How quickly did we contain it?</p><p>Those measurements are important.</p><p>But there is another resource that deserves attention:</p><h3><strong>Focused investigation time.</strong></h3><p>Not every question needs an immediate response.</p><p>Not every notification requires an interruption.</p><p>Not every analyst needs to join every incident call.</p><p>Sometimes the best thing a SOC leader can say is:</p><p><strong>“Let the analyst investigate. We’ll get an update when there is something meaningful to share.”</strong></p><p>That small change can improve the quality of an investigation.</p><p>Teams can establish simple expectations around:</p><ul><li>What requires an immediate interruption</li><li>What can wait</li><li>What should be escalated</li><li>Where questions should be queued</li><li>Who needs to be involved in an incident</li><li>When analysts should have uninterrupted investigation time</li></ul><p>The objective isn’t to isolate analysts.</p><p>It’s to protect the time they need to think.</p><p>Because sometimes <strong>30 minutes of focused investigation is more valuable than an hour of constant activity.</strong></p><h3><strong>Automation Should Give Analysts Time to Think</strong></h3><p>Automation is one of the most valuable capabilities available to modern SOCs.</p><p>But I think we need to be careful about how we define its purpose.</p><p>Automation shouldn’t simply help us process more alerts.</p><p>If we automate a process and use that capability to generate even more low-value alerts, we haven’t really solved the problem.</p><p>We’ve just made the noise faster.</p><blockquote>The better question is:</blockquote><blockquote><strong>What repetitive work can we remove from the analyst’s day?</strong></blockquote><p>For example:</p><ul><li>Automatically enrich IP addresses and domains</li><li>Pull threat intelligence context</li><li>Build investigation timelines</li><li>Populate incident tickets</li><li>Correlate related alerts</li><li>Identify duplicate events</li><li>Perform repetitive validation</li><li>Trigger controlled containment actions</li><li>Provide asset and user context automatically</li></ul><p>The objective should be simple:</p><p><strong>Let machines handle repetitive work so analysts can spend more time thinking.</strong></p><p>The best automation doesn’t replace analyst judgment.</p><p>It creates more space for it.</p><h3><strong>Don’t Treat Every Alert as an Emergency</strong></h3><p>Another operational challenge I’ve seen is the tendency to treat every high-severity alert as an immediate crisis.</p><p>But severity and business risk aren’t always the same thing.</p><p>A high-severity detection on a test system may have limited impact.</p><p>A seemingly moderate authentication anomaly involving a privileged account may require much more attention.</p><p>This is why SOC analysts and leaders need context.</p><p>Ask:</p><ul><li>What asset is involved?</li><li>Who is the user?</li><li>What privileges do they have?</li><li>What data is involved?</li><li>Is the system business-critical?</li><li>Is the system internet-facing?</li><li>What could happen if the activity is confirmed malicious?</li><li>Are other systems affected?</li></ul><p>The answer to these questions helps determine where attention should go.</p><p>And good prioritization also protects analysts.</p><p>If everything is treated as critical, eventually nothing feels critical.</p><h3><strong>What Should SOC Leaders Look At?</strong></h3><p>Traditional SOC metrics are important.</p><p>But I believe operational health should also be visible.</p><p>For example:</p><ul><li>Repeated overtime</li><li>Frequent shift extensions</li><li>Growing alert backlog</li><li>Increasing false-positive rates</li><li>Repeated manual investigation steps</li><li>Increasing dependency on specific individuals</li><li>Frequent after-hours escalations</li><li>Declining investigation quality</li><li>Increasing analyst turnover</li><li>Repeated process gaps</li></ul><p>These aren’t just people-management indicators.</p><p>They can become <strong>security risk indicators</strong>.</p><p>If the team is constantly overloaded, eventually something will be missed.</p><p>If the best analysts are exhausted, the organization’s ability to investigate complex incidents will eventually suffer.</p><p>If knowledge is concentrated in a few people, the SOC becomes fragile.</p><p>A good SOC dashboard should therefore tell us not only:</p><p><strong>“How are we performing?”</strong></p><p>but also:</p><p><strong>“How sustainable is the way we are performing?”</strong></p><h3><strong>Build a Culture Where People Can Learn</strong></h3><p>Security operations will never be perfect.</p><p>Alerts will be missed.</p><p>Investigations will take longer than expected.</p><p>A detection will sometimes be wrong.</p><p>A response action may not produce the expected result.</p><p>What matters is what happens afterward.</p><p>A mature SOC asks:</p><p><strong>What can we learn from this?</strong></p><p>Instead of immediately asking:</p><p><strong>Who made the mistake?</strong></p><p>Blameless reviews are particularly valuable here.</p><p>The objective isn’t to remove accountability.</p><p>It’s to understand the conditions that allowed something to happen.</p><p>Was the alert unclear?</p><p>Was the playbook outdated?</p><p>Was there missing telemetry?</p><p>Was the analyst overloaded?</p><p>Was the escalation process unclear?</p><p>Was the detection too noisy?</p><p>Was the necessary context unavailable?</p><p>These questions lead to improvements.</p><p>And every improvement should make the next incident easier to handle.</p><h3><strong>Sustainable Performance Is Still Performance</strong></h3><p>Sometimes conversations about analyst wellbeing are separated from operational performance.</p><p>I don’t think they should be.</p><p>When people are under sustained pressure, we may eventually see:</p><ul><li>More hesitation</li><li>More unnecessary escalation</li><li>Poorer documentation</li><li>Reduced investigation depth</li><li>Missed patterns</li><li>Less curiosity</li><li>Reduced ownership</li></ul><p>Supporting the team isn’t about lowering standards.</p><p>It’s about creating the conditions where people can consistently meet those standards.</p><p>There is a difference between:</p><p><strong>Working hard during a critical incident</strong></p><p>and</p><blockquote><strong>Designing a SOC where working at crisis intensity becomes normal.</strong></blockquote><blockquote>The first is part of security operations.</blockquote><blockquote>The second is an operational problem.</blockquote><h3><strong>Building a SOC That Can Scale</strong></h3><p>For me, building a scalable SOC isn’t simply about adding more analysts when the alert volume increases.</p><p>It’s about asking whether the entire operating model can handle growth.</p><p>As the organization grows, you may have:</p><p>More users.</p><p>More endpoints.</p><p>More cloud workloads.</p><p>More applications.</p><p>More logs.</p><p>More threats.</p><p>More compliance requirements.</p><p>More alerts.</p><p>If the only solution is:</p><p>“Add more people.”</p><p>the SOC will eventually become expensive and difficult to manage.</p><p>Instead, look at the complete system.</p><blockquote><strong>Can we reduce unnecessary alerts?</strong></blockquote><blockquote><strong>Can we improve detection quality?</strong></blockquote><blockquote><strong>Can we automate repetitive tasks?</strong></blockquote><blockquote><strong>Can we improve handovers?</strong></blockquote><blockquote><strong>Can we simplify escalation?</strong></blockquote><blockquote><strong>Can we improve analyst training?</strong></blockquote><blockquote><strong>Can knowledge be shared across the team?</strong></blockquote><blockquote><strong>Can we improve our use cases?</strong></blockquote><blockquote><strong>Can we make investigations easier?</strong></blockquote><blockquote><strong>Can we give analysts better context?</strong></blockquote><p>These improvements compound over time.</p><p>And that’s how a SOC becomes scalable.</p><h3><strong>My Biggest Takeaway</strong></h3><p>After spending years around SOC operations, I’ve learned that building a strong SOC isn’t only about having the right technology.</p><blockquote>Technology is important.</blockquote><blockquote>People are important.</blockquote><blockquote>Processes are important.</blockquote><p>But the way these three work together is what determines whether the SOC can actually sustain its performance.</p><p>A good SOC asks:</p><p><strong>How quickly can we respond?</strong></p><p>A mature SOC also asks:</p><p><strong>How consistently can we respond?</strong></p><p>And a truly sustainable SOC asks:</p><p><strong>Can our people continue doing this well over the long term?</strong></p><p>Sometimes the answer isn’t another security tool.</p><p>It might be better alert tuning.</p><p>A stronger handover process.</p><p>Better documentation.</p><p>More automation.</p><p>Clearer priorities.</p><p>Better training.</p><p>Fewer unnecessary interruptions.</p><p>Or simply giving analysts enough space to investigate properly.</p><h3><strong>Build the SOC for scale, Not Just for Today</strong></h3><p>Cybersecurity will always be demanding.</p><p>There will always be another alert.</p><p>Another vulnerability.</p><p>Another incident.</p><p>Another threat actor.</p><p>Another urgent request.</p><p>We can’t remove the pressure completely.</p><p>But we can decide how much <strong>unnecessary pressure</strong> we add to the operation.</p><p>That’s where SOC leadership and operational design really matter.</p><p>A sustainable SOC isn’t one where people never feel pressure.</p><p>It’s one where pressure is managed, work is structured, knowledge is shared, and people aren’t expected to rely on heroics every day.</p><p>Because ultimately, your SOC isn’t powered by the SIEM.</p><p>It isn’t powered by the EDR.</p><p>It isn’t powered by dashboards.</p><p>It isn’t even powered by automation.</p><p><strong>It is powered by people making thousands of security decisions every day.</strong></p><p>If we want better security outcomes, we need to build an environment where those people can continue to think clearly, investigate effectively, learn from incidents, and make good decisions.</p><p><strong>That’s what it really takes to build a sustainable SOC.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d986dc465a7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Anyone Can Review an Alert, From Alert to Action: What Separates Good SOC Analysts from Great Ones]]></title>
            <link>https://medium.com/@venkatesh0919/anyone-can-review-an-alert-great-soc-analysts-know-what-to-ask-next-528044d5cd9a?source=rss-57aaadeaddc6------2</link>
            <guid isPermaLink="false">https://medium.com/p/528044d5cd9a</guid>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security-operations]]></category>
            <category><![CDATA[soc-investigation]]></category>
            <category><![CDATA[cybersecurity-training]]></category>
            <dc:creator><![CDATA[Venkatesh]]></dc:creator>
            <pubDate>Tue, 11 Aug 2026 13:21:57 GMT</pubDate>
            <atom:updated>2026-08-14T03:49:08.845Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Because finding an alert is easy. Understanding what happened is the real skill. You Don’t Become a Great SOC Analyst by Mastering More Tools</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rb1pkIcN6roLmRHilum0Hw.png" /></figure><p><strong><em>When most people start their cybersecurity journey, they focus on technology.</em></strong></p><p>1. Learn networking.</p><p>2. Understand Windows and Linux.</p><p>3. Master a SIEM.</p><p>4. Learn EDR.</p><p>5. Study MITRE ATT&amp;CK.</p><p>6. Practice threat hunting.</p><p>7. Complete certifications.</p><p>8. Spend hours in labs.</p><p>9. That was my mindset too.</p><p>I initially believed that becoming a strong SOC Analyst was mainly about becoming technically good at security tools.</p><p><em>And there is nothing wrong with that approach.</em></p><p><strong>Technical knowledge is the foundation of a good SOC Analyst.</strong></p><p>But after spending more time working with security investigations, endpoint security, SIEM operations, incident response, documentation, and SOC processes, I realized something important:</p><p><strong>The best SOC analysts are not necessarily the ones who know the most tools. They are the ones who know how to think, investigate, communicate, and make decisions.</strong></p><blockquote>A SIEM can generate thousands of alerts.</blockquote><blockquote>An EDR can show you suspicious processes.</blockquote><blockquote>Threat intelligence can provide indicators.</blockquote><p>But none of these tools can completely answer the most important questions:</p><p><strong>What actually happened? How serious is it? What is the impact? What should we do next?</strong></p><p>That is where the analyst’s judgment comes in.</p><p>Over the years, I’ve come to appreciate several skills that don’t always get enough attention when people talk about building a SOC career.</p><h3>1. Documentation Is Not Administration — It’s Part of the Investigation</h3><p>Early in my career, I underestimated how important documentation would become.</p><p>I thought the investigation was the important part and documentation was simply something to complete afterward.</p><p>I eventually learned the opposite.</p><p><strong>If an investigation isn’t documented properly, part of the investigation is effectively lost.</strong></p><p>Consider a simple alert:</p><p>“Suspicious PowerShell activity detected.”</p><p>Technically, that may be enough to say an alert was received.</p><p>But it doesn’t tell the next analyst much.</p><p>A useful investigation record should answer questions such as:</p><ul><li>What triggered the alert?</li><li>Which user and host were involved?</li><li>When did the activity occur?</li><li>What command was executed?</li><li>Which parent process initiated PowerShell?</li><li>Was the activity successful?</li><li>What happened immediately before and after?</li><li>Were there related authentication events?</li><li>Were other endpoints involved?</li><li>What evidence supports malicious activity?</li><li>What evidence suggests legitimate activity?</li><li>What actions were taken?</li><li>Why was the alert closed or escalated?</li></ul><p>Compare:</p><p><strong>Weak:</strong></p><p>“Suspicious PowerShell activity observed. No further action.”</p><p><strong>Better:</strong></p><p>“PowerShell executed on FXX-LXT-024 under the user’s account. The command initiated an approved software deployment script from the organization’s management platform. No suspicious child processes, external connections, or related authentication anomalies were identified. Activity assessed as legitimate and the alert was closed.”</p><p>The second note tells the next analyst <strong>what happened, what was checked, and why the decision was made.</strong></p><p>This becomes especially important in a 24×7 SOC.</p><p>Your investigation may be handed over to another analyst six hours later.</p><p>They shouldn’t have to start from zero.</p><p>Good documentation provides continuity across:</p><p><strong>L1 → L2 → Incident Response → IT → Management</strong></p><p>I’ve learned to think of investigation notes as a form of <strong>security evidence</strong>.</p><p>Don’t document only what you found.</p><p>Document <strong>how you reached your conclusion.</strong></p><h3>2. Communication Is a Security Skill</h3><p>Finding something suspicious is only half the job. The other half is explaining what you found.</p><p>A SOC Analyst may communicate with:</p><ul><li>L1 and L2 analysts</li><li>Incident Responders</li><li>IT administrators</li><li>Network teams</li><li>Application owners</li><li>Identity teams</li><li>Management</li><li>Business stakeholders</li><li>End users</li></ul><p>And each audience needs a different level of detail.</p><p>A security engineer may want the exact process tree.</p><p>A manager may simply need to know:</p><p><strong>What happened? How serious is it? What is the impact? What are we doing about it?</strong></p><p>For example:</p><blockquote><strong>Technical communication:</strong></blockquote><blockquote>“Encoded PowerShell execution spawned from WINWORD.EXE, followed by an outbound connection to a newly observed external IP.”</blockquote><blockquote><strong>Management communication:</strong></blockquote><blockquote>“A user opened a potentially malicious document that triggered suspicious PowerShell activity. The endpoint blocked the activity, and our investigation has not identified evidence of successful compromise. We are validating whether any other users received the same document.”</blockquote><p>Same incident.</p><p>Different audience.</p><p>The ability to translate technical findings into business-relevant information is a major skill.</p><p><strong>And don’t underestimate escalation.</strong></p><p>Some analysts hesitate to escalate because they think:</p><p><em>“I should be able to solve this myself.”</em></p><p>That’s the wrong mindset.</p><p><strong><em>Strong analyst knows when the investigation has moved beyond their authority, expertise, or available evidence.</em></strong></p><blockquote><strong>Escalating at the right time is not a weakness. It’s good security judgment.</strong></blockquote><h3>3. Learn to Ask Better Questions</h3><p>One of the biggest differences between an alert reviewer and an investigator is the quality of the questions they ask.</p><p>A SIEM alert is usually just a starting point.</p><p>For example:</p><p>“Multiple failed logins followed by a successful login.”</p><p>A junior approach might be:</p><p>“Possible brute-force attack.”</p><p>An investigative approach asks:</p><ul><li>Which account?</li><li>Which source IP?</li><li>Was the source internal or external?</li><li>Was the successful login from the same source?</li><li>Was MFA completed?</li><li>Is the source IP known?</li><li>Is the user normally active at this time?</li><li>Was the account recently created or modified?</li><li>What happened after authentication?</li><li>Were privileged actions performed?</li><li>Did the same source target other accounts?</li><li>Did the user have an unusual location or device?</li><li>Are there endpoint alerts associated with the account?</li></ul><p>Now the alert has become an investigation.</p><p>The same applies to many common SOC alerts.</p><p><strong>PowerShell execution</strong></p><blockquote>Don’t immediately assume:</blockquote><blockquote>“PowerShell = malicious.”</blockquote><blockquote>Ask:</blockquote><blockquote>Who executed it?</blockquote><blockquote>What was executed?</blockquote><blockquote>Which process launched it?</blockquote><blockquote>What was the parent process?</blockquote><blockquote>Was the script signed?</blockquote><blockquote>Did it communicate externally?</blockquote><blockquote>Is this normal for this user or system?</blockquote><p><strong>Impossible travel</strong></p><blockquote>Don’t immediately conclude:</blockquote><blockquote>“The account is compromised.”</blockquote><blockquote>Ask:</blockquote><blockquote>Is the user traveling?</blockquote><blockquote>Is VPN involved?</blockquote><blockquote>Is the IP associated with corporate infrastructure?</blockquote><blockquote>Was MFA successful?</blockquote><blockquote>Was the device familiar?</blockquote><blockquote>Did any suspicious activity occur after authentication?</blockquote><p><strong>Malware detection</strong></p><blockquote>Don’t stop at:</blockquote><blockquote>“EDR blocked malware.”</blockquote><blockquote>Ask:</blockquote><blockquote>Was the file executed?</blockquote><blockquote>Where did it come from?</blockquote><blockquote>Was it downloaded by the user or another process?</blockquote><blockquote>Did it create persistence?</blockquote><blockquote>Were similar files found elsewhere?</blockquote><blockquote>Did the same hash appear on other endpoints?</blockquote><h3>Tools provide data. Good analysts create context.</h3><h3>4. Curiosity Is Powerful — But Objectivity Is Essential</h3><p>Curiosity makes a good investigator.</p><p>But uncontrolled assumptions can make a bad one.</p><p>One of the biggest risks during an investigation is <strong>confirmation bias</strong>.</p><p>You see something suspicious and form a theory:</p><p>“This is probably compromised.”</p><p>From that point, you unconsciously start looking only for evidence that supports your theory.</p><p>A better approach is to challenge yourself.</p><p>Ask:</p><p><strong>What evidence supports my conclusion?</strong></p><p>And then:</p><p><strong>What evidence contradicts it?</strong></p><p>For example, you investigate suspicious PowerShell activity.</p><p>Evidence suggesting compromise:</p><ul><li>Encoded command</li><li>Unknown external connection</li><li>Suspicious parent process</li><li>New scheduled task</li><li>Abnormal user behavior</li></ul><p>But you also discover:</p><ul><li>The script belongs to an approved IT deployment tool.</li><li>The host is part of a known testing environment.</li><li>The administrator performed the activity during a scheduled maintenance window.</li></ul><p>Now the investigation changes.</p><p>That’s good.</p><p><strong>Changing your conclusion when new evidence appears is not failure. That’s investigation.</strong></p><p>The goal of an analyst isn’t to prove their first assumption.</p><p>The goal is to find the most accurate explanation supported by evidence.</p><h3>5. Understand the Business Behind the Alert</h3><p>This is one of the skills that can dramatically change how an analyst prioritizes incidents.</p><p>Two alerts can look technically identical but have completely different business impact.</p><p>Imagine the same suspicious login occurring on:</p><p><strong>System A:</strong> A developer’s test machine.</p><p><strong>System B:</strong> A production finance application.</p><p>Technically, both may trigger the same detection.</p><p>Operationally, they may represent very different levels of risk.</p><p>Context matters.</p><p>Ask:</p><blockquote>How critical is the asset?</blockquote><blockquote>What data does it contain?</blockquote><blockquote>Is the account privileged?</blockquote><blockquote>Is the system internet-facing?</blockquote><blockquote>Is customer information involved?</blockquote><blockquote>Could the activity affect business operations?</blockquote><blockquote>Could there be regulatory or compliance implications?</blockquote><blockquote>What happens if the system becomes unavailable?</blockquote><p>This is why a SOC should not operate purely based on alert severity.</p><p>A detection might be marked <strong>Medium</strong> by a security product, but if it involves a highly privileged account accessing a critical production system, the actual business risk may be much higher.</p><p>The opposite can also happen.</p><p>A security product may generate a <strong>High</strong> severity alert on a development machine, but after investigation the activity may be expected and have minimal business impact.</p><p><strong>The SOC’s job isn’t to close alerts.</strong></p><p><strong>The SOC’s job is to reduce risk to the business.</strong></p><p>That mindset changes how you investigate and prioritize.</p><h3>6. Stay Calm When Everything Looks Urgent</h3><p>SOC environments can be stressful.</p><p>The dashboard is full of alerts.</p><p>A critical vulnerability is announced.</p><p>An EDR detection appears.</p><p>A privileged account triggers an anomaly.</p><p>Someone from management asks for an update.</p><p>And suddenly everything feels urgent.</p><p>But not everything that looks urgent is actually critical.</p><p>One of the most valuable skills I’ve developed is <strong>composure during investigations.</strong></p><p>When analysts panic, they tend to:</p><ul><li>Jump to conclusions</li><li>Skip investigation steps</li><li>Over-escalate</li><li>Miss important evidence</li><li>Take actions without understanding the impact</li></ul><p>A structured approach helps.</p><p>When faced with a potentially serious alert, I prefer to think through it systematically:</p><p><strong>1. Validate</strong></p><p>Is the alert actually triggered by the behavior we think it is?</p><p><strong>2. Investigate</strong></p><p>What evidence do we have?</p><p><strong>3. Scope</strong></p><p>Is this one user, one endpoint, or multiple systems?</p><p><strong>4. Assess impact</strong></p><p>What could the activity affect?</p><p><strong>5. Contain</strong></p><p>Is immediate containment required?</p><p><strong>6. Escalate</strong></p><p>Does this require Incident Response, IT, management, or another specialist team?</p><p><strong>7. Document</strong></p><p>Can another analyst understand exactly what happened?</p><p><strong>8. Learn</strong></p><p>Does the incident reveal a gap in our detection, process, control, or training?</p><p><strong>Speed matters in security operations.</strong></p><p>But speed without accuracy can make an incident worse.</p><h3>7. Learn to Distinguish “Interesting” From “Important”</h3><p>This is another lesson that comes with experience.</p><p>SOC analysts encounter a lot of interesting activity.</p><p>A strange PowerShell command.</p><p>A new IP address.</p><p>An unusual process.</p><p>A rare user agent.</p><p>A suspicious domain.</p><p>A failed login from an unusual country.</p><p>All of these can be interesting.</p><p>But not everything interesting is important.</p><p>The real question is:</p><p><strong>Does this activity represent meaningful risk?</strong></p><p>A great analyst learns to prioritize based on:</p><blockquote><strong>Evidence + Context + Impact + Likelihood</strong></blockquote><p>rather than simply reacting to whatever looks unusual.</p><p>This helps prevent alert fatigue and allows analysts to spend their time where it matters most.</p><h3>8. Learn From Every Investigation</h3><p>An investigation shouldn’t necessarily end when the ticket is closed.</p><p>Ask:</p><p>“What can we improve because of this incident?”</p><p>Maybe the detection was too noisy.</p><p>Maybe the alert didn’t contain enough context.</p><p>Maybe the analyst had to manually perform five searches to understand the event.</p><p>Maybe the escalation process wasn’t clear.</p><p>Maybe the same attack could have been detected earlier.</p><p>Maybe the organization lacked the right logging.</p><p>These observations can become improvements.</p><p>For example:</p><p><strong>Repeated phishing investigation → Improve email detection</strong></p><p><strong>Repeated account compromise → Improve identity monitoring</strong></p><p><strong>Repeated manual enrichment → Automate threat intelligence lookups</strong></p><p><strong>Repeated false positives → Tune the detection</strong></p><p><strong>Repeated investigation delays → Improve log onboarding or data quality</strong></p><p>This is where a SOC starts becoming mature.</p><p>The goal isn’t simply to investigate incidents.</p><p><strong>The goal is to make the next investigation faster and better.</strong></p><p><strong>The Real Skill Stack of a Great SOC Analyst</strong></p><p>When people talk about becoming a SOC Analyst, the conversation usually focuses on technical skills.</p><p>And yes, you should absolutely learn:</p><ul><li>Networking</li><li>Windows and Linux</li><li>SIEM</li><li>EDR</li><li>Threat intelligence</li><li>MITRE ATT&amp;CK</li><li>Detection engineering</li><li>Incident response</li><li>Threat hunting</li><li>Cloud security</li><li>Scripting and automation</li></ul><p>But that’s only one side of the equation.</p><p>The other side includes:</p><figure><img alt="Skill table" src="https://cdn-images-1.medium.com/max/326/1*JffuNAVjdc-atoExu13QcA.png" /><figcaption>Skill Table</figcaption></figure><p>The combination is what makes an analyst truly effective.</p><h3>My Biggest Lesson</h3><p>After spending years working around SOC operations and security investigations, one thing has become increasingly clear to me:</p><p><strong>Technical expertise may get you into cybersecurity. Judgment determines the value you create.</strong></p><p>You can learn another SIEM.</p><p>You can learn another EDR.</p><p>You can memorize hundreds of MITRE ATT&amp;CK techniques.</p><p>You can collect certifications.</p><blockquote>But if you cannot explain what happened, challenge your assumptions, understand business impact, document your investigation, or make a sound decision under pressure, your technical knowledge will have limited value.</blockquote><p>Cybersecurity is ultimately a human discipline supported by technology.</p><p><strong>Tools detect | Processes guide | Data provides evidence | Analysts create understanding | Judgment drives action.</strong></p><h3>Final Thoughts for Anyone Building a SOC Career</h3><p>If you’re preparing for a SOC career, don’t make your learning roadmap only about tools.</p><p>Yes, learn Splunk.</p><p>Learn Microsoft Defender.</p><p>Learn CrowdStrike.</p><p>Learn KQL.</p><p>Learn threat intelligence.</p><p>Learn networking.</p><p>Learn operating systems.</p><p>But at the same time, practice something equally important:</p><p><strong>Learn how to think like an investigator.</strong></p><p>When you investigate an alert, don’t just ask:</p><p>“How do I close this alert?”</p><p>Ask:</p><p>“What actually happened?”</p><p>Don’t just ask:</p><p>“Is this malicious?”</p><p>Ask:</p><p>“What evidence supports that conclusion?”</p><p>Don’t just ask:</p><p>“What does this alert mean?”</p><p>Ask:</p><p>“What does this mean for the business?”</p><p>And don’t just ask:</p><p>“How can I solve this?”</p><p>Ask:</p><p>“What can we improve so this becomes easier to detect and investigate next time?”</p><p>That’s the mindset shift that takes someone from <strong>alert monitoring to security investigation.</strong></p><p>And in my experience, that’s where a SOC Analyst starts becoming truly valuable.</p><p><strong>Great SOC analysts aren’t remembered by how many alerts they closed.</strong></p><p><strong>They’re remembered by the quality of the decisions they made.</strong></p><p><strong>What do you think?</strong></p><p>What skill — technical or non-technical — has made the biggest difference in your SOC or cybersecurity career?</p><p>I’d love to hear your experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=528044d5cd9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Splunk Works Behind the Scenes: Core Components, Deployment Models, and Smart Practices]]></title>
            <link>https://medium.com/@venkatesh0919/splunk-works-behind-the-scenes-core-components-deployment-models-and-smart-practices-0942cf544905?source=rss-57aaadeaddc6------2</link>
            <guid isPermaLink="false">https://medium.com/p/0942cf544905</guid>
            <category><![CDATA[splunk-architecture]]></category>
            <category><![CDATA[blueprint-of-splunk]]></category>
            <category><![CDATA[how-splunk-works]]></category>
            <category><![CDATA[demystifying-splunk]]></category>
            <category><![CDATA[splunk-components]]></category>
            <dc:creator><![CDATA[Venkatesh]]></dc:creator>
            <pubDate>Thu, 28 May 2026 16:18:59 GMT</pubDate>
            <atom:updated>2026-05-28T16:31:39.626Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s digital world, organizations generate massive amounts of machine data every second from servers, applications, firewalls, cloud platforms, and security devices. The challenge is not just collecting this data, but understanding it quickly enough to make better decisions.</p><p><strong>This is where Splunk becomes a game changer.</strong></p><p>Splunk helps organizations search, monitor, analyze, and visualize machine-generated data in real time. Whether you are working in cybersecurity, IT operations, cloud infrastructure, or business analytics, understanding Splunk architecture is an essential skill.</p><p>This guide explains Splunk architecture in a beginner-friendly way while also covering practical insights valuable for experienced professionals.</p><p>Splunk is a scalable data analytics platform used to collect, process, and analyze machine data from multiple sources.</p><p>Instead of manually checking logs from different systems, Splunk centralizes the data and provides real-time visibility through searches, dashboards, alerts, and reports.</p><p>Organizations commonly use Splunk for:</p><blockquote>· Security monitoring and threat detection</blockquote><blockquote>· IT infrastructure monitoring</blockquote><blockquote>· Application troubleshooting</blockquote><blockquote>· Business intelligence and analytics</blockquote><blockquote>· Cloud and IoT monitoring</blockquote><p>Splunk converts raw machine data into meaningful insights that help teams respond faster and make informed decisions.</p><p><strong>Why is Splunk Important?</strong></p><p>Modern environments generate terabytes of logs daily. Without a centralized platform, analyzing this data becomes difficult and time-consuming.</p><p>Splunk solves this problem by offering:</p><p><strong>Real-Time Monitoring</strong></p><p>Splunk continuously analyzes incoming data and can trigger alerts instantly when suspicious or unusual activity occurs.</p><p><strong>Fast Search and Investigation</strong></p><p>Using Splunk Processing Language (SPL), users can quickly search across millions of events in seconds.</p><p><strong>Data Visualization</strong></p><p>Dashboards, charts, and reports make complex data easier to understand for both technical and non-technical teams.</p><p><strong>Scalability</strong></p><p>Splunk can handle growing amounts of data, making it suitable for startups, enterprises, and cloud-native environments.</p><p><strong>Core Components of Splunk Architecture</strong></p><p>Understanding Splunk architecture becomes easier when you think of it as a pipeline:</p><blockquote><strong>Data Collection → Data Processing → Data Storage → Data Search &amp; Visualization</strong></blockquote><h3>Let’s explore each component.</h3><blockquote><strong>Data Sources → Forwarder → Indexer → Search Head ← User</strong></blockquote><h4>1. Forwarder</h4><p>The Forwarder is responsible for collecting logs and sending them to Splunk indexers.</p><p>It acts as the data collection agent installed on endpoints such as:</p><blockquote>· Servers</blockquote><blockquote>· Workstations</blockquote><blockquote>· Firewalls</blockquote><blockquote>· Applications</blockquote><blockquote>· Cloud systems</blockquote><p><strong>Types of Forwarders</strong></p><p><strong>Universal Forwarder (UF)</strong></p><p>The Universal Forwarder is lightweight and designed only to collect and forward data.</p><blockquote>· Minimal resource usage</blockquote><blockquote>· Fast data forwarding</blockquote><blockquote>· Commonly used in production environments</blockquote><p><strong>Heavy Forwarder (HF)</strong></p><p>The Heavy Forwarder performs additional processing before sending data.</p><blockquote>· Parsing and filtering data</blockquote><blockquote>· Routing logs to different destinations</blockquote><blockquote>· Protocol conversions</blockquote><p><strong>When to Use Heavy Forwarder?</strong></p><p>Heavy Forwarders are useful when organizations need advanced data manipulation before indexing.</p><h4>2. Indexer</h4><p>The Indexer is the heart of Splunk architecture.</p><p>Its primary role is to:</p><blockquote>· Receive incoming data</blockquote><blockquote>· Parse and process logs</blockquote><blockquote>· Convert logs into searchable events</blockquote><blockquote>· Store indexed data</blockquote><p><strong>How Indexing Works</strong></p><p>When logs arrive:</p><blockquote>1. Splunk breaks raw data into events</blockquote><blockquote>2. Metadata is added</blockquote><blockquote>3. Data is compressed and indexed</blockquote><blockquote>4. Events become searchable</blockquote><p>Splunk uses an inverted indexing mechanism, which significantly improves search speed and performance.</p><p><strong>Why Indexers Matter</strong></p><p>Without indexing, searching through terabytes of raw logs would be extremely slow. Indexers make real-time investigations possible.</p><h4><strong>3. Search Head</strong></h4><p>The Search Head is the user-facing component of Splunk.</p><p>This is where analysts, engineers, and administrators:</p><blockquote>Run searches, Create dashboards, Build reports</blockquote><blockquote>Configure alerts &amp; Investigate incidents</blockquote><p><strong>How Search Heads Work</strong></p><p>When a user runs a query:</p><p>1. The Search Head distributes the query to multiple indexers</p><p>2. Indexers process the request</p><p>3. Results are returned and combined</p><p>4. The Search Head displays the final output</p><p>This distributed search architecture improves performance and scalability.</p><h4><strong>4. Deployment Server</strong></h4><p>Managing hundreds of Splunk systems manually can become difficult. The Deployment Server helps administrators centrally manage configurations across multiple Splunk instances.</p><p>Key Functions</p><blockquote>· Configuration management</blockquote><blockquote>· App deployment</blockquote><blockquote>· Policy updates</blockquote><blockquote>· Centralized administration</blockquote><p>This ensures consistency across the environment.</p><p><strong>Understanding Splunk Data Flow</strong></p><p>To simplify the architecture, here’s how data moves inside Splunk:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2FkOh-sq1vRerxt5V1fFHA.png" /></figure><p><strong><em>Step-by-Step Flow</em></strong></p><p>Step 1: Data Collection → Forwarders collect logs from devices and applications.</p><p>Step 2: Data Transmission → The collected data is securely sent to Indexers.</p><p>Step 3: Data Indexing → Indexers parse, process, and store the data.</p><p>Step 4: Data Search → Search Heads execute user queries across Indexers.</p><p>Step 5: Visualization &amp; Alerts → Results are displayed through dashboards, reports, and alerts.</p><h4><strong>Splunk Deployment Models</strong></h4><p>Organizations deploy Splunk differently based on their size, infrastructure, and business requirements.</p><p><strong>1.Single Instance Deployment</strong></p><p>In this setup:</p><blockquote>· Search Head</blockquote><blockquote>· Indexer</blockquote><blockquote>· Forwarder</blockquote><p>all run on a single server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Tv99IfJENMYQrPoB120dQ.png" /><figcaption><em>Single Instance Deployment</em></figcaption></figure><p><strong>2. Distributed Deployment</strong></p><p>This is the most common enterprise architecture. Different Splunk components run on separate servers.</p><p>Benefits</p><p>· Scalability</p><p>· Organizations can add more indexers and search heads as data grows.</p><p>· Better Performance</p><p>· Workloads are distributed across multiple systems.</p><p>· High Availability</p><p>· Redundancy reduces downtime risks.</p><p>· Easier Management</p><p>· Dedicated roles improve operational efficiency.</p><p>· Common Enterprise Setup</p><p>· Multiple Forwarders</p><p>· Indexer Cluster</p><p>· Search Head Cluster</p><p>· Deployment Server</p><p>This model is widely used in Security Operations Centers (SOC).</p><p><strong>3. Splunk Cloud Deployment</strong></p><p>Splunk Cloud Platform provides Splunk as a managed cloud service. Organizations do not need to manage infrastructure manually.</p><p>Advantages</p><p>· Reduced Infrastructure Costs</p><p>· No need to purchase or maintain physical servers.</p><p>· Easier Maintenance</p><p>· Splunk handles upgrades and platform management.</p><p>· Faster Deployment</p><p>· Organizations can start quickly.</p><p>· Elastic Scalability</p><p>· Resources scale based on data volume.</p><p>· Challenges</p><p>· Less customization flexibility</p><p>· Dependency on cloud connectivity</p><p>· Shared responsibility model</p><p><strong>Splunk Architecture Best Practices</strong></p><p>Understanding architecture is important, but implementing best practices is what makes Splunk environments successful.</p><p><em>1. Use Universal Forwarders Whenever Possible</em></p><p>Universal Forwarders consume fewer resources and provide better performance for large-scale deployments.</p><p><em>2. Separate Roles in Enterprise Environments</em></p><p>Avoid running Search Heads and Indexers on the same system in production environments.</p><p>Dedicated systems improve stability and scalability.</p><p><em>3. Plan Indexing Strategy Carefully</em></p><p>Proper indexing improves:</p><blockquote>· Search performance</blockquote><blockquote>· Storage management</blockquote><blockquote>· Retention policies</blockquote><blockquote>· Data categorization</blockquote><p>Define indexes based on business requirements and log types.</p><p><em>4. Monitor Splunk Health Regularly</em></p><p>Monitor:</p><blockquote>· CPU utilization</blockquote><blockquote>· Disk storage</blockquote><blockquote>· Search latency</blockquote><blockquote>· Indexing performance</blockquote><blockquote>· Forwarder connectivity</blockquote><p>This helps prevent performance degradation.</p><p><em>5. Implement Role-Based Access Control (RBAC)</em></p><p>Security is critical in Splunk environments.</p><p>Use proper access controls to ensure users can only access authorized data.</p><p><em>6. Optimize Searches</em></p><p>Poorly written SPL queries can slow down the environment.</p><p>Tips</p><blockquote>· Avoid unnecessary wildcards</blockquote><blockquote>· Use indexed fields</blockquote><blockquote>· Limit search time ranges</blockquote><blockquote>· Schedule heavy reports during off-hours</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F6vE2g9CMTAaSALETYMn2Q.png" /><figcaption>Real-World Use Cases of Splunk</figcaption></figure><p><strong>Conclusion</strong></p><p>At the end of the day, Splunk is much more than just a tool for collecting logs it serves as the backbone for modern operational intelligence and resilient security strategies. But its true power isn’t unlocked by default. It requires an understanding of the architecture beneath the surface.</p><p>Whether you are a<strong> SOC Analyst</strong> hunting down advanced threats, a <strong>Security Engineer</strong> building out defensive infrastructure, or a <strong>Cloud Engineer</strong> managing intricate multi-cloud environments, knowing how data moves through Splunk changes how you approach problem-solving. The same goes for <strong>DevOps Teams</strong> optimizing deployment pipelines,<strong> IT Administrators</strong> fighting downtime, and <strong>Data Analysts</strong> turning chaotic machine data into business-shaping insights.</p><p>When you understand the <strong>architecture</strong>, you stop wrestling with the platform and start engineering actual solutions. By mastering these core components, scaling your deployment models thoughtfully, and practicing smart search habits daily, you transform raw, noisy machine data into your organization’s greatest strategic asset.</p><blockquote><em>Thanks for reading! If you found this helpful, feel free to give it some claps and share your own Splunk tips or questions in the comments. Don’t forget to follow for more straightforward, no-nonsense breakdowns of technical architectures.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0942cf544905" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build Your Own SOC Home Lab with Security Onion]]></title>
            <link>https://medium.com/@venkatesh0919/build-your-own-soc-home-lab-with-security-onion-c0e7ccaf6cc1?source=rss-57aaadeaddc6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0e7ccaf6cc1</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[siem]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Venkatesh]]></dc:creator>
            <pubDate>Tue, 17 Jun 2025 15:49:40 GMT</pubDate>
            <atom:updated>2025-06-17T15:49:40.115Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ready to Become a Cyber Defender? Build Your Own SOC Home Lab Today!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/0*YFOxF_UAzCnG6e5e.png" /></figure><p>Ever wondered what it’s like to be on the front lines of cyber defense, hunting down threats and protecting critical data? A career in cybersecurity is more accessible than you think, and the best way to start is by getting hands-on experience. Forget expensive courses — today, we’re going to build your very own Security Operations Center (SOC) right on your computer.</p><p>This guide will walk you through creating a safe, isolated virtual lab where you can learn to use professional-grade security tools, launch simulated attacks, and practice responding to incidents just like a real security analyst.</p><blockquote>What You’ll Build</blockquote><blockquote>Our SOC home lab will consist of three core virtual machines running on your main computer, all connected within their own private network. Check out the blueprint below:</blockquote><h4>Step 1: Gather Your Gear (It’s Mostly Free!)</h4><p>First, let’s make sure your computer is up to the task. You’ll need a machine with a decent multi-core processor, at least <strong>16GB of RAM (32GB is the sweet spot)</strong>, and about <strong>200GB of fast SSD storage</strong>.</p><p>Next, download your software toolkit.</p><p><strong>Always download from these official sources to ensure the files are legitimate and haven’t been tampered with.</strong></p><ul><li><strong>A Hypervisor:</strong> Think of this as the stage for your virtual lab. <a href="https://www.virtualbox.org/wiki/Downloads"><strong>VirtualBox</strong></a> is a fantastic free and open-source option.</li><li><strong>Your Analyst Hub: Ubuntu </strong>as analyst machine to login to<strong> </strong><a href="https://securityonionsolutions.com/software/"><strong>Security Onion</strong></a>, all-in-one cybersecurity Linux distribution. It’s your SIEM, IDS, and network analyzer rolled into one.</li></ul><blockquote><strong>Your “Attacker” Machine:</strong> <a href="https://www.kali.org/get-kali/"><strong>Kali Linux</strong></a> is the industry standard for ethical hacking and penetration testing. You’ll use this to safely simulate threats.</blockquote><ul><li><strong>Your “Vulnerable” Target:</strong> <a href="https://information.rapid7.com/download-metasploitable-2017.html"><strong>Metasploitable</strong></a> / <a href="https://www.vulnhub.com/"><strong>Vulnhub</strong> </a>is a virtual machine intentionally packed with security holes, giving you the perfect, legal target for your practice sessions.</li></ul><h4>Step 2: Build Your Private Digital Playground</h4><p>You wouldn’t test a science experiment in your kitchen without a tray, right? Same principle here.</p><p>We need to create an isolated virtual network to keep our lab activities from spilling over into our home network. In VirtualBox, this is as simple as creating a “Host-only Network.”</p><p>This ensures your Kali machine can only “attack” your Metasploitable machine, and your Security Onion can watch it all happen in a self-contained environment.</p><h4>Step 3: Assemble Your Virtual Machines</h4><p>Now for the fun part! Following the installation guides for each piece of software, you’ll create three separate VMs and connect them to your private network.</p><ol><li><strong>The Security Onion VM</strong> is your command center. Give it the most resources (at least 8GB RAM and 100GB disk space).</li><li><strong>The Kali Linux VM</strong> is your “Red Team” machine.</li><li><strong>The Metasploitable VM</strong> is your “Blue Team” practice target.</li></ol><p>Assign each one a simple, static IP address (like 192.168.56.100, .101, and .102) so they can easily talk to each other.</p><h4>Step 4: Flip the “On” Switch and Watch the Magic</h4><p>With everything set up, it’s time to see if it works. From your Kali Linux VM, launch a simple network scan against your Metasploitable VM using the command nmap -sV [Metasploitable’s IP].</p><p>Now, hop over to your Security Onion VM and open the web console. Head to the “Alerts” dashboard. You should see a flurry of activity! Suricata, the built-in Intrusion Detection System, will have flagged the Nmap scan. Congratulations — you are officially collecting and analyzing security data!</p><h4>Step 5: From Analyst to Threat Hunter</h4><p>Seeing an alert is one thing; knowing what to do with it is everything. This is where you start thinking like a real analyst:</p><ol><li><strong>Triage:</strong> Start with the Nmap alert. What is it telling you?</li><li><strong>Investigate:</strong> Use Security Onion’s powerful tools to pivot from the alert directly to the raw network traffic (PCAP). You can see the exact data packets the “attacker” sent.</li><li><strong>Hunt:</strong> Use the logs to trace the attacker’s every move.</li><li><strong>Respond:</strong> In a real scenario, you’d contain the threat. In our lab, you’ll take it a step further. Use the information you’ve gathered to launch a safe, simulated exploit from Kali against Metasploitable. Watch in Security Onion as the alerts for the <em>actual</em> attack come pouring in.</li></ol><p>By creating this loop — attacking, detecting, and investigating — you’ll gain invaluable, hands-on experience that is essential for any aspiring cybersecurity professional. Welcome to the world of threat hunting!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0e7ccaf6cc1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Comprehensive Phishing Email Analysis Guide]]></title>
            <link>https://medium.com/@venkatesh0919/comprehensive-phishing-email-analysis-guide-90533c39858b?source=rss-57aaadeaddc6------2</link>
            <guid isPermaLink="false">https://medium.com/p/90533c39858b</guid>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[phishing]]></category>
            <category><![CDATA[email-security]]></category>
            <dc:creator><![CDATA[Venkatesh]]></dc:creator>
            <pubDate>Tue, 10 Jun 2025 17:47:47 GMT</pubDate>
            <atom:updated>2025-06-10T17:47:47.879Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D7qbfoQlp6ybxiE3qByWJQ.png" /><figcaption>Analyst Analyzing Phishing email</figcaption></figure><blockquote><strong>Introduction</strong></blockquote><blockquote>Phishing attacks remain one of the most prevalent cybersecurity threats organizations face today. This document provides a detailed approach to analyzing suspicious emails and identifying potential phishing attempts.</blockquote><h3>1. Initial Assessment: Preliminary Identification &amp; Red Flags</h3><p>The first line of defense often starts with a user report or an automated flag. Your initial assessment is a quick, high-level review to determine if an email warrants deeper investigation.</p><p><strong>Steps:</strong></p><ol><li><strong>Check User Report/Automated Flags:</strong> Prioritize emails flagged by users or security systems (e.g., email gateways, EDR).</li><li><strong>Examine Sender Information (Visual Check):</strong></li></ol><ul><li><strong>“From” Name vs. Email Address:</strong> Does the displayed sender name (e.g., “Microsoft Support”) match the actual email address (e.g., &lt;random@suspicious-domain.com&gt;)?</li><li><strong>Domain Scrutiny:</strong> Look for subtle misspellings (typosquatting, e.g., micr0soft.com instead of microsoft.com) or irrelevant domains.</li><li><strong>Reply-To Address:</strong> In your email client, check if the “Reply-To” address is different from the “From” address (this is often visible without opening full headers).</li></ul><p><strong>3. Review Subject Line:</strong></p><ul><li><strong>Urgency/Threats:</strong> Does it demand immediate action, threaten consequences, or promise unrealistic rewards (e.g., “Account Blocked!”, “Urgent Payment!”, “Claim Your Prize!”)?</li><li><strong>Context Mismatch:</strong> Is the subject line irrelevant to your professional context or recent communications?</li><li><strong>Grammar/Spelling Errors:</strong> Frequent typos or awkward phrasing can be strong indicators.</li></ul><p><strong>4. Scan Email Body for Obvious Anomalies (Visual Scan):</strong></p><ul><li><strong>Generic Greetings:</strong> “Dear Customer” instead of your specific name.</li><li><strong>Poor Grammar/Spelling:</strong> Look for consistent errors in the email text.</li><li><strong>Unusual Requests:</strong> Does it ask for sensitive data (passwords, credit card numbers, personal info), or request unusual financial transfers?</li><li><strong>Embedded Links/Attachments:</strong> Note their presence.</li></ul><blockquote><strong><em>CRITICAL: DO NOT CLICK ANY LINKS OR OPEN ANY ATTACHMENTS at this stage.</em></strong></blockquote><p><strong>Key Indicators/Red Flags:</strong></p><ul><li>Mismatched “From” name and email address.</li><li>Suspicious or misspelled domains.</li><li>High sense of urgency, threats, or unrealistic promises.</li><li>Poor grammar, spelling, or unusual phrasing.</li><li>Generic greetings.</li><li>Requests for sensitive information or unusual actions.</li></ul><p><strong>Visual Aid Concept:</strong> A graphic showing a checklist for initial assessment with green/red flags next to common indicators.</p><h3>2. Header Analysis: Unveiling the Email’s True Origin</h3><p>Email headers contain a wealth of metadata that reveals the email’s true path and authentication status. This is crucial for identifying spoofing and determining the sender’s actual origin.</p><p><strong>Steps:</strong></p><ol><li><strong>Extract Full Email Headers:</strong></li></ol><ul><li><strong>Outlook (Desktop):</strong> Open the email, go to File &gt; Properties, then locate the “Internet Headers” section.</li><li><strong>Outlook (Web):</strong> Open the email, click the three dots (…) next to “Reply”, then “View message details” or “View message source”.</li><li><strong>Gmail:</strong> Open the email, click the three vertical dots (⋮) next to the Reply button, then select “Show original”.</li><li><strong>Other Clients:</strong> Look for options like “View Source,” “Message Options,” or “Show Original.”</li></ul><p><strong>2. Analyze Received Headers (Bottom-Up):</strong></p><ul><li>The Received headers form a chain, showing each server the email passed through. <strong>Always read them from the bottom up.</strong> The <em>lowest</em> Received header in the raw source indicates the initial sending server/IP.</li><li><strong>Extract IP Addresses:</strong> Identify the IP addresses listed in each Received header.</li><li><strong>Geolocate IPs:</strong> Use IP lookup tools (whois, ipinfo.io, AbuseIPDB) to determine the geographic location and ISP of the originating IP. Does it match the purported sender’s location?</li><li><strong>Domain/Hostname Mismatch:</strong> Does the hostname or domain associated with the Received IP address align with the sender’s purported domain?</li></ul><p><strong>3. Inspect Sender Authentication Headers:</strong></p><ul><li><strong>Authentication-Results:</strong> This composite header summarizes SPF, DKIM, and DMARC results.</li><li><strong>Received-SPF:</strong></li><li>pass: Sending IP is authorized by the sender’s domain.</li><li>fail: Sending IP is <em>not</em> authorized. Strong indicator of spoofing.</li><li>softfail: Sending IP is not explicitly authorized but not strictly forbidden. Still suspicious.</li><li>neutral/none: Domain doesn’t have an SPF record, or policy is not enforced.</li><li><strong>DKIM-Signature:</strong></li><li>pass: Digital signature is valid, email hasn’t been tampered with.</li><li>fail: Signature is invalid, indicates tampering or misconfiguration.</li><li>none: Domain doesn’t use DKIM.</li><li><strong>DMARC-Authentication-Results:</strong></li><li>pass: Both SPF and DKIM aligned and passed.</li><li>fail: Either SPF or DKIM (or both) failed alignment/authentication. If the domain’s DMARC policy is p=reject or p=quarantine, this email should ideally have been blocked by your mail gateway. Its presence in your inbox is a red flag.</li></ul><p><strong>4. Check Other Potentially Revealing Headers:</strong></p><ul><li><strong>Return-Path:</strong> The address where bounce messages are sent. Often reveals the true sender.</li><li><strong>X-Mailer / User-Agent:</strong> Can indicate the email client or software used to send the email. Unusual entries might be suspicious.</li><li><strong>Message-ID:</strong> A unique identifier. Can be used for tracking or looking up in logs.</li></ul><p><strong>Tools &amp; Techniques:</strong></p><ul><li><strong>Manual Header Inspection:</strong> Understanding the fields is crucial.</li><li><strong>Online Header Analyzers:</strong></li><li><strong>Microsoft Azure Header Analyzer:</strong> <a href="https://mha.azurewebsites.net/">https://mha.azurewebsites.net/</a></li><li><strong>MXToolbox EmailHeaders:</strong> <a href="https://mxtoolbox.com/EmailHeaders.aspx">https://mxtoolbox.com/EmailHeaders.aspx</a></li><li><strong>Gaijin Email Header Analyzer:</strong> <a href="https://www.gaijin.at/en/tools/email-header-analyzer">https://www.gaijin.at/en/tools/email-header-analyzer</a></li><li><strong>IP Lookup Tools:</strong> ipinfo.io, AbuseIPDB</li><li><strong>WHOIS Lookup:</strong> <a href="https://www.whois.com/">https://www.whois.com/</a> (for domain investigation).</li></ul><p><strong>Visual Aid Concept:</strong> An annotated screenshot of a raw email header, highlighting Received, Authentication-Results, and From fields with arrows indicating direction of analysis.</p><h3>3. Body Content Analysis: Dissecting the Message</h3><p>The email body is designed to trick the recipient. A systematic approach helps uncover deceptive elements.</p><p><strong>Steps:</strong></p><ol><li><strong>Examine Language and Tone:</strong></li></ol><ul><li><strong>Urgency/Coercion:</strong> Look for phrases demanding immediate action (“Act now!”, “Reply within 24 hours!”), threats (“Account will be suspended!”), or appeals to fear/greed.</li><li><strong>Emotional Manipulation:</strong> Attempts to evoke panic, excitement, or a sense of duty.</li><li><strong>Grammar, Spelling, Punctuation:</strong> Even sophisticated phishing emails can have subtle grammatical errors or awkward phrasing that legitimate companies usually avoid.</li></ul><p><strong>2. Scrutinize Personalization:</strong></p><ul><li><strong>Generic Greetings:</strong> “Dear Customer,” “Dear User,” “Attention Valued Client.” Legitimate organizations usually use your name if they have it.</li><li><strong>Incorrect Personal Details:</strong> If they attempt personalization but get your name or other details wrong, it’s a huge red flag.</li></ul><p><strong>3. Inspect Formatting and Visuals:</strong></p><ul><li><strong>Company Logos/Branding:</strong> Are logos pixelated, stretched, or loaded from external, non-company domains?</li><li><strong>Mismatched Fonts/Styles:</strong> Inconsistencies in font types, sizes, or colors within the email.</li><li><strong>Embedded vs. Linked Content:</strong> Images or elements that are embedded directly might be less suspicious than those linked from external, unknown sources.</li></ul><p><strong>4. Analyze Call to Action (CTA):</strong></p><ul><li>What is the email asking the recipient to do? (e.g., click a link, open an attachment, reply with info, call a number).</li><li>Does this request align with typical business practices for the purported sender?</li></ul><p><strong>5. Review Footer and Contact Information:</strong></p><ul><li>Does the footer contain standard company information (address, legal disclaimers)? Is it legitimate and consistent?</li><li>Are phone numbers or email addresses provided that are different from the sender’s domain or known company contacts?</li></ul><p><strong>Key Indicators/Red Flags:</strong></p><ul><li>Aggressive, urgent, or threatening language.</li><li>Obvious grammatical and spelling errors.</li><li>Lack of personalization or incorrect personal details.</li><li>Poorly rendered images, logos loaded from external sites.</li><li>Requests for sensitive information via insecure means.</li><li>CTA that deviates from normal procedures (e.g., “click here to verify account”).</li></ul><p><strong>Visual Aid Concept:</strong> Before-and-after screenshots of a phishing email body highlighting deceptive formatting, generic greetings, and suspicious calls to action.</p><h3>4. Link and Attachment Analysis: Safe &amp; Secure Examination</h3><p>This phase carries the highest risk. <strong>Absolutely never directly interact with links or attachments on a production or primary analysis machine.</strong> Always use isolated environments and specialized tools.</p><h4>4.1 Link Analysis:</h4><ol><li><strong>Hover (Don’t Click):</strong></li></ol><ul><li>In your email client, hover your mouse cursor over any embedded links. The actual URL will typically appear in the bottom-left corner of your email client or browser status bar.</li><li>Compare the displayed text of the link (e.g., “Login to Microsoft”) with the actual URL shown on hover (e.g., <a href="http://malicious.xyz/login).">http://malicious.xyz/login).</a> Mismatches are strong indicators.</li></ul><p><strong>2. Identify URL Shorteners:</strong> Be highly suspicious of shortened URLs (bit.ly, tinyurl.com, goo.gl, etc.) as they hide the true destination.</p><p><strong>3. Check for IP Addresses in URLs:</strong> Directly using IP addresses (e.g., <a href="http://192.168.1.100/login)">http://192.168.1.100/login)</a> instead of domain names is often suspicious.</p><p><strong>4. Use Safe URL Analysis Tools (in an isolated environment or dedicated tool):</strong></p><ul><li><strong>VirusTotal (URL Scanner):</strong> Copy the extracted URL and paste it into VirusTotal’s search bar. It will check the URL against numerous blacklists and provide reputation scores.</li><li>Link: <a href="https://www.virustotal.com/">https://www.virustotal.com/</a></li><li><strong>urlscan.io:</strong> Submit the URL to urlscan.io. It will visit the URL in a sandboxed environment, take screenshots, record network requests, and identify redirections, providing a detailed report.</li><li>Link: <a href="https://urlscan.io/">https://urlscan.io/</a></li><li><strong>ExpandURL:</strong> For shortened URLs, use a service like ExpandURL.net to safely resolve the full destination URL.</li><li>Link: <a href="https://www.expandurl.net/">https://www.expandurl.net/</a></li><li><strong>Threat Intelligence Platforms:</strong> Check the URL/domain/IP against internal or external threat intelligence feeds (e.g., IBM X-Force Exchange, Talos Intelligence) to see if it’s already known as malicious.</li></ul><p><strong>Key Indicators/Red Flags for Links:</strong></p><ul><li>Mismatched displayed text and actual URL on hover.</li><li>Use of URL shorteners.</li><li>URLs containing IP addresses instead of domain names.</li><li>Suspicious redirects (revealed by sandbox analysis).</li><li>Known malicious reputation from threat intelligence tools.</li></ul><p><strong>Visual Aid Concept:</strong> A screenshot sequence showing how to hover over a link in Outlook/Gmail to reveal the actual URL, and a flow diagram for using urlscan.io.</p><h4>4.2 Attachment Analysis:</h4><ol><li><strong>Never Open Directly:</strong> <strong>Do not open any suspicious attachments directly on your host machine or standard analysis environment.</strong></li><li><strong>Scrutinize File Types:</strong></li></ol><ul><li>Be extremely wary of executable files (.exe, .scr, .bat, .cmd, .ps1), script files (.js, .vbs), and archive files (.zip, .rar, .7z) that might contain hidden executables.</li><li>Look for double extensions (e.g., invoice.pdf.exe). Windows often hides the real extension, making it appear as invoice.pdf.</li><li>Be cautious of Office documents with macros (.docm, .xlsm) — they are often used for initial infection.</li></ul><p><strong>3. Use Online Sandboxes (Recommended for initial analysis):</strong></p><ul><li><strong>Any.Run:</strong> Upload the attachment to Any.Run for interactive malware analysis in a browser-based sandbox. You can see file system changes, network connections, and process trees in real-time.</li><li>Link: <a href="https://any.run/">https://any.run/</a></li><li><strong>Hybrid Analysis:</strong> Upload the file to Hybrid Analysis (powered by Falcon Sandbox). It executes the file and provides detailed behavioral reports, including TTPs (Tactics, Techniques, and Procedures).</li><li>Link: <a href="https://www.hybrid-analysis.com/">https://www.hybrid-analysis.com/</a></li><li><strong>JoeSandbox:</strong> Another highly regarded automated malware analysis system.</li><li>Link: <a href="https://www.joesandbox.com/">https://www.joesandbox.com/</a></li></ul><p><strong>4. Static Analysis with VirusTotal:</strong> Upload the file to VirusTotal. It will scan the file with numerous antivirus engines and provide hashes (MD5, SHA1, SHA256) and basic static information (e.g., PE file headers).</p><ul><li>Link: <a href="https://www.virustotal.com/">https://www.virustotal.com/</a></li></ul><p><strong>5. Offline Sandbox (for advanced analysis):</strong> For highly sensitive or complex cases, use a dedicated, fully isolated, and revertible virtual machine (e.g., a Flare VM, Remnux, or custom analysis VM) disconnected from all networks for dynamic analysis.</p><p><strong>Key Indicators/Red Flags for Attachments:</strong></p><ul><li>Unexpected file types or double extensions.</li><li>High detection rates on VirusTotal.</li><li>Suspicious behavior observed in sandboxes (e.g., network connections to known bad IPs, process injection, file modifications).</li><li>Macros in Office documents.</li></ul><p><strong>Visual Aid Concept:</strong> A flowchart demonstrating the safe attachment analysis process: “Receive Suspect Attachment -&gt; Upload to Sandbox -&gt; Analyze Report -&gt; Check VirusTotal -&gt; If needed, Offline Lab.” Include icons for different sandbox tools.</p><h3>5. Reporting and Escalation: Incident Closure &amp; Prevention</h3><p>Once a phishing email is confirmed, rapid and accurate reporting and escalation are vital for containment, eradication, and improving future defenses.</p><p><strong>Steps:</strong></p><ol><li><strong>Confirm Phishing:</strong> Based on your analysis, definitively confirm if the email is malicious.</li><li><strong>Document Findings (Incident Report Template):</strong></li></ol><ul><li><strong>Incident ID:</strong> Unique identifier for the incident.</li><li><strong>Analyst Name &amp; Timestamp:</strong> Who identified it and when.</li><li><strong>Source:</strong> How was it reported (user, automated system)?</li><li><strong>Recipient(s):</strong> Who received the email (original recipient, CC/BCC)?</li><li><strong>Sender Details:</strong> Original “From” address, actual originating IP, domain.</li><li><strong>Subject Line:</strong> Full subject.</li><li><strong>Key Indicators:</strong> Summary of suspicious elements found (e.g., DMARC fail, malicious URL, sandbox findings).</li><li><strong>IOCs (Indicators of Compromise):</strong></li><li>Malicious URLs (de-fanged, e.g., hXXps[://]evil[.]com).</li><li>Malicious IP addresses.</li><li>Attachment hashes (MD5, SHA256).</li><li>Malware family (if identified).</li><li><strong>Action Taken:</strong> Initial steps (e.g., confirmed malicious, blocked URL).</li><li><strong>Severity/Impact Assessment:</strong> Estimate potential impact if successful (e.g., credential theft, malware infection).</li><li><strong>Recommendations:</strong> Next steps for IR, blocking, user awareness.</li></ul><p><strong>3. Isolate &amp; Contain (If necessary):</strong></p><ul><li>If the email was clicked or an attachment opened, immediately trigger your organization’s <strong>Incident Response (IR) protocol</strong> for endpoint isolation, containment, and forensics.</li><li>Alert the affected user and instruct them on immediate actions (e.g., password reset).</li></ul><p><strong>4. Escalate to Relevant Teams:</strong></p><ul><li><strong>Email Security/IT Operations:</strong> Provide IOCs (sender, URLs, hashes) for blocking at email gateways, web proxies, and firewalls.</li><li><strong>Endpoint Security Team:</strong> Share IOCs and affected endpoint details for EDR/AV blacklisting and deeper endpoint forensics.</li><li><strong>Threat Intelligence Team (if applicable):</strong> Provide new IOCs for integration into intelligence feeds.</li><li><strong>Management/Leadership:</strong> Inform relevant stakeholders based on incident severity and potential impact.</li></ul><p><strong>5. Communication Protocols for Stakeholders:</strong></p><ul><li><strong>Initial Notification:</strong> Brief, clear, and actionable. State what happened, immediate impact, and what’s being done.</li><li><strong>Regular Updates:</strong> Provide consistent updates on progress, even if it’s “no new information.”</li><li><strong>Final Report:</strong> Summarize the incident, root cause, actions taken, and lessons learned.</li><li><strong>User Awareness:</strong> Potentially trigger a company-wide security awareness notification or targeted training based on the nature of the phishing attempt.</li></ul><p><strong>6. Eradication &amp; Recovery (IR Phase):</strong> Ensure all traces of the phishing attempt and any resulting compromise are removed, and affected systems/users are restored to a secure state.</p><p><strong>7. Lessons Learned:</strong> Conduct a post-incident review to identify gaps in defenses, improve detection rules, and update security awareness training.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90533c39858b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cyber Kill Chain Analysis with Splunk Use Cases]]></title>
            <link>https://medium.com/@venkatesh0919/cyber-kill-chain-analysis-with-splunk-use-cases-8cda44416d47?source=rss-57aaadeaddc6------2</link>
            <guid isPermaLink="false">https://medium.com/p/8cda44416d47</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[splunk]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Venkatesh]]></dc:creator>
            <pubDate>Tue, 15 Apr 2025 14:43:14 GMT</pubDate>
            <atom:updated>2025-04-15T14:43:14.020Z</atom:updated>
            <content:encoded><![CDATA[<p>Understanding the Cyber Kill Chain with Splunk Use Cases</p><p><strong>Summary:</strong><br>The Cyber Kill Chain is a critical framework for security analysts, offering a structured approach to understanding cyberattacks. This blog explores its seven stages, illustrating how each phase can be identified within security logs using Splunk queries. By leveraging these analytical techniques, security professionals can improve threat detection, enhance response strategies, and fortify overall cybersecurity defenses. Practical use cases highlight how Splunk facilitates real-time detection and investigation, making the Cyber Kill Chain an essential methodology for effective security operations and incident response.</p><p><strong>Key Concepts:</strong></p><p>The excerpt clearly outlines the seven stages of the Cyber Kill Chain, providing a brief description and a corresponding Splunk use case for each:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tFYAjju4bNqQ_F6Cg-hddw.png" /></figure><p><strong>1. Reconnaissance: </strong>This is the initial phase where attackers gather information about the target. The example provided focuses on identifying unusual web traffic patterns.</p><p><em>◦ Splunk Use Case: index=weblogs source=”*access.log” | stats count by clientip — This query is designed to “Identify abnormal web traffic spikes for potential reconnaissance.” It aggregates web access logs by client IP address to reveal potentially suspicious increases in activity from a single source.</em></p><p><strong>2. Weaponization:</strong> In this stage, attackers create a deliverable exploit and backdoor. The excerpt’s example focuses on detecting allowed firewall connections with known malware signatures.</p><p><em>◦ Splunk Use Case: index=firewall_logs action=”allowed” signature=”malware” — This query aims to “Monitor firewall logs for allowed connections with malware signatures.” It searches firewall logs for connections that were allowed despite containing a signature identified as malware.</em></p><p><strong>3. Delivery: </strong>This involves transmitting the weaponized payload to the target. The example highlights the detection of emails with executable attachments.</p><p><em>◦ Splunk Use Case: index=email_logs event_type=”delivery” attachment=”*.exe” — This query is designed to “Detect email deliveries with executable attachments.” It searches email logs for events indicating successful delivery of emails containing files with the “.exe” extension, which can often be malicious.</em></p><p><strong>4. Exploitation:</strong> This stage involves leveraging a vulnerability to gain unauthorized access. The example focuses on identifying successful network logins on Windows systems.</p><p><em>◦ Splunk Use Case: index=security_logs sourcetype=”windows” EventCode=4624 “Logon Type”=3 — This query is intended to “Identify successful network logins on Windows systems.” It looks for Windows security logs with Event Code 4624 (an account was successfully logged on) and a “Logon Type” of 3, which typically indicates a network logon attempt.</em></p><p><strong>5. Installation:</strong> This involves installing a persistent backdoor or implant on the compromised system. The example focuses on monitoring for the creation of executable files in a common program data directory.</p><p><em>◦ Splunk Use Case: index=endpoint_logs action=”file_created” path=”C:\\ProgramData\\*.exe” — This query is designed to “Monitor endpoint logs for executable file creation.” It searches endpoint logs for events indicating the creation of files with the “.exe” extension within the C:\ProgramData\ directory, a location often used by malware for persistence.</em></p><p><strong>6. Command and Control (C2)</strong>: This stage establishes a communication channel between the attacker and the compromised system for remote control and data manipulation. The example focuses on detecting connections to known C2 servers.</p><p><em>◦ Splunk Use Case: index=network_traffic dest_ip=”known_C2_server” — This query aims to “Detect connections to Command and Control servers.” It searches network traffic logs for connections where the destination IP address matches a known Command and Control server.</em></p><p><strong>7. Actions on Objectives</strong>: This is the final stage where the attacker achieves their intended goal, such as data exfiltration, disruption, or financial gain. The example focuses on looking for logs indicating data exfiltration patterns.</p><p><em>◦ Splunk Use Case: index=security_logs action=”data_exfiltration” — This query is designed to “Look for logs indicating data exfiltration patterns.” While the query itself is broad, it highlights the need to identify specific log events or patterns that signify data leaving the protected environment.</em></p><p><strong>Cyber Kill Chain Questions:</strong></p><p><strong>1. What is the fundamental purpose of understanding the Cyber Kill Chain for a security analyst?</strong></p><p><em>Understanding the Cyber Kill Chain helps security analysts systematically analyze and understand the different stages of a cyberattack, enabling them to proactively detect, prevent, and respond to threats more effectively.</em></p><p><strong>2. Describe the Reconnaissance phase of the Cyber Kill Chain and provide an example Splunk use case for detecting it.</strong></p><p><em>The Reconnaissance phase involves an attacker gathering information about the target. The Splunk use case index=weblogs source=”*access.log” | stats count by clientip helps identify abnormal web traffic spikes, which could indicate an attacker probing the target’s web infrastructure.</em></p><p><strong>3. Explain the Weaponization phase and how the provided Splunk query helps identify potential instances of it.</strong></p><p><em>The Weaponization phase involves an attacker pairing an exploit with a payload, such as malware. The Splunk query index=firewall_logs action=”allowed” signature=”malware” monitors firewall logs for allowed connections that have been identified as containing malware signatures, suggesting a potentially weaponized payload was delivered.</em></p><p><strong>4. What activity is characteristic of the Delivery phase, and what Splunk query could help an analyst detect this type of event?</strong></p><p><em>The Delivery phase is when the attacker transmits the weaponized payload to the target environment. The Splunk query index=email_logs event_type=”delivery” attachment=”*.exe” helps detect emails that were successfully delivered and contained executable attachments, a common method for delivering malicious payloads.</em></p><p><strong>5. Describe the Exploitation phase and what the given Splunk query for this stage is designed to identify on Windows systems.</strong></p><p><em>The Exploitation phase is when the attacker uses a vulnerability to gain unauthorized access to a system. The Splunk query index=security_logs sourcetype=”windows” EventCode=4624 “Logon Type”=3 identifies successful network logins on Windows systems, which could indicate an attacker successfully exploiting a vulnerability to gain access.</em></p><p><strong>6. What kind of activity occurs during the Installation phase, and how can Splunk help monitor for potential malicious installation?</strong></p><p><em>During the Installation phase, the attacker installs persistent access mechanisms on the compromised system. The Splunk query index=endpoint_logs action=”file_created” path=”C:\\ProgramData\\*.exe” monitors endpoint logs for the creation of executable files in common persistent locations, which could signal malicious software being installed.</em></p><p><strong>7. Explain the Command and Control phase and how the provided Splunk query assists in identifying this type of network activity.</strong></p><p><em>The Command and Control (C2) phase involves the attacker establishing communication with the compromised system to remotely control it. The Splunk query index=network_traffic dest_ip=”known_C2_server” detects network traffic going to known Command and Control server IP addresses, indicating a potential C2 connection.</em></p><p><strong>8. What does the “Actions on Objectives” phase signify in the context of a cyberattack, and what type of log data might indicate this?</strong></p><p><em>The “Actions on Objectives” phase is the stage where the attacker achieves their intended goal, such as data theft or system disruption. The Splunk query index=security_logs action=”data_exfiltration” looks for log entries that indicate patterns of data being copied or transferred out of the network, suggesting the attacker is acting on their objectives.</em></p><p><strong>9. Briefly describe the relationship between Splunk use cases and the stages of the Cyber Kill Chain as illustrated in the source.</strong></p><p><em>The provided Splunk use cases offer practical examples of how security analysts can leverage a Security Information and Event Management (SIEM) system like Splunk to monitor for specific activities and indicators associated with each distinct stage of the Cyber Kill Chain.</em></p><p><strong>10. Why is it beneficial for a security operations center (SOC) to utilize the Cyber Kill Chain framework?</strong></p><p><em>Utilizing the Cyber Kill Chain framework provides a structured approach for the SOC to understand attack progression, prioritize alerts based on the stage of an attack, develop targeted detection rules and threat intelligence, and improve incident response efforts.</em></p><p><strong>Conclusion</strong>:</p><p>This exploration has effectively introduced the Cyber Kill Chain as a fundamental framework for understanding and combating cyber threats. By demonstrating its practical application within a Security Operations Center (SOC) environment, particularly through the lens of Splunk, we’ve showcased how security analysts can transform raw log data into actionable intelligence. The concrete Splunk query examples provided for each stage of the Kill Chain serve as valuable tools, empowering both novice and seasoned analysts to proactively detect and comprehend the step-by-step progression of a cyberattack. Ultimately, leveraging such methodologies and tools is crucial for enhancing detection capabilities and fortifying an organization’s defenses against the ever-evolving landscape of cyber threats.</p><p><strong>Glossary of Key Terms</strong></p><p>• <strong>Cyber Kill Chain: </strong>A cybersecurity framework developed by Lockheed Martin that outlines the seven stages an attacker typically goes through during a targeted cyber intrusion.</p><p>• <strong>Security Analyst: </strong>A professional responsible for monitoring and analyzing security events, investigating security incidents, and implementing security measures to protect an organization’s assets.</p><p>• <strong>SOC (Security Operations Center):</strong> A centralized unit within an organization that deals with security issues on an organizational and technical level.</p><p>• <strong>Splunk: </strong>A software platform widely used for searching, monitoring, and analyzing machine-generated data, including security logs.</p><p>• <strong>Use Case:</strong> A specific scenario or application of a tool or technique to achieve a particular objective, in this context, using Splunk queries to detect specific stages of the Cyber Kill Chain.</p><p>• <strong>Reconnaissance: </strong>The initial phase of an attack where the attacker gathers information about the target.</p><p>• <strong>Weaponization:</strong> The phase where an attacker creates a deliverable exploit and backdoor.</p><p>• <strong>Delivery:</strong> The phase where the attacker transmits the weaponized payload to the target.</p><p>• <strong>Exploitation:</strong> The phase where the attacker uses a vulnerability to gain unauthorized access.</p><p>• <strong>Installation:</strong> The phase where the attacker installs persistent access mechanisms on the compromised system.</p><p>• <strong>Command and Control (C2):</strong> The phase where the attacker establishes communication with and remotely controls the compromised system(s).</p><p>• <strong>Actions on Objectives: </strong>The final phase where the attacker achieves their intended goal, such as data exfiltration or system disruption.</p><p>• <strong>Web Logs: </strong>Records of activity on a web server, often including information about requests, responses, and client IP addresses.</p><p>• <strong>Firewall Logs:</strong> Records of network traffic that has passed through or been blocked by a firewall.</p><p>• <strong>Malware Signature:</strong> A unique pattern or code associated with a known piece of malicious software.</p><p>• <strong>Email Logs:</strong> Records of email activity, including information about senders, recipients, and attachments.</p><p>• <strong>Executable Attachment (.exe):</strong> A file format that can contain and execute program code, often used to deliver malware.</p><p>• <strong>Security Logs:</strong> Comprehensive records of security-related events on a system or network.</p><p>• <strong>Logon Type=3 (Network Logon):</strong> In Windows security logs, this event code indicates a successful logon attempt made over the network.</p><p>• <strong>Endpoint Logs: </strong>Records of activity occurring on individual user devices or servers.</p><p>• <strong>Network Traffic:</strong> The flow of data across a network.</p><p>• <strong>Destination IP (dest_ip):</strong> The Internet Protocol address of the system receiving network traffic.</p><p>• <strong>Data Exfiltration:</strong> The unauthorized transfer of sensitive data from an organization’s network.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8cda44416d47" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LetsDefend — SOC119 — Proxy — Malicious Executable File Detected]]></title>
            <link>https://medium.com/@venkatesh0919/letsdefend-soc119-proxy-malicious-executable-file-detected-abbfc314cb16?source=rss-57aaadeaddc6------2</link>
            <guid isPermaLink="false">https://medium.com/p/abbfc314cb16</guid>
            <category><![CDATA[lets-defend]]></category>
            <category><![CDATA[letsdefendio]]></category>
            <category><![CDATA[analysis]]></category>
            <category><![CDATA[siem]]></category>
            <category><![CDATA[investigation]]></category>
            <dc:creator><![CDATA[Venkatesh]]></dc:creator>
            <pubDate>Tue, 07 Jan 2025 15:06:33 GMT</pubDate>
            <atom:updated>2025-01-07T15:06:33.945Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>LetsDefend — SOC119 — Proxy — Malicious Executable File Detected</strong></h3><p>This is a walkthrough for the “<strong>SOC119 — Proxy — Malicious Executable File Detected” </strong>alert on <strong>LetsDefend </strong>and it is “<strong>Medium” </strong>priority alert. If you are searching for this alert, then you will need to look for <strong>EventID 83</strong>.</p><p>On Practice use the <strong>Main channel</strong> to assign it to self. Once it is assigned use <strong>investigation channel</strong> for alert details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*bOgvmzhgh-PKZeDeKchV3Q.png" /></figure><p>Let’s begin our investigation by checking the alert details from the investigation channel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PPKIELDo9r0LsKIOEm_h1w.png" /></figure><p>Source Address: 172.16.17.5<br>Destination Address: 51.195.68.163<br>Request URL: hxxps://www.win-rar.com/postdownload.html?&amp;L=0&amp;Version=32bit<br>Device Action: Allowed</p><p>Its time to begin the investigation with the available information. Search the “<strong>Log management</strong>” tab for additional information about the connections by using the filter option and feed the “<strong>Source IP</strong>” &amp; “<strong>Destination IP</strong>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W6hCMhS3S9L2luFWAhtfYQ.png" /></figure><p>We got the requested URL from the logs present in the Log management tab, We could see that the request is GET and Device action is Allowed. Let’s do a OSINT investigation on the URL we got from the Log. I used the following websites;</p><h4><strong>AnyRun<br>VirusTotal<br>URLHouse<br>URLScan</strong></h4><p>VirusTotal: <a href="https://www.virustotal.com/gui/url/bc62b755250c21cf885d35ec4eac37a7fb5faf373f9786074dc33ad997286841">https://www.virustotal.com/gui/url/bc62b755250c21cf885d35ec4eac37a7fb5faf373f9786074dc33ad997286841</a></p><p>URLScan: <a href="https://urlscan.io/result/ae052611-a7ad-4887-a254-97be9b6beb11/">https://urlscan.io/result/ae052611-a7ad-4887-a254-97be9b6beb11/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K4l9wfhB2GMeRKc_CjwEuQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lRrIS-m_m7miLVwRDnCWLQ.jpeg" /><figcaption>URLScan &amp; Virustotal</figcaption></figure><p>Once the requested URL is submitted in URLscan.io, the screenshot is the result for the redirected URL. This confirms that the URL is Legit and redirecting to the Win-RAR download free and support post download webpage.</p><p><strong><em>The investigation confirms that the requested URL results in legitimate Win-RAR website download webpage. This is a clear indication that it is confirmed to be False positive.</em></strong></p><p><em>LetsDefend Questions:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/751/1*JaelbdpJB0FVaLeQ6EVtaA.png" /></figure><ol><li><em>Analyze the URL Address</em></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/787/1*7K6cso3RbZ6sCxpVFUPQQg.png" /></figure><p>Ans: Non-Malicious</p><p><em>Add Artifacts</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*HYB4biRJse_rBk5-HQdSxQ.png" /><figcaption>Artifacts</figcaption></figure><p><em>Analyst Note</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/737/1*wAeskUHIC9Q_P2hdpj10UQ.png" /><figcaption>Analyst Notes</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/1*DLTVFAsnI6zcThWHynLtWQ.png" /></figure><p><em>Closing note for the Alert</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/1*ZwnV9SkJN1eBJlBOQLJkIg.png" /></figure><p>The result once the alert is closed</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LowUQOXPn-sTO4vMl-dclQ.png" /></figure><p><em>Lets meet in another </em><strong><em>Alert walkthrough</em></strong><em> until then its </em>V<em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abbfc314cb16" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pocket Pal AI: Your personal AI assistant for Mobile]]></title>
            <link>https://medium.com/@venkatesh0919/pocket-pal-ai-your-personal-ai-assistant-for-mobile-15573dbb152b?source=rss-57aaadeaddc6------2</link>
            <guid isPermaLink="false">https://medium.com/p/15573dbb152b</guid>
            <category><![CDATA[hugging-face]]></category>
            <category><![CDATA[pocketpal]]></category>
            <category><![CDATA[tiny-ai]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[chatgpt]]></category>
            <dc:creator><![CDATA[Venkatesh]]></dc:creator>
            <pubDate>Sun, 22 Dec 2024 18:03:01 GMT</pubDate>
            <atom:updated>2024-12-22T18:03:01.055Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QSI8a4q36Hy_o0R-pqaHqw.png" /><figcaption>Tiny AI</figcaption></figure><p>After using this application for a day i thought of writing a small blog around this to spread this as it is useful as once the models are downloaded you don&#39;t need internet.</p><p><strong>Pocket Pal: Your Tiny Chat-GPT Companion on Your Phone</strong></p><p>In today’s digital world, access to information and assistance is crucial, but not everyone has the luxury of reliable internet connectivity or high-end devices. This challenge is especially significant in tier-3 rural areas where internet access is limited. However, a new open-source mobile application called <strong>Pocket Pal</strong> is here to bridge that gap, offering a powerful and accessible AI companion right in your pocket.</p><p><strong>The Innovation Behind Pocket Pal</strong></p><p>Pocket Pal is the brainchild of a forward-thinking developer “<a href="https://medium.com/@ghorbani59/about"><strong>Asghar Ghorbani</strong></a>” who saw the need for an AI solution that works offline and is accessible to a broader audience. Unlike traditional AI applications that rely on continuous internet connectivity, Pocket Pal utilizes smaller, optimized versions of popular AI models like <strong>Llama, H2O, Phi </strong>and <strong>Gemma</strong>. These models are tailored to run smoothly on your phone’s hardware, meaning you don’t need a high-end device to enjoy AI assistance. Even a phone with just <strong>4 GB o</strong>f RAM can handle Pocket Pal effortlessly.</p><p><strong>Getting Started with Pocket Pal</strong></p><p>Getting started with Pocket Pal is a breeze:</p><p><strong>Download the Pocket Pal</strong></p><ul><li>iPhone users can grab it here: <a href="https://apps.apple.com/us/app/pocketpal-ai/id6502579498">PocketPal AI on the App Store</a></li><li>Android users, please head over to <a href="https://play.google.com/store/apps/details?id=com.pocketpalai">PocketPal AI on Google Play</a></li></ul><p><strong>Choose and download the AI model</strong> you want to use from within the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/1*DfKSUrSdRUpFG4HiyT8J4w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*BkW9Fuc9OlZZk7cpgYwbBg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/776/1*tHOvo857SW2n7UktHuwIXw.jpeg" /><figcaption>PocketPal AI</figcaption></figure><p><strong>Start interacting</strong>! You can click and try out different responses to see how the AI performs.</p><p>The best part? Pocket Pal processes your requests in milliseconds, providing you with quick and efficient responses. Since all processing happens locally on your device, your chats and prompts never leave your phone. This means there’s no cloud server storing your data, ensuring maximum privacy and security.</p><p><strong>A Solution for Rural Areas</strong></p><p>Pocket Pal is a game-changer for tier-3 rural areas with limited internet access. By allowing users to interact with AI without needing an internet connection, it empowers individuals to access information and assistance whenever they need it. Whether it’s for educational purposes, personal assistance, or just casual conversation, Pocket Pal is a reliable companion that fits right in your pocket.</p><p><strong>Conclusion</strong></p><p>Pocket Pal represents a significant step forward in making AI accessible to everyone, regardless of their location or the sophistication of their device. With its offline capabilities and focus on privacy, it ensures that you have a powerful AI companion at your fingertips, ready to assist you whenever you need it. So, go ahead and download Pocket Pal today — your personal AI assistant awaits!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15573dbb152b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LetsDefend — SOC101 — Phishing Mail Detected]]></title>
            <link>https://medium.com/@venkatesh0919/letsdefend-soc101-phishing-mail-detected-6cab60c623de?source=rss-57aaadeaddc6------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cab60c623de</guid>
            <category><![CDATA[letsdefendio]]></category>
            <category><![CDATA[lets-defend]]></category>
            <dc:creator><![CDATA[Venkatesh]]></dc:creator>
            <pubDate>Tue, 10 Dec 2024 13:46:34 GMT</pubDate>
            <atom:updated>2025-01-07T14:05:56.013Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>LetsDefend — SOC101 — Phishing Mail Detected</strong></h3><p>This is a walkthrough for the <strong>SOC101- Phishing mail Detected </strong>alert on <strong>LetsDefend </strong>and it is “<strong>Medium” </strong>priority alert. If you are searching for this alert, then you will need to look for <strong>EventID 87</strong>.</p><p>On Practice use the <strong>Main channel</strong> to assign it to self. Once it is assigned use <strong>investigation channel</strong> for alert details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ky0_BxUovCEFoQqUz4y6CQ.png" /></figure><p>Lets begin our investigation by checking the alert details from the investigation channel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*OvDIpYkHIUxNbfSclJdTYw.png" /></figure><p>Source Address : lethuyan852[@]gmail[.]com<br>Destination Address : mark[@]letsdefend[.]io<br>E-mail Subject : Its a Must have for your Phone<br>Device Action : Allowed</p><p>Start the investigation with the available information. Search the “<strong>Email security</strong>” tab for additional information about the suspicious email.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*zptkNfbhWqLxg7KL4VdNmw.png" /><figcaption>Email Security</figcaption></figure><p>Use the detailed search option to narrow down the search. Add <strong>Sender</strong>, <strong>Recipient email ID and Subject </strong>of the email to get the actual email received by the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*i-nHYpPRyGgGH1UUf-nGXw.png" /><figcaption>Email Security</figcaption></figure><p>We got the actual email from the Email security tab, the content of the email contains a <strong>link</strong>, which seems to be suspicious. Lets use the OSINT tools to check the reputation of the URL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*wS-Sxs9qL1zGSp9GInrFfA.png" /><figcaption>Actual Email</figcaption></figure><p>Used Virustotal for URL analysis hxxp://nuangaybantiep[.]xyz [URL Defaced]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XWrqHtXvLxXoHOdc1suMxw.png" /></figure><p>Lets analyze the SMTP server IP <strong>146[.]56[.]195[.]192</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7QNQste31UCg3QYwZTksYg.png" /></figure><p>The above analysis confirms that the SMTP server IP is not relevant to Gmail as the IP is flagged as malicious by several vendors and it belongs to China as highlighted in the above screenshot.</p><p><strong><em>This is a clear indication that attacker user Email spoofing technique to deceive the Recipient to make the user access the link.</em></strong></p><p>LetsDefend Questions:</p><ol><li>Are there attachments or URLs in the email? : Yes</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/1*EFYqyYKPkpAcKCDg4m-EzQ.png" /></figure><p>2. Analyze URL/Attachment : Malicious</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*3YbcIHymupaRig4sJuiPBQ.png" /></figure><p>3. Check If Mail Delivered to User? : We can check the alert to see if it is delivered or not</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*dYClFqS3FKYKqYha0bOOBw.png" /><figcaption>Investigation channel</figcaption></figure><p>From the above information it is evident that the Device action is allowed confirms that the email is <strong>Delivered</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*w6tMXQ-5yabxN8WIuz19Ew.png" /></figure><p>4. Check If Someone Opened the Malicious File/URL?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/1*sNaRCAZf3I5dR4k1xetdlA.png" /></figure><p>To answer this question lets use log management to find.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*3S8dIHcxkk7lcDvv0dpGcg.png" /><figcaption>Log management</figcaption></figure><p>Answer is : <strong>Yes</strong></p><p>This is the step where we need to find the recipient IP address to contain the system as the user who accessed the link.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/1*kvGYHiXLrDr_msck_vXGAw.png" /></figure><p>To find the IP address used Log management and found the source IP address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/462/1*ir0VLAa_Hf-vv7TKvxNjCQ.png" /><figcaption>Log management</figcaption></figure><p>From Endpoint Security Tab found the user machine and contained it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*JMOzwqiMDCcQK-b_vMy1lA.png" /><figcaption>Endpoint Security</figcaption></figure><p>Adding the Artifacts to the case notes:</p><p>Sender Email: lethuyan852[@]gmail[.]com<br>SMTP Server Address: 146[.]56[.]195[.]192<br>Malicious URL: hxxp://nuangaybantiep[.]xyz</p><p>Once the artifacts is added close the case as <strong>True positive </strong>with proper investigation notes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/558/1*0N4LhOdu4Tv1GukxAKIkoQ.png" /></figure><p>Here we go the result is all Green.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iYxqhiBZxuia7lS_4f-yHw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cab60c623de" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>