01
Turning security evidence collection into a repeatable workflow
A PowerShell-based system transformed a multi-hour, ten-step evidence-gathering process into an on-demand workflow.
Signal~80 servers · hours → ~20 minutes
AI-native IT operations · systems · identity
I make complicated systems feel calm.
I design calmer identity, endpoint, SaaS, and security operations for growing teams—using thoughtful automation, clear documentation, and AI-assisted tools where they genuinely help.
Requestnew.hire@company.com → Okta · Slack · GitHub
- Identity verified (SSO)pass
- Phishing-resistant MFApass
- Device Trust · managed + compliantpass
- Least-privilege role (RBAC)pass
- Lifecycle sync (SCIM)pass
✓ Access allowedlogged · reviewable
What I do
Four capabilities, one calm system.
The same pattern across all of them: understand the real workflow, secure it by default, automate the repeatable parts, and document the rest.
Identity & access
Okta, SAML/OIDC/SCIM, MFA, Device Trust, RBAC, Entra ID and Active Directory.
Useful automation
PowerShell, Python, Bash, REST APIs, Okta Workflows, n8n and GitLab CI/CD.
Endpoint, SaaS & cloud
Kandji, Jamf, macOS, Google Workspace, Microsoft 365, AWS WorkSpaces, GCP.
Operations & response
Incident response, SLA management, root cause analysis, ITIL and PagerDuty.
Selected work
Systems with a before and an after.
02
An incident workflow that assembled the right context automatically
Slack, Okta Workflows, Zapier, and Notion worked together to reduce coordination and documentation overhead during defined incident scenarios.
SignalNotifications + docs + team assembly
03
Making secure access feel more like self-service
Okta Device Trust, Kandji, and access-request workflows created a more secure and understandable path to employee access.
Signal2,000+ employees and endpoints
The operating pattern
Find the friction. Make the path obvious.
My best work sits where people, security, and systems meet. I look for repeated effort, unclear ownership, and brittle handoffs—then turn them into understandable, reusable operations.
- 01Listen to the work
Map the real process, including the awkward exceptions.
- 02Design for trust
Secure defaults, visible decisions, and a human fallback.
- 03Leave a trail
Documentation and observability are part of the system.
Field notes
Things I’m learning out loud.
Why this site is a playground, not a finished monument
A portfolio can show polished outcomes and still expose the learning process that made them possible.
Read note →The runbook is part of the system
If an automation only works when its author is present, the automation is still carrying hidden manual work.
Read note →Now
This portfolio is part résumé, part lab notebook.
CURRENT EXPERIMENT
Building kellray.com as a public résumé, a writing practice, and a safe place to test the tools I’m learning.
Open the build note →