<?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 Vignesh Ambaykar on Medium]]></title>
        <description><![CDATA[Stories by Vignesh Ambaykar on Medium]]></description>
        <link>https://medium.com/@vignesh3967?source=rss-80ac91a923e6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*VKdG_aDDqMe-ZMWpa4azxQ.jpeg</url>
            <title>Stories by Vignesh Ambaykar on Medium</title>
            <link>https://medium.com/@vignesh3967?source=rss-80ac91a923e6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:03:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vignesh3967/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[T-Pot Honeypot Deployment]]></title>
            <link>https://medium.com/@vignesh3967/t-pot-honeypot-deployment-dcfa9f9f54b1?source=rss-80ac91a923e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcfa9f9f54b1</guid>
            <category><![CDATA[honeypot]]></category>
            <dc:creator><![CDATA[Vignesh Ambaykar]]></dc:creator>
            <pubDate>Tue, 23 Sep 2025 10:29:19 GMT</pubDate>
            <atom:updated>2025-09-23T10:29:19.182Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Collect real‑world attack telemetry in a safe, isolated sandbox — then explore it in Kibana and learn how honeypots behave.</em></p><p><strong>Intro — why honeypots matter</strong></p><p>A <strong>honeypot</strong> is a deliberately exposed system or service meant to attract attackers so you can study their behaviour, gather telemetry, and improve detection and response. Think of it as a controlled microscope for attacker activity: instead of attempting to block every probe, you invite the noise in a safe place and learn from it.</p><p><strong>Cybersecurity teams use honeypots to:</strong></p><ul><li>Detect novel tooling and campaigns before they hit production.</li><li>Collect realistic attack telemetry (payloads, commands, IPs, TTPs) for threat intelligence and threat hunting.</li><li>Validate detection rules by testing if your SIEM/EDR flags actual malicious behaviour.</li><li>Train analysts with real alerts and investigation scenarios in a low‑risk environment.</li></ul><p>Honeypots are best‑used as a supplemental data source — they do not replace perimeter defences — but they provide high‑fidelity signals that are hard for attackers to fake.</p><p><strong>How Honeypots Work in Real Life</strong></p><p>When you put a system on the internet, it doesn’t take long before someone — or something — comes knocking. Honeypots are designed to <strong>welcome those knocks</strong> in a safe, controlled way. Here’s how the flow typically works:</p><ol><li><strong>The Attacker Scans the Internet</strong><br> Automated bots, scanners, or human attackers continuously probe the internet for open ports and weak services.</li><li><strong>The Honeypot Pretends to Be a Target</strong><br> Instead of giving them a real production server, the honeypot mimics common services (SSH, HTTP, SMB, IoT, databases). To the attacker, it looks real.</li><li><strong>Every Action Gets Captured</strong><br> Login attempts, commands, exploit payloads, even malware download attempts are all recorded. Nothing goes unnoticed.</li><li><strong>Logs Are Centralized</strong><br> The honeypot sends this telemetry into a logging/analysis platform (in T-Pot’s case, <strong>Elasticsearch + Kibana</strong>).</li><li><strong>Security Teams Learn From It<br></strong>• Spot brute force attempts, SQL injection payloads, or IoT malware campaigns.<br>• Generate Indicators of Compromise (IOCs).<br>• Test if SIEM rules would actually catch these behaviours.<br>• Train analysts with real attacker data — but in a safe sandbox.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/811/1*uwxAe1SNtgXeNjqG_ivx2Q.png" /></figure><p><strong>What is T‑Pot and why I chose it</strong></p><ul><li>A multi‑sensor setup out of the box — you get many honeypots running together, saving setup time.</li><li>Centralized telemetry in Elasticsearch with Kibana dashboards for quick analysis.</li><li>A web UI &amp; attack map that makes results accessible to non‑technical audiences.</li><li>A community maintained installer — repeatable installs and sensible defaults.</li></ul><p>For this project I chose T‑Pot because it provides a production‑adjacent, fully integrated environment quickly: it’s ideal when you want to collect diverse attack telemetry and understand how honeypots actually work, without building and connecting individual ones manually.</p><p><strong>What you’ll build</strong></p><ul><li>A cloud VM (DigitalOcean droplet) running T‑Pot, a curated collection of honeypots bundled with Docker and an Elastic stack.</li><li>The full Hive profile (attack map, Kibana, ElasticVue, CyberChef, SpiderFoot).</li><li>A hardened, non‑root admin user and a non‑default SSH port (set automatically by T‑Pot).</li><li>A starting point to store and explore logs locally.</li></ul><p><strong>Ethics &amp; safety</strong></p><ul><li>Only deploy on infrastructure you control.</li><li>Isolate it from anything sensitive — this box is designed to be <em>attacked</em>.</li><li>Use unique credentials. Expect and plan for compromise of the honeypot.</li></ul><p><strong>Prerequisites</strong></p><ul><li>A DigitalOcean account (Vultr work too steps are similar).</li><li>An SSH client (Terminal, PowerShell).</li><li>Budget for a VM sized ~4 vCPU / 8 GB RAM (the full Hive profile is heavy).</li></ul><h4><strong>Step 1 — Create the droplet</strong></h4><ol><li>In DigitalOcean, click Create → Droplets.</li><li>Datacenter: pick the closest region (I used Bangalore).</li><li>Image: Ubuntu 24.04 LTS.</li><li>Plan: Regular / Basic. For reliability choose 4 vCPU, 8 GB RAM. (You can upsize later.)</li><li>Authentication: Password or SSH key (keys recommended).</li><li>Hostname: e.g., HoneyPot-Project</li><li>Leave firewalls off for now (honeypots need to be reachable). You can later add a cloud firewall that still exposes common ports while restricting management access.</li><li>Click Create Droplet.</li></ol><p><strong>Note: </strong>Cloud firewalls can co‑exist with honeypots, but don’t block the ports the honeypots expose, or you’ll starve the telemetry.</p><h4><strong>Step 2 — First SSH &amp; system update</strong></h4><p><strong>From your machine:</strong></p><pre>ssh root@&lt;PUBLIC_IP&gt;</pre><p><strong>Then update:</strong></p><pre>apt-get update &amp;&amp; apt-get upgrade -y</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DI0ON803imSfic--zT4pww.png" /></figure><h4><strong>Step 3 — Create a non‑root sudo user</strong></h4><pre>adduser zenitsu<br>usermod -aG sudo zenitsu<br>su - zenitsu</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SzkHpiakDnhsv-P182FjlA.png" /></figure><p><strong>Confirm:</strong></p><pre>whoami # should print: zenitsu</pre><h4><strong>Step 4 — Install T‑Pot (Hive profile)</strong></h4><p>Clone and run the installer:</p><pre>cd ~<br>git clone https://github.com/telekom-security/tpotce.git<br>cd tpotce<br>sudo ./install.sh</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZEuUmZrhtJnafK51BG3A6A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LqSonKKErmkFi73PX7mZGA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u-dV1v1Id6LgEquNFQ1wVw.png" /></figure><p><strong>During the wizard:</strong></p><ul><li>When asked for install type, choose H (Hive) for the standard, full install.<br> Other options include Mini (lighter), Mobile, Tarpit, and LLM Sensor (fun to try later).</li><li>Set a web UI username/password (separate from your SSH password unless you choose to reuse it).</li><li>Heads‑up: the installer will change your SSH port to 64295.</li></ul><p>When the script completes, you’ll be prompted to reboot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FuKXWY5jc1F0YtRGPZfNOw.png" /></figure><h4><strong>Step 5 — Reboot &amp; reconnect on the new SSH port</strong></h4><pre>sudo reboot<br># wait ~60–90 seconds<br>ssh -p 64295 root@&lt;PUBLIC_IP&gt;</pre><h4><strong>Step 6 — Verify &amp; (if needed) restart T‑Pot</strong></h4><p>Sometimes services need a nudge after first boot or a resize:</p><pre>sudo systemctl status tpot<br>sudo systemctl restart tpot<br>sudo systemctl status tpot</pre><p>You should see active (running).</p><h4><strong>Step 7 — Log into the web UI</strong></h4><p>Open your browser and visit:</p><pre>https://&lt;PUBLIC_IP&gt;:64297</pre><ul><li>Accept the self‑signed certificate warning (Advanced → Proceed).</li><li>Sign in with the web UI credentials you created during install.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZqR0pcQrG66d53DQfwlc6w.png" /></figure><p><strong>You’ll see:</strong></p><ul><li><strong>Attack Map —</strong> the classic “pew‑pew” globe/flows that execs love.</li><li><strong>Kibana —</strong> search &amp; visualize logs from the honeypots.</li><li><strong>ElasticVue —</strong> peek into indices/documents.</li><li><strong>CyberChef —</strong> handy data munging (hashing, decoding, etc.).</li><li><strong>SpiderFoot — </strong>OSINT automation.</li></ul><p>Why nothing shows yet? You’ve just gone live. Give it minutes to hours; the internet will find you. Early hits often come from scanners across many countries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YE1kHZCo0-pdi3LISi9ogA.png" /></figure><h4><strong>Kibana Dashboard Details — Interpreting Honeypot Results</strong></h4><p>Once you log into the T‑Pot web UI and open Kibana, you’ll likely see a dashboard showing attack counts per honeypot module. Each block represents a service emulated by T‑Pot. Here’s how to read them:</p><ul><li><strong>Cowrie (SSH/Telnet) —</strong> Captures brute‑force login attempts, shell commands, and malware download activity.</li><li><strong>Honeytrap (Generic Ports) —</strong> Listens on arbitrary ports and records random scans and worm traffic.</li><li><strong>Dionaea (Malware Capture) — </strong>Collects exploit attempts and malware binaries, often over SMB or HTTP.</li><li><strong>Adbhoney (Android Debug Bridge) — </strong>Exposed ADB honeypot, targeted by IoT malware campaigns.</li><li><strong>Honeyptr4p (Tarpit) —</strong> Deliberately holds connections open to slow attackers.</li><li><strong>ConPot (ICS/SCADA) —</strong> Emulates industrial control protocols like Modbus or Siemens S7.</li><li><strong>Sentypeer (VoIP/SIP) —</strong> Detects SIP/VoIP probing and PBX abuse attempts.</li><li><strong>Tanner (Web Exploits) —</strong> Catches and analyzes HTTP payloads such as SQL injection or XSS.</li></ul><p><strong>Tip: </strong>The relative numbers help you see which attack surfaces are most actively probed on the internet. Expect Cowrie and Honeytrap to dominate, with occasional niche hits on the others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RsWUB6M93gXMEFIlG_nAqg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*II5WZXBPmymZeQw_xuu_sQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zUzusebr7tojd7t13nKeAA.png" /></figure><h4><strong>Final thought</strong></h4><p>Honeypots are equal parts patience and curiosity. You’re not just building a sandbox — you’re building a lens that reveals what the internet looks like when it knocks on an unattended door. Keep the environment isolated, document your changes, and treat every new IP and payload as a learning opportunity. Share artefacts that don’t expose sensitive secrets: anonymized IOCs, sanitized payload examples, and short summaries of attacker behaviour help the community learn without risking exposure.</p><p>I built this project simply to learn how a honeypot behaves — to watch real probes and payloads, to understand what gets logged, and to practice extracting useful signals.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcfa9f9f54b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building My First IDS Lab with Snort 3]]></title>
            <link>https://medium.com/@vignesh3967/building-my-first-ids-lab-with-snort-3-37ac1ebc0345?source=rss-80ac91a923e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/37ac1ebc0345</guid>
            <dc:creator><![CDATA[Vignesh Ambaykar]]></dc:creator>
            <pubDate>Tue, 02 Sep 2025 19:00:47 GMT</pubDate>
            <atom:updated>2025-09-03T04:31:38.888Z</atom:updated>
            <content:encoded><![CDATA[<h3>𝐁𝐮𝐢𝐥𝐝𝐢𝐧𝐠 𝐚𝐧 𝐈𝐃𝐒 𝐰𝐢𝐭𝐡 𝐒𝐧𝐨𝐫𝐭 𝟑</h3><p>Over the past few days, I decided to get hands-on with <strong>Snort 3</strong> — an open-source IDS/IPS that’s widely used in both learning environments and production networks. My goal was simple:</p><p>Learn how to install Snort from source, understand how rules work, and test it against a PCAP to spot malicious activity.</p><p>This blog post is part <strong>study log</strong>, part <strong>lab notes</strong>. Hopefully, it helps anyone else who’s curious about intrusion detection systems get started quickly.</p><h3>Why Snort?</h3><p>Snort is an <strong>Intrusion Detection and Prevention System (IDS/IPS)</strong>. It analyzes network traffic in real time and alerts you to suspicious activity.</p><p>Some reasons I chose Snort 3 for this project:</p><ul><li>Open-source and free to use.</li><li>Strong rule community (free and paid).</li><li>Easy to spin up in a lab.</li><li>Lets you write your own signatures (great for learning).</li></ul><p>For production, some prefer <strong>Suricata</strong> (especially when paired with Zeek and Community ID for correlation). But for labs, Snort is perfect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/763/1*ZsbSKcJkCsC0WQAWG3ifnA.png" /></figure><h3><strong>Full Installation Steps (Ubuntu VirtualBox)</strong></h3><p>Here’s the exact sequence I followed to install Snort 3 from source in my Ubuntu VirtualBox VM. I kept everything inside ~/snort/ so it’s clean and easy to find later.</p><p><strong>STEP 0 — Install Pre-requisites</strong></p><pre>sudo apt-get install -y build-essential autotools-dev libdumbnet-dev libluajit-5.1-dev libpcap-dev \<br>zlib1g-dev pkg-config libhwloc-dev cmake liblzma-dev openssl libssl-dev cpputest libsqlite3-dev \<br>libtool uuid-dev git autoconf bison flex libcmocka-dev libnetfilter-queue-dev libunwind-dev \<br>libmnl-dev ethtool libjemalloc-dev</pre><p><strong>STEP 1 — Install PCRE</strong></p><p>Perl-Compatible Regular Expressions library, used for Snort’s pattern matching.</p><pre>cd ~/snort<br>wget https://sourceforge.net/projects/pcre/files/pcre/8.45/pcre-8.45.tar.gz<br>tar -xzvf pcre-8.45.tar.gz<br>cd pcre-8.45<br>./configure<br>make<br>sudo make install</pre><p><strong>STEP 2 — Install gperftools</strong></p><p>Google Performance Tools, helps Snort with optimized memory management and profiling.</p><pre>cd ~/snort<br>wget https://github.com/gperftools/gperftools/releases/download/gperftools-2.9.1/gperftools-2.9.1.tar.gz<br>tar xzvf gperftools-2.9.1.tar.gz<br>cd gperftools-2.9.1<br>./configure<br>make<br>sudo make install</pre><p><strong>STEP 3 — Install Ragel</strong></p><p>A state machine compiler, required for parsing protocols inside Snort.</p><pre>cd ~/snort<br>wget http://www.colm.net/files/ragel/ragel-6.10.tar.gz<br>tar -xzvf ragel-6.10.tar.gz<br>cd ragel-6.10<br>./configure<br>make<br>sudo make install</pre><p><strong>STEP 4 — Download Boost (C++ Libraries)</strong></p><p>Boost provides C++ libraries Snort depends on, especially for regex and filesystem operations.</p><pre>cd ~/snort<br>wget https://boostorg.jfrog.io/artifactory/main/release/1.77.0/source/boost_1_77_0.tar.gz<br>tar -xvzf boost_1_77_0.tar.gz</pre><p><strong>STEP 5 — Install Hyperscan</strong></p><p>A high-performance regex engine used by Snort 3 for fast pattern matching.</p><pre>cd ~/snort<br>wget https://github.com/intel/hyperscan/archive/refs/tags/v5.4.2.tar.gz<br>tar -xvzf v5.4.2.tar.gz<br>mkdir ~/snort/hyperscan-5.4.2-build<br>cd hyperscan-5.4.2-build/<br>cmake -DCMAKE_INSTALL_PREFIX=/usr/local -DBOOST_ROOT=~/snort/boost_1_77_0/ ../hyperscan-5.4.2<br>make</pre><p><strong>STEP 6— Install Flatbuffers</strong></p><p>A serialization library used for passing structured data inside Snort.</p><pre>cd ~/snort<br>wget https://github.com/google/flatbuffers/archive/refs/tags/v2.0.0.tar.gz -O flatbuffers-v2.0.0.tar.gz<br>tar -xzvf flatbuffers-v2.0.0.tar.gz<br>mkdir flatbuffers-build<br>cd flatbuffers-build<br>cmake ../flatbuffers-2.0.0<br>make<br>sudo make install</pre><p><strong>STEP 7 — Install DAQ</strong></p><p>(Data Acquisition library) — provides packet I/O for Snort (grabs packets from the network).</p><pre>cd ~/snort<br>wget https://github.com/snort3/libdaq/archive/refs/tags/v3.0.13.tar.gz -O libdaq-3.0.13.tar.gz<br>tar -xzvf libdaq-3.0.13.tar.gz<br>cd libdaq-3.0.13<br>./bootstrap<br>./configure<br>make<br>sudo make install</pre><p><strong>STEP 8 — Update Shared Libraries</strong></p><p>Reloads system library paths so new dependencies are recognized.</p><pre>sudo ldconfig</pre><p><strong>STEP 9 — Install Snort 3</strong></p><p><em>Finally, compile and install Snort itself.</em></p><pre>cd ~/snort<br>wget https://github.com/snort3/snort3/archive/refs/tags/3.9.0.3.tar.gz -O snort3–3.1.74.0.tar.gz<br>tar -xzvf snort3–3.9.0.3.tar.gz<br>cd snort3–3.9.0.3<br>./configure_cmake.sh --prefix=/usr/local --enable-jemalloc<br>cd build<br>make<br>sudo make install</pre><p><strong>STEP 10 — Disable LRO &amp; GRO (for packet inspection accuracy)</strong></p><p>Turns off hardware offloading so Snort can properly inspect every packet.</p><pre>Create a systemd service:<br>[Unit]<br>Description=Ethtool Configuration for Network Interface<br>[Service]<br>Requires=network.target<br>Type=oneshot<br>ExecStart=/sbin/ethtool -K enp0s3 gro off<br>ExecStart=/sbin/ethtool -K enp0s3 lro off<br>[Install]<br>WantedBy=multi-user.target<br>Replace &lt;network adapter&gt; with your actual adapter (e.g., ens33 or eth0).</pre><p><strong>STEP 11 — Install PulledPork3</strong></p><p>Automates downloading and updating Snort rule sets.</p><pre>cd ~/snort<br>git clone https://github.com/shirkdog/pulledpork3.git<br>cd pulledpork3<br>sudo mkdir /usr/local/bin/pulledpork3<br>sudo cp pulledpork.py /usr/local/bin/pulledpork3<br>sudo cp -r lib/ /usr/local/bin/pulledpork3<br>sudo chmod +x /usr/local/bin/pulledpork3/pulledpork.py<br>sudo mkdir /usr/local/etc/pulledpork3<br>sudo cp etc/pulledpork.conf /usr/local/etc/pulledpork3/</pre><p>After following these steps, Snort 3 and PulledPork3 were installed correctly in my <strong>Ubuntu VirtualBox VM</strong>, ready for testing custom rules and analyzing PCAPs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1CGtOxRQpzUaM08YF4owMg.png" /></figure><h3>Writing My First Custom Rule</h3><p>To see alerts in action, I wrote a basic <strong>ICMP detection rule</strong>.</p><p>Created a rules file:</p><pre>/usr/local/etc/rules/local.rules</pre><p>With this rule:</p><pre>alert icmp any any -&gt; any any (msg:&quot;ICMP detected&quot;; sid:1000001;)</pre><p>When I pinged my VM, Snort immediately flagged it with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/805/1*BqCIUSm7DbgoWQWXHVu_fg.png" /></figure><p>That was my First “yes it works!” Moment</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9f3XJRXtt9n-8B-R57tjPA.png" /></figure><h3>Automating Rules with PulledPork3</h3><p>I didn’t want to rely only on custom rules, so I set up <strong>PulledPork3</strong> to fetch and manage Snort rules automatically.</p><ul><li>Installed PulledPork3 into /usr/local/bin/pulledpork3.</li><li>Configured /usr/local/etc/pulledpork3/pulledpork.conf with my <strong>Oinkcode</strong> from Snort.org.</li><li><strong>Ran:</strong></li></ul><pre>sudo pulledpork.py -c /usr/local/etc/pulledpork3/pulledpork.conf</pre><ul><li>Verified it generated a pulledpork.rules file.</li></ul><p>Now I had a full ruleset on top of my custom rules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zUqlWaOwwDFzCffzsNYZbg.png" /><figcaption>Installing Pulledpork</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*STiTJFgtWfs94ltD-0jrFw.jpeg" /></figure><h3>Testing with a Malicious PCAP</h3><p>To put it to the test, I grabbed a sample pcap from Malware Traffic Analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fOy5hbwdk-xWB2EfCmHX4g.png" /></figure><p><strong>Ran:</strong></p><pre>snort -c /usr/local/etc/snort/snort.lua --plugin-path /usr/local/etc/so_rules/ -r 2022-02-23-traffic-analysis-exercise.pcap -A alert_fast -q</pre><p>Snort lit up with alerts. Using cut, sort, and uniq, I summarized the triggered signatures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aMZsDbBH4EMJjqdE_OiIqw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4suNJRzAp3c8odS_L9_3DQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ixEwKJDKFj-xPaMYPqx6Q.png" /></figure><p>One caught my eye:</p><pre>MALWARE-OTHER Win.Trojan.WhisperGate</pre><p>That was the “aha!” moment — Snort successfully flagged the malware traffic inside the PCAP.</p><h3>Conclusion</h3><p>Setting up <strong>Snort 3 inside an Ubuntu VirtualBox VM</strong> was both a challenge and a rewarding learning experience. Along the way, I learned:</p><ul><li>How to build Snort 3 and its dependencies (Hyperscan, Flatbuffers, DAQ) from source.</li><li>How to write a simple <strong>custom ICMP detection rule</strong>.</li><li>How to automate rule updates with <strong>PulledPork3</strong>.</li><li>How to validate Snort against real <strong>malicious PCAPs</strong> and quickly pivot to interesting indicators (like WhisperGate traffic).</li></ul><p>For me, the biggest takeaway wasn’t just getting Snort running — it was seeing how an IDS fits into a real-world workflow: rules, automation, traffic capture, and analysis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37ac1ebc0345" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Complete SOC Lab: Active Directory Detection & Response Automation Project]]></title>
            <link>https://medium.com/@vignesh3967/building-a-complete-soc-lab-active-directory-detection-response-automation-project-f48d2e82a84f?source=rss-80ac91a923e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/f48d2e82a84f</guid>
            <dc:creator><![CDATA[Vignesh Ambaykar]]></dc:creator>
            <pubDate>Fri, 06 Jun 2025 02:43:09 GMT</pubDate>
            <atom:updated>2025-06-06T02:43:09.649Z</atom:updated>
            <content:encoded><![CDATA[<p>This project is an advanced continuation of my earlier home lab titled <em>“</em><a href="https://medium.com/@vignesh3967/simulating-cyber-attack-and-analyzing-logs-in-an-active-directory-home-lab-with-splunk-640c4f88e667"><em>Simulating Cyber Attacks and Analyzing Logs in an Active Directory Home Lab with Splunk.</em></a><em>”</em> In that project, I focused on attack simulation using Kali Linux, Sysmon log integration, and real-time detection in Splunk. After successfully capturing and analyzing brute force and Atomic Red Team attack logs across a multi-OS environment, I wanted to take the next step — automation.</p><p>In this upgraded project, I built a fully cloud-hosted SOC lab designed to not only detect unauthorized RDP logins in an Active Directory environment but also automate the response by disabling the compromised account. Using tools like Splunk, Slack, and Shuffle, I orchestrated a complete detection-to-response pipeline that mirrors what real SOCs execute in production. This lab allowed me to deepen my SIEM and SOAR skills, gain operational experience with log forwarding and user behavior detection, and showcase end-to-end incident handling through custom automation.</p><p><strong>Project Overview:</strong></p><p>This project focuses on building a real-world SOC simulation in the cloud. The idea is to bring together the core components of detection and response in a seamless automated flow. In this lab:</p><p>★ Unauthorized RDP logins to Active Directory are detected in near real time.<br>★Windows event telemetry is forwarded to Splunk for centralized logging and analysis.<br>★ Alerts are automatically triggered when suspicious activity is detected.<br>★ Slack and Shuffle handle the response automation — notifying the SOC analyst and disabling the user account upon confirmation.</p><p>It’s not just a project — it’s a hands-on exercise in combining SIEM and SOAR to replicate what real SOCs do every day.</p><h3>Part 1: Creating the Environment Diagram</h3><p>Every solid SOC workflow starts with a clear plan. To map out how each component would interact, I used <strong>Draw.io</strong> to visualize the full architecture of the lab. The setup includes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K3qZEBT2zOZLywc5CJcrgg.jpeg" /><figcaption>Architectural Diagram</figcaption></figure><p>★ <strong>Domain Controller (Windows Server)</strong> — our central identity and authentication system.<br>★ <strong>Test Machine (Windows Server)</strong> — simulates an employee endpoint.<br>★ <strong>Splunk Server (Ubuntu)</strong> — acts as the SIEM collecting and analyzing logs.<br>★ <strong>Attacker Machine</strong> — mimics unauthorized activity to test detection.<br>★ <strong>Slack</strong> — serves as the communication channel for alert notification.<br>★ <strong>Shuffle</strong> — functions as the SOAR platform automating responses.</p><p><strong>The logic is simple but powerful:</strong></p><p>★ Telemetry from the Windows machines flows into <strong>Splunk</strong>, which analyzes and identifies unauthorized logins.<br>★ Once detected, <strong>Splunk triggers a webhook</strong> to <strong>Shuffle</strong>, which orchestrates the response.<br>★ <strong>Shuffle</strong> pushes an alert to <strong>Slack</strong> and emails the SOC analyst with a decision point.<br>★ If the analyst selects “Yes,” the <strong>user is automatically disabled</strong> in Active Directory.</p><p>This diagram laid the foundation for a well-connected, realistic SOC lab that could support the rest of the project.</p><h3>Part 2: Cloud Setup with Vultr</h3><p>To bring this lab to life, I chose <strong>Vultr Cloud</strong> for its flexibility and ease of deployment. The goal here was to simulate a real-world SOC infrastructure in a controlled, scalable cloud environment.</p><p><strong>I provisioned the following virtual machines:</strong></p><p>★ <strong>DC01:</strong> Windows Server acting as the Active Directory Domain Controller<br>★ <strong>Test Machine:</strong> Another Windows Server that simulates a standard user workstation<br>★ <strong>Splunk Server:</strong> An Ubuntu 22.04 instance configured to collect, parse, and alert on Windows telemetry</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZIgfR59VgyW_WWh8bkOE3g.png" /></figure><p><strong>Setup Highlights:</strong></p><p>★ Designed and configured a Virtual Private Cloud (VPC) to ensure secure internal communication between machines<br>★ Assigned static internal IPs to all hosts for consistent log forwarding and lookup<br>★ Set up firewall rules to enable essential services: <strong>RDP (3389)</strong>, <strong>SSH (22)</strong>, and <strong>Splunk ports (8000, 9997)<br></strong>★ Verified connectivity between all machines using ping and RDP/SSH sessions</p><p>This part ensured the underlying cloud network was solid, secure, and ready for log flow and analysis.</p><h3>Part 3: Active Directory Setup</h3><p>With the cloud environment ready, it was time to breathe life into the infrastructure by setting up Active Directory — the core of user authentication and management.</p><p><strong>Here’s what I did:</strong></p><p>★ <strong>Promoted DC01 to a Domain Controller</strong> using the custom domain Pheonix.local to simulate a real enterprise setup.<br>★ <strong>Created a test user, Naruto Uzumaki (NUzumaki),</strong> representing a standard domain user for login simulations.<br>★ <strong>Joined the Test Machine to the domain</strong> to enable centralized user control and policy management.<br>★ <strong>Enabled RDP access for domain users</strong> so we could simulate remote logins like a real attacker might exploit.<br>★ <strong>Verified DNS settings and login capability</strong> to confirm that the machine and user were properly integrated into the domain.</p><p>This step laid the groundwork for capturing authentication logs and simulating lateral movement scenarios — a critical part of our SOC detection pipeline.</p><h3>Part 4: Splunk Setup &amp; Alerting</h3><p>With the Active Directory foundation in place, it was time to build the detection engine. Splunk serves as the heart of our monitoring system, where all logs converge, get analyzed, and trigger alerts.</p><h4>Step 1: Installing Splunk on Ubuntu</h4><p>★ Deployed <strong>Splunk Enterprise</strong> on the Ubuntu server via .deb package.<br>★ Completed the setup via web interface and secured with custom admin credentials.<br>★ Opened <strong>port 8000</strong> on both the instance and cloud firewall for web access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2K2CZ8lkTBKpjMgVTsjBGQ.png" /><figcaption>Splunk Installation</figcaption></figure><h4>Step 2: Forwarding Logs with Universal Forwarder</h4><p>★ Installed <strong>Splunk Universal Forwarder</strong> on both Windows servers.<br>★ Configured them to forward <strong>Security Event Logs</strong> to the Splunk server on <strong>port 9997</strong>.</p><p><strong>Used the following inputs.conf configuration:</strong></p><blockquote>[WinEventLog://Security]</blockquote><blockquote>index = Pheonix-ad</blockquote><blockquote>disabled = 0</blockquote><h4>Step 3: Configuring Splunk for Ingestion</h4><p>★ Installed <strong>Splunk Add-on for Windows</strong> to parse logs effectively.<br>★ Created a dedicated index: Pheonix-ad.<br>★ Set up <strong>data inputs</strong> to receive logs on port 9997.<br>★ Verified real-time log flow from both Windows machines into Splunk.</p><h4>Step 4: Creating an Unauthorized Login Alert</h4><p>★ Designed a Splunk search query to identify <strong>suspicious RDP logins</strong> using Event ID 4624 with <strong>Logon Type 7 or 10</strong>.<br>★ Applied filters to flag only public IP logins (simulated attacker traffic):</p><blockquote><em>index=”pheonix-ad” EventCode=4624 (Logon_Type=7 OR Logon_Type=10) Source_Network_Address=* Source_Network_Address!=”-”<br>Source_Network_Address!=40.*<br>| stats count by _time, ComputerName, Source_Network_Address, user, Logon_Type</em></blockquote><p><strong>Query Explanation:</strong></p><p>This Splunk query is designed to <strong>detect successful remote or workstation logins</strong> (EventCode 4624 with Logon Types 7 and 10) from <strong>external/public IP addresses</strong>, excluding internal traffic and placeholders.</p><p>▹ EventCode=4624: Filters for successful login events.<br>▹ Logon_Type=7 OR Logon_Type=10: Focuses on <strong>Logon Type 7 (Unlock)</strong> and <strong>Logon Type 10 (Remote/Remote Desktop)</strong> — both common in suspicious access patterns.<br>▹ Source_Network_Address=*: Ensures the login has a recorded source IP.<br>▹ Source_Network_Address!=&quot;-&quot;: Excludes placeholder/no-value entries.<br>▹ Source_Network_Address!=40.*: Excludes trusted IPs (e.g., organization’s IP range starting with 40.).</p><p>The stats command groups the results to help visualize suspicious login patterns by time, user, system, and source IP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V0h0WN1wPFs8j7vRMhB0Pg.png" /></figure><p>★ Configured the alert to trigger <strong>every 1 minute</strong>.<br>★ Added a <strong>Webhook action</strong> to send alert data directly to the Shuffle workflow.</p><h3>Part 5: Shuffle &amp; Slack Integration (Detailed)</h3><p>This is where the project truly comes alive with automation. The goal was to reduce response time and simulate how real SOC teams use SOAR platforms to streamline decisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xBrv_l_pPHWMstdFzAruMQ.png" /><figcaption>Automation Workflow</figcaption></figure><p><strong>Webhook-Triggered Workflow in Shuffle:</strong></p><p>★Started with a <strong>Webhook node</strong> to capture incoming alerts from Splunk<br>★ Added a <strong>Slack action</strong> to post alert metadata to the #alerts channel</p><p><strong>Fields passed in the message:</strong></p><p>Alert: $exec.search_name<br>Time: $exec.result._time<br>User: $exec.result.user<br>IP: $exec.result.Source_Network_Address</p><p><strong>Human-in-the-Loop Decision:</strong></p><p><strong>★ </strong>Used <strong>User Input</strong> block to send an email to the SOC Analyst<br>★ Message asked: <em>“Do you want to disable this user?”</em> with Yes/No buttons</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uUBbaWYVzKBZcdQpX4SbQw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*iKcuK7H6eBtOQlxo9MQfQA.png" /></figure><p><strong>If Analyst Chooses Yes:</strong></p><p>★ Connected to Active Directory via <strong>LDAP over port 389<br></strong>★ Executed the <strong>Disable User</strong> action using DN path and AD admin credentials</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rq5BqcXipHZQLXvF3weiQg.png" /></figure><p><strong>Slack Notification After Action:</strong></p><p>★ Posted a follow-up message to Slack: <em>“✅ Account NUzumaki has been disabled based on SOC decision.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rRJh31EpMINNBao637tShw.png" /></figure><h4>Conclusion:</h4><p>This project marked a critical upgrade in my hands-on SOC journey. Building on my earlier experience of simulating attacks and analyzing logs, this lab took it further by engineering an automated incident detection and response pipeline.</p><p>From spinning up cloud infrastructure and configuring domain environments to wiring Splunk alerts and building Slack-integrated workflows in Shuffle, every component was aligned with how a real-world SOC functions. The highlight was turning detection into decisive action — not just logging suspicious logins, but automatically disabling accounts after analyst review.</p><p>This wasn’t just about tools — it was about building a practical and intelligent security pipeline that reflects the evolving demands of modern SOC teams. It proves that I can not only simulate adversarial activity but also operationalize a response just like in production environments.</p><p>Let’s keep building. Let’s keep defending.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f48d2e82a84f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SOAR EDR Project: Automating Incident Response with LimaCharlie and Tines]]></title>
            <link>https://medium.com/@vignesh3967/soar-edr-project-automating-incident-response-with-limacharlie-and-tines-9754364ec30c?source=rss-80ac91a923e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/9754364ec30c</guid>
            <dc:creator><![CDATA[Vignesh Ambaykar]]></dc:creator>
            <pubDate>Mon, 17 Feb 2025 16:00:23 GMT</pubDate>
            <atom:updated>2025-02-17T16:00:23.384Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s dynamic cybersecurity landscape, organizations need agile, automated response systems to counter threats in real time. Integrating Security Orchestration, Automation, and Response (SOAR) solutions with Endpoint Detection and Response (EDR) tools provides the precision and speed required to mitigate risks effectively. In this blog, I’ll share insights from my recent SOAR EDR project, where I integrated <strong>LimaCharlie</strong>, <strong>Tines</strong>, <strong>Slack</strong>, and <strong>Email</strong> to build an automated incident response workflow.</p><h3>Why Tines and LimaCharlie?</h3><p>In my previous SOC automation project, I used Shuffle as the SOAR tool. This time, I chose Tines to demonstrate that the choice of tool is secondary to the underlying concepts of automation and orchestration. LimaCharlie served as the EDR, with a Windows virtual machine (VM) in the cloud acting as the agent — any Windows machine with internet connectivity would suffice.</p><h3>What is LimaCharlie?</h3><p>LimaCharlie is a cloud-based security infrastructure that offers scalable detection, response, and telemetry capabilities. It empowers organizations to deploy their own security operations, detect malicious activities in real-time, and automate responses through customizable rules and integrations.</p><h3>What is Tines?</h3><p>Tines is a no-code automation platform that enables security teams to design workflows connecting various security tools. It facilitates automated incident response without the need for complex scripting. Integrating LimaCharlie with Tines allowed me to orchestrate security events, notify teams, and take decisive actions when threats were detected.</p><h3>What is Lazagne?</h3><p>Lazagne.exe is an open-source password recovery tool that extracts stored credentials from applications like browsers and email clients. Although useful for penetration testers, attackers can exploit Lazagne for credential theft, making its detection crucial for EDR systems.</p><h3>Project Breakdown</h3><p>To make this section more engaging, I have added bullet points:</p><ul><li><strong>Part 1:</strong> Architectural Diagram</li><li><strong>Part 2: </strong>Setting Up LimaCharlie</li><li><strong>Part 3:</strong> Detection Rules</li><li><strong>Part 4: </strong>Notifications Setup</li><li><strong>Part 5:</strong> Playbooks Automation</li></ul><h3>Part 1: Creating the Architectural Diagram</h3><p>Before diving into the implementation, I designed an architectural diagram outlining how LimaCharlie, Tines, Slack and Email would interact. This helped visualize the flow of events from detection to response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CXKzfU-Q9sTMckfBd2AARA.png" /><figcaption>Architectural Diagram</figcaption></figure><h3>Part 2: Setting Up LimaCharlie and Endpoint Detection</h3><h4>A) Installing and Setting Up LimaCharlie</h4><ul><li>Configured LimaCharlie within my security environment.</li><li>Installed the LimaCharlie sensor on an endpoint to collect telemetry.</li></ul><h4>B) Connecting the Endpoint and Verifying Event Generation</h4><p>To ensure that the setup was working correctly, I deployed a <strong>Windows Server machine on Vultr</strong> as the test environment. Once the LimaCharlie agent was installed, I verified that the endpoint was sending telemetry data and generating security events.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*egyN9Bx_b5LW3Zy4jIBYew.png" /></figure><h3>Part 3: Generating and Detecting Telemetry Events</h3><p>Here is the <strong>LimaCharlie Detection and Response Rule</strong> I created for detecting Lazagne:</p><pre>Detect:<br>events:<br>  - NEW_PROCESS<br>  - EXISTING_PROCESS<br>op: and<br>rules:<br>  - op: is windows<br>  - op: or<br>    rules:<br>      - case sensitive: false<br>        op: ends with<br>        path: event/FILE_PATH<br>        value: LaZagne.exe<br>      - case sensitive: false<br>        op: ends with<br>        path: event/COMMAND_LINE<br>        value: all<br>      - case sensitive: false<br>        op: contains<br>        path: event/COMMAND_LINE<br>        value: LaZagne<br>      - case sensitive: false<br>        op: is<br>        path: event/HASH<br>        value:  (hash Value)</pre><pre>Respond:<br>action: report<br>  metadata:<br>    author: Pheonix<br>    description: Detects Lazagne (SOAR-EDR Tool)<br>    falsepositives:<br>      - To The Moon<br>    level: medium<br>    tags:<br>      - attack.credential_access<br>  name: Pheonix - HackTool - Lazagne (SOAR-EDR)</pre><p>This rule ensures that any activity related to Lazagne is detected and reported efficiently. To test the EDR capabilities of LimaCharlie, I used <strong>Lazagne</strong>, a well-known password recovery tool, to simulate malicious activity.</p><ul><li>After executing Lazagne, I confirmed that LimaCharlie was successfully detecting its activity.</li><li>I then created a <strong>Detection and Response Rule (DRR)</strong> within LimaCharlie to automatically flag and log events related to Lazagne.</li><li>Once a detection was triggered, the event was forwarded to <strong>Tines</strong> for further automation.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r73pwhUX5gFYoiRuJqHKaA.png" /><figcaption>Detection</figcaption></figure><h3>Part 4: Setting Up Slack and Tines for Automated Notifications</h3><p>Next, I set up integrations between LimaCharlie, Tines, and Slack:</p><ul><li><strong>Slack:</strong> Configured a Slack workspace and a dedicated channel to receive security alerts.</li><li><strong>Tines:</strong> Connected LimaCharlie to Tines to automate responses based on triggered detections.</li><li><strong>Testing:</strong> To validate the setup, I executed Lazagne again, and LimaCharlie successfully detected the activity. The alert was forwarded to Tines, which then sent a notification to Slack.</li></ul><h3>Part 5: Automating Incident Response with Playbooks</h3><p>In this part, I ensured that when an alert is generated, I receive notifications in both <strong>Slack</strong> and <strong>Email</strong>. Additionally, I created an <strong>isolation dialogue box</strong> that prompts the user for action. Before the YES or NO prompt, a pop-up alert appears asking if you want to isolate the machine. If you click YES, it isolates the computer automatically, if you click NO, I receive a message to investigate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QxqFnsiYzC8rk5unUA9HWA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SZX8khkQ2JrlrzhEFnE7YA.png" /></figure><p>If <strong>YES</strong> is selected, Slack receives a message:</p><pre>Isolation Status: true<br>The Computer: pheonix-soar-edr Has been isolated.</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qESXtNLFRXLiolVCBBwHig.png" /></figure><p>If <strong>NO</strong> is selected, Slack receives:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q99fyMMF3Laf6se4T9Xu3Q.png" /></figure><p>Using the architecture diagram from Part 1, I created a <strong>playbook</strong> to automate response actions:</p><ol><li><strong>Tines</strong> receives the detection event from LimaCharlie.</li><li>It sends a <strong>Slack notification</strong> containing details about the detected threat.</li><li>An <strong>email alert</strong> is sent to the security team with relevant information.</li><li><strong>User Prompt:</strong> Tines asks the security analyst via Slack whether to isolate the affected machine.</li><li>If the analyst selects <strong>YES</strong>, LimaCharlie <strong>automatically isolates</strong> the machine from the network.</li></ol><p>This automation significantly reduces response time, ensuring quick containment of threats without manual intervention.</p><h3>Adding Visuals</h3><p>This is how the <strong>Tines Playbook</strong> looks like (photo attached below). I have attached a photo of the alert received in my <strong>email</strong> as well as a screenshot of the <strong>Tines Playbook</strong> I created for this project to provide a clearer understanding of the workflow and automation setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yUiYBGjxTsXmFTTS95vsZw.png" /><figcaption>Tines Automation</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/887/1*QLA9vKj3T-6AkePL6yJybA.png" /><figcaption>Email</figcaption></figure><h3>Conclusion</h3><p>This SOAR EDR project demonstrated the power of integrating LimaCharlie and Tines to create an automated incident response framework. By leveraging real-time detection, automated notifications, and response actions, organizations can efficiently mitigate security threats with minimal human intervention.</p><p>The successful execution of this project highlights the importance of automation in modern cybersecurity operations, and I’m excited to explore more integrations and advanced security workflows in the future!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9754364ec30c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installing Elastic Defend: A Step-by-Step Guide to Protecting Your Endpoints]]></title>
            <link>https://medium.com/@vignesh3967/installing-elastic-defend-a-step-by-step-guide-to-protecting-your-endpoints-6ee9a0008f96?source=rss-80ac91a923e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ee9a0008f96</guid>
            <dc:creator><![CDATA[Vignesh Ambaykar]]></dc:creator>
            <pubDate>Sun, 29 Sep 2024 20:01:07 GMT</pubDate>
            <atom:updated>2024-09-29T20:13:31.138Z</atom:updated>
            <content:encoded><![CDATA[<p>By the end of this blog, you’ll know how to successfully install Elastic Defend, Elastic’s own EDR (Endpoint Detection and Response) solution, and how to monitor the telemetry it generates.</p><h4>Let’s get started!</h4><p><strong>Elastic Defend</strong> provides a robust layer of protection for your endpoints, guarding them from malicious activity. With a free subscription, you can download and install Elastic Defend on your devices, though it’s important to note that <strong>remote host isolation</strong> is not available on the free tier. However, if you’re on a trial or paid version, full functionality is at your fingertips.</p><h4>Step 1: Installing Elastic Defend</h4><p><strong>Access the Integrations Menu</strong><br>Start by navigating to the <strong>hamburger icon</strong> in your Elastic interface. Scroll down to <strong>Integrations</strong>, and select <strong>Elastic Defend</strong>.</p><p><strong>Add the Integration</strong><br>Click <strong>Add Elastic Defend</strong> and provide a name for the integration, such as <strong>Pheonix-EDR</strong>. You can add a description like <em>Elastic EDR — Pheonix EDR</em> to keep track of your installations.</p><p><strong>Choose Your Configuration</strong><br>Elastic Defend offers four configuration types:</p><ul><li><strong>Data Collection</strong></li><li><strong>Next-Gen Antivirus</strong></li><li><strong>Essential EDR</strong></li><li><strong>Complete EDR</strong></li></ul><p>Since we are using the <strong>30-day trial</strong>, select <strong>Complete EDR</strong> to get full telemetry and protection.</p><p><strong>Select Endpoint Type</strong><br>You’ll be prompted to choose between traditional endpoints (e.g., desktops, laptops, VMs) and cloud workloads (Linux servers, Kubernetes). For our purposes, we’ll select <strong>traditional endpoints</strong>.</p><p><strong>Deploy Elastic Defend to Your Host</strong><br>Add this integration to your existing host policy. For this example, we’ll choose the <strong>Windows — Policy</strong>. Having a <strong>Fleet Server</strong> makes it easy to manage multiple agents centrally. Once selected, click <strong>Save and Deploy Changes</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Au-khfZ8QPnrh6WGpi3toQ.png" /></figure><h4>Step 2: Verify Installation and Endpoint Status</h4><p>Once you’ve deployed Elastic Defend to your Windows server:</p><p><strong>Navigate to Endpoints</strong><br>Click on the hamburger icon again, scroll down to <strong>Security</strong>, and select <strong>Manage Endpoints</strong>. You should see your endpoint listed as active and running Elastic Defend.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P8H-Vx526WZCAN5_UgtRQg.png" /></figure><p><strong>Host Isolation (For Paid Users)</strong><br>If you’re on the trial version, you’ll notice that you have the option to <strong>isolate the host</strong>. This feature is disabled for free-tier users.</p><h4>Step 3: Testing Elastic Defend with Malware Detection</h4><p>Let’s simulate a scenario where Elastic Defend blocks malicious activity.</p><p><strong>Simulate Malware Activity</strong><br>Open the console on your Windows server, and terminate the process for <strong>Pheonix-30.exe</strong>. If you try to run it again, Elastic Defend should automatically block it, identifying it as malware.</p><p>You’ll see a message that says:<br><em>“Operation did not complete successfully because the file contains a virus or potentially unwanted software.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*lnlU3e6mSs6OBkxmoIdu2A.png" /></figure><p><strong>Telemetry in Elastic</strong><br>Minimize your console and head over to Kibana. Open the <strong>Discover</strong> tab and search for <strong>malware</strong> to view the telemetry Elastic Defend has generated. You’ll see a <strong>malware prevention alert</strong>, indicating that Elastic Defend successfully blocked the malicious file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C0ULsdwkMJXpTlVxtR6OzA.png" /></figure><h3>Step 4: Investigating Malware Prevention Alerts</h3><p>Elastic Defend makes it easy to investigate security incidents.</p><p><strong>View the Alert</strong><br>Navigate to <strong>Security</strong> &gt; <strong>Alerts</strong> and open the malware prevention alert. Click <strong>View Details</strong> for more information.</p><p><strong>Telemetry Insights</strong><br>You’ll immediately find useful details such as the <strong>process executable</strong>, <strong>file path</strong>, and <strong>file hash</strong>. This information allows you to dig deeper into the incident.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UFgd3inD60aLEB8V5WjGDA.png" /></figure><p><strong>Set Up a Response Action</strong><br>Scroll down to the <strong>Response</strong> section and click <strong>Edit Rule Settings</strong>. Here, you can set up an automated response action. For instance, you could select <strong>Elastic Defend</strong> to isolate the host when malware is detected. After adding a comment (e.g., <em>Testing</em>), click <strong>Save Changes</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dK48zip7CoMTUfWH_cLqKQ.png" /></figure><p><strong>Re-Test the Response</strong><br>Open a command prompt and type ping 8.8.8.8 -t to simulate an ongoing network connection. Elastic Defend will isolate the server as part of the automated response to the malware detection, blocking further malicious activity.</p><h4>Step 5: Downloading the Mythic C2 Agent</h4><p>After Elastic Defend quarantines the <strong>Pheonix-30.exe</strong> file, you can attempt to download it again. However, Elastic Defend will immediately delete it, recognizing it as a threat.</p><p><strong>Note:</strong> If you’re using the free version of Elastic, remember that <strong>host isolation</strong> won’t be available, but Elastic Defend will still detect and quarantine malware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*QV9CkW-XsQ2ucM0KkuOHBg.png" /></figure><h4>Conclusion: Wrapping Up the 30-Day SOC Challenge</h4><p>Congratulations! You’ve successfully navigated the entire <strong>30-day SOC challenge</strong>, building critical skills for detecting, investigating, and responding to security threats. From deploying ELK stack components to setting up Elastic Defend and Mythic C2, each day presented new challenges and learning opportunities. You are now well-equipped to tackle real-world security operations, leveraging advanced tools and methodologies.</p><p>This blog marks the final step of our journey, culminating in the installation and configuration of <strong>Elastic Defend</strong> — your comprehensive endpoint detection and response (EDR) solution. We tested its features, witnessed how it handles malware threats, and automated responses to enhance security efficiency.</p><h4>30-Day SOC Challenge</h4><ul><li><strong>Day 1</strong>: Crafting a Logical Diagram</li><li><strong>Day 2</strong>: Deep Dive into the ELK Stack</li><li><strong>Day 3</strong>: Setting Up an Elasticsearch Instance on Vultr Cloud</li><li><strong>Day 4</strong>: Installing and Configuring Kibana</li><li><strong>Day 5</strong>: Deploying a Windows Server on Vultr Cloud</li><li><strong>Day 6</strong>: Introduction to Fleet Server and Elastic Agent</li><li><strong>Day 7</strong>: Deploying Fleet Server and Elastic Agent for Centralized Monitoring</li><li><strong>Day 8</strong>: Mastering Sysmon for Advanced Endpoint Monitoring</li><li><strong>Day 9</strong>: Installing Sysmon on Windows Server for Enhanced Monitoring</li><li><strong>Day 10</strong>: Ingesting Sysmon and Windows Defender Logs into Elasticsearch</li><li><strong>Day 11</strong>: Understanding Brute Force Attacks: Types, Prevention, and Tools</li><li><strong>Day 12</strong>: Setting Up an SSH Server and Analyzing Authentication Logs</li><li><strong>Day 13</strong>: Installing Elastic Agent on Ubuntu Server for Effective Monitoring</li><li><strong>Day 14</strong>: Creating SSH Brute Force Alerts and Dashboards with Elastic</li><li><strong>Day 15</strong>: Understanding RDP and How to Protect Against RDP Abuse</li><li><strong>Day 16</strong>: Setting Up Alerts for RDP &amp; SSH Brute Force Attacks</li><li><strong>Day 17</strong>: Building a Comprehensive Dashboard for RDP &amp; SSH Monitoring</li><li><strong>Day 18</strong>: Understanding Command &amp; Control (C2) — The Attacker’s Key Weapon</li><li><strong>Day 19</strong>: Mapping a Simulated Attack Path: From Initial Access to Exfiltration</li><li><strong>Day 20</strong>: Setting Up Your Own Mythic C2 Instance — A Beginner’s Guide</li><li><strong>Day 21</strong>: How to Perform a Brute Force Attack and Establish a Mythic C2 Session</li><li><strong>Day 22</strong>: Detecting Mythic C2 Activity — Creating Alerts and Dashboards in Elastic</li><li><strong>Day 23</strong>: Streamlining Alert Management with OS Ticket</li><li><strong>Day 24</strong>: Setting Up and Configuring OS Ticket — A Step-by-Step Guide</li><li><strong>Day 25</strong>: Seamlessly Integrating OS Ticket with Elastic Stack</li><li><strong>Day 26</strong>: Investigating SSH Brute Force Alerts — A Step-by-Step Guide</li><li><strong>Day 27</strong>: Investigating RDP Brute Force Alerts — A Step-by-Step Guide</li><li><strong>Day 28</strong>: Investigating a Mythic C2 Framework — A Step-by-Step Guide</li><li><strong>Day 29</strong>: Installing Elastic Defend: A Step-by-Step Guide to Protecting Your Endpoints</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ee9a0008f96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Investigating a Mythic C2 Framework: A Step-by-Step Guide]]></title>
            <link>https://medium.com/@vignesh3967/investigating-a-mythic-c2-framework-a-step-by-step-guide-a135d1dbe61c?source=rss-80ac91a923e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a135d1dbe61c</guid>
            <dc:creator><![CDATA[Vignesh Ambaykar]]></dc:creator>
            <pubDate>Sun, 29 Sep 2024 19:09:05 GMT</pubDate>
            <atom:updated>2024-09-29T19:09:05.178Z</atom:updated>
            <content:encoded><![CDATA[<p>By the end of this blog, you’ll know how to investigate a common <strong>C2 (Command and Control) framework</strong> called <strong>Mythic</strong> and what telemetry to look for during an investigation. Specifically, we will dive into the agent named <strong>svchost-Phenoixrocks.exe</strong> and trace its activities in our Elastic environment.</p><p>Let’s get started!</p><h4>Step 1: Initial Investigation — Discovering the Agent</h4><p>To begin, head over to your <strong>Elastic</strong> Web GUI, click the <strong>hamburger icon</strong>, and navigate to <strong>Discover</strong>. Make sure to set the time frame to <strong>30 days</strong>. Then search for the Mythic C2 agent <strong>svchost-Phenoixrocks.exe</strong> (or whatever name your agent might be using in your environment).</p><p>Let’s start investigating the chain of events. Imagine, for the sake of practice, that we didn’t already know the agent’s name was <strong>svchost-Phenoixrocks.exe</strong>. How would we identify a C2 agent?</p><h4>Step 2: Identifying C2 Activity</h4><p>There are a few ways to detect a C2 framework in operation:</p><h4>1. Network Telemetry</h4><ul><li><strong>C2 sessions</strong> often have a lot of back-and-forth traffic, typically reflected in the <strong>top 10 talkers</strong> — IP addresses that have the most bytes transferred.</li><li>Check for <strong>unusual traffic patterns</strong>, especially connections involving high data exchange, indicating potential malicious activity.</li></ul><h4>2. Heartbeat Activity</h4><ul><li>Look for periodic <strong>heartbeat-like network connections</strong>. C2 frameworks often maintain persistent communication with the attacker, sending regular check-ins.</li></ul><h4>3. Process Creations</h4><ul><li>If you have <strong>Sysmon telemetry</strong>, use <strong>event ID 3</strong> to track network creations and process executions. Look for processes like <strong>rundll32.exe</strong>, often used by malware to load DLL files for execution.</li></ul><h4>Step 3: Using Dashboards to Analyze Process Activity</h4><p>Let’s leverage the dashboards we created in previous blogs:</p><ol><li>Click the <strong>hamburger icon</strong>, go to <strong>Dashboards</strong> under <strong>Analytics</strong>, and select the <strong>Pheonix-Suspicious Activity</strong> dashboard.</li><li>Make sure the time frame is set to <strong>30 days</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*33SvrHGbn29ZodXO_2mFZg.png" /></figure><p>At the top of this dashboard, we can see a list of <strong>process creations</strong> like <strong>Powershell</strong>, <strong>cmd.exe</strong>, and <strong>rundll32.exe</strong>. I pay close attention to <strong>rundll32.exe</strong>, as it is often used by malware to load DLLs and execute malicious activities.</p><p>In this case, I found an unusual executable under the directory <strong>C:\Users\Public\Downloads</strong>. Even if it wasn’t called <strong>svchost-Phenoixrocks.exe</strong> and instead something more generic like <strong>update.exe</strong>, I would still investigate it. The reason? <strong>Executables</strong> in <strong>public directories</strong> initiating connections to external IP addresses — especially on <strong>port 80</strong> — raise red flags.</p><h4>Step 4: Diving Deeper — Timeline of Events</h4><p>Now, let’s pretend we’re doing a threat hunt and stumbled upon an outbound <strong>Powershell</strong> connection that looks suspicious. Here’s how we’ll investigate further:</p><p><strong>Copy the destination IP</strong> from the suspicious connection and search for it in <strong>Elastic Discover</strong> using the following query:</p><pre>event.code: 3 AND winlog.event_data.DestinationIp: &lt;Your Destination IP&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V5z8cC0SdPFt8dwSE8DDdw.png" /></figure><p>We can now build a timeline of events:</p><ul><li><strong>Sep 21, 2024 @ 19:05:22.093</strong>: A network connection was initiated towards the destination IP.</li><li><strong>Sep 21, 2024 @ 19:08:48.730</strong>: The connection continued.</li></ul><p>If you have <strong>Sysmon telemetry</strong>, check the <strong>process GUID</strong> for correlation. The <strong>process GUID</strong> will help track all events related to the <strong>Powershell</strong> session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XWjB1NtvMWTmbpl3WLlkDQ.png" /></figure><h4>File Creation and Execution</h4><ul><li><strong>Sep 21, 2024 @ 19:05:21.104</strong>: <strong>Event Code 11</strong> (File Created) — A file named <strong>svchost-Pheonixrocks.exe</strong> was created in <strong>C:\Users\Public\Downloads</strong> using a <strong>Powershell</strong> terminal.</li><li><strong>Sep 21, 2024 @ 19:05:23.610</strong>: <strong>Event Code 29</strong> (File Executed) — The file <strong>svchost-Pheonixrocks.exe</strong> was executed from the <strong>Downloads</strong> folder.</li></ul><p>Using <strong>SHA1 hash values</strong>, we can further investigate the file’s identity and behavior. This hash will help in tracking the origin and other instances of the file across the system.</p><h4>Step 5: Correlating the Process Chain</h4><p>The <strong>process GUID</strong> from <strong>svchost-Pheonixrocks.exe</strong> allows us to backtrack the event chain. Initially, we discovered the <strong>Powershell</strong> session, and now we can see that this session was responsible for retrieving and executing <strong>svchost-Pheonixrocks.exe</strong>.</p><p>Let’s use this <strong>process GUID</strong> to identify related processes:</p><ul><li>I’ll search for the <strong>Process ID (PID)</strong>: <strong>4460</strong>.</li><li>The <strong>Parent Process ID</strong>: <strong>3376</strong> tells me that the <strong>Powershell</strong> process initiated this activity.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DKnEpI6T22Yw9M_9KxXMCw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x002QJ_0_yT9NqKWwf_pMg.png" /></figure><p>Even though this process doesn’t appear to have spawned additional child processes, we can look for specific actions we know occurred. For example, we had a file named <strong>passwords.txt</strong> that was opened using <strong>Notepad</strong>.</p><p>By searching for <strong>passwords.txt</strong>, we found an event showing <strong>Explorer.exe</strong> as the parent process, and the command line showing <strong>Notepad.exe</strong> was used to view the file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PQdrphzRabLqWy7bbeBpQA.png" /></figure><h4>Step 6: Creating a Ticket for the Mythic C2 Alert</h4><p>Now that we’ve investigated the <strong>Mythic C2</strong> activity, it’s time to create an alert ticket in <strong>OS Ticket</strong> for proper tracking and further analysis.</p><h4>Here’s how to set it up:</h4><ol><li><strong>Navigate to Rules</strong>: Go to the <strong>Rules</strong> section in Elastic and locate the rule for <strong>Pheonix-Mythic-C2-Apollo-Agent-Detected</strong>.</li><li><strong>Edit the Rule</strong>: Click on <strong>Edit Rule Settings</strong> and navigate to the <strong>Actions</strong> tab.</li><li><strong>Select Webhook</strong>: Choose the <strong>Webhook</strong> option, configure the <strong>body code</strong> for alert arrangements, and click <strong>Save Changes</strong>.</li><li><strong>Set the Frequency</strong>: Ensure the rule is scheduled to run every <strong>1 minute</strong> by adjusting the <strong>Schedule</strong> settings.</li></ol><p>Now, every Mythic C2 alert will automatically create a ticket in your <strong>OS Ticket</strong> system for easy tracking and resolution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/1*DdOu5VO0-nZGCfAiuBu8Ug.png" /></figure><h3>Conclusion: Wrapping Up the Investigation</h3><p>In this blog, we peeled back the layers of a <strong>Mythic C2 agent</strong>, following its trail from initial network connections to suspicious process creations and file executions. By diving into the telemetry and piecing together the timeline, we built a clear picture of the C2 activity lurking within the system.</p><p>We didn’t stop there — we took it a step further by automating our defense, setting up a webhook in <strong>OS Ticket</strong> to ensure every future alert is swiftly documented and tracked for action.</p><p>But the investigation doesn’t end here! In the next blog, we’ll explore how to install and configure <strong>Elastic EDR (Elastic Defend)</strong> to add another layer of protection and wrap up our 30-day SOC challenge on a high note. The journey continues, so stay tuned for more insights and powerful tools to secure your environment!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a135d1dbe61c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Investigating RDP Brute Force Alerts: A Step-by-Step Guide]]></title>
            <link>https://medium.com/@vignesh3967/investigating-rdp-brute-force-alerts-a-step-by-step-guide-1128d4138eec?source=rss-80ac91a923e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/1128d4138eec</guid>
            <dc:creator><![CDATA[Vignesh Ambaykar]]></dc:creator>
            <pubDate>Fri, 27 Sep 2024 20:21:41 GMT</pubDate>
            <atom:updated>2024-09-27T20:21:41.683Z</atom:updated>
            <content:encoded><![CDATA[<p>In this blog, you’ll learn how to effectively investigate an <strong>RDP Brute Force alert</strong> and identify the critical indicators to look for during the investigation process. Whether you’re handling security incidents regularly or just starting out, this guide will help you navigate the steps involved in examining suspicious RDP activity.</p><p>Let’s jump in!</p><p>Just like with <strong>SSH Brute Force attacks</strong>, the investigative approach for <strong>RDP Brute Force attacks</strong> follows a similar pattern. Though the protocols differ, the core analysis techniques remain consistent. Additionally, once we’ve configured our alert system to work with <strong>OS Ticket</strong>, all our alerts will automatically be routed there — streamlining the process and ensuring no critical alert slips through the cracks. This automation will help you manage and track alerts efficiently.</p><h4>Step 1: Getting Started with Elastic</h4><p>Start by opening your <strong>Elastic Web GUI</strong> and navigating to the <strong>Security</strong> tab by clicking on the <strong>hamburger icon</strong>. Scroll down and select <strong>Alerts</strong>. Depending on the data in your system, the number of alerts may vary.</p><p><strong>Tip</strong>: Always ensure your <strong>time frame</strong> is set to 30 days for more comprehensive results.</p><p>In my case, I have a total of <strong>3,000 alerts</strong>, and one IP that stands out is <strong>23.164.57.20</strong>, using the <strong>username of Administrator</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4eCseJ77f2x18BwW9Vl7JQ.png" /></figure><h4>Step 2: Automating Alerts to OS Ticket</h4><p>If you remember from our previous blog on SSH Brute Force alerts, we modified the alerts to automatically create a ticket in <strong>OS Ticket</strong>. We can do the same for <strong>RDP Brute Force attacks</strong> to streamline alert management.</p><p><strong>Here’s how:</strong></p><ol><li><strong>Navigate to Rules</strong>: Go to the <strong>Rules</strong> section in Elastic and locate the <strong>RDP Brute Force</strong> rule.</li><li><strong>Edit the Rule</strong>: Click on <strong>Edit Rules</strong>, and at the top, you’ll see an <strong>Actions</strong> tab.</li><li><strong>Select Webhook</strong>: Under actions, select <strong>Webhook</strong>.</li><li><strong>Alert Configuration</strong>: Set up the body code for the alert arrangement and save the changes.</li><li><strong>Set the Schedule</strong>: Additionally, ensure the rule runs every 1 minute by going to <strong>Edit Rule Settings</strong>, clicking on <strong>Schedule</strong>, and setting the frequency.</li></ol><p>By doing this, you ensure that every alert is captured in <strong>OS Ticket</strong>, creating an automatic workflow for investigation.</p><h4>Step 3: Investigating the RDP Brute Force Alert</h4><p>Now, let’s focus on the core part of the investigation. Just like in SSH Brute Force attacks, we need to answer four critical questions:</p><ol><li><strong>Is the IP known for RDP Brute Force activity?</strong></li><li><strong>Are there any other users affected by this IP?</strong></li><li><strong>Were any of the login attempts successful?</strong></li><li><strong>If successful, what happened after the login?</strong></li></ol><h4>1. Checking the IP — 23.164.57.20</h4><p>To begin, we’ll check if this IP is known for malicious activity. As expected, the IP <strong>23.164.57.20</strong> is flagged as <strong>malicious</strong> and is known for performing <strong>RDP Brute Force attacks</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/834/1*OaBiGFy33R2zqfhO6PRPog.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uvUiuYKgq31UKZfSUQTqFA.png" /></figure><h4>2. Identifying Affected Users</h4><p>Next, let’s investigate if other users are impacted by this IP. In our case, we found that only the <strong>administrator</strong> account has been targeted by this IP.</p><h4>3. Checking for Successful Logins</h4><p>To determine if any of the login attempts were successful, search for the IP <strong>23.164.57.20</strong> in Elastic’s <strong>Discovery</strong> section. Use the event code <strong>4624</strong>, which corresponds to a successful login.</p><ul><li>In our example, there were <strong>no successful logins</strong> for this IP. So, we can conclude that no unauthorized access was gained.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*giyew7Xyf29yzMG8FJgttw.png" /></figure><p>However, in a different scenario we had previously tested (using a <strong>Mythic Command and Control</strong> attack), we did see a successful RDP brute force attempt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bW3rAaegWf1B1BGRTilExQ.png" /></figure><h4>4. What Happened After the Login?</h4><p>Let’s explore that earlier test where we <strong>successfully logged in</strong>:</p><ul><li><strong>Login Time</strong>: The attacker logged in successfully on <strong>September 21, 2024, at 18:23:50.112</strong>.</li><li><strong>End Time</strong>: The session lasted until <strong>21:02:10.629</strong> the same day.</li></ul><h4><strong>Within this time frame, several things could have occurred:</strong></h4><ul><li><strong>Process Creations</strong>: Did the attacker launch new processes?</li><li><strong>Persistence Mechanisms</strong>: Did they try to establish a persistent backdoor?</li><li><strong>Lateral Movement</strong>: Did they attempt to move across the network?</li><li><strong>Exfiltration Attempts</strong>: Were there any signs of data theft?</li><li><strong>Command and Control</strong>: Did they communicate with an external server?</li></ul><p>These are just a few possibilities to investigate when analyzing the <strong>time frame</strong> of a successful brute force login. Always keep an eye on unusual behavior, such as command execution, file downloads, or privilege escalation.</p><h4>Step 4: Investigating Previous Attacks</h4><p>As we’ve discussed before, we had previously used <strong>Mythic C2</strong> for a simulated RDP brute force attack on a Windows Server. During that investigation, we confirmed:</p><ul><li><strong>Administrator</strong> was the targeted user.</li><li>The login was successful, and further investigation uncovered potentially suspicious activity within the session.</li></ul><p>This highlights the importance of knowing what to look for after a successful login. The real work begins once you uncover <strong>what actions</strong> were taken by the attacker.</p><h4>Step 5: Building a Bigger Picture</h4><p>By now, you’ve probably realized that investigating brute force attacks follows a similar pattern, regardless of the protocol (SSH, RDP, etc.). This consistency is a <strong>blessing</strong> because once you master the steps, it becomes much easier and faster to analyze future attacks.</p><p>However, don’t underestimate the importance of understanding the <strong>big picture</strong> — what happens after an attacker gains access, and how can you spot it quickly? These are the questions that separate a basic investigation from a comprehensive one.</p><h4>Step 6: Automated Ticket Creation in OS Ticket</h4><p>Now that we’ve completed the investigation, you’ll notice that the RDP alert we just investigated has already been routed to <strong>OS Ticket</strong>. This automatic ticket creation allows you to track and manage alerts more efficiently. Once in <strong>OS Ticket</strong>, you can assign the ticket to yourself or another team member for further review and action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/859/1*UzAoqeZpJX_XCfA8nqncxg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/1*xNzLHc1s45I1-K-4-1lzJg.png" /></figure><h4>Conclusion: Mastering Brute Force Investigations</h4><p>Congratulations! You’ve now walked through the steps of investigating an <strong>RDP Brute Force attack</strong> and even automated your alert system with <strong>OS Ticket</strong>. As you’ve seen, the core methodology remains the same across protocols, and the more you practice, the quicker and more efficient your investigations will become.</p><p>In my next blog, we’ll dive deeper into the world of <strong>Mythic C2</strong> — a powerful tool for simulating and investigating advanced attacks. We’ll analyze the activity generated by a Mythic C2 agent, giving you further insights into what to look for during a post-attack investigation.</p><p>Stay tuned — there’s much more to uncover in the exciting world of cybersecurity!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1128d4138eec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Investigating SSH Brute Force Alerts: A Step-by-Step Guide]]></title>
            <link>https://medium.com/@vignesh3967/investigating-ssh-brute-force-alerts-a-step-by-step-guide-e349bfd16c9f?source=rss-80ac91a923e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/e349bfd16c9f</guid>
            <dc:creator><![CDATA[Vignesh Ambaykar]]></dc:creator>
            <pubDate>Thu, 26 Sep 2024 19:24:01 GMT</pubDate>
            <atom:updated>2024-09-26T19:24:01.100Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s interconnected digital landscape, security threats are ever-present, and one of the most common attacks that organizations face is the <strong>SSH Brute Force attack</strong>. Attackers try thousands of login attempts, hoping to crack credentials and gain unauthorized access. If you’re responsible for securing your systems, investigating and responding to these alerts is crucial.</p><p>But where do you start, and what should you look for? In this blog, we’ll break down the key steps to investigate an SSH Brute Force alert effectively. By the end, you’ll know exactly how to determine whether an attack was successful, the signs to watch out for, and how to automate your response for seamless alert management.</p><p>Let’s dive in and uncover the steps to securing your systems against brute force threats!<br>Getting Started</p><p>First, let’s navigate to our security dashboard. Click on the <strong>hamburger icon</strong>, scroll down, and select <strong>Alerts</strong> under the <strong>Security</strong> tab. You should now see the alert screen, which may show a large number of alerts — mine displays over 2,000! Depending on your situation, you might have more or fewer alerts to review.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vBsLbmB2tUjDcEBpwqtuUg.png" /></figure><h4>Key Areas to Investigate</h4><p>When investigating an SSH Brute Force alert, there are several crucial aspects to consider:</p><ol><li><strong>IP Address</strong>: Is this IP known for brute force activity?</li><li><strong>Affected Users</strong>: Are there any other users affected by this IP?</li><li><strong>Successful Logins</strong>: Were any of these login attempts successful?</li><li><strong>Post-Login Activity</strong>: If successful, what activities occurred after the login?</li></ol><p>Now, let’s dive into our alert and investigate the log using these criteria.</p><h4>Step 1: Investigate the IP Address</h4><p>For our investigation, we’ll use the IP address <strong>83.222.191.62</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oH250yucZIB4X2jbGy1u3w.png" /></figure><p><strong>Check the IP on Abuse IPDB</strong>:</p><ul><li>Copy the IP address and paste it into <a href="https://www.abuseipdb.com/">Abuse IPDB</a>. This tool will help us determine if the IP is associated with malicious activity.</li><li>The result indicates that this IP is indeed known for performing brute force attacks.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/835/1*NI2RtAPQnD9XASUGrkn6TQ.png" /></figure><p><strong>Check the IP on GreyNoise</strong>:</p><ul><li>Next, open <a href="https://greynoise.io/">GreyNoise</a> and click on <strong>Get Started for Free</strong>.</li><li>Enter the same IP address in the search bar. The result again confirms that this IP is malicious.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eYyjdR1_VhdIiR__7lpWng.png" /></figure><p><strong>Conclusion</strong>: The answer to our first question — <strong>Is this IP known for brute force activity?</strong> — is <strong>YES</strong>.</p><h4>Step 2: Identify Affected Users</h4><p>Next, we need to determine which users are affected by this IP.</p><ul><li>Go to <strong>Elastic</strong> and select <strong>Discover</strong>.</li><li>Paste the copied IP in the search bar.</li><li>Check the <strong>user.name</strong> field (located on the left-hand side under field names).</li></ul><p>From our search, we find that the affected user is <strong>1</strong> and the user is <strong>root</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6watCUbDzTiK719wAfsUxQ.png" /></figure><h4>Step 3: Check for Successful Logins</h4><p>Now, let’s investigate whether any of the login attempts were successful.</p><ul><li>Remain on the same page as the previous step and modify your search query to include both the IP address and <strong>“Accepted”</strong>.</li><li>In my case, there were <strong>no successful logs</strong>, leading us to conclude that the answer to our question — <strong>Were any of these logins successful?</strong> — is <strong>NO</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*afq96Jz3RUmxM8dI3iOKgg.png" /></figure><h4>Step 4: Investigate Post-Login Activity</h4><p>This question is crucial: If there had been a successful login, what activities occurred afterward? Possible actions could include:</p><ul><li>Downloading malicious scripts</li><li>Executing discovery commands</li><li>Establishing persistence</li><li>Running privilege escalation tools like <strong>LinPEAS</strong></li></ul><p>Since we found no successful logins, we will simply state <strong>NO</strong> for our fourth question.</p><h4>Conclusion of the Investigation</h4><p>Given that there were no successful logins, we can confidently close this particular alert.</p><h4>Automating Alerts to Your Ticketing System</h4><p>Next, let’s modify our rules to send alerts to our ticketing system. Here’s how:</p><ol><li>Click on <strong>Rules</strong> on the left sidebar and select <strong>Detection Rules</strong>.</li><li>Locate <strong>SSH Brute Force Attempt</strong> and click on it.</li><li>Inside, select <strong>Edit Rule Settings</strong>, then navigate to the <strong>Action</strong> tab at the top and select <strong>Webhook</strong>.</li></ol><p>You should see your <strong>OS Ticket connector</strong> available. For <strong>Action Frequency</strong>, choose <strong>for each alert</strong>. In the <strong>Body</strong>, use the same OS Ticket GitHub test body and edit it as needed for your context.</p><p>Once you’ve made your changes, click <strong>Save Changes</strong>. It may take some time to receive an alert ticket, so let’s be patient.</p><h4>Step 5: Managing Your Tickets in OS Ticket</h4><p>Now, let’s head over to <strong>OS Ticket</strong> to manage our newly created alert ticket:</p><ol><li>Navigate to the <strong>Admin Panel</strong> in OS Ticket.</li><li>Once you are inside, you should see the ticket for your alert.</li><li>Click on the ticket to open it. From here, you can assign the ticket to a specific user, or you can assign it to yourself.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*1oWWAMNczAZtyvty9-gR2w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*b2pH4OSFsCEfOwN6kuRf1Q.png" /></figure><h4>Conclusion</h4><p>Congratulations! You’ve now successfully navigated the entire process of investigating an SSH Brute Force alert — from identifying malicious IPs to managing your alerts in a ticketing system. By following this structured approach, you’re not only safeguarding your systems but also streamlining your incident response workflow.</p><p>Remember, every alert is a potential threat, and by mastering these investigative steps, you’re staying one step ahead of attackers. You’ve also taken the extra step of integrating your alerts with OS Ticket, ensuring that no critical notification slips through the cracks.</p><p>In the fast-paced world of cybersecurity, there’s always something new to learn and refine. In my next blog, we’ll turn our focus to <strong>RDP Brute Force activity</strong>, diving into how to detect and mitigate these attacks just as efficiently.</p><p>Stay sharp and stay secure — until next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e349bfd16c9f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Seamlessly Integrating OS Ticket with Elastic Stack: A Complete Guide]]></title>
            <link>https://medium.com/@vignesh3967/seamlessly-integrating-os-ticket-with-elastic-stack-a-complete-guide-d7597c1aca90?source=rss-80ac91a923e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7597c1aca90</guid>
            <dc:creator><![CDATA[Vignesh Ambaykar]]></dc:creator>
            <pubDate>Wed, 25 Sep 2024 17:06:46 GMT</pubDate>
            <atom:updated>2024-09-25T17:06:46.396Z</atom:updated>
            <content:encoded><![CDATA[<p>In this guide, I’ll walk you through how I successfully integrated <strong>OS Ticket</strong> with my <strong>Elastic Stack</strong>. This integration automates ticket creation in OS Ticket whenever an alert is triggered in Elastic, enhancing your incident management and tracking workflow. Let’s dive in!</p><h4>Step 1: Access Your OS Ticket Admin Panel</h4><p><strong>Login to your OS Ticket instance</strong>.</p><p><strong>Navigate to the Admin Panel</strong>:</p><ul><li>Click on <strong>Admin</strong> at the top right corner of the page.</li></ul><p><strong>Add a New API Key</strong>:</p><ul><li>Under the Admin Panel, click on <strong>Manage</strong> and select <strong>API</strong>.</li><li>Click <strong>Add New API Key</strong>.</li></ul><p>For the IP address, use your <strong>ELK server’s private IP</strong>, as both the OS Ticket server and ELK server are in the same Virtual Private Cloud (VPC). If they were not in the same VPC, you would use the public IP instead.</p><blockquote><strong><em>Note</em></strong><em>: If you forgot your ELK server’s private IP, you can retrieve it from Vultr:</em></blockquote><ul><li>Go to <strong>Vultr</strong> and select your ELK server.</li><li>On the left side, click on <strong>Settings</strong> and then select <strong>VPC 2.0</strong>. The private IP will be listed here.</li></ul><p>Copy the private IP and paste it into the OS Ticket API form.</p><p><strong>Set Permissions and Notes</strong>:</p><ul><li>Enable <strong>Create Tickets</strong> under the Services section.</li><li>For Internal Notes, you can add any description you like. In this example, we’ll use “Phoenix 30-Day Elastic Connector.”</li><li>Click <strong>Add Key</strong>.</li></ul><p>Now that the API key is created, <strong>copy it</strong> and save it in a notepad for future use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*6cQe1LhZnuY7-SPU_5AEdg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*otgyswKHKXZ1NQclKlRHGA.png" /></figure><h4>Step 2: Configure Elastic for API Integration</h4><p><strong>Log into Elastic</strong>:</p><ul><li>Click on the <strong>hamburger icon</strong> (menu) and scroll down to the <strong>Management</strong> tab.</li></ul><p><strong>Navigate to Stack Management</strong>:</p><ul><li>Under <strong>Alerts and Insights</strong>, select <strong>Connectors</strong>.</li><li>Click on <strong>Create Connector</strong>.</li></ul><blockquote><strong><em>Important</em></strong><em>: Elastic’s free tier does not support API integration. You need to activate a 30-Day Free Trial to enable this feature.</em></blockquote><p><strong>Activate the 30-Day Trial</strong>:</p><ul><li>Go to <strong>Manage License</strong> and select <strong>Start a 30-Day Trial</strong>.</li></ul><p>Once the trial is active, you’ll have access to third-party integrations, including API connectors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ad_y3jUmuEjvzHY0YQ3eOQ.png" /></figure><p><strong>Create a Webhook Connector</strong>:</p><ul><li>Click on <strong>Create Connector</strong>.</li><li>Select <strong>Webhook</strong> as your connector type.</li><li>Name the connector “OS Ticket.”</li></ul><p>For the <strong>Post Request URL</strong>, use your OS Ticket’s private IP. The format should be:</p><pre>http://(Private-IP-OS-Ticket)/osTicket/upload/api/tickets.xml</pre><p><strong>Configure Authentication</strong>:</p><ul><li>Select <strong>None</strong> under Authentication.</li><li>Add an <strong>HTTP header</strong>:</li><li>Key: X-API-Key</li><li>Value: Your OS Ticket API Key (which you copied earlier).</li><li>Click <strong>Save and Test</strong>.</li></ul><p>Elastic will then prompt you to <strong>create an action</strong> and define the body of the request. You can find an example body on the OS Ticket GitHub page to ensure the format is correct.</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br>&lt;ticket alert=&quot;true&quot; autorespond=&quot;true&quot; source=&quot;API&quot;&gt;<br>    &lt;name&gt;Angry User&lt;/name&gt;<br>    &lt;email&gt;api@osticket.com&lt;/email&gt;<br>    &lt;subject&gt;Pheonix-30DayChallenge-Pheonixrocks&lt;/subject&gt;<br>    &lt;phone&gt;318-555-8634X123&lt;/phone&gt;<br>    &lt;message type=&quot;text/plain&quot;&gt;&lt;![CDATA[Message content here]]&gt;&lt;/message&gt;<br>    &lt;attachments&gt;<br>        &lt;file name=&quot;file.txt&quot; type=&quot;text/plain&quot;&gt;&lt;![CDATA[<br>            File content is here and is automatically trimmed<br>        ]]&gt;&lt;/file&gt;<br>        &lt;file name=&quot;image.gif&quot; type=&quot;image/gif&quot; encoding=&quot;base64&quot;&gt;<br>            R0lGODdhMAAwAPAAAAAAAP///ywAAAAAMAAwAAAC8IyPqcvt3wCcDkiLc7C0qwy<br>            GHhSWpjQu5yqmCYsapyuvUUlvONmOZtfzgFzByTB10QgxOR0TqBQejhRNzOfkVJ<br>            +5YiUqrXF5Y5lKh/DeuNcP5yLWGsEbtLiOSpa/TPg7JpJHxyendzWTBfX0cxOnK<br>            PjgBzi4diinWGdkF8kjdfnycQZXZeYGejmJlZeGl9i2icVqaNVailT6F5iJ90m6<br>            mvuTS4OK05M0vDk0Q4XUtwvKOzrcd3iq9uisF81M1OIcR7lEewwcLp7tuNNkM3u<br>            Nna3F2JQFo97Vriy/Xl4/f1cf5VWzXyym7PHhhx4dbgYKAAA7<br>        &lt;/file&gt;<br>    &lt;/attachments&gt;<br>    &lt;ip&gt;123.211.233.122&lt;/ip&gt;<br>&lt;/ticket&gt;</pre><h4>Step 3: Update OS Ticket Network Settings</h4><p>Before testing the integration, update the OS Ticket server’s IP address configuration:</p><p><strong>Connect to your OS Ticket server via RDP</strong>.</p><p><strong>Change IP Settings</strong>:</p><ul><li>Open <strong>Control Panel</strong> &gt; <strong>View Network Status and Tasks</strong>.</li><li>Click on <strong>Change Adapter Settings</strong>.</li><li>Select <strong>Ethernet Instance 0</strong> &gt; <strong>Properties</strong>.</li><li>Choose <strong>Internet Protocol Version 4 (TCP/IPv4)</strong> and select the option to manually enter an IP address.</li><li>Input the private IP address for your OS Ticket server (you can find it in Vultr under <strong>Settings &gt; VPC 2.0</strong>).</li><li>Click <strong>OK</strong> and <strong>Apply</strong>.</li></ul><h4>Step 4: Test the Integration</h4><p><strong>Run a Test in Elastic</strong>:</p><ul><li>Go back to Elastic, and click <strong>Run Test</strong>.</li><li>If successful, the test will generate a ticket in OS Ticket.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jxSstfwWnoohDvWBL336mg.png" /></figure><p><strong>Verify in OS Ticket</strong>:</p><ul><li>Log into your OS Ticket Admin Panel and check the ticketing section.</li><li>You should see a new ticket titled <strong>Pheonix-30DayChallenge-Pheonixrocks</strong> (or the subject name you provided).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*CgWSqrEsg2gZmAX1ZMmUOQ.png" /></figure><p>Congratulations! You’ve successfully integrated OS Ticket with Elastic. This allows you to automatically generate tickets from Elastic alerts, improving your auditing and incident tracking.</p><h4>Recap: What We’ve Accomplished</h4><ol><li><strong>Spun up Elastic and Kibana instances</strong>.</li><li><strong>Set up two servers</strong> (Windows and Linux) and installed agents to push data to Elastic.</li><li><strong>Created alerts and dashboards</strong> for monitoring brute force attacks on SSH and RDP.</li><li><strong>Identified common Command and Control (C2) frameworks</strong>, like Mythic.</li><li><strong>Integrated a ticketing system (OS Ticket)</strong> into the stack to manage and track alerts.</li></ol><p>By following these steps, you’ve created a fully functioning mini-Security Operations Center (SOC) environment with Elastic and OS Ticket.</p><p>In my next blog, we will dive into investigating the alerts we’ve set up, starting with the SSH brute force alerts. Stay tuned!</p><p>I hope this guide helped you integrate OS Ticket into your tech stack. If you have any questions or need further clarification, feel free to leave a comment!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7597c1aca90" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Set Up and Configure osTicket: A Step-by-Step Guide]]></title>
            <link>https://medium.com/@vignesh3967/how-to-set-up-and-configure-osticket-a-step-by-step-guide-4b61bba87506?source=rss-80ac91a923e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b61bba87506</guid>
            <dc:creator><![CDATA[Vignesh Ambaykar]]></dc:creator>
            <pubDate>Tue, 24 Sep 2024 12:20:54 GMT</pubDate>
            <atom:updated>2024-09-24T12:20:54.696Z</atom:updated>
            <content:encoded><![CDATA[<p>In this blog, I’ll walk you through the process of setting up and configuring osTicket, a powerful open-source ticketing system. By the end of this guide, you’ll have a fully operational osTicket instance ready for your team to start managing requests and incidents. Let’s dive in!</p><h4>Step 1: Deploy a Server on Vultr</h4><p>To start, head over to <a href="https://www.vultr.com/">Vultr</a> and log in to your account. Follow these steps to deploy your server:</p><p><strong>Deploy a New Server:</strong></p><ul><li>Click on the <strong>Deploy</strong> button in the top-right corner.</li><li>Select <strong>Deploy New Server</strong>.</li><li>Since osTicket doesn’t require heavy resources, choose <strong>Cloud Compute (Shared CPU)</strong>.</li></ul><p><strong>Configure the Server:</strong></p><ul><li><strong>Location:</strong> Choose your preferred location (I selected London).</li><li><strong>Operating System:</strong> Select <strong>Windows Standard 2022</strong>.</li><li><strong>Plan:</strong> Use the default plan, which includes 55 GB SSD, 1 vCPU, 2 GB RAM, and 55 GB storage.</li><li><strong>Extras:</strong> Unselect <strong>Auto Backup</strong> and <strong>IPv6</strong>, but enable <strong>Virtual Private Cloud 2.0</strong>.</li><li><strong>Name Your Server:</strong> I named mine <strong>Phoenix-osTicket</strong>, but you can choose your own.</li></ul><p><strong>Deploy:</strong> Click <strong>Deploy Server</strong> and wait for your server to start running.</p><p>Once the server is up, you’ll need to Remote Desktop Protocol (RDP) into the machine. Copy the username and password provided, and log in to your new server.</p><h4>Step 2: Set Up a Firewall</h4><p>Before we proceed, it’s essential to secure your server since it will host a web server that could be accessible to the public. Here’s how to add a firewall:</p><p><strong>Go to Firewall Settings:</strong></p><ul><li>Navigate to <strong>Settings</strong> and then select <strong>Firewall</strong>.</li><li>I used the <strong>Phoenix-SOC-Challenge</strong> firewall.</li></ul><p><strong>Why Set Up a Firewall?</strong> The firewall ensures that only authorized users can access your ticketing system. It will prevent unauthorized traffic from accessing the web server.</p><h4>Step 3: Install XAMPP to Host the Web Server</h4><p>We need a web server to host osTicket. For this, we’ll use XAMPP, which is an easy-to-use package from Apache.</p><p><strong>Download XAMPP:</strong></p><ul><li>Search for XAMPP and download it from <a href="https://www.apachefriends.org/">Apache Friends</a>.</li><li>Choose version <strong>8.2.12</strong> and click <strong>Download</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*84c9IzrjDWkYN4CnCSPjyQ.png" /></figure><p><strong>Install XAMPP:</strong></p><ul><li>Run the installer and keep all settings as default. Click <strong>Next</strong> until the installation is complete.</li><li>Once installed, open the <strong>XAMPP Control Panel</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/497/1*-513nqfj2E9jaxFE5wEKHg.png" /></figure><h4>Step 4: Configure XAMPP for osTicket</h4><p>With XAMPP installed, we now need to configure it for osTicket.</p><p><strong>Update Apache Configuration:</strong></p><ul><li>Navigate to C:\XAMPP and find the Apache configuration file.</li><li>Change the domain name from localhost to your server’s public IP address.</li><li>Save the changes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/428/1*2Abab-2PV07fRkhQY1jjig.png" /></figure><p><strong>Configure phpMyAdmin:</strong></p><ul><li>In the XAMPP directory, go to phpMyAdmin/config.inc.php.</li><li>Make a backup of this file and open the original with Notepad.</li><li>Change the server host from 127.0.0.1 to your osTicket server&#39;s public IP address.</li><li>Save and exit.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/769/1*REiu7fr487atBgAXS_0-LQ.png" /></figure><p><strong>Set Up Firewall Rules:</strong></p><ul><li>Open <strong>Windows Defender Firewall</strong> and navigate to <strong>Inbound Rules</strong>.</li><li>Create a new rule to allow inbound connections on <strong>Port 80</strong> and <strong>Port 443</strong>.</li><li>Name this rule and save it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/1*vdzglF8nU58clSWM8Z5wZA.png" /></figure><p><strong>Start Apache and MySQL Services:</strong></p><ul><li>Open the XAMPP Control Panel and start <strong>Apache</strong> and <strong>MySQL</strong> services.</li><li>Click on <strong>Admin</strong> under Apache to access <strong>phpMyAdmin</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*yYV1gleY6ljbAnk5xSpP5g.png" /></figure><h4>Step 5: Install osTicket</h4><p>Now that your web server is ready, it’s time to install osTicket.</p><p><strong>Download osTicket:</strong></p><ul><li>Visit osTicket and download the <strong>Self-Hosted</strong> version (<strong>1.18.1</strong>).</li><li>Extract the downloaded file.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T42p5e7MY4vcH6Z-ocTsrQ.png" /></figure><p><strong>Move osTicket to XAMPP:</strong></p><ul><li>In your XAMPP directory, navigate to htdocs.</li><li>Create a new folder called osTicket and move the extracted osTicket files into it.</li></ul><p><strong>Launch the osTicket Setup:</strong></p><ul><li>Open your browser and go to http://[Your Server IP]/osTicket/upload.</li><li>Follow the setup instructions.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gsKeoEfQts9AcG5zmuTUwg.png" /></figure><p><strong>Fix Missing Extensions:</strong></p><ul><li>During the setup, you may see warnings about missing extensions like <strong>GDlib</strong> or <strong>PHP Imap</strong>. For this challenge, these extensions aren’t necessary, so you can safely ignore the warnings and proceed with the installation.</li></ul><p><strong>Configure osTicket:</strong></p><ul><li>Set up your Help Desk Name (e.g., <strong>Phoenix Support</strong>).</li><li>Fill in your default email, admin name, and other relevant details.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BfPpjOgzxdhTMyqoWQLVsA.png" /></figure><h4>Step 6: Create and Configure the Database</h4><p>Before completing the osTicket installation, we need to create a MySQL database:</p><p><strong>Create the Database in phpMyAdmin:</strong></p><ul><li>Go to phpMyAdmin, click <strong>New</strong>, and create a database named Phoenix-30-Day-DB.</li></ul><p><strong>Grant Privileges:</strong></p><ul><li>Navigate to <strong>User Accounts</strong> and select the root user.</li><li>Ensure that this user has privileges to access the new database.</li></ul><p><strong>Complete osTicket Installation:</strong></p><p>Return to the osTicket setup page and fill in the database details (DB name, root username, and password).</p><ul><li>Click <strong>Install</strong> and wait for the process to complete.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/819/1*re0MsgfKC542Cli0A6M4WA.png" /></figure><h4>Step 7: Final Configurations</h4><p>Once osTicket is installed, you’ll need to finalize a few settings:</p><p><strong>Set File Permissions:</strong></p><p>Open <strong>PowerShell</strong> as an administrator.</p><ul><li>Navigate to the osTicket configuration file (ost-config.php), located in htdocs/include.</li><li>Run the following command to reset permissions:</li></ul><pre>icacls .\ost-config.php /reset</pre><p>You should see a success message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/1*47F9CL9FSJ9cpwzvqoD3Iw.png" /></figure><p><strong>Access osTicket Admin Panel:</strong></p><ul><li>Copy the <strong>Staff Control Panel URL</strong> and open it in your browser.</li><li>Log in using your credentials.</li></ul><h4>Step 8: Outsider Login (End-User Access)</h4><p>Once osTicket is set up, end-users (customers or internal team members) will be able to submit tickets through the client portal. Here’s how they can access it:</p><p><strong>Access the Client Portal:</strong></p><ul><li>Users can visit the public osTicket URL. This is typically in the format:</li></ul><pre>http://[Your Server IP]/osTicket/upload</pre><ul><li>This is the page where outsiders (or customers) can log in or create new tickets.</li></ul><p><strong>Submit a Ticket:</strong></p><p>Users can create new tickets by providing their name, email, and issue details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Eabe-81iRud7OiltnGhd8g.png" /></figure><h4>Step 9: Admin Login (Staff and Agent Access)</h4><p>The admin login is where your support team will manage and resolve incoming tickets. Here’s how to log in as an admin:</p><p><strong>Access the Admin Panel:</strong></p><ul><li>To access the admin (staff) control panel, visit the following URL:</li></ul><pre>http://[Your Server IP]/osTicket/upload/scp</pre><ul><li>This will prompt you to log in with the credentials you set during the installation process.</li></ul><p><strong>Admin Dashboard:</strong></p><ul><li>After logging in, admins will have access to the full osTicket dashboard where they can:</li><li>View, assign, and respond to tickets.</li><li>Manage staff and departments.</li><li>Configure system settings and plugins.</li><li>Access various reports and analytics about ticket activity.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5mH84L1tLEFUxWb6G8wujg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZAwNSVWyXDdYqChnrUqmNQ.png" /></figure><h4>Conclusion</h4><p>Congratulations! You’ve successfully set up your own osTicket instance. You now have a fully functional ticketing system ready to handle requests. In my next blog, I’ll cover how to integrate osTicket with your tech stack to automate alert generation and ticket creation.</p><p>Stay tuned, and feel free to share your thoughts or ask any questions in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b61bba87506" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>