Track Common Adversary Tasks Performed Using AADInternals

By Ashwin Venugopal -

 







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







Overview

Although Azure AD, which is heavily utilized by Microsoft Office 365 and around 2900 other third-party programs, is usually thought to be secure, there are some significant identification, authentication, and other security issues that shouldn't be ignored. AADInternals is one such program, a PowerShell-based framework used for managing, listing, and manipulating Azure AD that is freely accessible on GitHub.

As the name implies, it has to do with on-premises and cloud services, and the features could lead to security problems such the creation of backdoor users, password theft, encryption key theft, etc.

Misuses of AADInternals

If not handled appropriately, AADInternals can be quickly exploited by bad actors. For example, if identity data is synchronised between on-premises AD and Azure AD, the applications utilized may enable an attacker to target and steal sensitive data from the victim Azure AD tenancy, which then allows them to carry out the following actions:
  1. Dumping encryption keys.
  2. Exfilteration of Azure AD connector account password.
  3. Creating backdoor to Azure AD.
  4. Update Azure AD connect credentials for Azure AD. 
  5. Create users only in Azure AD.

Detections

  • Log Inspection- This one can help in monitoring all the PowerShell activity events of the host.

  • Activity Monitoring- This module can detect processes, files, AMSI, and network activities on endpoints running Workload Security.

  • Utilizing Trend Micro Vision One- As the name suggests, this one collects all the detections from workload security and correlates them to offer a comprehensive visibility across all data in one console. 








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