-
Notifications
You must be signed in to change notification settings - Fork 282
CLI Walkthrough
Gabe Stocco edited this page May 22, 2024
·
3 revisions
This page has screenshots with a step-by-step demonstration for doing a simple file system analysis with AttackSurfaceAnalyzer.
- First perform your baseline scan. This baseline scan collects files
-f
only in the relative directorytest
, which we can see begins empty (for this demonstration).asa collect -f --directories test
- Next perform your test actions. In this case we create an unsigned binary and a text file in the directory.
- Next we perform our compare scan using the same arguments as the baseline scan.
asa collect -f --directories test
- Now we can perform a comparison between the two runs and run the analyses built into ASA. When running
export-collect
you can specify the runId, when not specified it will compare the latest two collection runs. In this case, we've chosen to output sarif using the--outputsarif
argument.asa export-collect --outputsarif
- View the sarif in the sarif viewer of your choice, for example, the Sarif Web Component.
- The default report includes changes to the system that did not match a rule, with their default severity level from the ruleset. To exclude those findings add
--disableimplicitfindings
likeasa export-collect --outputsarif --disableimplicitfindings