microsoft / microsoft/AttackSurfaceAnalyzer
Track Exceptions when Gathering Info
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3k
- Forks
- 294
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
Some rules depend on boolean values (like Signature checking) but it may be possible for the data gathering to fail for one reason or another - the default value will then trigger the analysis rule, which may or may not be correct as the data is not gathered. Per #696.
Describe the solution you'd like
Ideally, we would retain information about exceptions that were encountered and modify rules to account for that the data was actually gathered as an additional clause in the rules for these fields, or perhaps gather these data points as nullable ro allow for cases where data collection failed to distinguish between true detections of, for example, missing signatures, vs exceptions which prevented data from being gathered.
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
No files, tests, or entry points are named. Start by reading the data-gathering and rule behavior discussed in this issue and review the related context in #696. Done requires an agreed design that distinguishes collection exceptions from valid boolean results and identifies which rules must account for that distinction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100