{{ c.title }}
{{ c.what }}
{{ c.did }}
CompTIA Security+ · AI & Detection
I am a Cybersecurity major who builds with AI as well as defends against it. I trained a phishing detector on more than 80,000 emails, my Azure honeypot logged over 10,000 brute force attempts in 24 hours, and I placed 2nd in the Zscaler Capture the Flag beta. CompTIA Security+ certified, 3.9+ GPA at Southeast Missouri State University.
I am a Cybersecurity major with a strong interest in artificial intelligence, and I look for creative ways to bring the two together. That interest shows up in what I build. The phishing email detector on this page was trained on a dataset of more than 80,000 emails, and I rebuilt a web scraping agent around a locally hosted Llama 3.2 model to understand how these systems work from the inside.
My view of security is that you have to stay a step ahead of your adversaries, which means thinking about how someone might attack you before they try. AI is changing that landscape quickly, and it works in both directions. Attackers are already using it, so defenders need to understand it just as well.
That is why I spend time on both sides of it: attacking models in a vendor cyber range, training my own, and teaching other people how to use AI tools without putting company data at risk.
With a short note on where each one comes from
Enterprise IT and university IT support
OneHope is a global nonprofit with staff and partners in more than 100 countries, so its data is spread across many regions and regulations. I spent the internship on the governance side of that problem: deciding how sensitive data should be labeled, monitored, and retained inside Microsoft 365.
Front line support for students, faculty, and staff. A lot of good security habits come from this job: verifying who is asking before you help them, documenting what you changed, and following policy even when a shortcut would be faster.
Vendor run cyber ranges, scored against other participants
{{ c.what }}
{{ c.did }}
Home lab and university lab, all hands on keyboard
A honeypot is a deliberately exposed machine that has no legitimate users, so every login attempt against it is hostile by definition. I stood one up on Azure, opened it to the internet, and configured firewall rules and logging so I could study who came knocking.
Within 24 hours it recorded more than 10,000 failed brute force login attempts. I forwarded the security event logs into a workbook, geolocated the source addresses, and built the map shown here so the traffic could be read at a glance instead of line by line.
What surprised me most was the concentration. A handful of very persistent sources accounted for the bulk of the traffic, with the top one alone responsible for 12.1 thousand attempts, and the busiest cluster sat in the United States rather than overseas.
This work is done on physical Cisco routers and switches rather than in a simulator. I cable the pods, configure them over a serial console, assign addressing across separate subnets, bring the interfaces up, and confirm the result with show commands.
Covered so far: DHCP, TCP/IP addressing, static routing, subnetting, VLAN switching, and console recovery on a device I managed to lock myself out of. Once you know how traffic is supposed to move through a network, odd entries in a log stand out much faster.
Documents get shared far more often than anyone reviews them line by line, and a single invoice or intake form can carry a social security number or a full card number. I built an application that reads a PDF, finds sensitive information inside it, and redacts it before the file goes anywhere.
It looks for personally identifiable information such as names, addresses, phone numbers, email addresses, and social security numbers, along with payment data like credit card numbers. Structured values are matched by pattern and validated, while names and addresses need context, since a nine digit number is only a social security number depending on where it sits in the document.
One detail I made sure to get right is that the redaction removes the underlying text rather than drawing a black box over it. Plenty of published documents have leaked because someone covered the text visually and left it selectable underneath. This project came out of the data governance work I did at OneHope, where classifying sensitive data is the first step before you can protect it.
Phishing is still one of the most common ways an attacker gets in, and no team has time to read every suspicious message by hand. I trained a supervised machine learning classifier on a labeled set of roughly 80,000 legitimate and phishing emails so the obvious cases get sorted automatically.
The pipeline cleans and tokenizes each message, converts the text into numerical features, then scores it as phishing or legitimate. The lesson I took from it was about false positives. If a filter quarantines real business mail, people stop trusting it and turn it off, so I tuned the model toward precision instead of chasing the highest overall accuracy.
It pairs well with the honeypot project. The honeypot showed me how automated attacks behave at the network level, and this one gave me a look at how they arrive in someone's inbox.
I took apart a web scraping AI application to understand how it worked, then rebuilt and ran it myself. It takes a URL and a plain English instruction, fetches the page, and uses Llama 3.2 running locally to pull out only the information you asked for. Because the model runs on my own machine, none of the scraped content leaves it.
I learned far more from this than I expected, and honestly I was surprised how straightforward an AI powered scraper is to put together. It also showed me a real risk from the defensive side, since an agent that reads untrusted web pages can be fed instructions by those pages. That is the same prompt injection problem I worked on in the Cisco AI Defense range. I am using what I learned here as the starting point for a larger project.
Bachelor of Science in Cybersecurity at Southeast Missouri State University in Cape Girardeau, MO. GPA 3.9 or higher, degree conferred December 2027. Each credential below is verifiable and dated.
Every tool here is one I have used hands on
{{ goal.body }}