Reporting a security vulnerability

Thank you for looking. This is the policy that /.well-known/security.txt points to, on riyasystems.com and on every service we operate (RFC 9116). It states what is in scope, what we ask you not to do, and what we commit to in return, including an explicit safe harbor for good-faith research.

This is a disclosure policy, not a bug bounty. We do not pay for findings. We will credit you if you want to be credited.

How to report

Use the address in Contact: at https://<service>/.well-known/security.txt, which every service serves, or email security@riyasystems.com. Please include enough for us to reproduce the issue: what you did, what happened, and what you expected.

If a report contains data belonging to someone else, say so in the first line and do not attach it. We will arrange a way to receive it that does not spread it further.

What we commit to

  • Acknowledgment within three business days. A human, not an auto-reply.
  • A decision within ten business days of acknowledgement: whether we consider it a vulnerability, what severity we assign, and whether we intend to fix it.
  • Progress updates while a fix is outstanding, at least every ten business days.
  • Credit, where you want it, when the fix ships, and no credit if you would rather not be named.
  • No legal action against you for research conducted within this policy. See safe harbor below.

We handle every report as an incident, and raise its severity on any sign the issue has been exploited, so it reaches someone on call rather than waiting in an inbox.

Safe harbor

If you follow this policy, we will not pursue or support legal action against you for your research, and we will not report you to law enforcement for it. If a third party brings action against you for research we can see was conducted within this policy, we will say so publicly and in writing.

We consider research under this policy to be authorized access. If you are unsure whether something is in scope, ask first: a question costs you nothing, and we would rather answer it than argue about it afterwards.

This commitment is ours to give and cannot bind our customers. If a deployment is operated by a customer in their own environment, their authorization is theirs to give, not ours.

In scope

  • Riya's services and web applications, on hosts we operate, riyasystems.com, and menulogik.com, its former address, while it redirects.
  • Source code and container images we publish, once we publish any.
  • Our documentation site, once it is published.

Test only what you can reach yourself: our public sites, sign-in pages, and any account you legitimately hold. We don't provide test accounts or test environments. If a finding needs access you don't have to confirm, describe what you'd do and what you expect, and we'll reproduce it ourselves and tell you the outcome. Do not test against a deployment belonging to a customer, and never access anyone else's data.

Out of scope

A report about one of these tells us nothing we can act on:

  • Third-party services we consume, which should be reported to their owners.
  • Findings that require a compromised device, a malicious browser extension, or physical access to a signed-in machine.
  • Automated scanner output with no demonstrated impact. A severity score from a tool is not a finding.
  • Missing hardening headers, cookie flags or TLS configuration with no described attack.
  • Rate limiting on an endpoint, absent a demonstrated amplification.
  • Social engineering of our staff or our customers, and anything involving their credentials.
  • Reports that a version number is old, without a reachable vulnerability in it.

What we ask you not to do

These are the conditions of the safe harbor above.

  • Do not access, modify, or retain data that is not yours. If you reach someone else's data, stop, and tell us what you saw so we can assess the exposure. Do not download it to prove you could.
  • Do not degrade the service. No denial of service, no load testing, no resource exhaustion.
  • Do not persist. No backdoors, no maintaining access, no lateral movement after demonstrating the initial issue.
  • Do not social-engineer anyone, including our staff, our customers, or their users.
  • Do not disclose publicly before we have fixed it, or before 90 days have passed, whichever comes first. If we need longer we will ask, with a reason.
  • One account, yours. Do not create accounts in bulk or use someone else's.

If we disagree

Tell us. We would rather have the argument than have you conclude that reporting was a waste of your time. If we decide something is not a vulnerability and you think we are wrong, say why, and a second person will look at it.