Data security lab

Result: an isolated lab exercises OpenSSL, GnuPG, Nmap, and Snort. Scope evidence is add scope statement and sanitized outputs.

Problem

Security tools are often listed on a resume without evidence. This lab exists to make the tools concrete: create a certificate, sign and verify a file, scan an owned host, and write an intrusion detection rule.

Data

The lab environment is add host setup, network range, and isolation method. Every scan is limited to systems I own or have written permission to test. Sensitive values are removed from the evidence.

Approach and why

Build an isolated network with an owned target.
Use OpenSSL to create a key pair, a certificate signing request, and a self signed certificate. Verify the chain.
Use GnuPG to sign and verify a file. Document key handling.
Use Nmap to scan only the owned target and capture the output.
Use Snort to write and test a rule for a known test pattern.

The scope is the first artifact. A lab without scope is a liability, not a skill.

Results

Tool	Exercise	Evidence
OpenSSL	Certificate chain	add sanitized output
GnuPG	Sign and verify	add sanitized output
Nmap	Owned host scan	add sanitized output
Snort	Rule test	add rule and alert output

Evaluation

Scope: an isolated environment and a written permission note.
Evidence: commands and outputs, with keys, tokens, and addresses sanitized.
Reproducibility: a setup script or a step by step lab guide.
Ethics: no third party systems. No real credentials in the repository.

A reviewer should challenge any security claim without scope and evidence. They should also check that no sensitive data is exposed.

Limitations

This is a lab, not a production assessment. It does not cover web application security, cloud identity, or incident response. It stays in the archive because it is not the first thing an AI engineering reviewer needs.

Next steps

Add the sanitized evidence, a lab diagram, and a short note on what each tool proved and what it did not.