Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log ProbeUpdate metadata for anomaly detection #925

Open
LDiazN opened this issue Jan 22, 2025 · 0 comments
Open

Log ProbeUpdate metadata for anomaly detection #925

LDiazN opened this issue Jan 22, 2025 · 0 comments
Assignees
Labels

Comments

@LDiazN
Copy link
Contributor

LDiazN commented Jan 22, 2025

This is a follow up issue for #923

The Probe Update function in the old orchestra component logs useful metadata that we can use for anomaly detection. (see: https://github.com/ooni/orchestra/blob/master/registry/registry/handler/registry.go#L25)

If we assume that the update requests are not going to be tampered with as much as the measurement submit ones, we can use this to determine which inconsistencies are due to our geoip being off compared to the probe one, vs those which are due to the measurement metadata being inconsistent due to malice.

This can be done through the new update endpoint in the ooniprobe service, see #923, (

@router.put("/update/{client_id}", tags=["ooniprobe"])
)

@LDiazN LDiazN self-assigned this Jan 22, 2025
@hellais hellais added this to Roadmap Jan 22, 2025
@LDiazN LDiazN moved this to Sprint Backlog in Roadmap Jan 22, 2025
@hellais hellais added the priority/medium Normal priority issue label Jan 28, 2025
@hellais hellais removed this from Roadmap Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants