mandiant / mandiant/capa-rules
reconsider att&ck classification for get/set-uefi-variable.yml
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 736
- Forks
- 245
- Avg merge
- 4d 53m
- Merged PRs (30d)
- 2
Description
We should reconsider the `att&ck` classification for https://github.com/mandiant/capa-rules/blob/64b174e50253cbd506df40e7728531b801636a56/host-interaction/bootloader/get-uefi-variable.yml#L11 and https://github.com/mandiant/capa-rules/blob/64b174e50253cbd506df40e7728531b801636a56/host-interaction/bootloader/set-uefi-variable.yml#L11.
Without additional indicators, I'm not sure that we can draw the conclusion that getting/setting UEFI variables results in boot persistence.
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 with the ATT&CK classification at line 11 of host-interaction/bootloader/get-uefi-variable.yml and set-uefi-variable.yml, then review the surrounding rule definitions. Determine whether getting or setting UEFI variables alone supports the boot-persistence conclusion; done means the classifications and any supporting rationale are consistent with that decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100