New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New atm features rebased #10018
New atm features rebased #10018
Conversation
...rimental/adaptivethreatmodeling/lib/experimental/adaptivethreatmodeling/EndpointFeatures.qll
Fixed
Show resolved
Hide resolved
...rimental/adaptivethreatmodeling/lib/experimental/adaptivethreatmodeling/EndpointFeatures.qll
Fixed
Show resolved
Hide resolved
javascript/ql/experimental/adaptivethreatmodeling/modelbuilding/debug/CompareFeatures.ql
Fixed
Show resolved
Hide resolved
javascript/ql/experimental/adaptivethreatmodeling/modelbuilding/debug/CompareFeatures.ql
Fixed
Show resolved
Hide resolved
...rimental/adaptivethreatmodeling/lib/experimental/adaptivethreatmodeling/EndpointFeatures.qll
Fixed
Show resolved
Hide resolved
b5495b4
to
2c28d24
Compare
|
Before we can merge this, we need to (at least) train/evaluate/release the models, and add a commit here that makes the branch depend on the new model. |
|
I just requested a review from @henrymercer - this is a pretty big change set. This is the branch we're aiming to release, as discussed yesterday evening. We've been using most of it for many months now, which IMO means it'd be most important to take a look at the changes I've done today. I've spotted one minor bug in one of the features when doing this, but I'd rather keep everything as stable as possible to minimize changes as much as possible (the bug also affects current |
A bunch of comments around the definition of the new features. No comments on the tests — those look great.
Before we can merge this, we need to (at least) train/evaluate/release the models, and add a commit here that makes the branch depend on the new model.
In addition to what you state here, we should also run the security-extended vs security-extended-plus-atm experiment to confirm that this change keeps us within our runtime performance budget.
...rimental/adaptivethreatmodeling/lib/experimental/adaptivethreatmodeling/EndpointFeatures.qll
Outdated
Show resolved
Hide resolved
...rimental/adaptivethreatmodeling/lib/experimental/adaptivethreatmodeling/EndpointFeatures.qll
Outdated
Show resolved
Hide resolved
...rimental/adaptivethreatmodeling/lib/experimental/adaptivethreatmodeling/EndpointFeatures.qll
Outdated
Show resolved
Hide resolved
...rimental/adaptivethreatmodeling/lib/experimental/adaptivethreatmodeling/EndpointFeatures.qll
Outdated
Show resolved
Hide resolved
...rimental/adaptivethreatmodeling/lib/experimental/adaptivethreatmodeling/EndpointFeatures.qll
Outdated
Show resolved
Hide resolved
...rimental/adaptivethreatmodeling/lib/experimental/adaptivethreatmodeling/EndpointFeatures.qll
Outdated
Show resolved
Hide resolved
...rimental/adaptivethreatmodeling/lib/experimental/adaptivethreatmodeling/EndpointFeatures.qll
Outdated
Show resolved
Hide resolved
...rimental/adaptivethreatmodeling/lib/experimental/adaptivethreatmodeling/EndpointFeatures.qll
Show resolved
Hide resolved
javascript/ql/experimental/adaptivethreatmodeling/test/generic_feature_testing/EmptyFeature.ql
Show resolved
Hide resolved
javascript/ql/experimental/adaptivethreatmodeling/test/generic_feature_testing/test.html
Outdated
Show resolved
Hide resolved
|
Experiment came back, 34% slowdown. @tiferet, is this a blocker? |
I think that's a question for @henrymercer: is this still within the acceptable time cutoff relative to a run without boosted queries? |
|
The KR is 25%. I think we should spend some time optimizing the new features to keep us within this performance budget. |
Is this a 34% slowdown relative to the unboosted version or relative to the current version of ATM? Also, @kaeluka do you have ideas for how to optimize this? We should do that before proceeding with the new data generation, because we want to generate data from the final version of the PR exactly as we're going to merge it. |
Relative to the unboosted version :)
Optimizing CodeQL performance is one area where I know next to nothing :( the best I can do is to look for "obvious" mistakes, but in my experience the obvious ones I'm able to recognize are also caught by QL-for-QL (and QL-for-QL is coming up with nothing for this PR). I'd be very eager to help out on the optimization, but I think I can't drive this. |
73ab279
to
a82d9e2
Compare
Co-authored-by: Henry Mercer <henrymercer@github.com>
…se positives for XSS query
…g concatenation leaves are usually not sinks
Co-authored-by: Henry Mercer <henrymercer@github.com>
a82d9e2
to
81d02cc
Compare
This PR
This takes the
new-atm-featuresbranch (but excludes a few experimental commits near its top), rebases it on top of currentmain, and removes the obsolete features that have been replaced.