Track Common Adversary Tasks Performed Using Cobalt Strike

By Ashwin Venugopal -

 





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





Cobalt Strike

Cobalt Strike introduced first time in 2012,  is commonly known as a commercial adversary simulation software which is often stolen and used by various threat groups. Its payloads used for intrusion have been detected by many network defenders. It is widely used as a post-exploitation tool containing various malware droppers like IcedID, ZLoader, Qbot, Bazar, Hancitor, etc. Threat actors use Cobalt Strike as it is easy to use and accessible. 

How does Cobalt Strike Work?

As stated above, Cobalt Strike is highly popular among threat actors because it is stealthy and customizable. First of all, it sends beacons to detect the vulnerabilities of a system and then execute the actual attack. Its beacon can also execute PowerShell scripts, carry out Keylogging activities, take screenshots, spawn other payloads, etc. 

Special Features of Cobalt Strike

Cobalt Strike also provides the following features in order to detect as well as mitigate the vulnerabilities:
  • Attack Package- It offers various attack packages like Java Applet Attacks, Microsoft Office Documents, Website Clone Tools, etc. that can easily convert a regular file into a trojan horse to simulate an attack.

  • Browser Pivoting- It's a powerful technique that can allow an exploited system an access to the browser's authenticated sessions also making it useful to demonstrate risk with a targeted attack. 

  • Spear Phishing- It is a method of targeting particular individuals or groups in an organization by detecting their weak spots like an employee more prone to security attacks. 

  • Reporting & Logging- It also provide post-exploitation reports including the timeline as well as the spots of compromise and can export them as both PDF and MS Word document.

Conclusion

All-in-all Cobalt Strike can be considered as a useful tool for both legitimate researchers and threat actors. It's a robust and effective tool which can help in siphoning data, moving laterally, and adding malware payloads. 







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

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