Skip to content

[IMPROVE] Include registry name/hive in the reporting #244

Description

@LM-CT

Improvement

NOTE!
Before submitting, please go through our roadmap and phases to see if the improvement you want is already defined there.

Is your improvement suggestion is related to a problem? please describe.

When registry events occur, there is no information about what hive, name and type of entry was modified/created/deleted. This information is not present on the web UI nor the JSON output of the reporting module and partially exists in the <analysis>/<task>/events/registry.json output (only the hive/name of the registry, but not the value).

Improvement type

  • Quality of life (Ex: Make custom config item easier to set; Expose internal artifact download; etc)
  • Performance (Ex: Do to speedup pre-processing; is uneeded to do and can be dropped; etc)
  • Web interface (Ex: There could be a button for ; Add a graph for ; etc)
  • CLI interface (Ex: Add parameter to cuckoosafelist add; Change command name from to in cuckoonode; etc)
  • API (Ex: Add information to endpoint response; etc)
  • Documentation (Ex: Move section for to location; Add screen capture in instructions; etc)
  • Logging (Ex: Add exception error treatment in function; Add debug log to ; etc)
  • Code refactoring (Ex: Improve <funtion/class> readability; Make <function/class> more concise by extracting into helper function; etc)

Proposed solution

Describe the solution you'd like.

Add the missing information to the reporting output in JSON and, ideally, to the web UI.

Additional context

Additional context

Values can be helpful, but they only tell part of the story.

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    improvementExisting functionality that needs improvements

    Type

    Fields

    No fields configured for Task.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions