trynton@houston:~
Recruiter overview
CybersecurityAnalyst
SecurityAutomation
AIDevelopment

Hi, I'm trynton.johnson

Cybersecurity Analyst / Security Automation / AI Development

I've spent 4+ years in 24x7 security operations and I'm currently working on contract. Most days I'm reading Falcon detections, following suspicious sign-ins through Entra ID, and connecting the evidence in Splunk and Sentinel. I bring that same curiosity into what I build, exploring AI, automation, and new ways to solve problems. Thanks for stopping by.

From signal to evidence

  1. Every alert starts as noise.
  2. Endpoint, identity and network telemetry, correlated until it agrees.
  3. What's left is evidence that I can act on.
Security operations

Four years reading evidence in 24x7 security operations

Three security operations centres, from multi-tenant monitoring at a cybersecurity technology company to contract investigations for an energy and utilities company today. This is the work, in the order I do it.

Reading process trees, command lines, file and registry activity; coordinating malware remediation and validating removal.

  • CrowdStrike Falcon
  • Defender for Endpoint

All three roles

Where I’ve done it

    • Investigate CrowdStrike Falcon detections by reviewing process trees, command lines, file and registry activity; correlate endpoint evidence with Splunk ES and Sentinel to assess scope and escalate confirmed threats.
    • Conduct targeted threat hunts across Falcon and SIEM telemetry for suspicious processes, credential abuse and lateral movement, pivoting on hosts, accounts, IP addresses and indicators.
    • Coordinate endpoint malware remediation with response teams, validate removal of suspicious files and registry entries, review follow-up scans, and document actions in ServiceNow.
    • Investigate phishing and suspicious sign-ins using Proofpoint, Entra ID and Microsoft Defender, corroborating user context and authentication evidence before escalation or closure.
    • Review firewall and WAF activity alongside endpoint and identity logs to assess web requests, malicious IP indicators and downstream activity; summarise findings for shift handoff.
    • Analyse failed authentication and credential-scanning patterns across multiple accounts, correlating Falcon detections with identity logs to assess source activity and escalation needs.

Tools, and where I used them

ToolAreaWhere
Splunk Enterprise SecuritySIEMCurrent and previous role
Microsoft Sentinel and KQLSIEMCurrent role
QRadarSIEMPrevious roles
CrowdStrike FalconEndpointAll three roles
Microsoft Defender for EndpointEndpointCurrent role
Entra IDIdentityCurrent role
ProofpointEmailCurrent role
Microsoft PurviewInsider riskCurrent role
ServiceNowCase managementCurrent role
Wireshark and NetFlowNetworkPrevious role
Nessus and TenableVulnerabilityPrevious role
WazuhSIEM (home lab)Home lab: Ubuntu server; Windows, Ubuntu and Kali agents
Investigative thinking

Work the case from alert to disposition

Real investigations stay confidential, so this one is simulated: an identity case in seven stages. Move through it, select any line of evidence to see why it matters, and make the final call yourself.

SIM-0421Suspicious authentication activitySimulated dataStage 1 of 7

Unfamiliar sign-in after repeated failures

AlertSimulated
Alert
Unfamiliar sign-in properties following failed attempts
Source
Microsoft Sentinel analytics rule
Severity
Medium
Account
d.reyes@corp.example
IP address
203.0.113.77
Location
NL (user's history: US only)
First event
2026-10-21 08:41:03 UTC
Tactics
Credential Access, Initial Access

Simulated investigation written for this site. Every account, host and result is synthetic; IP addresses come from documentation ranges. It is not an employer incident.

08:47 · Alert received
Microsoft Sentinel, KQL

How I spot a password spray

Line 1 of 6

Entra ID sign-ins, as Sentinel stores them.

Engineering and automation

Automation built like a security control

I write Python, TypeScript and workflow automation, and I build AI agents. The rules come from the day job, so the systems stay explainable and safe to run unattended.

  1. Least access

    Every service gets only what its job needs. The assistant has no network; the dashboard can't read credentials.

  2. A human decides

    Models draft and summarise. Submitting, booking or changing settings waits for my approval.

  3. Everything recorded

    Actions and refusals go into an append-only, hash-chained log, so tampering breaks the chain.

Inside the agent platform

The architecture as deployed. Select a component to see what it can and cannot reach.

Assistant

Answers questions about the platform's data. It runs with no network access and can only ask the tools service for data.

Can
Call read-only tools
Cannot
Reach the internet or see contact details
Selected work

Things I built and what they prove

What I build on my own time, alongside the day job. Each one states the problem, my role, the stack and where it stands today. Open any one for the architecture, the decisions and real screenshots.

  1. AI and automationRunning on a private server

    Approval-Gated Agent Platform

    A self-hosted automation platform built like a security control: least-privilege services, human approval, a hash-chained audit log, and an AI assistant with no network access. Its workload is my own job search.

    Role
    Sole designer, developer and operator.
    Stack
    Python, SQLite, Playwright (real Chrome), Flask, systemd timers, Anthropic API, OpenAI API
  2. SecurityBuilt

    Wazuh Detection Lab

    A home SOC lab: a Wazuh server on Ubuntu with agents on Windows, Ubuntu and Kali Linux, used to attack a monitored Windows host and watch the activity land in the SIEM.

    Role
    Built and ran the lab: the Wazuh server, the agents, and the attacks.
    Stack
    Wazuh, Ubuntu, Windows, Kali Linux
  3. SecurityWorking prototype

    Aegis

    An AI-security learning platform: prompt injection, tool poisoning and MCP risk, with labs where you attack and then detect.

    Role
    Designer and developer.
    Stack
    Next.js, TypeScript, Vitest, Expo (mobile, in progress)
Trynton Johnson
About

Analyst first, builder after

I started in security operations in 2021 at a cybersecurity technology company, monitoring security events for 500+ users across client tenants. At an IT and security services firm I investigated Falcon alerts in a 24x7 SOC and followed indicators from the endpoint into Splunk, NetFlow and packet captures. Today I work on contract, investigating endpoint, identity, email and network activity across Falcon, Splunk ES and Sentinel.

Outside work I build AI agents and automation, with the same rules as the day job. Least access, a human approving anything that matters, and a record of what happened.

What drew me to cybersecurity was the challenge of understanding how systems work, spotting what doesn’t belong, and figuring out why something happened. I enjoy the investigative side: analysing information, connecting the dots, and making decisions based on evidence rather than assumptions.

What keeps me in it is that there’s always something new to learn. Threats evolve, technology changes, and there’s always room to sharpen my skills. Over time my interest has grown beyond responding to alerts. I want to understand threats more deeply, improve detection, build automation, and find better ways to protect environments.

Now
Contract SOC Analyst, energy and utilities company
Experience
4+ years, three SOCs, currently contracting
Certified
CompTIA Security+ (CE)
In progress
CompTIA CySA+
Education
Prince George's Community College, general studies coursework
Based
Houston, Texas

Beyond the screen

Outside of cybersecurity, I enjoy going for runs, keeping up with crypto markets, grabbing a good coffee, and winding down with my girlfriend and our cat over a good movie or series. I’m always curious about what’s next, but I appreciate the simple things too.

  • Running
  • Crypto markets
  • Good coffee
  • Movies and series
Connect

Hiring for security operations, detection or automation?

OverviewSkills, experience and projects →Full résumé available on request.