added more structure

2024-04-30 22:52:03 -06:00
parent b1b7563c46
commit d6daf8d680
19 changed files with 0 additions and 0 deletions
--- a/docs/tech_docs/lab/AD_planning.md
+++ b/docs/tech_docs/lab/AD_planning.md
@@ -0,0 +1,58 @@
+### Planning Phase for Active Directory Deployment
+
+The planning phase is critical in setting up an Active Directory (AD) environment that is scalable, secure, and meets the organizational needs efficiently. Let's delve deeper into each aspect of this phase.
+
+#### 1. **Determine Domain Structure**
+
+- **Single vs. Multiple Domains:** A single domain is often sufficient for small to medium-sized organizations with a centralized management structure. Multiple domains might be necessary for large or geographically dispersed organizations, especially if there are distinct administrative boundaries, different password policies, or security requirements.
+- **Example:** A multinational corporation with operations in the US and Europe might opt for `us.corp.example.com` and `eu.corp.example.com` to cater to specific regulatory requirements and administrative autonomy in each region.
+
+#### 2. **Design OU Structure**
+
+- **Purpose of OUs:** Organizational Units (OUs) are containers in AD that help in grouping objects such as users, groups, and computers. They facilitate delegation of administrative rights and the application of policies at a granular level.
+- **Planning Considerations:** When designing the OU structure, consider factors like the number of departments, the need for delegation of administrative rights, and the granularity required for Group Policy application.
+- **Example Structure:**
+  - Root Domain: `corp.example.com`
+    - `Employees`
+      - `HR`
+      - `Engineering`
+      - `Sales`
+    - `Service Accounts`
+    - `Workstations`
+      - `Laptops`
+      - `Desktops`
+    - `Servers`
+      - `Application Servers`
+      - `File Servers`
+
+#### 3. **Plan AD Sites and Services**
+
+- **Role of AD Sites:** Sites in AD represent physical or network topology. Their correct configuration is crucial for optimizing authentication and replication traffic, especially in a geographically dispersed environment.
+- **Site Planning:** Base your site structure on the location of your network’s subnets and the physical topology, ensuring efficient replication across WAN links and optimal client authentication processes.
+- **Example Configuration:**
+  - Site Names: `SiteNY`, `SiteLA`
+  - `SiteNY` associates with subnet `192.168.10.0/24`
+  - `SiteLA` associates with subnet `192.168.20.0/24`
+  - Define site link `NY-LA` to manage replication between the two sites.
+
+#### 4. **Decide on Naming Conventions**
+
+- **Importance:** Consistent naming conventions enhance clarity, simplify management, and support automation.
+- **Considerations:** Include readability, uniqueness, and future scalability in your naming conventions. Avoid using special characters or overly complex formats.
+- **Examples:**
+  - **Usernames:** `firstname.lastname@corp.example.com`
+  - **Computers:** `[location]-[dept]-[serial]` e.g., `NY-HR-12345`
+  - **Groups:** `[purpose]-[scope]-[region]-[description]` e.g., `Access-Global-HR-Managers`
+
+#### 5. **Design Group Policy Objects (GPOs)**
+
+- **GPO Strategy:** Start with a minimal number of GPOs and only create more as needed to meet specific requirements. This approach keeps the environment manageable and reduces troubleshooting complexity.
+- **Common GPOs:**
+  - **Security Policy:** Enforces password policies, account lockout policies, and Kerberos policies.
+    - Example: Password Policy GPO with settings for password complexity, minimum length, and history.
+  - **Desktop Configuration:** Manages desktop environments across users or computers, including settings for desktop icons, wallpaper, and start menu layout.
+    - Example: Desktop Lockdown GPO that restricts access to control panel and command prompt.
+  - **Software Deployment:** Facilitates centralized deployment and updates of applications.
+    - Example: Office Suite Deployment GPO that automatically installs or updates Microsoft Office for all users in the `Employees` OU.
+
+By meticulously planning each of these aspects, you lay a solid foundation for your Active Directory deployment that aligns with organizational needs, simplifies management, and scales effectively with your business.
--- a/docs/tech_docs/lab/ad_lab.md
+++ b/docs/tech_docs/lab/ad_lab.md
@@ -0,0 +1,77 @@
+Certainly, creating a more detailed and structured guide with a visual component will make the setup process clearer and more approachable. Below is an enhanced guide that outlines a sample framework for setting up an Active Directory (AD) environment focused on cybersecurity testing. This includes both markdown documentation and a Mermaid diagram for visualization.
+
+---
+
+# Active Directory Setup Framework for Cybersecurity Testing
+
+## Overview
+
+This guide provides a detailed starting point for setting up a simulated Active Directory environment tailored for cybersecurity exploration and testing. It covers essential steps from initial planning and installation to security configurations and testing groundwork.
+
+## 1. Planning and Design
+
+Before diving into the installation, it's crucial to lay out the design and planning of your AD environment. This includes determining the domain structure, planning the network infrastructure, and deciding on security group and OU designs.
+
+### Domain Structure
+- **Domain Name:** `cyberlab.local`
+- **Forest Design:** Single forest, single domain
+
+### Network Infrastructure
+- Consider a simple network layout with a primary domain controller (PDC) and additional domain controllers (ADCs) as needed.
+
+### Security Groups and OUs
+- Create OUs for different departments or teams, e.g., `IT`, `HR`, `Sales`.
+- Plan security groups for role-based access control (RBAC), e.g., `IT Admins`, `HR Managers`.
+
+## 2. Installation and Core Setup
+
+### Install Windows Server
+- **Version:** Windows Server 2019 Standard
+- **Machine:** VM or physical server for the PDC
+
+### Promote to Domain Controller
+- Install the Active Directory Domain Services role.
+- Run the AD DS Configuration Wizard to promote the server to a domain controller.
+
+## 3. Security Configuration
+
+### Baseline Security Policies
+- Implement GPOs for security policies affecting users and machines.
+
+### Test Accounts
+- Populate the AD with test user accounts and groups reflecting various roles.
+
+## 4. Advanced Features and Testing Preparation
+
+### Advanced AD Services
+- Optionally, explore setting up ADFS, AD CS, and AD RMS for advanced testing scenarios.
+
+## 5. Maintenance and Continuous Improvement
+
+### Regular Updates
+- Apply updates and patches regularly to keep the environment secure.
+
+## Sample Mermaid Diagram
+
+To visualize the setup, here's a Mermaid diagram illustrating a basic AD setup:
+
+```mermaid
+graph TD;
+    A[Windows Server 2019] -->|Installs AD DS| B(PDC: Primary Domain Controller);
+    B --> C{Domain: cyberlab.local};
+    C --> D[OU: IT];
+    C --> E[OU: HR];
+    C --> F[OU: Sales];
+    D --> G[Security Group: IT Admins];
+    E --> H[Security Group: HR Managers];
+    B --> I[ADCS Advanced Services];
+    I --> J[ADFS];
+    I --> K[AD CS];
+    I --> L[AD RMS];
+```
+
+This diagram illustrates the foundational elements of the AD setup, including the primary domain controller (PDC) setup with Windows Server 2019, the creation of organizational units (OUs) for IT, HR, and Sales departments, and the setup of security groups within those OUs. It also highlights the incorporation of advanced AD services like ADFS, Certificate Services, and Rights Management Services for comprehensive security testing.
+
+---
+
+This framework and visual guide offer a solid starting point for setting up an AD environment optimized for cybersecurity testing and training. It's a flexible template; you can expand or adjust it based on specific testing requirements or to explore various cybersecurity scenarios.