microsoft / microsoft/AttackSurfaceAnalyzer
Add Export Sarif Button to GUI
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3k
- Forks
- 294
- PR merge metrics
- No merged PRs in 30d
Description
It would be nice to be able export the entire analysis report to a single HTML file, or other browser format, so that it can be passed to anyone and they can open it in any web browser and see the results without having to look through the json file or create a tool to parse the json file or have access to the original instance of the ASA where the report was created.
Option to select to export ASA report to an HTML
Describe alternatives you've considered
The alternative is creating a tool to parse the json and display it in a useful visual format or zipping up the entire instance of the ASA where the report was created and attaching it where others can download it to see the report. Another alternative is to use the browser's Save As feature to save the current data in the page to an html file, the issue with this is you only get the data for the current page of the report that you are on so you would have to save a file for every page which is not very useful when there are 30+ pages of data in the report.
System Configuration (please complete the following information):
- OS: Windows 11
- OS Version: Windows 11 Enterprise version 21H2
- Application Version: 2.3.299
- CLI or GUI: both
Additional context
N/A
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the GUI presents the full analysis report and how report data is currently represented in JSON. Compare the requested single HTML export with the current-page browser Save As alternative, then define completion as one browser-openable file containing the entire report rather than only the visible page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100