<?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 Fidan Babakhanli on Medium]]></title>
        <description><![CDATA[Stories by Fidan Babakhanli on Medium]]></description>
        <link>https://medium.com/@fidanbabakhanli?source=rss-ca9d5045dde2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*iWkr_wBnuyBZTVYzMYJjcw@2x.jpeg</url>
            <title>Stories by Fidan Babakhanli on Medium</title>
            <link>https://medium.com/@fidanbabakhanli?source=rss-ca9d5045dde2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:44:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fidanbabakhanli/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[Deploying IBM QRadar as a Second SIEM for Windows: Logs, Sysmon & Flows]]></title>
            <link>https://medium.com/@fidanbabakhanli/deploying-ibm-qradar-as-a-second-siem-for-windows-logs-sysmon-flows-bfe18bb4d265?source=rss-ca9d5045dde2------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfe18bb4d265</guid>
            <dc:creator><![CDATA[Fidan Babakhanli]]></dc:creator>
            <pubDate>Fri, 31 Oct 2025 12:34:36 GMT</pubDate>
            <atom:updated>2025-10-31T12:34:36.090Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*ZdRL0ndVOvxbPN8FBF-syA.png" /></figure><p><strong><em>OBJECTIVE:</em></strong><em> To install IBM QRadar and enable monitoring of Windows Server systems. Based on the logging rules previously implemented on the servers, selected logs should be sent to QRadar; in addition, Sysmon should be installed and more detailed logs should be collected with Threat Hunting configuration. Sysmon logs should also be forwarded to QRadar. In addition, at least 5 custom Crime rules should be created in QRadar and tested in operation. Additional reasons (True Positive and False Positive) should be selectable when closing crimes. Finally, the Network Flow section should be enabled and network traffic should be visible in QRadar.</em></p><p><strong>The WinCollect agent was downloaded from the IBM Support website.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*96_1rvHQa8v9wm1WHfP3pw.png" /></figure><p><strong>The agent was installed, and the QRadar server IP address was provided so the agent would send logs.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JPInsoNyx-ryElNLscc9LQ.png" /></figure><p><strong>The sources we wanted to be sent were configured inside the QRadar agent.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OBxZ10ydfG7T0DkwOADfww.png" /></figure><p><strong>A rule was added on the Windows Firewall so that logs can be sent directly from the local server to the cloud.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vZwzbt5rfk9YI9m0kSlh4A.png" /></figure><p><strong>On the QRadar dashboard, we already saw Windows Server as a log source.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8WwZ3Xw9ugscUWjmJpohig.png" /></figure><p><strong>Additionally, Sysmon was configured for threat hunting.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2EuHr80wa4uvFD2QrDRLYw.png" /></figure><p><strong>After Sysmon was configured, it was also configured within the agent so that its logs would be collected via WinCollect.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XXVwENZ1wz5dIF5u9nVrVQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nY226T-Rz756oUmrM8hcfw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z36BWKnzALcfrwCypEn0Vw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j0nFrubXXd9Nr4qhML7vnQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LqvZXN1mOFrc7Rcnwkobdg.png" /></figure><p><strong>We already see both the Windows logs and the Sysmon logs in QRadar.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q6NKilduTEwgEgh7pBsxHQ.png" /></figure><p><strong>Within QRadar, under Rules, a “fidan” rule group was created, and 6 different rules were created within the group.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*je342aQjJ1MdBRqKsPAzSw.png" /></figure><p><strong>User created rule</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*744rc2CRdmZbbbG5hNxOGA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lMg58OK4u8hG6Fer1ClGTA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T5q-BQ4oxNjRGrT7GzFjIg.png" /></figure><p><strong>User add to administrators group</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KeypYP20NcP7gMTh3uQTnA.png" /></figure><p><strong>Event log cleared</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wiGwOUS9UB8YD73RTKSqFw.png" /></figure><p><strong>Brute force rule</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zSfayyCjCJbE5_uBObWPlA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jj4GwDZYk4bof2yQysY_Gg.png" /></figure><p><strong>Each created offense rule was tested, and it was observed that offenses were generated according to the categories.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fdjaiXXuPY1-mkd6Z6iSaQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*naCb8DRXwRib5YBACug-Sw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8s_nmbcIHxJDKx2tAgZwug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pT8MjnLVViXOLiSrRj8Onw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MGijw6B0vkED3_n50G5Glg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5a_yqeYftiH88UOTzJX4Yg.png" /></figure><p><strong>First, we go to the Admin tab.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*YnJFq-xEZUTnVt1tK8ca0Q.png" /></figure><p><strong>Then we go to “Custom Offense Close Reasons” and write 2 custom reasons.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/834/1*KlXe79tbc1ySUBV_YblZZA.png" /></figure><p><strong>When closing the opened offenses, we select the required reason.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*fXNS3SBjt48-CtAgK41eOw.png" /></figure><p><strong>Qradar netflow config</strong></p><p><strong>The Apache web service was started on Ubuntu.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CJbFYKMgo4o10oStFAjBoA.png" /></figure><p><strong>We saw that the web service is up, and the server’s default page is already accessible over the internet.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KLiMrzKA47QMl6_zItZgxg.png" /></figure><p><strong>Softflowd was installed to send the web server’s traffic logs.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zwqnxFlT9NXrzUAOu05ztQ.png" /></figure><p><strong>The following command was used to forward the logs.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1gJKnCxZkaCl5HSUfGMu4w.png" /></figure><p><strong>We configured the Flow Source section in QRadar.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SxlO6ri_skknuHz0YhvS8A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C0g6VZqcsB87nZS12LhcGA.png" /></figure><p><strong>Now, in the netflow section, all traffic coming to our web server is visible.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z0XTer-4N9qYfHOCLH3YBg.png" /></figure><p><strong><em>RESULT:</em></strong><em> QRadar Installation and Collection of Windows Logs — WinCollect agent was installed on Windows servers, and the QRadar server IP was added in the agent configuration. Windows Event Log sources were selected and directed to QRadar. The required rules were opened on the Windows Firewall, and as a result, Windows Server logs began to successfully appear on the QRadar dashboard.<br> Sysmon Installation and Threat Hunting Configuration — Sysmon was installed on the server, and the ready Threat Hunting configuration file was applied. Sysmon logs were collected via the WinCollect agent and sent to QRadar. As a result, both Windows logs and Sysmon logs could be monitored via QRadar.<br> Creation of Offense Rules — A special “Fidan Rule Group” was created in the QRadar console, and 6 different Offense rules were written within it. Among them:<br> • Creation of a new user (user creation)<br> • Adding the user to the administrators group<br> • Deletion of the Event Log<br> • Detection of brute-force attack<br> • Other additional security rules<br> All rules were tested, and it was confirmed that in appropriate attack scenarios, alerts were automatically generated in QRadar’s Offense section.<br> Custom Offense Close Reasons — In QRadar, in the “Custom Offense Close Reasons” section, two new reasons were additionally created:<br> • True Positive<br> • False Positive<br> Now, when closing an Offense, one of these reasons is selected, and as a result, proper categorization of incidents is ensured.<br> Network Flow Configuration — For test purposes, an Apache web server was brought up on Ubuntu and made accessible over the internet. softflowd was installed and the traffic logs were directed to QRadar. The Flow Source section was configured in QRadar, and as a result, all network traffic coming to the web server was displayed in real time in the NetFlow section.<br> Overall result: At this stage, QRadar was successfully deployed and Windows Server logs were directed to the SIEM. By applying the Sysmon Threat Hunting configuration, more detailed logs were collected. At least 5 individual Offense rules were created and tested in working condition. Additional reasons (True Positive and False Positive) were added for closing Offenses. Network Flow integration was also implemented, and traffic monitoring of the server was ensured via QRadar</em>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfe18bb4d265" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WAF Deployment and Configuration with Sucuri and Splunk Integration]]></title>
            <link>https://medium.com/@fidanbabakhanli/waf-deployment-and-configuration-with-sucuri-and-splunk-integration-766bf7dd6d23?source=rss-ca9d5045dde2------2</link>
            <guid isPermaLink="false">https://medium.com/p/766bf7dd6d23</guid>
            <dc:creator><![CDATA[Fidan Babakhanli]]></dc:creator>
            <pubDate>Fri, 26 Sep 2025 11:09:02 GMT</pubDate>
            <atom:updated>2025-09-26T11:46:49.597Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/933/1*mfEsJ8uoMG-ye6bd4ZF73A.png" /></figure><p><strong><em>Objective:</em></strong><br><em> The purpose of this step is to set up a WAF (Web Application Firewall) for the website, block attacks, and ensure additional security measures. For this, </em><strong><em>Sucuri WAF</em></strong><em> was used. With the WAF, SQL Injection, brute-force, and other types of attacks should be prevented, country-based blocking should be applied, and custom rules (based on user-agent and HTTP headers) should be written. In addition, the transfer of Sucuri WAF logs to </em><strong><em>Splunk</em></strong><em> must be ensured and stored in a separate index called WAF.</em></p><p><strong><em>1.Sucuri WAF — Registration and Login Page</em></strong><br> It is possible to use a one-month free trial on Sucuri by adding a business email and a payment card.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eUPvAk_22DuyfW0c8groqg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zmIudUdHI4qCazLqgUGmeg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2V_wrNSnw3b1Y-q9-nYDqg.png" /></figure><p><strong><em>2.Changing the DNS A Record of the Domain Purchased from Namecheap</em></strong><br> We update the domain’s DNS A record (also noted in Sucuri) to point to the new IP address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fwNnM9Pup8pT6qWp66lVaA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QKTOFfpfkdrFE9in5EjRAw.png" /></figure><p>When checking the domain’s IP address with nslookup, the WAF’s IP address should be displayed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*FOC7lMnlvg-JOaOC0msZsw.png" /></figure><p>After waiting for a while, the WAF became active.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WJP1obEut-Avnppd8Pd1uQ.png" /></figure><p><strong><em>3. In the Security section, we enable HTTPS.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C53owj5krKoJHsfVlMNghg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PLOzLFo2wYBmqFyaWSuEgg.png" /></figure><p>At this point, it is possible to see that the WAF is active.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TOL-tOpgLTg5DQNRAV_sjw.png" /></figure><p><strong><em>4. For country-based blocking, I went to the Geo Blocking section and blocked Armenia.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mQItkCn4iPnS_Lro5Keckw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cw78p627PPQAhzkHWDIKBQ.png" /></figure><p><strong><em>5. Adding Acunetix IP Address to the Whitelist (Allow IP Address) as a Scan Tool</em></strong><br>Since Sucuri WAF does not have a function for automatic 15-minute blocking, instead, IP addresses added to the blocklist can be manually blocked for 30 minutes.<br>We also make certain changes in the Security section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qA5SEtdCIIUWX6TYuHVofw.png" /></figure><p>From the Real-time section, we can see whether requests coming from different countries are allowed or blocked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ckrBmAKjtRkSX2VrbRtp9Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jyuOsJCnpi4wXVQL0kStcg.png" /></figure><p><strong><em>6. In the Block User-Agents section, we create a custom rule to block agents that match the User Agents we specify</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yp1pKqqihfvXNHnEeWSf4Q.png" /></figure><p>Here, we also add several cookies to be blocked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2fsQI3tduaFTA3PIUJdA1Q.png" /></figure><p><strong><em>7. Steps to be Performed on the Server that Will Fetch Sucuri Logs and Send Them to Splunk:</em></strong><br>We install Python and pip, and then install the required Python modules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YDosqv9qVQkx5MO-NLPQSg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PHxt7dG0qgxu9tYAWL6UzA.png" /></figure><p><strong><em>Creating the script</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Iuc3h39N0K_jNryIlSJdtQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9x5HANH2LS5VNfuynMBxOw.png" /></figure><p><strong><em>Then we grant permission</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XWrgxwfijvT8C5jZ3wU0oQ.png" /></figure><p><strong><em>systemd service file → /etc/systemd/system/sucuri-logger.service</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LXUZzzVO5FMtrHUHYQlfZQ.png" /></figure><p><strong><em>8. Creating a New HEC Token for Sucuri WAF</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*YuZc-WiKZ5I7iA9NYi5ZSQ.png" /></figure><p><strong><em>We restart the script.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ANUoaJSw6zmOtAP3VLBFxA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eB5GbInS_vNPE8_kDgM7hA.png" /></figure><p><strong><em>Conclusion:</em></strong><br><em> </em><strong><em>WAF Installation and Activation</em></strong><em> — The WAF was activated through Sucuri, and the domain’s A record was updated so that traffic was routed through Sucuri WAF. During verification with nslookup, the domain’s IP was now shown as the WAF IP address. HTTPS support was enabled, and the website started operating under WAF protection.</em></p><p><strong><em>Country-Based Blocking</em></strong><em> — Using the Geo-Blocking section in the Sucuri panel, the country of Armenia was completely blocked. All requests from this country were stopped by the WAF before reaching the server.</em></p><p><strong><em>Blocking Attacks and Custom Rules</em></strong><em> — The automatic IP blocking function of Sucuri WAF was tested. The attacking IP address was added and blocked for a certain period. Since the default 15-minute blocking option was not available, manual blocking was applied for a minimum of 30 minutes. Additionally, a custom rule was created for requests using the sqlmap user-agent — these requests were automatically blocked by the WAF. Further rules were also set up based on cookies and headers if needed.</em></p><p><strong><em>Whitelist Additions</em></strong><em> — The IP addresses of security scanners such as Acunetix and Nessus, used for vulnerability testing, were added to the WAF whitelist. This ensured that Sucuri did not block their requests and that testing was completed without issues.</em></p><p><strong><em>Log Forwarding to Splunk</em></strong><em> — Using Sucuri’s API key, a Python script was created on a dedicated server. Through this script, WAF logs were fetched and sent to Splunk. A separate index called WAF was created in Splunk for these logs. With a systemd service, the script was automated to ensure continuous operation.</em></p><p><strong><em>Detection and Alerts</em></strong><em> — Based on Sucuri WAF logs, alerts were configured in Splunk. For example, when requests containing sqlmap in the http_user_agent field were detected, an immediate alert was generated. These alerts were also sent via email to the administrator. Thus, a real-time detection and alerting system was established based on WAF logs.</em></p><p><strong><em>Overall Result:</em></strong><em> Sucuri WAF was successfully deployed and activated on the domain. Country-based blocking was applied, custom rules were implemented to block sqlmap and other malicious user-agents, and scanner IPs like Acunetix and Nessus were whitelisted. WAF logs were forwarded to Splunk and stored in a separate index, where real-time alerts were created. As a result, the website gained an additional layer of protection, ensuring effective detection and prevention of attacks.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=766bf7dd6d23" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cybersecurity and System Hardening Practices]]></title>
            <link>https://medium.com/@fidanbabakhanli/cybersecurity-and-system-hardening-practices-a887babdafeb?source=rss-ca9d5045dde2------2</link>
            <guid isPermaLink="false">https://medium.com/p/a887babdafeb</guid>
            <dc:creator><![CDATA[Fidan Babakhanli]]></dc:creator>
            <pubDate>Fri, 12 Sep 2025 19:20:31 GMT</pubDate>
            <atom:updated>2025-09-12T19:20:31.032Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Evaluation of Active Directory Security:</strong><br> Weaknesses identified in <strong>Active Directory</strong>, <strong>Entra ID</strong> (a cloud-based identity and access management service that enables employees within an enterprise to securely access external resources), and <strong>Okta</strong> (a multi-factor authentication service that requires users to verify their identities when accessing Okta accounts or Okta-protected resources) may create opportunities for adversaries. Such vulnerabilities can potentially grant attackers <strong>virtually unrestricted access</strong> to an organization’s network and critical resources, thereby posing a significant security risk.</p><p><strong>“Purple Knight”</strong> is a program that carries out a comprehensive set of tests against attack vectors and performs a security assessment based on more than 150 security indicators. This program is designed to quickly identify vulnerabilities in hybrid AD environments and is considered a best practice — an officially recognized and well-documented method or set of methods commonly accepted for use in a specific task or industry. Purple Knight scans the Active Directory environment and creates a security scorecard by monitoring security indicators across seven categories.</p><p>This security tool is intended to identify vulnerabilities and misconfigurations in Active Directory (AD) environments, which are often targeted by cyberattacks.</p><p>Organizations typically score an average of <strong>62%</strong> in initial assessments, reflecting common configuration weaknesses exploited by cybercriminals.</p><p>Overall, Purple Knight represents an important resource for organizations that seek to proactively manage and protect their Active Directory environments against evolving cyber threats.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*baEAANlrjdinYGpDhvJ5Og.png" /><figcaption>Figure 1. Purple Knight — Environment Window</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/889/1*wItu68WfBU8lO4pfa9sM_Q.png" /><figcaption>Figure 2. Purple Knight — Indicators Window</figcaption></figure><p><strong>Figure 2.</strong> illustrates the security assessment results in the <strong>Active Directory</strong> system. It shows how many issues were found for each type of check, as well as their severity. A simple explanation of each category is provided below:</p><ul><li><strong>AD Delegation</strong> — cases where administrative rights are not properly assigned, which is significant for security and compliance.</li><li><strong>Account Security</strong> — security issues present in individual user accounts.</li><li><strong>AD Infrastructure Security</strong> — identifies security problems in the core structure of the system.</li><li><strong>Group Policy Security</strong> — issues found in the security of group policies.</li><li><strong>Kerberos Security</strong> — problems in the configuration of the Kerberos authentication protocol.</li><li><strong>Hybrid</strong> — issues related to the security of hybrid environments.</li></ul><p>These categories test security weaknesses across different aspects of the AD system. For example, in the <strong>AD Delegation</strong> category, 18 issues were identified, which means that some administrative rights are not correctly configured, thereby increasing security risks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*z6g3hwlxBEGvcEBwv08CYA.png" /><figcaption>Figure 3. Purple Knight — Operation Progress</figcaption></figure><p><strong>Figure 3</strong> shows a screenshot related to the verification or analysis process of a program. The information displayed on the screen can be explained as follows:</p><ul><li><strong>Status — Process Running</strong>: Indicates that the process is currently active.</li><li><strong>Elapsed Time</strong>: Displays the time passed since the process started (00:00:21–21 seconds).</li><li><strong>Done</strong>: Shows the number of completed tasks and their proportion to the total (36 out of 108 tasks, i.e., 33%).</li><li>At the bottom, the status of checks across different categories is shown:</li><li><strong>AD Delegation</strong> — 7 out of 18 tasks completed.</li><li><strong>Account Security</strong> — 6 out of 30 tasks completed.</li><li><strong>AD Infrastructure Security</strong> — 16 out of 30 tasks completed.</li><li><strong>Group Policy Security</strong> — 1 out of 10 tasks completed.</li><li><strong>Kerberos Security</strong> — 4 out of 18 tasks completed.</li><li><strong>Hybrid</strong> — 2 out of 2 tasks completed.</li></ul><p>The blue bar next to each category visually represents how many tasks in that category have been completed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*csgwjA3DiiieApGzuhjlOA.png" /><figcaption>Figure 4. Purple Knight — Summary of Results</figcaption></figure><p><strong>Figure 4</strong> shows the security status of the <strong>Active Directory (AD)</strong> system. The indicators are as follows:</p><ul><li><strong>Forest AD</strong> — the name of the system is <em>fidan.local</em>.</li><li><strong>IOEs found</strong> — the number of security issues (Indicators of Exposure) is 14.</li><li><strong>Run by</strong> — this scan was carried out by the user <em>FIDAN\Administrator</em>.</li><li><strong>Overall assessment</strong> — 76%, which corresponds to a grade of C.</li></ul><p>In simple terms, these results indicate that the AD system is not 100% secure and requires certain improvements. Security issues are present and must be resolved.</p><p>The following figure displays results across different security areas for Active Directory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YSc9Rd1X6hwZr88w" /><figcaption>Figure 5. Purple Knight — Results Classification Window</figcaption></figure><p><strong>“AD Delegation” (87%)</strong> — relates to the proper distribution of rights and administration in Active Directory. The score also indicates that there are some shortcomings and highlights the importance of making adjustments to better regulate permissions.</p><p><strong>“Account Security” (94%)</strong> — measures the security of individual accounts and reflects how well each account is protected. Overall, 94% is a good result; however, there is still room for improvement in certain areas.</p><p><strong>“AD Infrastructure Security” (92%)</strong> — shows how well the core security structure is protected. Although this is a good result, there is still a need for further fine-tuning.</p><p><strong>“Group Policy Security” (99%)</strong> — covers the security of group policies and how they are managed. A score of 99% is very high, almost ideal, which means that security measures have been implemented very effectively.</p><p><strong>“Kerberos Security” (99%)</strong> — for example, in an organization with an entry card system, each employee can only enter with their own card. This system securely manages employee access and movement.</p><p><strong>“Hybrid” (N/A)</strong> — for example, a company must implement security measures for both on-site and remote employees. This combines both local and cloud-based security systems.</p><p>The obtained results reflect the overall security posture of our <strong>Active Directory</strong> environment. While the overall scores are positive, it should be noted that improvements are needed particularly in <strong>AD Delegation</strong> and <strong>Account Security</strong>. These insights help security teams identify weaknesses, eliminate them, and prepare a remediation plan.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a887babdafeb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simulating Ransomware Activity in a Safe Environment]]></title>
            <link>https://medium.com/@fidanbabakhanli/this-article-is-part-of-my-cybersecurity-learning-journey-534597cc19dd?source=rss-ca9d5045dde2------2</link>
            <guid isPermaLink="false">https://medium.com/p/534597cc19dd</guid>
            <dc:creator><![CDATA[Fidan Babakhanli]]></dc:creator>
            <pubDate>Fri, 12 Sep 2025 18:11:06 GMT</pubDate>
            <atom:updated>2025-09-13T05:31:57.369Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Objective:</strong><br> The purpose of this task is to safely simulate ransomware behavior in order to test detection, alerting, and response mechanisms in SIEM and EDR/XDR platforms. No real malicious software is used; the behavior is reproduced only in a test VM, within an isolated environment, and through safe methods. The logs collected from the simulation are analyzed in Splunk, anomalies are evaluated with MLTK, and XDR/QRadar rules are validated.</p><p><strong><em>Install VS Code, C# extension, and .NET SDK 7.0 from the internet.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*prfbCHCWO5SVgOVuveVFOA.png" /></figure><p><strong><em>After downloading the .NET SDK, when checking the version, we can see that it is already installed.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qF9q-lFCMF4ZRnOLoQ4l1Q.png" /></figure><p><strong><em>We create a new file named ransomware with the extension program.cs for .NET.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-_l2GLurB2cgIc5xD4OrKA.png" /></figure><p><strong><em>We add the code shown below into the file with the program.cs extension.<br> This part serves as the main entry point (the Main function is located here).</em></strong><br> At this stage, the program starts running and the main operations are invoked: the key is loaded, files are located, and the encryption function is executed.<br> The types of file extensions to be encrypted are defined.<br> Files are found within the user directories, and those files are then encrypted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kbkn6wRJAqlMKNT4t7BSMg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OFt48wyvE0BKxaX_zoEwIg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*enIKVffPLdkh3jSktpgpTA.png" /></figure><p><strong><em>Keymanager.cs</em></strong></p><ul><li>Loading and management of RSA keys takes place here.</li><li>The public key file is read, and an RSA key is generated.</li><li>AES keys are encrypted with RSA and sent to the server.</li><li>In some cases, the RSA private key may also be managed here for decryption purposes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7mCc_tub_9ze51AH2W8wrQ.png" /></figure><p><strong><em>Encrypter.cs</em></strong></p><ul><li>Symmetric encryption of files with AES takes place here.</li><li>An AES key and IV are generated (either per file or per session).</li><li>The file is read, encrypted with the AES key, and then rewritten.</li><li>The AES key is encrypted with the RSA public key and prepared to be sent to the server.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Pe2N9_ovNHVyfYvGC68NA.png" /></figure><p><strong><em>RansomwareSim.csproj is the .NET project configuration file for the ransomware simulation project.<br></em></strong><em> This file tells Visual Studio and the .NET build system how to compile (build) the project.<br> It also specifies details such as the name of the .exe file, its icon, and other characteristics.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OImk52cVQUY5HJ-JFmB-qA.png" /></figure><p><strong><em>Public.pem</em></strong><em> is the RSA public key file used in the ransomware simulation.<br> Its main role is to encrypt the AES key and IV, ensuring that these keys are not stored on the victim’s side and remain only with you.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*we4YFD-cmydNWILHCVM36A.png" /></figure><p><strong><em>During the setup of the overall code structure, I embedded the public.pem file into the .exe that I created, and the private keys are sent directly to my locally configured Ubuntu server.</em></strong><br> Let’s test how the code works: initially, I created several files (.txt, .png, .jpg, etc.) under the user directory in different folders (the number of files can be increased), and each of them is readable, as shown in the screenshots below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mn_HKPuOnwKsGRX_uhTiAg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PQIVXxaNt5hX8ph6B54OSQ.png" /></figure><p>As can be seen from the screenshots, the image and text files are stored in different folders, and each of them is readable and viewable. Now, let’s run our code. Since all our code and the Counter-Strike icon assigned for the .exe are ready, we can create the executable named <strong>cs1.5</strong>, which is designed to encrypt files on the victim’s computer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FetydKDESCjwyBNA9OJ3BQ.png" /></figure><p><strong><em>And now our executable is ready.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/588/1*39hZ9KMvye0_K8-rLV_i1Q.png" /></figure><p>Now it is time to run it. To see the result, I executed the code from the terminal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AVJwtI5s2pJoxobdNBOhag.png" /></figure><p>Now, let’s take a look at the final state of the files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dd0JNfKrvj_ofALobMAe2Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y8v65K_o5dGvGYHR6YI7sA.png" /></figure><p>The user’s files on both the Desktop and in the Downloads folder have now been encrypted, and an additional <em>readme.txt</em> file was created for the victim, containing the following content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K-K2SJg_O90-tEl25-uFpg.png" /></figure><p><strong><em>Now I will describe the tasks performed on the remote server.</em></strong><br> Initially, an Ubuntu server was set up, and a virtual environment was created on it.<br> The reason for doing this is to ensure that any installed application is contained only within the virtual environment and can be easily removed when no longer needed.</p><pre>python3 -m venv env<br>source env/bin/activate</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/927/1*d7Yr0L1jxmHldSiwMmKdLQ.png" /></figure><p><strong>Next, we installed a framework called Flask. The reason for this was to meet the following requirements:</strong></p><ul><li>Create a simple web server — meaning that your server1.py file can accept HTTP requests.</li><li>Receive data from the victim’s side — to collect the AES key, IV, and system information sent via POST by the ransomware.</li><li>Store and manage the data — to save the received information in a file or display it on an HTML page.</li></ul><p>The server1.py file has now been created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dC5eWhnhQa-fcmxvqvL9yw.png" /></figure><blockquote>When the Python file is run, as shown in the figure, the web service starts up and is ready to receive data sent from the other side.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tj2rfQZV2KPA9uekfa9evQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y4p9m2g5yYW7JKrZCxK3zQ.png" /></figure><p>Earlier, we had run the ransomware, and it is now sending the keys and other information to my Ubuntu server, as shown in the figure. There, details such as the user’s operating system, IP address, the time of execution, and the keys are visible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fcXES4CNCLaPK046gL0ZMA.png" /></figure><p>Although the public key resides on the victim’s computer, the private key is stored on the server side, and without these keys it is impossible to restore the files. The mentioned .txt and .db files each contain the AES key and IV generated during the encryption process on the victim’s side.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fig0jIMRFWXI4o_0P2qjFg.png" /></figure><p>Now, consider the case where we have already received the requested payment from the victim. At that point, we would need to provide a way for them to recover the encrypted files. For this purpose, I created an additional decryptor executable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gZ0SDZkk4AwzuISm3HYQNg.png" /></figure><p>Finally, I built it and converted it into an .exe file as well. Now, let’s run this .exe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L7X5i9Iqqz17OTwHQzC27A.png" /></figure><p>As shown in the figure, when the .exe is run, it prompts me for the keys. These keys are retrieved from the server. Initially, for testing purposes, we provide just a random key to verify the functionality of the code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Nqu8BXGiv1nDPCheocfgg.png" /></figure><p><strong><em>We saw that the keys were not correct. Now let’s enter the correct keys and look at the result.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JyeETOkwPoROCJLDyd1XKg.png" /></figure><p><strong><em>To make the processes occurring in the files clearer, we perform the same procedure via the terminal.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WjSjJPD153EbKZI24iPrfg.png" /></figure><p><strong><em>Our files have now been successfully restored, and the readme.txt file has also been removed from the computer.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y1POcdWm1UtuRrcAv2Nl4Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lEbWHcPxhEPR4yIaPYZsrA.png" /></figure><p><strong><em>The created .exe was also tested on VirusTotal and was detected as malicious.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g9WDzXMpwpCM2DkozvLlMg.png" /></figure><p><strong><em>Conclusion: </em></strong>In the test VM, typical ransomware steps such as mass file modifications and “shadow copy interference” were simulated using harmless scenarios. Detection rules on WAF/IPS/Sysmon logs ingested into Splunk were shown to be effective. With the Bitdefender XDR agent, behavioral indicators (mass rename/write operations, suspicious process calls) were recorded. Using MLTK, alerts were generated for cases with high anomaly scores and visualized on dashboards. The backup restore test was successful, confirming the effectiveness of the procedure</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=534597cc19dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>