API security in payment infrastructure: BOLA, OAuth 2.1 and FAPI 2.0
What an authorisation model that holds up looks like, why mTLS identifies a client and not a user, and what the FAPI 2.0 profile adds on top of plain OAuth.
Six technical guides on financial infrastructure security. Each one comes with diagrams, code and update dates — and filtering by topic will come later.
What an authorisation model that holds up looks like, why mTLS identifies a client and not a user, and what the FAPI 2.0 profile adds on top of plain OAuth.
From etcd encryption to rotating secrets without a redeploy: three approaches, how they differ, and what stays open in each of them.
FIPS 203/204/205, a cryptographic inventory, hybrid key exchange in TLS 1.3, and a migration plan in four stages.
From mTLS to enforcing authorisation with OPA, including what actually breaks, and what a 90-day implementation plan looks like.
The order path against the data pipeline, FIX against SBE, and the places where event-driven architecture breaks.
FIPS 140-3 levels, PKCS#11, the KEK/DEK hierarchy and the practical difference between CloudHSM and a physical HSM.
If the terminology in the articles looks unfamiliar, start with the Glossary — 30 short definitions, each with a link to deeper reading. If you want the wider picture, the What we cover page explains what each kind of content gives you and who it suits.
A new article appears roughly every two months. There is no newsletter and there is no sign-up — you can come back here, or follow the sitemap.