Track Common Adversary Tasks Performed Using AuditCred

By Ashwin Venugopal -

 



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










Overview

The Lazarus group employed the malicious DLL AuditCred in their 2018 attacks. This malware is capable of doing simple operations including searching through the system's files, deleting files, opening a reverse shell to conduct commands, and using a proxy for communication. It can also simply inject code from files into other processes that are currently operating. It uses XOR and RC4 to perform code decryption activities and can be installed as a new service on your computer.

Capabilities

The following are some of the tasks that AuditCred is capable of:
  • It can quickly search through your files for specific information, inject code into running processes, and delete files, all of which can facilitate easy access to memory, system resources, elevated rights, etc.

  • It can misuse the Windows Command Shell to move tools or other files into a compromised environment.

  • With the use of obfuscated files, it can also conceal the artifacts of an incursion from any type of forensic investigation.

  • It can falter the Windows services in order to execute malicious payload repeatedly to establish persistence.

  • In order to repeatedly execute a malicious payload to achieve persistence, it can cause the Windows services to malfunction.

  • By deciding how to route network data across systems, it can also take advantage of the connection proxy.

 Prevention

The techniques listed below can assist in protecting your network from this malware:
  • Monitor any known and unknown deletion tools that are not on the systems already in a business network, or monitor the Windows API calls that may signal any type of code injection, and safeguard them.

  • By only inspecting the packet contents, it is possible to identify communications that don't behave according to the expected protocol behavior.

  • Keep track of the files that are created and moved throughout the network.

  • Identify and keep an eye out for scripts, system utilities, and service binary routes that might be   acting maliciously.

  • Examine the network data for any odd data flows of any kind.










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...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Deployment (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 3, please click  here Microsoft Sentinel Content Hub Content in Microsoft Sentinel includes any of the following types: Data connectors offer log ingestion from different sources into Microsoft Sentinel. Parsers give log formatting/transformation into ASIM formats, supporting usage across various Microsoft Sentinel content types and scenarios. Workbooks provide monitoring, visualization, and interactively with data in Microsoft Sentinel, highlighting meaningful insights for users.  Analytics rules give alerts that point to relevant SOC actions via incidents.  Hunting Queries are used by SOC teams to proactively hunt for threats in Microsoft Sentinel. Notebooks help SOC teams in using advanced hunting features in Jupyter and Azure Notebooks. Watchlists support the ingestion of specific data for enhanced threat detection and reduced alert fatigue.  Playbooks and Azure Logic Apps Custom Connectors provide featu...
Read more