Vulnerable Active Directory Scripts (Part 1)

By Ashwin Venugopal -

 




About

There are different types of Vulnerable Active Directory Scripts that make AD environment vulnerable to various kinds of attacks. Every script is written in PowerShell. 

ACL

In Active Directory, this is used to establish an Organizational Unit and configure Access Control Lists (ACLs). The script's first two lines import the Active Directory module, which sets the current location to the AD disc and offers the cmdlets required to operate with AD.   

The script then defines the "SetAcl" function, which has four parameters: $right, $inheritance, $for, and $to." The username of the user for whom the ACL is being set is represented by the $for parameter, the name of the OU to which the ACL is being applied is represented by the $to parameter, and the right being granted to the user is represented by the $right parameter. To indicate if the access rule should be inherited by child objects, use the $inheritance argument. Additionally, the function contains an extra input called $extendedRight that can be used to define an extended right.

AnonymousLDAP

In an AD system, this script is used to set the anonymous LDAP bind user and enable anonymous LDAP access. The script's initial line imports the Active Directory module, which offers the cmdlets required to work with AD. 

ASRPRoasting

This PowerShell command can be used to change an AD user account's settings. This command specifically sets the "DoesNotRequirePreAuth" value of the user account "korin.z" to true using the Set-ADAccountControl cmdlet.

The "DoesNotRequirePreAuth" attribute determines whether or not the user account pre-authentication step is required by the Kerberos authentication protocol. The user can authenticate to the domain without supplying any evidence of their prior domain authentication when this attribute is set to true, indicating that the user account does not require pre-authentication. Because anyone can authenticate to the domain as the designated user without having to provide a working password or other kind of identity verification, this lowers security.

Note- This command only affects the account on the Kerberos authentication protocol, and does not affect other authentication protocols such as NTLM or LDAP. 

Conclusion

This topic talks about different Vulnerable Active Directory Scripts and their uses. 



































































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