mandiant / mandiant/capa-rules

rule: detect secure desktop protection bypass

Open
#86 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

migrated-rule rule idea
Dominant language
No language data
Stars
736
Forks
245
Avg merge
4d 53m
Merged PRs (30d)
2

Description

@mike-hunhoff
> Technique discussed [here](https://www.blackhat.com/docs/sp-14/materials/arsenal/sp-14-Almeida-Bypassing-the-Secure-Desktop-Protections-Slides.pdf).
>
> Example may be `b7841b9d5dc1f511a93cc7576672ec0c::10013310`

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked Black Hat technique and examining the example sample identifier b7841b9d5dc1f511a93cc7576672ec0c::10013310. Determine the rule's observable scope from those references; done means capa-rules contains a rule that detects the described secure desktop protection bypass.

Written by the indexing model from the issue text.

Assessment

Domain
reverse-engineering, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.