Technical blog · Financial infrastructure security

Security architecture for financial systems

In-depth analysis of code, protocols and architecture in financial infrastructure: trading systems, payments, cryptography and key management. Written for developers, architects and security teams — not investment advice, and not a consulting service.

This site is operated by Sanpu17 · Registered address: 1 Raffles Place, #20-01, One Raffles Place, Singapore 048616 · Privacy policy

Illustration of a server network lit in green tones

Latest from the blog

All articles →

Three areas, clear boundaries

What we cover →
Architecture

Security architecture analysis

Analysis from protocol level down to infrastructure level, grounded in open NIST and OWASP standards, with code and diagrams you can check.

Trading infrastructure

Trading infrastructure reviews

How matching and clearing systems are built, how FIX differs from a binary data feed, and where the bottleneck actually appears.

Cryptography

Practical cryptography guides

Encryption, key management, HSMs and TLS — guides that describe what works in production, including what broke along the way.

How we approach an analysis

Every article goes through the same four steps, and the transparency of the process is part of its credibility. If a finding has not been verified, it does not get published.

1. Architectural mapping

Before you test a specific weakness, you need a map: who talks to whom, where each service’s boundary ends, and how data flows between them.

2. Threat modelling

What can change for the worse, who benefits from it, and what the damage would be. STRIDE serves as a thinking framework, not a checklist you tick off.

3. Verification and documentation

Every finding is tested in a lab environment — with openssl s_client, with Wireshark or with a dedicated tool — and documented with the output.

6technical guides
30glossary terms
2024launch year

Featured articles

All articles →

Frequently asked questions

Is Zero Trust really different from what we did before?

The idea itself dates back to at least 2004, when the Jericho Forum talked about de-perimeterisation. What has changed is the maturity of the tooling: automated mTLS, service mesh and policy engines such as OPA make the model practical even for a team of five.

Do you need an HSM to comply with PCI DSS?

The standard requires protection of keys, not a specific product. In practice, storing keys without hardware isolation struggles to pass an audit — which is why most organisations end up with an HSM or a KMS service backed by a certified module. The article on HSMs walks through the trade-offs.

How do you choose between Istio and Linkerd?

By team size, not by feature list. Linkerd gives you transparent mTLS with a small install; Istio suits an organisation with a platform team that wants a rich policy engine. If nobody is around to maintain the control plane, the simpler option is the one that survives.

Do you provide consulting, penetration testing or SOC services?

No. The blog publishes technical content only and does not sell services. If someone contacted you in the name of Sanpu17 offering a paid service, it was not us.

Who writes the content?

The content is written by Charlotte Lee, founder and editor of Sanpu17, with technical review by subject-matter experts before publication. Full details are on the About the author page.

Glossary

Thirty terms every financial infrastructure security team runs into — short definitions in plain English and a link to go deeper. Useful when you need to know quickly what a CBOM or a BOLA is.

Browse the glossary →

Who writes the blog

Charlotte Lee, a security engineer with more than a decade of experience in DevSecOps and financial systems architecture. The page sets out what she covers, and what she does not.

About the author →