> For the complete documentation index, see [llms.txt](https://ajmal-anwar.gitbook.io/zyberspace-by-ajmal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ajmal-anwar.gitbook.io/zyberspace-by-ajmal/zyberlab/00-start-here/lab-safety.md).

# Lab Safety & Responsible Testing

ZyberLab is intended for controlled learning and authorized security testing.

## Core Rule

Only test systems, accounts, applications, and networks that you own or have explicit permission to assess.

Do not scan, exploit, disrupt, or attempt to bypass security controls on public systems or third-party environments without authorization.

## Keep the Lab Isolated

Use virtual machines and controlled virtual networks whenever possible.

For beginner exercises, VMware NAT networking is usually sufficient. More isolated host-only networks can be introduced later when a lab requires them.

Avoid exposing intentionally vulnerable applications directly to the public internet.

## Use Snapshots

Before making significant changes:

* Shut down unnecessary applications.
* Confirm the correct VM is selected.
* Take a VMware snapshot when appropriate.
* Give the snapshot a clear name describing the state.

Snapshots make it easier to recover from configuration mistakes without rebuilding the entire environment.

## Use Test Accounts

Create dedicated lab accounts instead of using personal or production credentials.

Example naming:

* `labuser01`
* `testuser01`
* `adminlab01`

Use simple passwords only when a specific controlled exercise requires them, and never reuse real passwords from personal or work accounts.

## Protect Sensitive Information

Before publishing screenshots or notes, check for:

* Passwords and secrets
* Email addresses
* Personal information
* Production hostnames
* Public IP addresses that should remain private
* Organization-specific architecture
* Internal logs or customer data

Sanitize or replace sensitive values with safe lab examples.

## Understand Before Running Commands

Do not copy and execute commands simply because they appear in a tutorial.

Before running a command, understand:

* What it does
* Which system it affects
* Whether it changes configuration
* Whether administrator privileges are required
* How to reverse the change

## Responsible Learning

The purpose of security testing in ZyberLab is to understand systems, identify security behavior, practice detection, and improve defensive knowledge.

All exercises should remain within a safe, legal, and authorized environment.