3.5b's ordered exec-lineage proved inert in clean A/Bs; replace it with a general write->exec data-flow feature: WindowSummary.self_written_execs (exec of a file written earlier in the same window) at x[42], tracked via OpenWindow.written_paths. Honest status: this is the conceptually-correct provenance feature (it separates download->exec-the-same-file from download->exec-unrelated), but it ALSO shows no AUC gain on detector-labeled data -- for the same structural reason as 3.5b: the teacher labels (DownloadThenExecute etc.) correlate with existing count/location features or re-derive the detector. Validating provenance LEARNING requires the novel-chain generalization benchmark (train on detector-covered, hold out detector-evading attacks); committed as that benchmark's feature foundation. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| strawberry | ||
| tinyfsm.hpp | ||