Persistence (Part 3)

By Ashwin Venugopal -

 






Overview

Deploying persistence by a penetration tester is important during penetration testing assessment. Hence, implementing persistence throughout the AD compromise process, the tester can ensure that his access cannot easily be revoked by the blue team. 

ACLs

AdminSDHolder container exist in every AD domain and its Access Control List (ACL) can be used as a template to copy permissions to all protected groups. A process known as SDProp takes the ACL of the AdminSDHolder container and applies it to all protected groups every 60 minutes. If the blue team is unaware of this persistence, then, every time they remove the inappropriate permission on the protected object or groups, it will reappear within an hour. Since this reconstruction occurs via normal AD process, it would not show any alert, making it more difficult to pinpoint the source of the persistence.

GPOs

They are also excellent in deploying persistence. A penetration tester can hide GPO in a way that it becomes almost impossible to remove it. Some common GPO persistence techniques are:
  • Restricted Group Membership- It can allow administrative access to all hosts in the domain.
  • Logon Script Deployment- It makes sure to get a shell callback every time a user authenticate to a host in the domain.

Numerous hooks are available for deployment. Even though it's good to have access to every host, it could be even better if we could make sure we could access them when administrators were actively working on them. In order to accomplish this, we will establish a GPO connected to the Admins OU, enabling a shell on a host each time one of them logs in. 

Conclusion

A penetration tester can linger in an AD environment in a number of ways. A few of these methods are more durable than others. Depending on the environment and the various configurations he has at his disposal, he must consider innovative ways to deploy the persistence so that the blue team is unable to remove it. Moreover, he shouldn't put off deploying persistence until after the entire domain has been compromised. Persistence should be used following each round of lateral movement and privilege escalation. Other viable options for the penetration testers are:
  1. Computer Accounts
  2. Skeleton Keys
  3. Directory Service Restore Mode (DSRM)
  4. Malicious Security Support Provider (SSP) 






















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