For websites
Add reporting to a website
A participating website carries one link on each page. Everything else — the form, confidentiality, validation and the record — is handled once, centrally, on digosar.com.
The link
Each participating page carries a Report this page link that opens DIGOSAR with the page’s own address. If the page marks its sections with stable identifiers, the section the visitor was reading goes with it. The link sends nothing else — no cookie, no identifier of the visitor.
How DIGOSAR confirms the page
- The address must belong to a participating website and use HTTPS. Anything else is refused.
- DIGOSAR fetches the page itself and reads its title, its canonical address and a fingerprint of the version served. The visitor’s browser is never trusted to say what the page was.
- The confirmed page is shown to the visitor — “You are reporting”, with the title and address — before they write anything.
- The page details travel signed from the form to the submission, so they cannot be altered on the way.
Protection built in
- Server-side validation of every field; the report is stored and delivered as plain text, never executed.
- Protection against forged submissions (a same-site security token bound to the form), rate limits per network address, duplicate detection, and a check that a person, not a script, filled in the form.
- The reporter’s identity never passes through the participating website and never enters its statistics.
What a participating site receives
The substance of a concern and, where warranted, a correction to make. A reporter’s identity is not passed on, as set out under confidentiality.
Sources
- OWASP Foundation. Cross Site Request Forgery (CSRF). https://owasp.org/www-community/attacks/csrf