Kali Linux and Security Testing (Lab and Coursework)

I use Kali Linux in controlled lab environments to practise structured security testing and understand how common weaknesses are identified, verified, and communicated clearly.

Tools and activities:

• Nmap: host discovery and port/service scanning to map exposure and build an attack surface view.
• Nessus: vulnerability scanning to identify patching gaps and weak configurations in lab servers.
• Burp Suite: web request inspection and basic testing aligned to OWASP Top 10 concepts.
• Metasploit: used only on intentionally vulnerable systems (e.g., Metasploitable) to understand exploitation steps and typical indicators.
• Wireshark: packet capture for protocol understanding, troubleshooting, and spotting unexpected traffic.
• Snort: basic IDS setup to observe alerts and how activity appears in logs.

This work helped me link findings to real outcomes such as reducing exposed services, improving patching and configuration, strengthening web application behaviour, and understanding how attacks and detections look from both sides. All testing is done only in authorised environments.

Windows, Windows Server, and Microsoft 365 (Foundational)

I’ve built Microsoft-based lab environments to understand how typical business systems are structured and how core security controls are applied.

Tools and activities:

• Windows Server: configured roles such as DNS and DHCP in lab networks.
• Active Directory (AD): created users/groups and applied basic access controls and permissions.
• Group Policy (GPO): applied baseline settings to standardise and harden endpoints.
• Microsoft 365: regular use in work/study, with awareness of identity and access fundamentals.

Most real business risk comes from weak identity and access practices-too many privileged accounts, inconsistent configurations, and poor user lifecycle management. This foundation helps me understand where common weaknesses come from and how basic controls reduce risk.

Network Security and Firewall Fundamentals (Lab)

I’ve designed and tested small network setups in lab scenarios, focusing on practical controls that reduce attack surface and limit unnecessary access.

Tools and activities:

• Firewall rules: inbound/outbound controls using IPs, ports, and services.
• Exposure reduction: validating filtered/closed services through scanning and testing.
• Basic segmentation concepts: separating guest and internal access where supported.
• HTTPS/TLS basics: confirming secure access is enabled and unnecessary ports are restricted.

Good network security is mostly good decisions-only expose what is required, restrict management access, and keep internal services internal. These basics reduce common attack paths like exposed admin panels, accidental service exposure, and easy lateral movement.

Web Application Security (Foundational, Hands-on)

I’ve carried out structured web testing in university and lab environments to understand how common web weaknesses appear and how to report them clearly.

Tools and activities:

• Testing aligned with OWASP Top 10 concepts (authentication, access control, input handling, configuration).
• Basic vulnerability validation with evidence (requests, responses, screenshots) in controlled environments.
• Focus on fix thinking: input validation, least privilege, and safe configuration.

Web issues are a common entry point for real attacks. Practising this helps me identify practical risks (e.g., account abuse, data exposure, unsafe uploads) and communicate the fixes in a way that can actually be implemented, not just listed.

Wireless Network Security (Lab and Demonstrations)

I’ve built and secured wireless networks in lab and small-office style setups, focusing on secure configuration and understanding legacy weaknesses.

Tools and activities:

• Secure encryption configuration (e.g., WPA2/WPA3 in supported labs) and strong passphrases.
• Basic segmentation approaches for guest vs internal access where supported.
• Controlled testing of legacy weaknesses (e.g., WEP) to understand why insecure standards should not be used.

Wireless is often overlooked in small environments. Secure configuration and segmentation can prevent casual access, reduce risk from weak devices, and limit how far an attacker can move if a network is misconfigured.

Digital Forensics (Fundamentals)

I’ve used forensic tools in coursework and controlled practice to understand evidence handling, integrity, and basic artefact analysis.

Tools and activities:

• FTK Imager: forensic imaging of drives/USB media and integrity verification via hashes.
• Autopsy: review of files, browser artefacts, and basic timeline-style analysis from test images.
• Write-protection basics and documentation: following repeatable steps and avoiding changes to source data.

Even basic investigation work depends on doing things carefully and consistently. Understanding integrity and documentation reduces mistakes and helps ensure results are defensible.

Programming and Scripting (Security Support)

I use code to support learning, automation, and repeatable security tasks—mainly small tools and helper scripts.

Tools and activities:

• Python: basic automation (parsing, helper scripts, simple workflows to reduce repetitive tasks).
• C++ / Java: academic projects building understanding of programming and OOP.
• C# (Windows Forms): simple interfaces/tools for user interaction in coursework.
• HTML / CSS / JavaScript: basic web builds to understand how apps handle input and why security issues occur.

Being able to read and write code helps in security because it improves understanding of how systems fail and makes it easier to automate repeatable work. I don’t position myself as a full-time developer, but I can build and adapt practical tooling to support security tasks.

Legislation and Standards (Awareness)

I have a foundational understanding of key UK legislation and common security standards that guide ethical, legal, and responsible testing.

Key areas:

• UK GDPR and Data Protection Act (DPA)
• Computer Misuse Act
• ISO/IEC 27001 (conceptual awareness)

It keeps work responsible and scope-led: consent, authorisation, data minimisation, and clear documentation are part of good security practice, not optional extras.