medusa/the_information_nexus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update docs/tech_docs/cyber_lab.md

Browse Source
This commit is contained in:
medusa
2024-04-10 06:13:19 +00:00
parent c24a27b8f7
commit 83afd8a2fd
1 changed files with 43 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files

84
docs/tech_docs/cyber_lab.md
View File

@@ -1,63 +1,63 @@
To provide a more detailed guide for setting up an Active Directory (AD) domain `homelab.local` tailored for your home environment, including a cybersecurity lab, home LAN/WLAN, NAS, laptops, IT equipment, and servers, we’ll delve deeper into the specifics. This setup aims to enhance management, security, and operational efficiency across all devices and users in your home network. To refine our discussion into a final draft for setting up an Active Directory (AD) domain `homelab.local` for your home, including a detailed cybersecurity lab and efficient management of your home network, NAS, laptops, and other IT equipment, we'll structure the guide with precise steps and configurations.
## Detailed Active Directory Domain Setup for Home Use # Final Guide: Setting Up `homelab.local` AD Domain
### Domain Name: `homelab.local` ## Introduction
- **Primary Domain Controller (PDC):** A robust machine (physical or virtual) that runs Windows Server, designated to manage the domain `homelab.local`. This guide outlines the process for creating an Active Directory (AD) domain, `homelab.local`, tailored for a comprehensive home network that includes personal devices, a cybersecurity lab, network-attached storage (NAS), and various IT and server equipment. It focuses on security, management, and operational efficiency.
- **Secondary Domain Controller (SDC):** Optional but recommended for redundancy, can be a less powerful machine or virtual instance.
### Organizational Units (OUs) Structure ## Domain Configuration
1. **CyberLab:** ### Step 1: Domain and Controller Setup
- Purpose: Contains resources specifically for cybersecurity research and testing.
- Sub-OUs: `Testing Environments`, `Research`, `Tools`.
2. **HomeDevices:** 1. **Primary Domain Controller (PDC):** Choose a dedicated or virtual server with sufficient resources to run Windows Server. This server will manage the `homelab.local` domain.
- Purpose: Manages personal and home devices.
- Sub-OUs: `Personal Laptops`, `Smart Home Devices`.
3. **NAS:** 2. **Secondary Domain Controller (SDC):** Optional but recommended for redundancy. Can be less resource-intensive and also runs Windows Server.
- Purpose: Organizes access to different NAS functionalities.
- Sub-OUs: `Media`, `Personal Storage`, `Lab Data`.
4. **Users:** ### Step 2: Organizational Units (OUs) and Structure
- Purpose: Manages all user accounts.
- Sub-OUs: `Admins`, `Family`, `Guests`.
### Security Groups 1. **Create OUs for Major Areas:**
- `CyberLab`: For cybersecurity research and testing.
- `HomeDevices`: For personal and home devices.
- `NAS`: For network-attached storage access and management.
- `Users`: For managing user accounts and permissions.
- **LabAdmins:** Full access to CyberLab resources. 2. **Define Sub-OUs:**
- **FamilyMembers:** Standard access to home devices, personal storage, and media. - Under `CyberLab`: Create `Testing Environments`, `Research`, `Tools`.
- **MediaAccess:** Special access to media storage on the NAS. - Under `NAS`: Create `Media`, `Personal Storage`, `Lab Data`.
- **Guests:** Restricted access to certain home devices and internet.
### User Accounts ### Step 3: Security Groups and User Accounts
- **Admin Account(s):** For managing AD and critical resources. 1. **Establish Security Groups:**
- **Family User Accounts:** Individual accounts for family members with appropriate access rights. - `LabAdmins`, `FamilyMembers`, `MediaAccess`, `Guests`, with permissions tailored to their needs.
- **Guest Accounts:** Temporary accounts for visitors, with internet access and limited resource access.
### Network Configuration and Security 2. **Create User Accounts:**
- Setup `Admin Account(s)` for AD and resource management.
- Create individual `Family User Accounts` and `Guest Accounts` as needed.
- **LAN/WLAN Segmentation:** Separate networks for `CyberLab` and `HomeDevices` to isolate traffic and enhance security. ### Step 4: Network Configuration and Security
- **Firewall and Access Rules:** Configure firewall rules to control traffic between segments and protect sensitive resources in the `CyberLab`.
### NAS Configuration 1. **Segment LAN/WLAN:**
- Differentiate between `CyberLab` and `HomeDevices` networks for security and traffic isolation.
- **Media Storage:** Shared storage for family media like photos, videos, and music. 2. **Implement Firewall Rules:**
- **Personal Storage:** Private folders for each family member. - Control traffic between network segments, especially protecting `CyberLab` resources.
- **Lab Data:** Storage for cybersecurity research, tools, and data.
### GPOs for Security and Management ### Step 5: NAS Configuration and Access
- **Password Policy:** Strong passwords for all users, with regular mandatory changes. 1. **Set Up Storage Areas:**
- **Update Policy:** Automatic updates for Windows devices to ensure security patches are applied. - Allocate `Media`, `Personal Storage`, and `Lab Data` areas within the NAS, setting appropriate access permissions for each user or group.
- **Software Restrictions:** Limit software installation on `HomeDevices` to prevent malware.
## Mermaid Diagram for Enhanced Detail ### Step 6: Group Policy Objects (GPOs)
Here’s a more detailed Mermaid diagram for your setup: 1. **Define Key Policies:**
- Enforce a strong `Password Policy`.
- Set an `Update Policy` for automatic Windows updates.
- Apply `Software Restrictions` to limit installations on personal and home devices.
## Enhanced Mermaid Diagram
To accompany the final guide, the following Mermaid diagram provides a visual representation of the `homelab.local` setup:
```mermaid ```mermaid
graph TD; graph TD;
@@ -86,4 +86,6 @@ graph TD;
P --> S[Guest Accounts] P --> S[Guest Accounts]
``` ```
This enhanced setup and diagram provide a more granular view of how to structure your home AD domain, focusing on both cybersecurity lab needs and home networking requirements. By following this detailed guide, you can create a secure, manageable, and efficient environment that supports both your professional and personal digital life. ## Conclusion
This guide and diagram serve as a comprehensive blueprint for setting up a secure and efficient Active Directory domain for your home network and cybersecurity lab. By following these steps, you can create a well-organized, manageable environment that supports both your professional and personal digital activities.