Representative Foreword

After the Code, the Structure Remains

The representative foreword of this blog: security now fails less at finding issues than at absorbing, sustaining, and acting on what has already been found.

This essay frames the entire site first. The posts on technical analysis, method, and governance all start from this same problem statement.

After the Code, the Structure Remains

Detection, Method, Governance

🔥 A Mind That Dissects Systems

🔥 Trust and Culture Beyond Technology

🔥 Code That Fixes, Not Just Runs

From a Security Development Spec for Small LLMs to Regression Tests and Fuzzing Validation

This article explains how I split an XSS security development specification for small local models into core/verify/dev/test overlays, and what I learned while connecting LLM-based judgment to regression-test generation and Jazzer/Jazzer.js fuzzing seeds.

June 8, 2026 · 26 min · 5449 words

MCP Is Repeating the History of RPC Security

MCP security risks are not about prompt injection. They stem from the same configuration-to-execution escalation pattern that has plagued RPC, local security software, and CI/CD pipelines for decades.

May 7, 2026 · 5 min · 895 words

Supply Chain Security Does Not End with SBOM: Governing AI Development Tools and Automation Connections

AI IDEs, MCP, and automation connectors are not merely developer convenience tools. They are supply-chain assets that affect the trust path of how code is written, reviewed, and shipped.

May 2, 2026 · 8 min · 1685 words

Security Assessment Becomes a Development Process, Not an Outsourced Event

AI-era security assessment is not primarily about reducing outsourcing cost. It is about embedding repeatable verification into the development process while separating automation candidates from human judgment.

May 1, 2026 · 10 min · 1927 words

Security Diagnostics Reports Die Upon Publication

We point out the limitations of traditional security diagnostic reports and share the necessity and practical application cases of ‘Security Testing as Code’, managing diagnostic results not as ‘documents’ but as ’executable code (PoC)’.

March 17, 2026 · 6 min · 1209 words

Common Security Myths Developers Tell Themselves

Debunking developer security myths around responsibility deflection, tech overconfidence, and risk underestimation with real-world examples.

April 1, 2025 · 3 min · 507 words