docs: design CVE-to-invariant mining and executable witnesses - #54
Draft
PhysShell wants to merge 2 commits into
Draft
docs: design CVE-to-invariant mining and executable witnesses#54PhysShell wants to merge 2 commits into
PhysShell wants to merge 2 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
docs/security-invariant-mine.md;dependency-only,consumer-analyzable,library-author-analyzable,configuration, andunknown;confirmed,static-only,runtime-only,inconclusive);Why OwnAudit
OwnAudit is already the evidence-heavy orchestration boundary and contains
LeakFixMine, runtime correlation, artifacts, and the standalone audit direction. Own.NET should remain the pure SAST engine. Moving advisory feeds, checkout/build orchestration, generated witness execution, licensing, or billing into Own.NET would couple the analyzer core to a second product.Positioning
This proposal is deliberately not framed as a new vulnerable-package scanner. Existing SCA products already report vulnerable dependency versions, and current products also provide forms of vulnerability reachability and runtime evidence. The narrower differentiator proposed here is the complete qualification chain:
The document treats novelty as an empirical claim to test against SCA reachability, SAST, IAST, patch-mining, and PoC-generation prior art rather than as marketing fact.
Safety boundary
The runtime artifact is called an executable witness, not an exploit generator. It is restricted to disposable isolation, no external targets, no ambient credentials, no network by default, unprivileged execution, strict resource limits, deterministic inputs, and vulnerable/fixed discrimination. Hosted execution requires a hardened VM-equivalent boundary; a container alone is not accepted as sufficient for arbitrary generated code.
Commercial boundary
The proposed split keeps the analyzer semantics open and makes the commercial OwnAudit value come from continuous curation, private-repository mining, hardened witness execution, proprietary calibration corpora, evidence management, enterprise integration, policy, and support. It explicitly rejects charging merely to repeat public CVE metadata or requiring a secret remote verdict for local diagnostics.
Validation
mainand 0 behind;LeakFixMinedesign.