Jeremy BryantCybersecurity portfolio

Cybersecurity student · Australia

Understand
the system.
Prove the work.

I'm Jeremy Bryant. I’m building a career in cybersecurity through hands-on learning, careful investigation and clear documentation.

Explore the home lab Meet me on LinkedIn
Systems & IoTNetwork fundamentalsSecurity writing
Conceptual drawing of the LG home lab An owner-controlled television with a community home screen, protected SSH access from a computer, and a route back to the original LG Home. This is an illustrative system diagram, not a screenshot or a network inventory. SYSTEM STUDY / 01 CONCEPTUAL DIAGRAM Maintenance KEY-BASED SSH CONTROLLED ADMINISTRATOR ACCESS Stock fallback ORIGINAL LG HOME A TESTED ROUTE BACK OWNER-CONTROLLED HARDWARE LOCAL LAB ENVIRONMENT GLASSHOUSE / COMMUNITY HOME A more considered home. COMMUNITY TOOLS. DOCUMENTED CHANGES. HOME SCREEN · RESTART CHECKS · RECOVERY FIG. 01 — ILLUSTRATIVE SYSTEM VIEW NOT A SCREENSHOT
FIG. 01 / OWNER-CONTROLLED HOME LABExplore. Configure. Verify.

01 Selected work

A real device. Real constraints.
A result that still has to work tomorrow.

Home labwebOS / LinuxCompleted core setup

A television.
A complete
systems project.

Turning my LG television into a more controllable home-lab device—with community Homebrew, a custom home screen, key-based administration and a tested route back to LG Home.

The interesting part was getting the changes to survive a restart while keeping the television useful for everyday gaming and streaming.

Read the case study
October 2026Owner-authorised · Verified setup
Two ways to use one device
Custom homeGlasshouseA simpler home screen
PS5HDMI picture & sound
StreamingNormal app playback

Stock LG Home remains available as a fallback. This is a conceptual system map, not a live device dashboard.

Local networkMaintenance PCAuthenticated SSH connection
LG webOSKey-based SSH · Telnet disabled
Verify & recoverRestart checks · Preserved configuration

Configuration checked during the lab. These checks do not constitute a comprehensive security assessment.

AdministrationKey-based SSH
ContinuityRestart verified
RecoveryLG Home fallback

Guided practice

Security foundations.
30 practice labs.

26 exercises with supplied evidence, plus four hands-on tool workflows.
Independent practice pending.

01

Network investigation

Explain a DNS lookup from packet evidence.

Separate successful replies, name-not-found responses and unanswered requests.

 02

Security operations

Investigate a pattern of failed logins.

Build a timeline, check context and write a measured escalation.

 03

Cloud-security foundations

Review access without breaking legitimate work.

Practise least privilege in a small offline storage-permission model.

 04

Web investigation

Read a web request without guessing its outcome.

Interpret paths, response codes and context in fictional access logs.

 05

Change investigation

Find what changed. Check whether it was expected.

Compare file hashes and review changes against an agreed baseline.

 06

Network boundaries

Follow the rules that allow or block traffic.

Review rule order while preserving the traffic needed for normal work.

Explore 20 more foundation labs ↗

Explore four hands-on tool labs ↗

Follow the practice guide ↗

02 How I approach a problem

Curiosity is
the starting point.
Evidence is the next.

I’m studying computing at Deakin University and developing my cybersecurity skills through practical projects and technical writing.

I enjoy understanding how a system fits together: what it exposes, what a change affects, and how to tell whether it actually worked. My portfolio follows that process, including the parts that needed another attempt.

These are learning projects. I credit community developers and distinguish tested results from work still in progress.

More about my path
01 / OBSERVE

Establish what is actually there.

Identify the device, software and network state before deciding what a result means. A page loading is an observation; administrator access needs separate evidence.

02 / CHANGE

Keep changes understandable.

Work in manageable steps. Preserve the previous configuration and understand the path back before making a change persistent.

03 / VERIFY

Check the outcome in real use.

Restart the device, try its normal functions and record the result. A successful command is only part of the story.

03 Study notes

Making the technical clear.

Short explanations of the security concepts I’m learning.
Published on LinkedIn · October 2026

01

Application security

SQL injection: keeping data separate from database instructions

Why query structure and user input belong on different sides of the boundary.

 02

Web security

XSS and CSRF: two questions about browser trust

Understanding what a browser executes and whether a user intended an action.

 03

Network defence

Reading a Snort alert without jumping to conclusions

Separating a rule match, the surrounding evidence and the conclusion it supports.

The next step

Let’s talk about
what comes next.

I’m interested in entry-level cybersecurity opportunities, practical learning and conversations with people who build and defend systems.

Connect on LinkedIn Explore the project source