Building a trading or exchange platform: security requirements to write down first
Discuss selected web-security requirements for trading products without mistaking them for a complete custody, settlement or regulatory checklist.
Platforms that hold money or assets raise the stakes of ordinary security mistakes. This article does not describe how to build an exchange or promise any outcome. It lists web and API security requirements, taken from OWASP pages we read, that a client should put in writing before development starts. Each one links to a longer article of ours.
Requirements from sources we read
| Area | What OWASP says (summary) | Our article |
|---|---|---|
| Password storage | Prefer Argon2id; use supported alternatives only for their applicable constraints, with a unique salt and benchmarked settings; never plain text | Password storage |
| Sessions | Random, meaningless session IDs; renew at login; server-enforced idle and absolute timeouts; reauthenticate after risky events such as password change or new device | Session management |
| Input | Validate on the server by allowlist; limit size before parsing; do not rely on client checks | Input validation |
| Resource limits | Rate limits, page-size limits, throttling of sensitive operations and spending limits for paid providers | API rate limits |
| Logging | Log authentication, authorization and high-risk actions such as admin use and data export; keep passwords, tokens and card data out of logs; guard against log injection | Application logging |
| Confirming money-moving actions | OWASP's transaction authorization sheet: show the user the significant data (such as target account and amount), make confirmation different from sign-in, enforce everything server-side, make each authorization single-use and time-limited, control the order of steps and check authorization again just before execution | Transaction authorization |
| Extra sign-in factors | MFA recommended for all users and required for privileged ones (OWASP MFA sheet); do not rely on SMS where there is financial risk (OWASP says NIST classes it as restricted) | MFA options compared |
| Automated login attacks | Layered defences against credential stuffing and password spraying, with MFA first | Credential stuffing defenses |
These are selected generic web-security topics, not a sufficient or complete exchange launch checklist. Custody, settlement, reconciliation, market integrity, financial controls and applicable law need separate specialist work before a real-money product is built or marketed. OWASP's own wording on session timeouts, for example, ties values to how critical the application and its data are, so the right numbers need a risk decision.
What this article does not cover
- Matching engine, speed and liquidity. Performance and liquidity depend on design and on the market, not on a template. We found no primary source for this article and make no claims. Anyone selling "fast, liquid, secure" without test results has given you no evidence.
- Custody and key management. Not researched.
- Regulation. Trading, exchange, remittance and crowdfunding products are regulated in many places. We have not researched Indian or other rules. Take advice from qualified counsel on licensing before building, marketing or accepting funds.
Questions to ask a vendor
- Which of the requirements above are implemented, and how was each tested?
- What independent security testing has been done, and can we see the report?
- What load and failure testing has been done, and under what conditions?
- Which legal and licensing work is the client responsible for?
Limits
Partial and generic. This is not a security audit or a legal guide, and it says nothing about the safety of any named product.
By Omnistu.
Sources
- https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html
- https://cheatsheetseries.owasp.org/cheatsheets/Session_Management_Cheat_Sheet.html
- https://cheatsheetseries.owasp.org/cheatsheets/Input_Validation_Cheat_Sheet.html
- https://owasp.org/API-Security/editions/2023/en/0xa4-unrestricted-resource-consumption/
- https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html
- https://cheatsheetseries.owasp.org/cheatsheets/Transaction_Authorization_Cheat_Sheet.html
- https://cheatsheetseries.owasp.org/cheatsheets/Multifactor_Authentication_Cheat_Sheet.html
- https://cheatsheetseries.owasp.org/cheatsheets/Credential_Stuffing_Prevention_Cheat_Sheet.html