I found this "blog post masquerading as a white paper" quite insightful. I would recommend to start reading at "2. HOW CAN WE MAKE PROGRESS?". The way the auth

I found this "blog post masquerading as a white paper" quite insightful. I would recommend to start reading at "2. HOW CAN WE MAKE PROGRESS?". The way the authors breaks security down into a "hierarchy" of 3 different strategies to remove vulnerabilities from large, complex systems was particularly insightful. And also highlighting the different "distractions" that people chase down. As a developer, I have definitely chased the "distractions" mentioned. As a security engineer, it's helpful to have the frame of reference the author pitches in the article. This was linked from this[0] post the other day and I felt it deserves it's own post on HN. :) Bonus Points: If anybody has any additional papers/posts to continue chasing down this style of writing code via dataflows and by partitioning code along "trust boundaries", I would really appreciate it! [0]: https://tailscale.com/blog/modules-monoliths-and-microservices/ https://tailscale.com/blog/modules-monoliths-and-microservic...