Skip to content

FAQ's

Jump to bottom
Gabe Stocco edited this page Apr 22, 2020 · 17 revisions

Quick Hits

  • Attack Surface Analyzer requires administrator privileges to accurately gather system data.
  • The tool has high CPU and memory demands, and may take a considerable amount of time to complete depending on the collectors run and scope of data available on the system.
  • Analyses should never be run on live production servers since it can severely degrade the performance of the system.
  • The older classic version of the tool produced .cab files which are not compatible with this rewritten version which stores results in a local SQLite db file.

Can I still access the Attack Surface Analyzer 1.0 (classic) version of the tool?

Yes. It is still available for download but not supported. Access it here at https://www.microsoft.com/en-us/download/details.aspx?id=24487

Windows Defender is consuming a lot of CPU when running ASA

You can add an exclusion in Windows Defender. First open the "Windows Security" application, Navigate to "Virus & Threat Protection", "Manage Settings", "Add or remove exclusions", and then add an exclusion for "asa.exe".

Why isn't Attack Surface Analyzer notarized for macOS?

This is a current limitation of our build pipeline. In the meantime you can build Attack Surface Analyzer from source, disable Gatekeeper, or install the .NET Core runtime and run dotnet tool install -g Microsoft.CST.AttackSurfaceAnalyzer.CLI to add asa to your path.

What do I need to run Attack Surface Analyzer on Windows 7?

Make sure you have KB2999226 and KB2533623 installed. Or you'll see The library hostfxr.dll was found, but loading it from C:\<path_to_app>\hostfxr.dll failed

Clone this wiki locally