mandiant / mandiant/capa-rules
Cleanup Nt* and Zw* api definitions
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 736
- Forks
- 245
- Avg merge
- 4d 53m
- Merged PRs (30d)
- 2
Description
Various rules have just the Nt* function or just the Zw* function. Some have both.
Example: NtQuerySystemInformation listed but ZwQuerySystemInformation was missing (until upcoming PR here).
Cleaning this up would solve it for the current rules, but what about future ones?
- add a lint? (we have a semi-related lint for "feature api may overlap with ntdll and ntoskrnl")
- modify a) the feature extractor or b) the rule parser to emit Nt*/Zw*/... extractor
- downside: could emit non-existing apis
- upside: easier rule writing
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 comparing current rules that define Nt* and Zw* APIs, then inspect the existing lint for feature APIs overlapping ntdll and ntoskrnl. Decide whether cleanup belongs in a new lint or in the feature extractor or rule parser, and define how to avoid emitting nonexistent APIs; done means the chosen approach covers current and future rules.
Written by the indexing model from the issue text.
Assessment
- Domain
- reverse-engineering, security, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100