How to report
Email security@walilock.com. Tell us the version, platform or page, the steps to reproduce, and the impact you see. One report per root cause. You can write in English, French or Japanese.
Do not put real vault contents, passwords or other people’s data in a report. Show that you could read something with your own test data instead.
Rewards
We do not pay rewards yet. With your agreement, we credit you by name in the advisory and in the acknowledgments on our security advisories page. If we start a paid program, this page will say so first.
In scope
- The sync relay API: authentication, authorization, access to another user’s or another company’s data, single sign-on and user provisioning, the IP allowlist, and injection or request-parsing flaws.
- The Walilock apps for Windows, Mac, iOS and Android, current release: disclosure of keys or vault data, getting past biometric unlock, and abuse of the app’s internal commands, links or update channel.
- The browser extension, current release: filling a password into the wrong site, and attacks from a hostile page.
- The share page (
/s) and its encryption: opening a share without its key, or running script on the page.
- The
wali command-line tool and agent access: reading a secret without a grant, widening an agent’s access, or changing the access log without detection.
- The account pages on walilock.com: sign-in, passkey sign-in, password reset and account settings.
Out of scope
- Denial of service, load or volume testing, brute force at scale, and raw scanner output.
- Social engineering or phishing of our staff, customers or partners, and physical attacks.
- Services we use but do not run, such as our hosting, database, email and payment providers. Report those to the provider, and tell us if Walilock users are affected.
- Attacks that need malware already running as the user with the vault unlocked, a rooted or jailbroken device, or a modified app.
- Limits we already document on our security model page, such as trusting a contact’s key the first time it is seen. A way around a documented protection is in scope.
- Missing headers or cookie flags with no demonstrated impact, self-XSS, version banners, and clickjacking on pages with no sensitive action.
- Issues already listed on our security advisories page, and issues only in builds older than the current release.
Rules for research
- Use only accounts and devices you own. Ask us for a free Business test account if you need one.
- If you reach someone else’s data, stop, do not keep or share it, and tell us.
- Keep automated requests below 5 per second, and do not degrade the service for others.
- Do not change or delete data that is not yours.
- Keep the finding private until the disclosure date below.
What we promise
- We acknowledge your report within 3 business days.
- We confirm whether it is valid, and how severe it is, within 7 days.
- We send you an update at least every 14 days until it is fixed.
- We aim to fix critical issues within 30 days, high within 60, medium within 90, and low in the next release.
- We publish an advisory in English, French and Japanese, and credit you if you want.
Disclosure
We ask you to wait 90 days from your report before publishing, or until a fix has shipped and users have had time to update, whichever comes first. If a fix needs longer, we will explain why and agree a new date with you.
Safe harbour
If you make a good-faith effort to follow this policy, we consider your research authorized. We will not take or support legal action against you for it, and we will not ask anyone else to. If someone else takes action against you for research within this policy, we will make it known that it was authorized.
For research within this policy, we waive any restriction in our Terms of Service or software licenses that would otherwise forbid it, including on reverse engineering and on getting around our protections, to the extent the research needs.
This policy binds only Walilock. It does not authorize testing systems that belong to others, and it cannot override the law that applies to you. If you are unsure whether something is allowed, ask us first. Researchers in France may also report to ANSSI, the French national cybersecurity agency, under article L.2321-4 of the Code de la défense.
Contact
security@walilock.com. The same contact is in our security.txt.