Track Common Adversary Tasks Performed Using Mimikatz

By Ashwin Venugopal -

 








To know more about it, you can go through my detailed document by clicking here





Mimikatz

Mimikatz is a credential dumper that can obtain plaintext Windows account logins, passwords, and other features which also helps the users to view as well as save authentication credentials like Kerberos tickets. It was created by Benjamin Delpy in order to prove Microsoft that their authentication protocols are vulnerable to attacks. This toolset is still works with the Windows to include the latest attacks techniques. 

However, attackers also use Mimikatz to steal credentials and escalate privileges; although most of the attacks are detected by antivirus systems as well as endpoint protection software and deleted. Researchers commonly use Mimikatz to test the level of security of the networks. 

Common Features of Mimikatz

Mimikatz can demonstrate the following techniques:

  • Pass-the-Hash- Attackers use this technique to steal the hash string for a computer login which enables them to hack a system without even cracking a password.

  • Pass-the-Ticket- It's almost as same as pass-the-hash, but here, Mimikatz allows a user to pass the kerberos ticket to another computer in order to login with that user's ticket.

  • Over-Pass the Hash (Pass the Key)- This technique can provide a unique key that can impersonate a user from a domain controller.

  • Kerberos Golden Ticket- It's a type of pass-the-ticket attack which offers you non-expirable domain admin credentials to any computer on the network.    

  • Kerberos Silver Ticket- It's also a type of pass-the-ticket attack, but it provides you a TGS ticket (that's generally not checked by the Microsoft after it's issued) which helps the user to login to any services available on the network. 

  • Pass-the-Cache- It's almost the same as a pass-the-ticket attack, but, it makes use of the saved as well as encrypted login data on a Mac/UNIX/Linux system. 

Protection against Mimikatz

Although it's quite challenging to protect your system against Mimikatz, but some methods can be applied to defend or mitigate the risks against Mimikatz:
  1. Admin privileges can be limited to only those users who actually needs them.
  2. Systems can also be upgraded to Windows 10 or 8.1 in order to mitigate the risks of an attacker using Mimikatz against you. 
  3. The Local Security Authority (LSA) can also be tightened to prevent any kind of code injection.
  4. Ensuring that each Windows system have their own unique passwords rather than a single administrative password across an enterprise. 
  5. Running LSASS in protected mode on Windows 8.1 or higher can make Mimikatz ineffective., etc...etc...









To know more about it, you can go through my detailed document by clicking here






Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more