Build
Create the working environment instead of stopping at theory.
About Shimori Cyber
Cybersecurity, Linux, infrastructure, networking, development, and automation documented through projects and technical writeups.
Kizura / Shimori Cyber
Shimori Cyber is the professional record of my hands-on work across cybersecurity, systems, infrastructure, development, and automation. I use projects and writeups to show the reasoning behind the work rather than only listing tools.
How I Work
The same process applies whether I am working on a Linux service, a network boundary, a website deployment, or a development system.
Create the working environment instead of stopping at theory.
Validate behavior, security, reliability, and assumptions.
Trace failures and understand what the system is actually doing.
Preserve decisions, commands, failures, and useful lessons.
Refine the architecture so the next iteration is stronger.
Proof in Practice
Infrastructure / Security
Trust boundaries, service exposure, credentials, recovery, monitoring, and documentation in a practical Linux environment.
View Case Study →Linux / Systems
A workstation build focused on administration, security, tooling, repeatable configuration, and day-to-day usability.
Read Writeup →Networking / Security
Practical trust boundaries, isolation, firewall thinking, and why network structure matters to security and troubleshooting.
Read Writeup →Background
My professional background includes communications and IT work with the Canadian Armed Forces, along with independent Linux administration, networking, infrastructure, technical troubleshooting, and software development.
That experience shaped how I approach cybersecurity. Security is connected to users, services, networks, software, operations, and recovery. Understanding those relationships is more useful than treating security as an isolated layer.
Shimori Cyber is where I continue building that capability in public through practical work, technical documentation, and case studies that can be inspected rather than simply claimed.
Next
Projects show the implementation. Writeups preserve the reasoning, failures, and lessons learned.