My name is Josh and I am looking to get started in Cyber Security.
01.
Value Statement
I’m a cybersecurity graduate with a strong interest in digital forensics and information security. I bring real‑world experience in physical security and a proactive, hands‑on approach to problem‑solving. I learn best by doing, and I’m motivated to keep building practical skills that help make people and systems safer.
02.
About Me
I will be graduating with a degree in Information Technology in April and I am looking for a position that will help me grow and develop my skills in IT and Cyber Security.
I thoroughly enjoyed studying a wide range of IT topics, with particular interest in Digital Forensics, Information Security, and my Capstone Project.
I’m motivated to keep learning and developing new skills, especially in cybersecurity and digital forensics. I care deeply about helping people understand online risks, including common social engineering attacks like phishing and tailgating. I’m skilled at identifying physical security vulnerabilities and equally comfortable analysing and solving problems in digital environments.
03.
Core Skills
1. Information Security Awareness
Recognising common threats such as phishing, tailgating and social engineering attempts while being able to communicate these to others clearly.
2. Digital Forensics Fundamentals
Basic understanding of how to analyse digital artefacts while following a structured investigative process.
3. Physical Security Risk Identification
Real-world experience in the physical security industry.
4. Hands-On Problem Solving
Proactive practical approach to problem solving. I prefer 'doing' over reading.
5. Continuous Learning and Skill Development
Motivated to grow in a cybersecurity or DFIR role where growth is not only wanted, but expected.
04.
Project Showcase
Overview
A key part of my studies in the final year was the completion of a Capstone Project.
My team was tasked by the client to develop a system that took known vulnerabilites and generated a report that was readable to non-technical stakeholders and contained actionable information.
The process was automated from start to finish, the only user input was where the program was going to scan to retrieve vulnerability data.
My Role
I contributed across several roles throughout the project, primarily in development and research before specialising in system integration. I also served as the main minute‑taker and supported the team as a backup project manager.
Tools Used
This project was multi-faceted and required many tools throughout the development cycle. Some of the main tools used were:
- NMap
- Python3
- Ollama
- Linux Server
- LaTeX
The Process
Our capstone team followed the Design Science Research Methodology (DSRM), which allowed us to incorporate continuous expert feedback throughout the project. We began with several weeks of planning and foundational research, exploring suitable methodologies while also strengthening our practical skills. During this phase, we practiced programming, experimented with different approaches, and became more confident working within Linux environments.
The first major development milestone involved retrieving valid system information and formatting it into a basic, readable report. This early version included the target address, port number, and a list of identified CVEs. Once this workflow was stable, we expanded the functionality to operate across an entire subnet, allowing the tool to scale beyond a single host.
Building on that success, the team moved into the next phase: mapping the identified CVEs to relevant risk mitigations and remediation recommendations. This step proved challenging, as there is no single consolidated database that provides consistent, actionable mitigation guidance. With limited time and fragmented sources, we had to design workarounds and make pragmatic decisions to deliver meaningful results within the project constraints.
Our team was successful in developing a functional prototype that demonstrated the core capabilities we set out to achieve. The tool reliably gathered system information, identified relevant CVEs, and generated structured reports for both individual hosts and entire subnets. While the mitigation‑mapping component was limited by the lack of a unified remediation database, we were still able to produce meaningful, actionable insights within the scope of the project. Overall, the prototype validated our approach and showed clear potential for further development.
What I learned
This project pushed me well outside my comfort zone, as nothing similar had been publicly developed before. Working in an area with no existing blueprint meant the entire team — and especially myself — had to navigate uncertainty from start to finish. As my role focused heavily on integration and development, I needed to understand how every script worked, how each component interacted, and how to bring everything together into a functioning system.
Many hours were spent in trial and error, reading through code, streamlining processes, and managing unexpected errors. Through this, I developed stronger problem‑solving skills, became more confident working in Linux environments, and learned how to approach complex technical challenges without relying on pre‑existing solutions. The experience taught me how to stay adaptable, persistent, and methodical when working on a project with no clear roadmap.
Contact Me
If you are interested in meeting and discussing potential roles, please reach out at the address below of the number provided in my CV.