<?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 Sina Mohebi on Medium]]></title>
        <description><![CDATA[Stories by Sina Mohebi on Medium]]></description>
        <link>https://medium.com/@sinamohebi?source=rss-b89fd100820c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nTpj_sJ_Xbk4L6UIVZSt5A@2x.jpeg</url>
            <title>Stories by Sina Mohebi on Medium</title>
            <link>https://medium.com/@sinamohebi?source=rss-b89fd100820c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 10:37:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sinamohebi/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[EventCode 4672 — Understanding Special Logon Privileges in Windows Security]]></title>
            <link>https://sinamohebi.medium.com/eventcode-4672-understanding-special-logon-privileges-in-windows-security-696b53cf5193?source=rss-b89fd100820c------2</link>
            <guid isPermaLink="false">https://medium.com/p/696b53cf5193</guid>
            <category><![CDATA[windows-security]]></category>
            <category><![CDATA[soc]]></category>
            <category><![CDATA[special-logon]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[eventcode-4672]]></category>
            <dc:creator><![CDATA[Sina Mohebi]]></dc:creator>
            <pubDate>Sat, 31 Aug 2024 19:35:47 GMT</pubDate>
            <atom:updated>2024-08-31T19:35:47.308Z</atom:updated>
            <content:encoded><![CDATA[<h3>EventCode 4672 — Understanding Special Logon Privileges in Windows Security</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D5In-91tSeucpy6RHCqp6g.png" /></figure><p>In the realm of <strong>Windows security</strong>, special logon privileges play a crucial role in managing <strong>user permissions</strong> and maintaining <strong>system integrity</strong>. These privileges enable specific actions that can significantly impact the <strong>security posture</strong> of a system. In this blog post, we will explore various special logon privileges, their descriptions, and practical examples to illustrate their importance in safeguarding your Windows environment.</p><pre><br>  +-------------------------------+----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+<br>|          Privilege Name       |            Description            |                                                                  Example                                                                                                                                                                                                  |<br>+-------------------------------+----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+<br>| SeAssignPrimaryTokenPrivilege  | Required to assign the primary   | A system administrator launches a service under a different user account to access specific resources.                                                                                                                                                                                                                               |<br>|                               | token of a process.              |                                                                                                                                                                                                                                                                                                                                          |<br>| SeAuditPrivilege               | Enables a user to add entries to | A security analyst logs failed login attempts to identify unauthorized access attempts.                                                                                                                                                                                                                                              |<br>|                               | the security log.                |                                                                                                                                                                                                                                                                                                                                          |<br>| SeBackupPrivilege              | Required to perform backup       | A backup administrator backs up critical files, ensuring all necessary data is included.                                                                                                                                                                                                                                             |<br>|                               | operations, bypassing file       |                                                                                                                                                                                                                                                                                                                                          |<br>|                               | permissions.                     |                                                                                                                                                                                                                                                                                                                                          |<br>| SeCreateTokenPrivilege         | Allows a process to create a     | A custom application creates tokens for each user session to ensure proper access control.                                                                                                                                                                                                                                            |<br>|                               | token object for accessing local  |                                                                                                                                                                                                                                                                                                                                          |<br>|                               | resources.                       |                                                                                                                                                                                                                                                                                                                                          |<br>| SeDebugPrivilege               | Required to debug and adjust the | A developer attaches a debugger to a service running under a different user account for troubleshooting.                                                                                                                                                                                                                             |<br>|                               | memory of processes owned by     |                                                                                                                                                                                                                                                                                                                                          |<br>|                               | other accounts.                  |                                                                                                                                                                                                                                                                                                                                          |<br>| SeEnableDelegationPrivilege    | Allows a user to set the        | An IT administrator configures a service account to access resources on behalf of users for single sign-on scenarios.                                                                                                                                                                                                                  |<br>|                               | “Trusted for Delegation” setting |                                                                                                                                                                                                                                                                                                                                          |<br>|                               | on user or computer objects.     |                                                                                                                                                                                                                                                                                                                                          |<br>| SeImpersonatePrivilege         | Allows a user to impersonate     | A web application impersonates the authenticated user to access user-specific resources.                                                                                                                                                                                                                                              |<br>|                               | other accounts after             |                                                                                                                                                                                                                                                                                                                                          |<br>|                               | authentication.                  |                                                                                                                                                                                                                                                                                                                                          |<br>| SeLoadDriverPrivilege          | Required to load and unload      | A system administrator installs a new device driver for a hardware component.                                                                                                                                                                                                                                                         |<br>|                               | device drivers.                  |                                                                                                                                                                                                                                                                                                                                          |<br>| SeRestorePrivilege             | Necessary for restoring files     | A system administrator restores a critical system file from a backup after corruption.                                                                                                                                                                                                                                               |<br>|                               | and directories, bypassing       |                                                                                                                                                                                                                                                                                                                                          |<br>|                               | permissions during the restore   |                                                                                                                                                                                                                                                                                                                                          |<br>|                               | process.                         |                                                                                                                                                                                                                                                                                                                                          |<br>| SeSecurityPrivilege            | Allows users to manage auditing   | A compliance officer sets up auditing for sensitive files to log access attempts for review.                                                                                                                                                                                                                                          |<br>|                               | and security logs, including     |                                                                                                                                                                                                                                                                                                                                          |<br>|                               | specifying object access         |                                                                                                                                                                                                                                                                                                                                          |<br>|                               | auditing options.                |                                                                                                                                                                                                                                                                                                                                          |<br>| SeSystemEnvironmentPrivilege    | Required to modify firmware       | An IT technician updates firmware settings to optimize system performance.                                                                                                                                                                                                                                                             |<br>|                               | environment values.              |                                                                                                                                                                                                                                                                                                                                          |<br>| SeTakeOwnershipPrivilege       | Allows a user to take ownership  | A system administrator takes ownership of a locked file to modify or delete it as needed.                                                                                                                                                                                                                                           |<br>|                               | of files or other objects        |                                                                                                                                                                                                                                                                                                                                          |<br>|                               | without being granted            |                                                                                                                                                                                                                                                                                                                                          |<br>|                               | discretionary access.            |                                                                                                                                                                                                                                                                                                                                          |<br>| SeTcbPrivilege                 | Identifies its holder as part    | A background service performs actions on behalf of users, accessing shared resources seamlessly.                                                                                                                                                                                                                                      |<br>|                               | of the trusted computer base,    |                                                                                                                                                                                                                                                                                                                                          |<br>|                               | allowing impersonation of any    |                                                                                                                                                                                                                                                                                                                                          |<br>|                               | user.                            |                                                                                                                                                                                                                                                                                                                                          |<br>+-------------------------------+----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+</pre><h3>Example of Special Privileges Assigned to a New Logon</h3><p><strong>Subject:</strong></p><ul><li><strong>Security ID</strong>: WIN-R9H529RIO4Y\Administrator</li><li><strong>Account Name</strong>: Administrator</li><li><strong>Account Domain</strong>: WIN-R9H529RIO4Y</li><li><strong>Logon ID</strong>: 0x4b842</li></ul><p><strong>Assigned Privileges:</strong></p><ul><li>SeSecurityPrivilege</li><li>SeTakeOwnershipPrivilege</li><li>SeLoadDriverPrivilege</li><li>SeBackupPrivilege</li><li>SeRestorePrivilege</li><li>SeDebugPrivilege</li><li>SeSystemEnvironmentPrivilege</li><li>SeImpersonatePrivilege</li></ul><h3>Importance of Special Logon Privileges</h3><ol><li><strong>Robust Privileges</strong>: The system has a robust set of privileges that enable it to perform critical administrative functions.</li><li><strong>Security and Auditing Management</strong>: These privileges allow the system to manage security and auditing effectively, ensuring compliance with best practices.</li><li><strong>Device Driver Handling</strong>: The privileges facilitate the handling of device drivers, ensuring proper installation and management of hardware components.</li><li><strong>Data Integrity Assurance</strong>: They ensure data integrity through backup and restore operations, allowing for the recovery of critical data when needed.</li><li><strong>System Security Maintenance</strong>: These privileges are essential for maintaining overall system security and protecting against unauthorized access.</li><li><strong>Support for Application Development</strong>: They support application development by providing necessary permissions for debugging and impersonation, enhancing development efficiency.</li><li><strong>Regulatory Compliance</strong>: The privileges help ensure compliance with regulatory standards, which often require strict access controls and auditing capabilities.</li><li><strong>Importance of Proper Management</strong>: Proper management of these privileges is crucial to prevent unauthorized access and maintain system integrity.</li><li><strong>Overall Security Posture</strong>: Effective management helps maintain the overall security posture of the system, reducing vulnerabilities and risks.</li></ol><p>For more details, you can check the official Microsoft documentation on <a href="https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/auditing/event-4672">special logon privileges</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=696b53cf5193" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MITRE ATT&CK Top techniques & sub-techniques 2023]]></title>
            <link>https://sinamohebi.medium.com/mitre-att-ck-top-techniques-sub-techniques-2023-a396245d5a1f?source=rss-b89fd100820c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a396245d5a1f</guid>
            <dc:creator><![CDATA[Sina Mohebi]]></dc:creator>
            <pubDate>Wed, 24 Apr 2024 07:48:33 GMT</pubDate>
            <atom:updated>2024-04-24T07:48:33.611Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lNF5IKPGUhB_6xbN1eOXmA.jpeg" /></figure><p>MITRE ATT&amp;CK provides a framework for classifying attacker tactics, techniques, and procedures (TTPs). Each year, security researchers analyze real-world attacks to identify the most prevalent techniques and sub-techniques used by adversaries. By understanding these top techniques and sub-techniques, security professionals can prioritize their defenses and focus on the areas most likely to be targeted by attackers.</p><h3>Top 10 Most Frequently Seen Techniques 2023</h3><pre>|                                                  |<br>|--------------------------------------------------|<br>| 1                                                |<br>| T1059: Command and Scripting Interpreter         |<br>| 2                                                |<br>| T1027: Obfuscated Files or Information           |<br>| 3                                                |<br>| T1083: File and Directory Discovery              |<br>| 4                                                |<br>| T1021: Remote Services                           |<br>| 5                                                |<br>| T1082: System Information Discovery              |<br>| 6                                                |<br>| T1070: Indicator Removal                         |<br>| 7                                                |<br>| T1071: Application Layer Protocol                |<br>| 8                                                |<br>| T1033: System Owner/User Discovery               |<br>| 9                                                |<br>| T1140: Deobfuscate / Decode Files or Information |<br>| 10                                               |<br>| T1190: Exploit Public-Facing Application         |</pre><ul><li><strong>T1059</strong>: Command and Scripting Interpreter | Executes malicious code through a command shell or scripting language, allowing attackers to automate tasks, deploy malware, or steal data.</li><li><strong>T1027</strong>: Obfuscated Files or Information | Hides malicious content, such as malware or exploit code, by employing techniques like encryption, packing, or encoding to evade detection by security scanners and analysts.</li><li><strong>T1083</strong>: File and Directory Discovery | Identifies and locates files and folders on a system, which can be used by attackers to find sensitive data, configuration files, or potential hiding places for malware.</li><li><strong>T1021</strong>: Remote Services | Interacts with remote systems to manage or exploit them. Attackers can use remote services to establish persistent access, launch denial-of-service attacks, or steal data from remote machines.</li><li><strong>T1082</strong>: System Information Discovery | Gathers information about a system&#39;s configuration, software, and hardware. This information can be used to identify vulnerabilities, plan attacks, or tailor exploits to specific systems.</li><li><strong>T1070</strong>: Indicator Removal | Attempts to erase traces of malicious activity, such as logs, files, or registry entries, to impede forensic investigations and make it difficult to detect the attack.</li><li><strong>T1071</strong>: Application Layer Protocol | Uses legitimate application protocols, such as HTTP or SMB, for malicious purposes. This technique can help attackers bypass security controls that are designed to detect suspicious network traffic.</li><li><strong>T1033</strong>: System Owner/User Discovery | Identifies the users or administrators on a system. This information can be used by attackers to target specific individuals for spear phishing attacks or privilege escalation attempts.</li><li><strong>T1140</strong>: Deobfuscate/Decode Files or Information | Reverses obfuscation techniques to reveal hidden malicious content. Deobfuscation can be a complex process, but it is essential for security analysts to understand the true nature of a threat.</li><li><strong>T1190</strong>: Exploit Public-Facing Application | Targets vulnerabilities in publicly accessible applications, such as web servers or remote desktop services. These vulnerabilities can allow attackers to gain unauthorized access to a system, steal data, or deploy malware.</li></ul><h3>Top 5 Most Frequently Seen MITRE ATT&amp;CK Sub-Techniques 2023</h3><pre>|---|------------------------------------|<br>| 1 | T1059.001: PowerShell              |<br>| 2 | T1071.001: Web Protocols           |<br>| 3 | T1021.001: Remote Desktop Protocol |<br>| 4 | T1569.002: Service Execution       |<br>| 5 | T1070.004: File Deletion           |<br>|---|------------------------------------|</pre><ul><li><strong>T1059.001</strong>: PowerShell | Executes commands using the PowerShell scripting language, a powerful tool for automating tasks and interacting with the Windows operating system. Attackers can leverage PowerShell to download malware, steal data, or manipulate system settings.</li><li><strong>T1071.001</strong>: Web Protocols | Uses protocols like HTTP, HTTPS, FTP, or SMB to communicate with a remote system. These protocols are commonly used for legitimate web browsing and file transfer, but attackers can abuse them to exfiltrate data, deliver malware, or establish remote connections.</li><li><strong>T1021.001</strong>: Remote Desktop Protocol | Leverages the Remote Desktop Protocol (RDP) to establish a remote connection to a system. RDP allows legitimate users to access their desktops remotely, but attackers can exploit vulnerabilities in RDP to gain unauthorized access to a system.</li><li><strong>T1569.002</strong>: Service Execution | Executes commands through a service running on the target system. Services are programs that run in the background on a system and perform specific tasks. Attackers can exploit vulnerabilities in services or abuse legitimate functionalities to execute malicious commands.</li><li><strong>T1070.004</strong>: File Deletion | Permanently removes files from the system. Attackers may delete files to destroy evidence of their activity, remove critical system files to disable security software, or free up disk space for malware.</li></ul><blockquote><em>Source : </em><a href="https://cloud.google.com/security/resources/m-trends?utm_source=ads-in-product&amp;utm_medium=mandiant&amp;utm_campaign=FY24-Q1-global-MAND942-website-dl-dgcsm-m-trends-2024&amp;utm_content=-&amp;utm_term=-&amp;hl=en"><em>Mandiant M-Trends 2024 report</em></a><em><br></em><strong><em>Find More articles on </em></strong><a href="http://blog.sinamohebi.com/"><strong><em>blog.sinamohebi.com</em></strong></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a396245d5a1f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Defending Against Mail Spoofing: Technical Solutions for Enhanced Email Security & Disabling SMTP…]]></title>
            <link>https://sinamohebi.medium.com/defending-against-mail-spoofing-technical-solutions-for-enhanced-email-security-disabling-smtp-ffae82c42474?source=rss-b89fd100820c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffae82c42474</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[mail]]></category>
            <category><![CDATA[phishing]]></category>
            <dc:creator><![CDATA[Sina Mohebi]]></dc:creator>
            <pubDate>Thu, 09 Nov 2023 11:41:21 GMT</pubDate>
            <atom:updated>2023-11-09T11:41:21.424Z</atom:updated>
            <content:encoded><![CDATA[<h3>Defending Against Mail Spoofing: Technical Solutions for Enhanced Email Security &amp; Disabling SMTP Relaying</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*ogEhIXTZYMSUANaoYdIvBg.jpeg" /></figure><p>Introduction: In today’s digital landscape, mail spoofing poses a significant threat to individuals and organizations. It allows malicious actors to forge email headers, deceiving recipients into believing the messages are legitimate. To safeguard against such attacks, implementing technical solutions becomes crucial. In this article, we will explore several measures that can enhance your email security and protect against mail spoofing.</p><p>Email Authentication Protocols: Implementing robust email authentication protocols can help verify the authenticity of incoming messages. Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM), and Domain-based Message Authentication, Reporting, and Conformance (DMARC) are widely used protocols. SPF verifies if the server sending the email is authorized to send on behalf of a specific domain, DKIM adds a digital signature to validate email integrity, and DMARC combines SPF and DKIM to provide enhanced authentication and reporting capabilities.</p><p>DMARC Policy Enforcement: Setting up a DMARC policy allows domain owners to specify how receiving servers should handle unauthenticated emails originating from their domain. By implementing a “reject” or “quarantine” policy, organizations can instruct receiving servers to discard or flag suspicious emails, respectively, reducing the impact of mail spoofing attempts.</p><p>Implementing SPF Record: Creating a Sender Policy Framework (SPF) record for your domain can significantly reduce the risk of mail spoofing. SPF records specify the authorized mail servers for a domain, helping receiving servers verify the authenticity of incoming emails. By configuring SPF records correctly, organizations can prevent attackers from sending spoofed emails using their domain.</p><blockquote><em>Disabling SMTP Relaying in Exchange: In Microsoft Exchange, it is crucial to disable SMTP relaying to mitigate the risk of mail spoofing. SMTP relaying allows unauthorized users to use the Exchange server to send emails, potentially enabling them to forge email headers and send spoofed messages. By disabling SMTP relaying and configuring proper restrictions, organizations can prevent unauthorized external entities from abusing their Exchange server for malicious purposes.</em></blockquote><p>User Awareness and Training: Educating users about mail spoofing techniques and how to identify suspicious emails is paramount. Conduct regular training sessions to inform employees about common spoofing tactics, such as email address impersonation or domain name forgery. Teach them to be vigilant and scrutinize email details like sender addresses, email content, and unexpected attachments or links.</p><p>Email Server Configuration: Regularly reviewing and updating email server configurations can help mitigate vulnerabilities that could be exploited by spoofing attacks. Ensure that your email server is properly configured to reject or flag emails with invalid or mismatched sender information.</p><p>Conclusion: Defending against mail spoofing requires a multi-faceted approach, combining technical solutions and user awareness. By implementing email authentication protocols like SPF, DKIM, and DMARC, enforcing DMARC policies, disabling SMTP relaying in Exchange, deploying advanced threat protection solutions, and conducting user training, individuals and organizations can bolster their email security posture. Additionally, maintaining up-to-date email server configurations and promoting a culture of vigilance among users will further strengthen defenses against mail spoofing. By adopting these technical solutions and fostering awareness, you can enhance your email security and thwart mail spoofing attempts effectively.</p><p>provide by me with best regards</p><p>Sina Mohebi</p><p>Find more post on my <a href="https://sinamohebi.com/">Blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffae82c42474" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Detecting Webshells with Sysmon: A Technical Analysis]]></title>
            <link>https://sinamohebi.medium.com/detecting-webshells-with-sysmon-a-technical-analysis-ed9fb0554efd?source=rss-b89fd100820c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed9fb0554efd</guid>
            <category><![CDATA[soc]]></category>
            <category><![CDATA[webshell]]></category>
            <category><![CDATA[securityoperationscenter]]></category>
            <category><![CDATA[sysmon]]></category>
            <dc:creator><![CDATA[Sina Mohebi]]></dc:creator>
            <pubDate>Sun, 05 Nov 2023 15:13:32 GMT</pubDate>
            <atom:updated>2023-11-05T15:13:32.230Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5KWMUZ7PxunApjwpoJL0og.png" /></figure><p>Introduction: Webshells are malicious scripts or programs that attackers deploy on web servers to gain unauthorized access and control. Detecting these webshells is crucial for maintaining the security of web applications and protecting sensitive data. In this article, we will explore how Sysmon, a powerful Windows system monitoring tool, can be utilized to detect and mitigate webshell threats. We will dive into the technical details of using Sysmon, explore relevant event IDs, and provide insights on enhancing your web server security.</p><p>Understanding Sysmon: Sysmon is a lightweight, command-line utility developed by Microsoft for Windows systems. It provides advanced monitoring capabilities by collecting and logging detailed information about system activities, including process creation, network connections, file modifications, and more. Leveraging this tool’s extensive event logging capabilities, we can effectively track and detect suspicious activity related to webshells.</p><ol><li>Monitoring Webshell Execution (Event ID: 1): To identify webshell activities, Sysmon can be configured to monitor process creation events (Event ID: 1). By enabling the “Image” and “CommandLine” fields in Sysmon’s configuration, we can capture detailed information about processes being launched on the system. Webshells are often executed through malicious scripts or processes, and monitoring process creation can help us detect their presence.</li><li>Tracking Network Connections (Event ID: 3): Webshells typically establish communication channels with external servers to receive commands or exfiltrate data. Sysmon allows us to log network connection events (Event ID: 3), including source and destination IP addresses, ports, and protocols. By monitoring network connections, we can identify suspicious communication patterns associated with webshells.</li><li>Monitoring File Modifications (Event IDs: 11, 12, 13): Webshells often modify existing files or create new files on the compromised server. Sysmon can be configured to track file modifications (Event IDs: 11, 12, 13), providing crucial insights into potential webshell activity. By monitoring file creation, modification, and deletion events, we can identify unauthorized changes made by webshells.</li><li>Detecting Suspicious Process Behavior (Event ID: 7): Sysmon enables us to monitor process behavior (Event ID: 7), including command-line arguments, parent-child process relationships, and DLL loads. Webshells may exhibit unusual behavior, such as executing commands with elevated privileges or injecting malicious code into legitimate processes. By analyzing Sysmon logs for abnormal process behavior, we can flag potential webshell activities.</li></ol><p>Here’s a real example of how Sysmon can be used to detect a webshell activity:</p><p>Let’s say you have configured Sysmon on your web server and are monitoring Event ID 1 (Process Creation) and Event ID 3 (Network Connection). One day, you notice a suspicious process being created with a webshell-like name, “cmd.aspx”.</p><pre>Process Create: RuleName: - UtcTime: 2022-01-10 15:30:45.1234567 ProcessGuid: {12345678-1234-1234-1234-123456789abc} ProcessId: 1234 Image: C:\inetpub\wwwroot\cmd.aspx CommandLine: C:\Windows\System32\cmd.exe /c echo &quot;Hello, webshell!&quot; CurrentDirectory: C:\inetpub\wwwroot\ User: NT AUTHORITY\SYSTEM</pre><p>Upon further investigation, you find that this process establishes an outbound connection to a suspicious IP address.</p><p>Sysmon Event ID 3 log entry:</p><pre>Network Connect:<br>    RuleName: -<br>    UtcTime: 2022-01-10 15:31:00.9876543<br>    ProcessGuid: {12345678-1234-1234-1234-123456789abc}<br>    ProcessId: 1234<br>    Image: C:\Windows\System32\cmd.exe<br>    User: NT AUTHORITY\SYSTEM<br>    Protocol: TCP<br>    Initiated: true<br>    SourceIp: 192.168.0.100<br>    SourcePort: 12345<br>    DestinationIp: 123.456.789.123<br>    DestinationPort: 8080</pre><p>In this example, the webshell “cmd.aspx” is created by a legitimate Windows process “cmd.exe” and executed with elevated privileges (NT AUTHORITY\SYSTEM). It establishes an outbound network connection to an unknown IP address on an unusual port (123.456.789.123:8080). These activities raise suspicion and indicate a potential webshell presence on the server.</p><p>By regularly reviewing and analyzing Sysmon logs, paying attention to relevant event IDs, and using tools like SIEM (Security Information and Event Management) solutions, you can detect and respond to webshell activities promptly, mitigating potential security risks.</p><p>Remember, this is just one example, and the characteristics of webshells can vary. It is crucial to stay updated on the latest webshell threat indicators and adjust your monitoring and detection techniques accordingly.</p><p>Conclusion: Deploying Sysmon as part of your web server security strategy can significantly enhance your capability to detect and mitigate webshell threats. By leveraging Sysmon’s comprehensive event logging features and implementing proper monitoring and analysis techniques, you can proactively identify and respond to webshell attacks. Remember to regularly review and analyze Sysmon logs, paying close attention to relevant event IDs, to stay vigilant and keep your web applications secure.</p><p>Please note that while Sysmon is a powerful tool for monitoring system activities, its configuration and analysis require technical expertise. It is recommended to consult security professionals or refer to official documentation for specific implementation details suitable for your environment.</p><p>provide by me with best regards</p><p>Sina Mohebi</p><p>Find More post in My <a href="https://www.linkedin.com/in/sinamohebi/">Linkedin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed9fb0554efd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Use MITRE ATT&CK in SOC]]></title>
            <link>https://sinamohebi.medium.com/how-to-use-mitre-att-ck-in-soc-3393700fe965?source=rss-b89fd100820c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3393700fe965</guid>
            <category><![CDATA[mitre-attack-framework]]></category>
            <category><![CDATA[soc]]></category>
            <category><![CDATA[mitre]]></category>
            <category><![CDATA[mitre-attack]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Sina Mohebi]]></dc:creator>
            <pubDate>Wed, 16 Aug 2023 07:27:15 GMT</pubDate>
            <atom:updated>2023-08-16T07:28:17.006Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*RlVGMQHnVC9AxIzSB_2gog.png" /></figure><p>Using MITRE ATT&amp;CK in a Security Operations Center (SOC) can greatly enhance threat detection and response capabilities. Here are the steps to effectively utilize MITRE ATT&amp;CK framework in a SOC</p><blockquote><strong>Familiarize Yourself with MITRE ATT&amp;CK</strong></blockquote><ul><li>Understand the purpose and structure of the MITRE ATT&amp;CK framework.</li><li>Explore the ATT&amp;CK website (<a href="https://attack.mitre.org/">https://attack.mitre.org/</a>) and review the ATT&amp;CK matrix, techniques, tactics, and sub-techniques.</li></ul><blockquote><strong>Map ATT&amp;CK to Your Environment</strong></blockquote><ul><li>Identify the relevant MITRE ATT&amp;CK techniques and tactics that align with your organization’s infrastructure, applications, and data.</li><li>Map the MITRE ATT&amp;CK techniques to your existing security controls, such as firewalls, intrusion detection systems, and endpoint protection solutions.</li></ul><blockquote><strong>Create Detection Rules</strong></blockquote><ul><li>Develop detection rules and use cases based on specific MITRE ATT&amp;CK techniques and tactics.</li><li>Leverage your security information and event management (SIEM) system or threat intelligence platforms to create rules that trigger alerts when suspicious activities related to specific ATT&amp;CK techniques are detected.</li></ul><blockquote><strong>Implement Threat Hunting</strong></blockquote><ul><li>Utilize MITRE ATT&amp;CK as a guide for proactive threat hunting exercises.</li><li>Search for indicators of compromise (IOCs) associated with known ATT&amp;CK techniques and use them to identify potential threats within your environment.</li></ul><blockquote><strong>Enhance Incident Response</strong></blockquote><ul><li>Incorporate MITRE ATT&amp;CK into your incident response procedures</li><li>Develop playbooks and response plans that align with specific ATT&amp;CK techniques and tactics to effectively handle and mitigate threats.</li></ul><blockquote><strong>Collaborate with Threat Intelligence</strong></blockquote><ul><li>Leverage external threat intelligence sources that align with MITRE ATT&amp;CK.</li><li>Stay updated on the latest threat intelligence reports that reference ATT&amp;CK techniques and tactics.</li></ul><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><h3>How to use MITRE ATT&amp;CK in action</h3><h3>Step 1 : Find what you looking for 🔎</h3><ul><li>Find <strong>Tactics, technique</strong>, <strong>Sub-technique or</strong> ID</li><li>Example : <a href="https://attack.mitre.org/techniques/T1053/005/"><strong>Scheduled Task/Job: Scheduled Task</strong></a></li><li><strong>ID:</strong> T1053.005</li><li><strong>Sub-technique of:</strong> <a href="https://attack.mitre.org/techniques/T1053">T1053</a></li><li><strong>Tactics:</strong> <a href="https://attack.mitre.org/tactics/TA0002">Execution</a>, <a href="https://attack.mitre.org/tactics/TA0003">Persistence</a>, <a href="https://attack.mitre.org/tactics/TA0004">Privilege Escalation</a></li></ul><h3>Step 2 : Learn about it 📖</h3><ul><li><strong>Understand ATT&amp;CK</strong></li><li>Familiarize yourself with the overall structure of ATT&amp;CK ****</li><li><strong>Find the behavior</strong></li><li>Find parameters and tools attacker should use to implement the ATT&amp;CK</li><li><strong>Research the behavior / tools</strong></li><li>Search about the <strong>technique</strong> or <strong>Sub-technique</strong> on the other resources</li><li><strong>Read Procedure Examples section</strong></li><li>Learn how Groups or tools use the <strong>technique</strong> or <strong>Sub-technique</strong></li></ul><h3>Step 3 : Defeat it 🗡️</h3><ul><li><strong>Mitigations section</strong></li><li>Find the <strong>Mitigation</strong></li><li><strong>Detection section</strong></li><li>Find the <strong>Detection</strong></li></ul><h3>Step 4 : Convert TTP to SIEM rule / use case</h3><ul><li>Find Detection rule at MITRE <a href="https://car.mitre.org/">CAR project</a></li><li>Example : <a href="https://car.mitre.org/analytics/CAR-2021-12-001/"><strong>Scheduled Task Creation or Modification Containing Suspicious Scripts</strong></a></li></ul><h3>Data Sources</h3><blockquote><em>You can identify </em><strong><em>technique</em></strong><em> or </em><strong><em>Sub-technique</em></strong><em> based on data source that you have like </em><a href="https://attack.mitre.org/versions/v13/datasources/DS0024"><em>Windows Registry</em></a><em> or </em><a href="https://attack.mitre.org/versions/v13/datasources/DS0029"><em>Network Traffic</em></a></blockquote><h3>Examples</h3><ul><li><strong>Process and process command line monitoring</strong></li><li>Often collected by Sysmon, Windows Event Logs</li><li><a href="https://attack.mitre.org/versions/v13/datasources/DS0017/">Command, Data Source DS0017 | MITRE ATT&amp;CK®</a></li><li><strong>Registry monitoring</strong></li><li>A Windows OS hierarchical database that stores much of the information and settings for software programs</li><li><a href="https://attack.mitre.org/versions/v13/datasources/DS0024/">Windows Registry, Data Source DS0024 | MITRE ATT&amp;CK®</a></li><li><strong>Network Traffic</strong></li><li>such as capturing socket information with a source/destination IP and port(s) (ex: Windows EID 5156, Sysmon EID 3, or Zeek conn.log)</li></ul><h3>ATT&amp;CK Navigator</h3><p>The <a href="https://mitre-attack.github.io/attack-navigator/">ATT&amp;CK Navigator</a> is a web-based tool for annotating and exploring ATT&amp;CK matrices. It can be used to visualize defensive coverage, red/blue team planning, the frequency of detected techniques, and more.</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — -</p><p>Credit by <a href="https://www.linkedin.com/in/sinamohebi/">Sina Mohebi</a> &amp; <a href="https://blog.sinamohebi.com/">blog.sinamohebi.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3393700fe965" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RDP Event logs tracking 4624 / 4625]]></title>
            <link>https://sinamohebi.medium.com/rdp-event-logs-tracking-4624-4625-f0d6d0409954?source=rss-b89fd100820c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0d6d0409954</guid>
            <category><![CDATA[rdp]]></category>
            <category><![CDATA[security-operation-center]]></category>
            <category><![CDATA[soc]]></category>
            <category><![CDATA[windows-event-logs]]></category>
            <category><![CDATA[remote-desktop]]></category>
            <dc:creator><![CDATA[Sina Mohebi]]></dc:creator>
            <pubDate>Wed, 02 Aug 2023 16:34:09 GMT</pubDate>
            <atom:updated>2023-08-02T16:36:41.730Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Event ID 4624</strong> is generated in the Windows Security Log when a successful logon occurs on a local computer. This event is generated on the computer that was accessed, meaning that it is the computer where the logon session was created. A related event, <strong>Event ID 4625</strong>, is generated when a logon attempt fails.</p><p>The following information is included in Event ID 4624:</p><ul><li><strong>Subject:</strong> The account that requested the logon.</li><li><strong>Logon Type:</strong> The type of logon that occurred.</li><li><strong>New Logon:</strong> The account that was logged on.</li><li><strong>Workstation Name:</strong> The name of the computer that was logged on to.</li><li><strong>IP Address:</strong> The IP address of the computer that was logged on to.</li></ul><p>This information can be used to track who logged on to a computer, when they logged on, and from where they logged on. This information can be helpful in troubleshooting security issues and in identifying unauthorized access to computers.</p><h3>Example</h3><pre>An account was successfully logged on.<br>Subject:<br>   Security ID:  SYSTEM<br>   Account Name:  WIN-R9H529RIO4Y$<br>   Account Domain:  WORKGROUP<br>   Logon ID:  0x3e7<br>Logon Type:3<br>New Logon:<br>      Security ID:  WIN-R9H529RIO4Y\\Administrator<br>   Account Name:  Administrator<br>   Account Domain:  WIN-R9H529RIO4Y<br>   Logon ID:  0x19f4c<br>   Logon GUID:  {00000000-0000-0000-0000-000000000000}<br>Process Information:<br>   Process ID:  0x4c0<br>   Process Name:  C:\\Windows\\System32\\winlogon.exe<br>Network Information:<br>     Workstation Name: WIN-R9H529RIO4Y<br>   Source Network Address: 10.42.42.211<br>   Source Port:  1181<br>Detailed Authentication Information:<br>     Logon Process:  User32 <br>   Authentication Package: Negotiate<br>   Transited Services: -<br>   Package Name (NTLM only): -<br>   Key Length:  0</pre><h3>Description of Logon Type</h3><p>Event 4624 &amp; 4625 provides important information, including:</p><ul><li><strong>Logon Type:</strong> This field indicates the type of logon that occurred and how the user logged on. There are nine different types of logons, with the most common being logon type 2 (interactive) and logon type 3 (network). Any logon type other than 5 (which denotes a service startup) should be considered a red flag.</li></ul><h3>Logon types and descriptions</h3><pre><br>+------------+-------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+<br>| Logon Type |       Logon Title       |                                                                                                                                                        Description                                                                                                                                                         |<br>+------------+-------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+<br>|          0 | System                  | Used only by the System account, for example at system startup.                                                                                                                                                                                                                                                            |<br>|          2 | Interactive             | A user logged on to this computer.                                                                                                                                                                                                                                                                                         |<br>|          3 | Network                 | A user or computer logged on to this computer from the network.                                                                                                                                                                                                                                                            |<br>|          4 | Batch                   | Batch logon type is used by batch servers, where processes may be executing on behalf of a user without their direct intervention.                                                                                                                                                                                         |<br>|          5 | Service                 | A service was started by the Service Control Manager.                                                                                                                                                                                                                                                                      |<br>|          6 | Proxy                   | Proxy logon.                                                                                                                                                                                                                                                                                                               |<br>|          7 | Unlock                  | This workstation was unlocked.                                                                                                                                                                                                                                                                                             |<br>|          8 | NetworkCleartext        | A user logged on to this computer from the network. The user’s password was passed to the authentication package in its unhashed form. The built-in authentication packages all hash credentials before sending them across the network. The credentials do not traverse the network in plaintext (also called cleartext). |<br>|          9 | NewCredentials          | A caller cloned its current token and specified new credentials for outbound connections. The new logon session has the same local identity, but uses different credentials for other network connections.                                                                                                                 |<br>|         10 | RemoteInteractive       | A user logged on to this computer remotely using Terminal Services or Remote Desktop.                                                                                                                                                                                                                                      |<br>|         11 | CachedInteractive       | A user logged on to this computer with network credentials that were stored locally on the computer. The domain controller was not contacted to verify the credentials.                                                                                                                                                    |<br>|         12 | CachedRemoteInteractive | Same as RemoteInteractive. This is used for internal auditing.                                                                                                                                                                                                                                                             |<br>+------------+-------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+</pre><p>According to the table above, the value for RemoteInteractive (Remote Desktop) is “10”. However, there is something that Microsoft did not tell you!</p><blockquote><strong>If you try to connect to a computer using mstsc.exe (Remote Desktop) with its IP address, the Logon type field will be equal to 3 (Network). However, if you use the computer&#39;s hostname(FQDN), such as &quot;sinamohebi.lib.dc2&quot;, we expect to see Logon type 10.</strong></blockquote><p>Here is the explanation:</p><ul><li>When you connect to a computer using its IP address, the Remote Desktop Protocol (RDP) uses the TCP/IP protocol to establish a connection. This is considered a network logon.</li><li>When you connect to a computer using its hostname, the RDP uses the DNS protocol to resolve the hostname to an IP address. Once the IP address is known, the RDP uses TCP/IP to establish a connection. This is considered a remote interactive logon.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0d6d0409954" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>