Security
Protecting the community’s identity is why passport.lgbt exists. Here are the measures in place, what is planned before launch, and how to report a vulnerability.
Where are we?
- The service is under construction and not yet open to the public. The measures below already apply to our test environment and will apply to the production service.
- Before opening to the public: a privacy impact assessment and a full security review.
- We do not hold any security certification yet. We will say so here when we do, and not before.
Hosting
- The service is hosted by OVHcloud in Canada (primary site), with a backup copy in France.
- The infrastructure is run by our team. Our error-tracking and audience measurement tools are open-source software we host ourselves.
Our security measures
- Encryption: every connection uses HTTPS, and databases and storage are encrypted at rest.
- Restricted access: each team member only has the access they need; production access is limited and logged.
- Two-factor authentication is mandatory for the team on every tool and on the infrastructure.
- Backups: automatic and regular, with tested restores.
- Encrypted secrets: no password or key is stored in plain text in our code.
- Minimal logs: no email address, phone number, password or token in logs and error reports.
- Isolated applications: unprivileged containers, pinned versions reviewed at every update.
Protecting your passport
- Sign in with a passkey, a code or a password, and two-factor authentication with an authenticator app, with backup codes.
- Each app receives a different identifier for you: two apps cannot cross-reference their data.
- A standard, proven protocol: OpenID Connect.
Report a vulnerability
- Think you have found a vulnerability in passport.lgbt? Write to the address at the bottom of this page. Describe the problem, how to reproduce it and its possible impact.
- If your report contains sensitive information, first send a message without details: we will offer you an encrypted channel.
- Acknowledgement within 72 hours, then regular updates until it is fixed.
- Fix or coordinated disclosure within 90 days, unless agreed otherwise with you.
- Please do not access other people’s data, degrade the service, attempt phishing or physical attacks, and give us time to fix the issue before publishing anything.
Our commitment to people who report
- If you act in good faith and follow the rules above, we will not take legal action against you or ask anyone else to.
- With your consent, we will thank you publicly on this page. We do not offer financial rewards.
Acknowledgements
- No one yet. Your name could be the first.
To report a vulnerability or ask a security question: security@passport.lgbt.