Security
Found a vulnerability?Tell us first.
We take reports seriously and we read every one. Write to support@nanoflags.io with “Security” in the subject. This page explains what helps us act quickly and what you can expect in return.
How to report
- E-mail support@nanoflags.io with “Security” at the start of the subject line. Write in English or Arabic.
- Describe the issue and its impact, the affected URL, endpoint, SDK or package and version, and the steps to reproduce it. A proof of concept helps; keep it minimal.
- Tell us how you would like to be credited, if at all.
- Do not include other people's personal data in the report. If you came across any, say so and delete your copy.
In scope
- nanoflags.io (website and documentation) and app.nanoflags.io (dashboard)
- edge.nanoflags.io (configuration delivery, live connections, OFREP, CI, admin and Management API)
- The client packages in the public nanoflags-sdk repository: @nanoflags/sdk, @nanoflags/openfeature-provider, @nanoflags/cli, the Python, Go, Java, .NET, PHP and Ruby SDKs and the GitHub Action
- The NanoFlags GitHub App and the signed configuration format (signature bypass, key confusion, downgrade)
Out of scope
- Denial-of-service and load testing, spam, social engineering, and physical attacks
- Findings from automated scanners without a demonstrated impact (for example missing headers, TLS cipher lists, version banners)
- Rate limits that work as documented, and the public nature of browser (client) keys and client-exposed flags, which is by design
- Vulnerabilities in the services of our providers: report those to them directly
Rules for good-faith research
- Only test against accounts and workspaces you created yourself. Never access, change or delete data that is not yours.
- Stop and report as soon as you can show the issue; do not escalate access, pivot to other systems or keep a foothold.
- Do not degrade the service for other customers, and do not run automated tools at high volume.
- Keep the details confidential until we have fixed the issue, or until we have agreed on a disclosure date with you.
What you can expect
- We aim to acknowledge your report within three business days and to keep you informed until it is resolved.
- We will tell you when the issue is fixed and, with your permission, credit you on this page.
- If you follow this policy in good faith, we will not pursue legal action against you for your research, and we will say so if a third party asks.
- We do not run a paid bug bounty programme at the moment.
More
How NanoFlags protects data is described on the security page and in the security documentation. The providers that process data for us are on the sub-processors page. Machine-readable contact details: /.well-known/security.txt.
Acknowledgements
No reports have been credited yet.