MISP / MISP/misp-objects

Regkey object

Open
#90 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
110
Forks
139
Avg merge
12h 28m
Merged PRs (30d)
3

Description

in the same way like Path object, #89

we have differents state for the reg keys:

  • use for persistence

  • read for steal informations

  • set the malware configuration like proxy settings

Contributor guide

No contributing guide indexed for this repository

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 reviewing issue #89 and the existing Path object it references, then compare how registry-key states are represented in this repository. Define the requested Regkey object for persistence, information reading, and malware configuration use cases, and verify that its structure matches the repository's object conventions.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 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.