CASE / 01Public project
Infrastructure / Security
TomSec Homelab Infrastructure ↗
Public applications, private administration and storage boundaries on an existing Linux server.
UPDATED / 2026-09-20
01 / WHOAMI
> whoami
Tom / Cybersecurity student ↗
TOMSECURITY / SYSTEMS / CURIOSITY
Understand the system.
Question the boundary.
Exploring how networks, software and people fit together—and how to make those connections more secure.
SCROLL TO INSPECTINTERACTIVE SESSION / 001
$ whoami
Tom / Cybersecurity student
$ status
Building. Learning. Breaking. Securing.
Type help to explore. Nothing here runs a shell.
NO SHELL ACCESSANOTHER WAY TO EXPLORE ↓
> focus --currentOffensive securityNetworkingLinuxCloudInfrastructure
02 / PROFILE
> cat /etc/tomsec/profile
A practical kind
of curiosity.
My interests sit where offensive security meets practical engineering: Linux, networking, automation and the systems behind everyday services. This workstation collects the projects and notes from that learning process.
- ROLE
- Cybersecurity student
- LOCATION
- Scotland, UK
- CURRENT STUDY
- Cybersecurity
- PRIMARY FOCUS
- Networks & infrastructure
- LAB STATUS
- Operating / evolving
03 / PROJECTS
> mount ~/projects --read-only
Open a case file.
01private-homelabPUBLIC PROJECT02nextcloudOPERATING03xray-routingIMPLEMENTED04tomsec-pipelineDEPLOYED
CASE / 02Operating
Storage / Infrastructure
Nextcloud Private Cloud ↗
A document and coursework cloud with filesystem-enforced limits and consistent local recovery snapshots.
RECORD / 2026-09-08
PUBLIC / TECHNICAL RECORDOpen case file ↗
CASE / 03Implemented
Networking / Security
Custom Xray Privacy Tunnel ↗
Predictable routing boundaries between ordinary Internet traffic and private homelab access.
RECORD / 2026-09-08
PUBLIC / TECHNICAL RECORDOpen case file ↗
CASE / 04Deployed
Development / Security
TomSec Portfolio & Secure Draft Pipeline ↗
A public Next.js portfolio with an authenticated draft queue and a separate human publishing step.
RECORD / 2026-09-08
PUBLIC / TECHNICAL RECORDOpen case file ↗
04 / INFRASTRUCTURE
> inspect --routes
Every connection
has a boundary.
Public applications, private administration and privacy routing serve different purposes. Select a path to see where it leads.
Inside the homelab ↗FRAME / 02 · CONCEPTUAL TOPOLOGY
Public surface. Private control.
NO PRIVATE TELEMETRY
INSPECT / INTERNET
Visitors reach published applications. This conceptual map makes no live requests to the lab.
05 / CAPABILITIES
> systemctl start capabilities.target
Connected disciplines.
Active areas of learning, grounded in projects and coursework.
SECLEARNING / 01
Offensive security
- Reconnaissance
- Enumeration
- Web security
- Security research
NETLEARNING / 02
Networking
- TCP/IP
- DNS
- Routing
- Network design
SYSLEARNING / 03
Systems
- Linux
- Docker
- Storage
- Service administration
CLDLEARNING / 04
Cloud
- Identity boundaries
- Reverse proxies
- HTTPS
- Cloud architecture
DEVLEARNING / 05
Automation
- Shell scripting
- Python
- TypeScript
- APIs
AILEARNING / 06
AI & review
- Assisted research
- Draft validation
- Human review
- Safe publishing
06 / CREDENTIALS
> tail -f /var/log/education.log
Learning, in progress.
A clear distinction between current study, earned credentials and future plans.
IN PROGRESS
Cyber Security & Forensics
Edinburgh College · My current college-level cybersecurity education, developing the foundation established through the NPA.
Education log ↗ACHIEVED
AWS Certified Cloud Practitioner
Completed certification. View the learning record for knowledge covered and its application to cybersecurity.
Credential details ↗PLANNED
Next learning steps
Continue developing networking, offensive security and infrastructure skills. No planned certification is presented as earned.
07 / FIELD NOTES
> ls ~/field-notes
Notes from the workbench.
08 / CONTACT
> ./contact --secure
Let’s compare notes.
Explore the work, ask about a design decision, or start a conversation.