Security and reliability
Built to the standard of the money it moves.
A broker's platform holds identities, balances and collateral. These are the protections every brokerage on LSNEP gets from the first day of its pilot. We describe what we do, not certificates we do not hold.
Sign-in code
482 913
- 09:58:12Staff sign-in, 2FA passedbranch-02
- 10:04:37Client limit changedrisk-desk
- 10:05:02Payout approved, second checkaccounts
- 10:11:48Sign-in blocked, wrong codeunknown
Defence in layers
Four layers, each with its own controls
Clients and staff
- Two-factor sign-in
- Roles per branch and desk
- Session limits
Application
- Audit log on every change
- Input validation
- Rate limits on sign-in
Data
- One data store per brokerage
- Encrypted in transit
- Daily backups
Operations
- Uptime monitoring
- Security test before go-live
- Incident process
Separation
Your clients' data never sits beside another broker's.
- Separate data store per brokerage
- Traffic encrypted in transit with modern TLS
- Backups taken daily and tested by restoring them
- Client data stays under your control when you leave: full export, then deletion on request
No shared tables. No cross-firm queries.
Access
Everyone sees exactly what their job needs
Roles are set per brokerage and can be adjusted to how your firm works. These are the defaults.
| Role | Can | Cannot |
|---|---|---|
| Branch staff | Open accounts and answer clients of their own branch | See other branches or change fees |
| Risk desk | Set margin limits, haircuts and send margin calls | Edit client KYC records |
| Compliance | Read every record and the full audit log, export reports | Change balances or limits |
| Client | See their own portfolio, ledger and statements | See anything belonging to another client |
Every sign-in for staff uses two factors. Clients can turn on two-factor sign-in in the app, and brokers can require it.
Audit trail
Who did what, and when, for every record
Every change to a client record, a balance, a limit or a fee is written to an audit log that staff cannot edit. Compliance can filter it by client, user or date and export it for SEBON, NEPSE or your auditor.
Audit log
Sample data- 10:42:08risk.deskMargin limit, client 041255% → 50%
- 10:31:55branch.pokharaKYC approved, client 1187NID verified
- 09:58:12complianceExported ledger reportOctober
Reliability
Watched around the clock, tested before launch
Monitoring
Security test before go-live
Incident process
Independent of your trading system
Ask us the hard security questions.
Bring your IT head to the demo. We walk through data separation, access roles, backups and incident handling in detail.