20 lines
1.1 KiB
Markdown
20 lines
1.1 KiB
Markdown
|
# Observation, attacks, and findings
|
||
|
|
|
||
|
|
kings-guard evaluates observations/posture and proposes bounded response.
|
||
|
|
Containment actuation is not its capability. Its pilot supports real-event input,
|
||
|
|
but that does not establish continuous production observation or automatic
|
||
|
|
isolation. An older companion statement and a newer pilot README need owner
|
||
|
|
evidence, not a guessed production status.
|
||
|
|
|
||
|
|
whitehat-security designs independent adversarial probes within approved rules
|
||
|
|
of engagement and target-specific authorization. Offline calibration establishes
|
||
|
|
fixture behavior only. A pass means the tried attacks did not work, not that a
|
||
|
|
live boundary is universally secure. Do not run live probes from this package.
|
||
|
|
|
||
|
|
Route findings to risk-nexus for severity/disclosure and to the owning repository
|
||
|
|
for repair; doctrine findings also go to gate-house. Preserve evidence and its
|
||
|
|
limitations. Do not claim independent adversarial review from self-authored tests
|
||
|
|
or suppress a finding because the control owner calls itself conforming.
|
||
|
|
|
||
|
|
Source owner IDs (cite the relevant owner, not an invented umbrella): `kings-guard`, `whitehat-security`, `risk-nexus`, `gate-house`.
|