Draft - pending legal review
Vulnerability disclosure policy
Vulnerability disclosure policy
Terabyte Network welcomes reports of security vulnerabilities in the platform at terabytenetwork.co.ke. This policy says how to report a vulnerability and what you can expect from us. It is published at `/legal/vulnerability-disclosure/` and referenced from `/.well-known/security.txt` (RFC 9116).
How to report
Email security@terabytenetwork.co.ke. Include:
- the affected URL or component;
- the steps to reproduce the problem;
- what an attacker could achieve;
- your contact details, if you want a reply.
Do not include real personal data in the report. If you came across any, tell us what kind of data it was but not the data itself.
What we ask of you
- Test only against your own account or a demo account. Never access, change or delete data belonging to another ISP or its subscribers.
- Stop and report as soon as you have shown the problem. Do not keep or share data you came across.
- Do not run denial-of-service tests, spam, social engineering, physical attacks, or tests against routers, RADIUS servers or other network equipment.
- Do not use automated scanners that send large volumes of requests.
- Give us a reasonable time to fix the problem before you disclose it publicly. We suggest 90 days.
What we will do
- Acknowledge your report within 3 business days.
- Give you an initial assessment within 10 business days, and keep you informed until the problem is fixed.
- Credit you when the fix is published, if you want credit.
- Not take legal action against you, or ask others to, for research done in good faith within this policy. This includes research that might otherwise be treated as unauthorised access under the Computer Misuse and Cybercrimes Act, 2018, as far as we are able to give that assurance.
Out of scope
- Reports from automated tools without a working proof of concept.
- Missing security headers that have no demonstrated impact.
- Clickjacking on pages without sensitive actions.
- Self-XSS.
- Rate limits on non-sensitive pages.
- Software versions without a demonstrated vulnerability.
We do not currently run a paid bug bounty.
Status
This is a draft pending legal review, version 0.1-draft, effective 16 November 2026.