Hacker Directory — Understand what you hack.Hacker Directory — Understand what you hack.
Continue learning
TR

Isolated lab guide

Observe normal behavior in an isolated learning environment. This page does not connect to production systems.

This page connects to no system and runs no commands.

01

Draw the boundary

Choose a virtual network completely separate from production. Do not use real accounts, company data, or production DNS. Do not expose AD ports to the open internet.

A diagram showing the isolated network separated from the internet and production.

02

Start with three machines

One DC, one member server, and one client are enough to start. Example names are DC01, FS01, and WS01; domain iyelabs.example. Validate OS licensing and virtualization compatibility separately.

Inventory containing device role, OS/build, resource capacity, and network addresses.

03

Keep identity and data synthetic

Use sample users named Tunahan and Jordan, the Finance group, and harmless text files as the data model to be created. Separate the administration account from the ordinary-use account.

Account/group and sample resource relationship map; not a real password list.

04

Observe normal behavior

Inspect DNS discovery, time state, current tickets, group membership, and resultant GPO reports with read-only methods. The tool is only for seeing evidence.

Expected result, actual result, and time for each observation.

05

Change one condition

Choose only one teaching variable, such as a permission or a GPO scope. Write your prediction first, then compare the result. Do not go outside the authorized test scope.

One hypothesis, one controlled change, and an explained result.

06

Reset and extend

Keep an approved clean baseline. Do not equate AD rollback methods with unplanned snapshot rollback. Plan the need for a second DC, a separate forest, and a CA as later independent extensions.

Repeatable work note and validated rollback conditions.

Learn how to move from a browser example to observation.

  1. Read the lesson’s browser example and expected behavior first.
  2. If you have a Windows environment, plan the observation only in an authorized isolated environment.
  3. Record version, configuration and evidence together, then compare with the lesson’s claim.

A Windows lab is optional for this course. If you have one, learn to evaluate the model separately from observation.