Track Common Adversary Tasks Performed Using PsExec

By Ashwin Venugopal -

 








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






PsExec

It's a free Microsoft tool that can be used to execute processes on other systems with full interactivity without even installing a client software manually. Hence, it is widely used by both IT administrators and attackers. 

PsExec is extremely versatile as well as capable due to its compelling characteristics and easy to use functionality which also makes it popular among Windows administrators for remote command execution.

Prerquisites

These include:
  1. PsExec is a Windows-only solution that works between Windows computers.
  2. A Windows host computer is required to connect to the target Windows host.
  3. Admin share should be available on the target Windows system. 
  4. Proper connectivity should be maintained between the host you are running PsExec, and the target computer you want to manage. 

How does PsExec works?

Its workflow is as follows:
  1. Firstly, it extracts an embedded Windows service called Psexesvc via its executable image.
  2. After that, this service is copied to the Admin share of the remote system.
  3. In order to have remote access with the target computer, Windows Service Control Manager API is used. 
  4. Now, the Psexesvc service is started on the remote system. 
  5. The executable remote specified by you is also launched including your specified options.

How to use PsExec?

This command can be used in many ways like:
  • Running a specific remote command on a single computer.
  • Running a generic command or PowerShell prompt on a remote computer.
  • Running a remote command against multiple computers.
  • Reading computers from a file.
  • Launching programs remotely and interactively. etc...

Conclusion

PsExec is a powerful tool that easily allows the IT admins to remotely connect to the Windows hosts and issue commands on the remote system, which also makes the organizations to hesitate to whitelist PsExec and other command-line tools globally as they can be easily used for malicious purposes. The best way is to allow minimal workstations to use PsExec, that can reduce the attack surface in case any occurs. 










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