Who is behind Sanpu17
An independent technical blog focused on the security architecture of financial systems. We write about what we know from the field — not from vendor marketing decks.
How it started
Sanpu17 began with a simple frustration. Working with DevSecOps teams in financial institutions, every search for deep technical material on the security architecture of trading systems ended in the same place: either a generic article about "the importance of security", or content locked behind the paywall of a consultancy that sells exactly the service it is writing about.
In 2024 I started writing it myself. Not on the assumption that I know everything, but on the belief that there is room for a blog that speaks plainly — with real code, real diagrams and references you can check. No adverts, no sponsors and no sponsored content.
One rule stays fixed: if I write about something, I understand it in depth first. If I cannot explain it with a code example or a diagram, I probably do not understand it well enough to write about it.
What we do — and what we do not
Sanpu17 is a technical blog. We publish articles, guides and reviews on the security architecture of financial infrastructure: trading systems, cryptography infrastructure, identity management and secure communication protocols. Every article goes through a technical accuracy check before publication, and is updated when a standard or a tool changes.
What we do not do: there is no commercial consulting here, no penetration testing services and no investment recommendations. We sell nothing but content — and even that is free. If someone approaches you in the name of Sanpu17 and offers a paid service, it is not us.
Our methodology
Every analysis published on Sanpu17 goes through four stages. Full transparency about the process is a condition for being able to assess how reliable the findings are, which is why the stages are set out here and not on a marketing page.
1. Architecture mapping
The first stage is always mapping. Whether it is a review of the TLS 1.3 protocol or an analysis of an exchange’s clearing system, we start from the overall structure: what the components are, how they communicate, where the boundary between one service and the next runs, and what flows between them. Without a map, any analysis is an educated guess.
In practice that means reading technical documentation, RFCs and protocol specifications. In exchange analyses I rely on public documentation published by SGX — Singapore Exchange, Eurex, CME and others. On security protocols the main sources are IETF RFCs and NIST publications.
2. Threat model
Once there is a map, we build a threat model. Not something formal at the level of a full OWASP Threat Modeling exercise, but a focused analysis: what can go wrong, who might exploit it and what the damage is. The STRIDE model serves as a frame for thinking — Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service and Elevation of Privilege — but not as a rigid checklist.
3. Verification
Every technical finding is verified before publication. If I write that a particular TLS configuration is vulnerable, I test it with openssl s_client, with Wireshark or with a dedicated tool. Automated vulnerability scanners are used only as a first layer of checking, because their false positive rate does not allow relying on them alone.
4. Documentation and conclusions
The last stage is writing. Every article includes the findings, the evidence (code, tool output, screenshots), the recommendations and the order of priority. I separate "must fix now" from "worth improving in the next step" and from "worth considering long term". A report that does not distinguish between levels of urgency is a report that helps nobody.
The operating entity
The site and its content are operated by Sanpu17. Registered address: 1 Raffles Place, #20-01, One Raffles Place, Singapore 048616.
For legal or commercial enquiries: contact@sanpu17.com · +65 3159 1284
Who writes here
Charlotte Lee, founder and editor-in-chief of Sanpu17. A security engineer with more than a decade of experience in DevSecOps and in the architecture of financial systems. Her specialities are service mesh, applied cryptography and trading infrastructure built on event-driven architecture.
The wider writing team is still being set up. As of today, most of the content is written by the editor-in-chief, with informal peer review from specialists in the field. The full detail is on the about the author page.
Updates and changes
- November 2026: Full expansion of the site — six technical guides, a glossary and an author page.
- August 2026: All articles updated with architecture diagrams and visible update dates.
- May 2026: The about page was updated and a detailed methodology section was added.
- March 2026: The site structure was rewritten, with better support for mobile and screen readers.
- January 2025: The blog launched in its first version.
Want to ask something?
Technical questions, corrections and topic suggestions are welcome — e-mail is better than social media, because there the discussion stays tidy and can be linked to.