Skip to content

docs(sensors): correct the per-host budget page (lowest limit wins, what is and is not bounded) - #310

Merged
0xmanhnv merged 3 commits into
mainfrom
docs/per-host-budget
Nov 17, 2026
Merged

0xmanhnv merged 3 commits into
mainfrom
docs/per-host-budget

Conversation

@0xmanhnv

Copy link
Copy Markdown
Member

Follow-up to #308, which merged with its first-revision text.

  • States that a job's per-host budget is the lowest of the sensor's level, the job's signed budget, the operator's ceiling and the built-in ceiling, and that a job can only lower it.
  • Says what the sensor holds (new connections, plain HTTP requests, HTTPS requests including on kept-alive connections for the scan tools it runs) and what it does not (requests packed together on one HTTPS connection, and runs with the sandbox off, which rely on the tools' own flags).
  • Names packet-rate port scanning as the exception.
  • Fixes the descriptions of SENSOR_PACING_LEVEL and the local policy host ceiling to match.

The feature ships with the next sensor release.

Checked: docs_check (0 problems), brand and private-path scripts.

…icy host ceiling

Signed-off-by: Nguyen Manh <18032641+0xmanhnv@users.noreply.github.com>
…ost budget, what holds it and what does not

- A job can only lower what a host gets: the budget is the lowest of the
  sensor level, the signed job budget, the operator ceiling and the
  built-in ceiling.
- The tools under the budget, the port scan (packets per second) and the
  tools that send nothing to the targets.
- What the sensor holds outside the tools, what only the flags of the
  tools hold, and what an unsandboxed run loses.
- The canary request is fixed and only slows a host.

Signed-off-by: Nguyen Manh <18032641+0xmanhnv@users.noreply.github.com>
Signed-off-by: Nguyen Manh <18032641+0xmanhnv@users.noreply.github.com>
@0xmanhnv
0xmanhnv merged commit 9317958 into main Nov 17, 2026
10 checks passed
@0xmanhnv
0xmanhnv deleted the docs/per-host-budget branch November 17, 2026 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant