tegwick
beab2a04d1
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a0260c-4067-7052-9647-ad000d576e38
27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
# Noisy-neighbour characterization
|
|
|
|
There is no standing authorization or default ceiling for this technique. A
|
|
run requires a separate operator-approved target, namespace, time window,
|
|
aggressor allowance, concurrency/resource ceilings, service classes, headroom
|
|
threshold, and abort thresholds.
|
|
|
|
For each co-resident consumer the artifact records a quiet baseline and a
|
|
loaded sample: latency, error rate, throughput and the declared service class.
|
|
The aggressor may reach but never exceed its own allowance. The artifact also
|
|
records whether the governor bound, peak versus ceiling, aggregate headroom,
|
|
and each neighbour's measured degradation.
|
|
|
|
Zero degradation is not the expected assertion on shared infrastructure.
|
|
Whether measured degradation is acceptable belongs to the responsible owner;
|
|
whitehat records the observation. A governor that does not bind, an exceeded
|
|
probe ceiling, missing neighbour samples, or an abort threshold produces a
|
|
finding/abort rather than a stronger retry.
|
|
|
|
The evaluator is calibrated offline with:
|
|
|
|
```sh
|
|
PYTHONPATH=src python3 -m whitehat_security.cli capacity-fixture
|
|
```
|
|
|
|
That command generates no load and is not P1/P2 target evidence.
|
|
|