The interesting detail.
A permission check. An unexpected response. A workflow that behaves differently across users. Small details can reveal the larger issue.
SECURITY RESEARCH / ASWSEC
Penetration tester.
Security researcher.
I investigate how applications and systems behave when their assumptions are challenged. Here, I share the security research I pursue after hours.
Understand the system.
Question the assumptions.
Follow the evidence.
A selection of public work.
Open to exploration.
01 / The person behind the work
I’m a penetration tester and security researcher. I’m drawn to the places where software behaves differently from what its designers intended.
My work brings together hands-on testing, vulnerability research, and coordinated disclosure. I look closely at access controls, application logic, and the trust decisions that connect one part of a system to another.
ASWSEC brings together the research, disclosures, recognition, and community contributions I can share publicly. This is one part of my experience and capabilities.
A permission check. An unexpected response. A workflow that behaves differently across users. Small details can reveal the larger issue.
I care about reproducible behavior, the conditions that make a weakness possible, and the impact that follows.
A finding becomes more valuable when someone else can understand it, reproduce it, and use it to make a system stronger.
02 / Areas of expertise
Selected technical and research practices reflected in the work shared here.
I investigate authentication, authorization, and the application logic behind everyday workflows. The interesting questions often start with who can do what—and what happens when those boundaries are challenged.
03 / How I think
I’m interested in how one condition leads to another: an entry point, a trust decision, an unintended path, and a consequence.
Trace how an authorization gap can expose another user’s data.
HOW I COMMUNICATE A FINDING
The path from an observation to a useful explanation: behavior, evidence, impact, and remediation.
04 / Selected research
Selected vendor advisories that acknowledge research I pursue after hours. These public examples represent part of my experience; each links to its original publication.
Security vulnerability · Critical Patch Update
Stored cross-site scripting
Stored cross-site scripting · SECURITY-1253
Cross-site scripting
76 linked references, organized by vendor and publication.
Research acknowledgments reflect individual contributions to responsible disclosure.
05 / Selected public milestones
Selected milestones from the research and community contributions shared on this site.
Published disclosures in the ASWSEC archive document research shared with the wider security community.
Recognition through the DC3 Vulnerability Disclosure Program.
View the recognitionCVE-2023-21909, one of the research references in a collection spanning 26 Oracle Critical Patch Updates.
Read the advisoryRanked #108 on the Microsoft Security Researcher Leaderboard for Quarter 3, 2023.
The public record includes CVE-2024-25693 and the corresponding Portal for ArcGIS security update.
Read the security update06 / Recognition & industry involvement
Research is also a community. Recognition, conversations, and contributions connect my work to a much wider group of people.
FEATURED IN
Part of the published collection of perspectives from the offensive security community.
View the bookFEDERAL HACKING PROGRAMS
07 / Elsewhere on the web
Public profiles, code, research, and conversations across the security community.