Ryan Bailey Reasons
Cybersecurity & Infrastructure
For more than 14 years, troubleshooting complicated systems has been a normal part of my work.
I started in industrial maintenance, controls, and mechatronics, where downtime mattered and guessing could get expensive fast. Now I bring that same mindset into networking and cybersecurity: understand what is actually happening, isolate the problem, make the change, and prove it worked.
This site is where I document that process, including the parts that did not work the first time.
Featured Projects
Controlled Uncontrolled Network: Full Segmentation & Remediation
I am rebuilding my live homelab as if I had inherited somebody else's network. It started with old 10.1.x.x dependencies, broad access, temporary fixes, and enough accumulated technical debt that the environment was becoming harder to explain. The rebuild moves it toward clearer trust boundaries, dual-stack IPv6, application-level access through Nginx, and NetBox as the documented source of truth.
Project Coming Soon
Additional infrastructure and security projects are being documented and will be published here once there is enough evidence behind them.
Project Coming Soon
Additional infrastructure and security projects are being documented and will be published here once there is enough evidence behind them.
Latest Writing
RyanReasons.com Security Validation
I tested my own portfolio from the public Internet and from inside the lab, rejected evidence I could not defend, remediated what I found, and left one result inconclusive.
Firewall Policy Validation
A firewall rule can look completely correct in the management interface and still not prove what the network is actually doing. I started treating configuration as intent and traffic, listener state, counters, and packet captures as the evidence.
IPv6 Security in Dual-Stack Networks
IPv6 is not just IPv4 with longer addresses. Once a network becomes dual-stack, addressing, router discovery, firewall policy, monitoring, DNS behavior, and validation all have another path that needs to be understood and tested.
Currently Working On
I'm still working through validation on the network rebuild and documenting what I find as I go.
More infrastructure and security projects will get added once there is enough real evidence behind them to be worth publishing.
From Industrial Systems to Cybersecurity
Troubleshooting complicated systems is nothing new to me. For more than 14 years, my previous career centered on operational technology, industrial control systems, mechatronics, and machinery in high-uptime facilities across Tennessee, Mississippi, and Georgia.
That meant working across hardware, software, high- and low-voltage electrical systems, controls, and component-level failures. A large part of the job was root cause analysis: taking a symptom that might be vague or incomplete, tracing it through the system, isolating variables, and getting to the actual failure without making the situation worse.
When equipment is down and every minute costs money, there is not much room for panic or sloppy communication. You have to explain what is wrong, what you know, what you still need to test, and what you are doing about it. Then document the failure and the corrective action well enough that someone else can understand it later.
Those habits transferred into networking and cybersecurity almost perfectly. Packets, services, routes, firewall rules, hosts, and logs may be different from industrial equipment, but the troubleshooting process feels very familiar: trace the problem, isolate the variables, verify the fix, and document what actually happened.
Core Areas of Focus
- Network Architecture & Segmentation
- Dual-Stack IPv6 Deployment
- Application Access Boundaries & Nginx
- NetBox IPAM & DCIM Automation
- Security Testing & Packet Tracing