Active Directory (Part 5)

By Ashwin Venugopal -

 







Basics

Group Policies

Group Policy Objects (GPOs) can centrally manage and configure settings for users and computers. They help the administrators in applying policies, configurations, and settings for specific users or groups of users in an Active Directory domain. It is one of the many powerful tools for system administrators that automate and synchronizes a process. These policies can be used to configure a wide range of settings, and some of them are:
  1. Security settings, such as password policy, account lockout policy, and auditing policy.
  2. Software deployment and updates.
  3. Network and connectivity settings.
  4. Desktop and taskbar settings.
  5. Internet Explorer settings.
  6. Folder redirection and roaming profiles.
  7. Remote access and VPN settings.
GPOs are very useful and can save time and reduce the risk of errors, because administrators do not have to manually configure each individual computer or user. They also allow easy roll back changes or application of updates to all affected computers and users at once.

However, if it is not used correctly, it may lead to serious consequences (like any other tool). Few ways that an attacker or penetration tester can leverage misconfigured GPOs to navigate through a network, they are:

  • Use and execute arbitrary code on targeted systems. If an attacker is capable of modifying a GPO to include a script or other executable, they can also successfully run that code on any system or systems that GPO applies to. It allows the attacker to execute malware or other malicious code on the targeted systems. 

  • Use of configured network settings like firewall rules and proxy settings. A misconfigured GPO can be used to bypass all the security controls or redirect network traffic to an attacker's server. 

  • Use granted permissions and privileges to users and groups. A misconfigured GPO can be used to grant attackers administrative privileges on targeted systems. This allows them to perform actions that they could not perform otherwise.

It is highly important to properly secure and configure GPOs to prevent attackers from leveraging them to navigate through a network. This can be done by setting strong passwords for GPOs, restricting access to GPOs, to ensure that they are properly configured.

Conclusion

This part of Active Directory talks about Group Policies and various ways that a threat can use as a leverage against a network. It also provides information about safeguarding the same via some effective methods. 
































































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