Security
How we protect accounts and money
Our products hold people's identities and move their money. This page says what we do about that, and how to tell us if you find something wrong.
Reporting a vulnerability
If you believe you have found a security problem in any Aftian product or service, please write to security@aftian.org before disclosing it anywhere else.
What to include
- · Which product or hostname is affected
- · What the problem is, and what it would let someone do
- · The steps to reproduce it
- · Anything that helps us confirm it — a request, a response, a screenshot
What we will do
- · Acknowledge your report, and tell you whether we can reproduce it
- · Keep you informed while we fix it
- · Credit you when it is fixed, if you would like that
- · Not pursue you for a report made in good faith under the terms below
What we ask of you
- Use your own account. Do not access, modify or download data belonging to anyone else. If you prove a problem with one account, stop there — you do not need a second to make the point.
- Do not degrade the service. No load testing, no denial of service, no spam to real users. These are live systems people depend on to be paid.
- Give us time. Let us fix it before you publish. We will not ask you to stay quiet indefinitely.
- No social engineering. Attacks on our staff, our suppliers or anyone's physical security are out of scope.
We do not run a paid bug bounty. We do read every report, and we respond.
What we do on our side
One place holds credentials
No product of ours stores a password or issues a token. Sign-in happens at a single identity service, so there is one system to secure rather than four, and revoking a session revokes it everywhere at once.
Databases are not on the internet
Our databases publish no public port. They are reachable only from the private network the services share. The only things exposed to the internet are the HTTPS front door and an administrative SSH port.
Everything is encrypted in transit
All traffic to and from our services is over HTTPS, with certificates renewed automatically.
We never hold a mobile-money PIN
Payment approval happens with MTN or Orange, on your own handset. A PIN is never entered into our software and never reaches our systems.
Service credentials are proved, not assumed
Every key between two of our services is verified with a real request and a deliberately wrong one. A key that matches on both sides proves nothing; a refusal for the wrong key does.
Misconfiguration refuses rather than permits
A service that is missing a secret it needs returns an error instead of accepting anything. An unset webhook secret would otherwise turn an endpoint into an open door, so it is treated as a hard failure at startup.
No system is beyond compromise, and we do not claim otherwise. If data we hold is ever exposed, we will tell the people affected rather than wait to be asked.