Thirteen project and learning entries. Status labels separate reported hands-on work, a source-backed release candidate, historical practice and future development. Reported outcomes are not presented as independent audit results.
PROJECT / 01Reported build
Mark 2000 — Earlier Ubuntu VPN Gateway
Self-hosted private VPN/proxy work on an older Ubuntu laptop with scripting and operational troubleshooting.
UbuntuXray-coreBashPython
Read project notes
Scope & evidence
- Purpose: Build private, flexible remote access from a personally managed server.
- Reported work: Server provisioning, Xray protocol configuration, local proxy interfaces, management scripting and performance experiments.
- What the available evidence supports: Historical personal project discussions; a current machine snapshot or benchmark is not preserved.
- Next evidence step: Sanitised architecture, service inventory, reproducible test logs and security retrospective.
PROJECT / 02Source-backed RC1
JACG-2300 — Security Gateway Release Candidate
A safer successor gateway centred on least privilege, transactional configuration changes and recovery.
PythonLinuxWireGuardTests
Read project notes
Scope & evidence
- Purpose: Re-engineer remote access services with secure defaults and safe failure recovery.
- Recovered evidence: Complete RC1 source archive, deployment notes, security reviews and recorded automated test outputs.
- Reported test scope: Local tests and simulated crash scenarios. Production deployment, regional compatibility and hardware validation remain unverified.
- Current constraints: Treat the old installers as untrusted for live use; preserve the existing router and test in isolated staging before approval.
PROJECT / 03Practice · evidence limited
Metasploitable 2 — Lab Network Troubleshooting
An authorised Kali/Metasploitable lab focused on getting the network topology reachable before assessment.
Kali LinuxMetasploitable 2RoutingNmap
Read project notes
Scope & evidence
- Historical exercise: A Kali host and intentionally vulnerable VM were reported on different IPv4 subnets.
- Problem: The target needed confirmed layer-3 reachability before reliable discovery or vulnerability work.
- Approach: Inspect interfaces, routing and the hypervisor’s lab network; then run permissioned discovery only inside the isolated lab.
- Evidence limit: No archived successful exploitation result, Nessus report or root-shell output was recovered; those are not claimed here.
PROJECT / 04Learning workflow
Network Reconnaissance — Repeatable Nmap Method
A structured, authorised workflow for inventorying hosts and understanding visible services.
NmapIP networkingDiscoveryReporting
Read project notes
Scope & evidence
- Scope: Only a home network or an isolated test subnet with permission.
- Method: Establish target list and network reachability, record host discovery, then examine approved service fingerprints.
- Defensive value: Inventory exposed services and recommend minimisation, segmentation and patching.
- Evidence limit: Historical lab reports are incomplete; exact host counts, ports and scan findings are not published as verified results.
PROJECT / 05Planned lab
Nmap / Firewall Behaviour — Planned Lab
Compare discovery and port-state behaviour across a deliberately isolated virtual firewall.
FirewallNmapLab designDetection
Read project notes
Scope & evidence
- Proposed scope: Use disposable VMs and private virtual switches under explicit ownership.
- Question: How do filtering rules change observed port states and defender logs?
- Deliverables: Topology diagram, permitted probe matrix, firewall log correlations and precise limitations.
- Status: A learning plan, not an already-completed EVE-NG evaluation.
PROJECT / 06Planned lab
Wireless Security — Defensive Lab Roadmap
A controlled wireless-learning plan centred on authentication, safe audit scope and hardening.
WPA2 / WPA3WPSSegmentationWireless
Read project notes
Scope & evidence
- Proposed environment: An owned lab access point and test clients separated from household production access.
- Focus: Configuration inventory, passphrase policy, WPA3 compatibility, WPS disablement and protected management frames.
- Output goal: Sanitised observations and clear remediation advice.
- Evidence limit: No preserved captured handshakes, wireless cracking results or WPS test logs were recovered.
PROJECT / 07Reported operational
GE230 — WireGuard Remote Access
Real router-level VPN configuration and UK-to-Bangladesh troubleshooting, including restrictive-network limitations.
WireGuardTP-LinkDNSMTU
Read project notes
Scope & evidence
- Objective: Maintain private remote connectivity without disrupting the existing household router.
- Reported evidence: Working WireGuard handshake and transferred data from a UK client.
- Troubleshooting: Investigated routing, DNS, mobile application behaviour and networks where handshake did not guarantee connectivity.
- Next step: Redacted repeatable connectivity measurements; avoid posting public endpoints or client keys.
PROJECT / 08Study / reported grades
CCNA & Linux — Training Foundations
Networking fundamentals and Linux administration developed through training and practice.
TCP/IPLinuxSubnettingRouting
Read project notes
Scope & evidence
- Training topics: Addressing, subnetting, switching, routing, DHCP/DNS and Linux administration.
- The user previously reported A+ results in CCNA and Linux training modules; a formal vendor CCNA certification is not claimed.
- Individual simulator files and graded lab outputs were not recovered for public review.
- Next step: Publish reproducible Packet Tracer examples and verified output once collected.
PROJECT / 09Historical practice
Kali Linux — Installation & Lab Setup
Hands-on familiarity with Kali Linux and the practical challenges of building a clean isolated lab.
KaliLinuxVirtualisationNetworking
Read project notes
Scope & evidence
- Early practice with Kali installation and networking was reported retrospectively from 2014–2015.
- Later practice involved Kali and a Metasploitable test VM on separate networks.
- Useful lessons: Document hypervisor network settings and isolate intentionally vulnerable targets.
- Evidence limit: Original early installation images or command logs were not preserved.
PROJECT / 10Source-backed work
Bash & Python — Automation for Operations
Configuration tooling and checks developed around the private gateway and its safer rebuild.
BashPythonsystemdValidation
Read project notes
Scope & evidence
- Available artifacts include historical installers and a Python-based release candidate.
- Practical topics: Configuration generation, health reporting, backup/restore design and safer error handling.
- Key lesson: A working script is not automatically safe for production; use linting, tests, reviews and rollback plans.
- Source is being reviewed before deciding what can safely become public.
PROJECT / 11Learning roadmap
Cloud Security & OSINT — Learning Roadmap
Future demonstrable labs in cloud identity, least privilege and ethical open-source research.
IAMCloudOSINTAudit
Read project notes
Scope & evidence
- Proposed cloud exercise: Build a small low-cost sandbox with tightly scoped IAM policies.
- Proposed OSINT exercise: Investigate only owned or consented assets and record data provenance.
- Deliverables: Redacted policy diffs, reproducible tests and a short security report.
- No verified GCP IAM or Maltego lab artifacts have been retrieved; completed claims have been removed.
PROJECT / 12In planning
Private CCTV / NVR — Secure Design
A proposed private recording system that keeps camera access separated from public-facing services.
Network isolationNVRStorageBackup
Read project notes
Scope & evidence
- Reported hardware: Imou Ranger 2 Dual camera; NVR/cloud integration is not verified.
- Design questions: Local streams, segmented access, secure backups, retention and UPS impact.
- Risk: Never expose camera feeds or administrative panels directly to the public internet.
- Next step: Confirm device-supported protocols and test within a restricted network.
PROJECT / 13User-reported case
Windows Trojan Recovery — Personal Case
A 2022 personal incident involving detection, containment, Windows reinstallation and account recovery.
WindowsContainmentRecoveryMFA
Read project notes
Scope & evidence
- Context: Assisted another person with suspected Windows malware and affected online accounts.
- Reported actions: Windows Security detection, device isolation, OS reinstallation and account recovery.
- The exact malware signature, forensic acquisition and post-recovery validation were not preserved.
- This is documented personal troubleshooting experience, not a professional DFIR engagement.