Charlotte Lee

Founder and editor-in-chief of Sanpu17. A security engineer with more than a decade of experience working with development, infrastructure and security teams in financial institutions.

Who I am

My name is Charlotte Lee, and I write Sanpu17. I am a security engineer with more than a decade of experience working with development, infrastructure and security teams in financial institutions — from the side of someone who has to design the architecture and also be on call when it falls over.

Most of my working years have gone into the same kind of problem: a system that looks fine on the diagram, but where something at the seam between two services is not encrypted, not authenticated or not documented. Those problems cannot be found with a vulnerability scanner, and most commercial tools do not look for them at all.

That is why I write about architecture and not about "ten tips": about what breaks between components, about what happens when a certificate expires on a Saturday, and about the decisions that determine whether the system still holds up in its third year.

Areas of expertise

  • Service identity and mTLS — issuing, rotating and enforcing certificates in a multi-service environment, including service mesh and Vault PKI.
  • Applied cryptography — key management, HSMs, KEK/DEK, and a staged move to post-quantum encryption.
  • Event-driven architecture — Kafka and Flink in the data pipeline of trading systems, with an emphasis on consistency and recovery.
  • API security — authorisation models, BOLA, OAuth 2.1 and the FAPI profiles in payment infrastructure.
  • Practical regulation — how requirements from PCI DSS, the MAS Technology Risk Management Guidelines and DORA become controls you can maintain.

How I write

  1. I choose a topic that has practical value. Not "what is Zero Trust" but "how to rotate certificates without downtime".
  2. I read the source. RFCs, NIST specifications, the official documentation of the tools — not posts that summarise them.
  3. I test it in the lab. Every configuration and every code snippet in an article has been run in a test environment. If something did not work, that goes into the article too.
  4. Someone reviews it critically. Before publication, a specialist in the field reads the draft and looks for technical errors and unsupported assumptions.
  5. I update it. Every article carries an update date. When a standard changes or a tool changes, the article is updated — it does not stay "correct as of 2024".
Corrections policy

Found a mistake? Write to me and I will fix it, with a note of the correction at the bottom of the article. I would rather make a precise correction than a general apology.

What I do not do

  • I do not give investment advice, analyse shares or recommend investment channels.
  • I do not perform penetration tests, provide SOC services or sell consulting hours.
  • I do not write sponsored content for security vendors, and I do not take payment for mentioning a product.
  • I do not give legal opinions — that needs a lawyer, not a technical blog.

If one of these is what you are looking for, there are good people in the market who do exactly that. This blog is meant to help you understand your own system, not to replace a professional.

Contact

Technical questions, topic suggestions and corrections — all are welcome. I usually reply within three business days.

Write to me Go to the contact page