FILE_TYPE: TECHNICAL DOSSIER CLASSIFICATION: UNCLASSIFIED REVIEW CYCLE: ONGOING

SYSTEMS ENGINEER
& SECURITY RESEARCHER

A technologist who works comfortably at every layer of the stack — from bare-metal infrastructure and network plumbing up through automation tooling and application logic. General IT competency, a cybersecurity specialization, and an active independent research practice, all backed by a verified professional credential.

CREDENTIAL: VERIFIED DOMAIN: CYBERSECURITY DISCIPLINE: SYSTEMS & INFRASTRUCTURE PRACTICE: INDEPENDENT SECURITY RESEARCH
FILE_01 // SUBJECT PROFILE

Working Across The
Full Stack

Operates as a systems engineer with a specialization in cybersecurity — the kind of technologist equally comfortable racking hardware, wiring up network infrastructure, and reading through application logic looking for the one line that shouldn't be there.

Background spans general IT operations, server administration, Docker-based deployment, persistent tmux workflows, and integration work against APIs of every shape. A long-running home lab serves as a private proving ground — new tooling, network topologies, and hardening techniques get tested there before anything is trusted elsewhere.

Fluent in Python and Bash for automation and tooling, comfortable in Duckscript for build and task orchestration, and grounded in HTML for structuring and shipping interfaces. This dossier itself is one such interface.

CORE COMPETENCY LEDGER
DisciplineSystems Engineering
SpecializationCybersecurity
IT FoundationGeneral IT / Ops
InfrastructureServers, Docker, Networking
AutomationPython, Bash, Duckscript
Research PracticeIndependent / Bugcrowd
Lab StatusActive Home Lab
I AM NOT A SCRIPT KIDDIE 😫

Running someone else's tool is not the same as understanding what it does — and the gap between those two things is where this work actually lives. Every scanner, script, and workflow here is built from the ground up: modular Bash automation designed around real vulnerability taxonomies, not copy-pasted one-liners.

That means reading protocol documentation instead of guessing at flags, understanding why a finding matters instead of just that a tool flagged it, and building infrastructure — servers, containers, networks — well enough to know what breaking it actually looks like. The home lab exists specifically to make sure theory gets tested before it gets trusted.

The credential in the next section, and the tooling described further down, are the receipts.

— filed under: professional standards, not vibes
FILE_02 // SKILLSET MANIFEST

Inventory Of
Working Tools

Grouped by function rather than fashion — languages used to build things, infrastructure used to run things, and the domains this work is actually applied to.

Languages & Scripting
Python Primary
Tooling, automation, and general-purpose scripting.
Bash Primary
Large-scale automation, including modular scanning tooling mapped to formal vulnerability taxonomies.
Duckscript Build
Task orchestration and build-time scripting.
HTML Interface
Structuring and shipping interfaces, including this dossier.
Infrastructure & Tooling
Servers Ops
Provisioning, hardening, and maintaining server environments.
Docker Ops
Containerized deployment and isolated testing environments.
tmux Workflow
Persistent, multi-pane terminal workflows across long-running sessions.
APIs Integration
Consuming and integrating third-party and internal APIs.
Network Infrastructure Core
Routing, segmentation, and traffic behavior across managed networks.
Home Labbing R&D
A standing personal lab for testing infrastructure, tooling, and hardening approaches.
Applied Domains
General IT Foundation
Broad operational IT knowledge underpinning every other discipline here.
Cybersecurity Specialization
Certified specialization — see the Clearance section for credential details.
Vulnerability Research Practice
Independent research aligned to formal vulnerability rating taxonomies.
Systems Engineering Discipline
Designing and operating systems end-to-end, not just individual components.
FILE_03 // CLEARANCE ON RECORD

A Verified
Credential

Fortinet Training Institute Issuing Authority
Fortinet Certified Associate — Cybersecurity
AchievedJune 15, 2026
Valid UntilJune 15, 2028
Validation No.4983193513FF
VALIDATION ID · 4983193513FF
Active & Independently Verifiable

This credential — the Fortinet Certified Associate in Cybersecurity — is issued by the Fortinet Training Institute and confirms foundational, industry-recognized competency across core cybersecurity concepts: threat landscapes, security operations fundamentals, and the baseline principles that underpin every layer of defensive work described elsewhere in this dossier.

It's not decorative. It sits on top of the hands-on infrastructure and research work already described — the home lab, the network administration, the tooling — as a formal, third-party checkpoint on that foundation.

  • Issued directly by Fortinet Training Institute, not a third-party reseller.
  • Carries a unique validation number tied to this record specifically.
  • Independently verifiable on Fortinet's own platform — see FILE_05.
  • Currently active, with a defined validity window through 2028.
FILE_04 // FIELD WORK

Independent
Security Research

Vulnerability research pursued on Bugcrowd as an independent practice — driven by curiosity and craft rather than assignment, and treated with the same rigor as any other engineering discipline.

Approach
Taxonomy-Driven Testing
Research is structured against Bugcrowd's Vulnerability Rating Taxonomy (VRT) rather than ad-hoc guesswork — every finding gets mapped back to a defined class of issue.
Tooling
Custom Bash Automation
Purpose-built scanning tooling, engineered from the ground up in modular Bash, designed to deduplicate findings and map output directly to VRT categories.
Scope
Comprehensive Coverage
Coverage-first mindset — tooling is built to check for breadth across the full range of web-applicable vulnerability classes, not just the easy wins.
Research Platform
Bugcrowd
Engagement Type
Independent / Self-Directed
Methodology
VRT-Aligned Testing
FILE_05 // VERIFICATION

Verify This
Credential Directly

Nothing in FILE_03 needs to be taken on faith. Fortinet publishes an official verification tool — the steps below walk through confirming the credential independently, in under a minute.

01
Open The Verification Tool
Visit training.fortinet.com/admin/tool/certificate/index.php — Fortinet's official certificate validation page.
02
Enter The Validation Number
Input the validation code 4983193513FF exactly as shown into the lookup field on that page.
03
Confirm The Record
Fortinet returns the certificate record directly — confirming the Fortinet Certified Associate in Cybersecurity credential, its issue date, and its current validity status.
ANNEX A // ADDITIONAL NOTES ON FILE

Supplementary
Qualifications

A few items that support the record above but didn't fit neatly into any single section.

A.1
Tooling Built For Coverage, Not Convenience
Personal automation projects are scoped around comprehensive coverage of a problem space rather than the smallest script that technically works — preferring modular, maintainable architecture over quick one-offs.
A.2
Infrastructure-First Mindset
Security work is treated as inseparable from the infrastructure it runs on — time spent administering real servers and networks directly informs how vulnerabilities are found and understood.
A.3
Continuous Home Lab Iteration
The home lab is not a one-time setup — it's an evolving environment used to trial new network topologies, containerized services, and hardening configurations on an ongoing basis.
A.4
Comfortable With Ambiguity
General IT breadth means unfamiliar systems, undocumented setups, and messy environments are a starting point, not a blocker.
Note: this dossier documents skills and a verified credential — not a live task board. It's reviewed and updated periodically as new work, tooling, or certifications come on file.