MISP / MISP/misp-objects

Object: Log Entry

Open
#25 0 comments 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

It would be nice to have an dedicated object for "log-Entry" that then can be used to build a timeline

  • Timestampt (UTC)
  • Timestamp description (e.g. in what log have you found it)
  • System (e.g. which system is your log entry covering)
  • Event description / raw log line
  • Notes
  • involved user
  • Added by
  • malicious yes / no

That way you could create a nice timeline during an investigation

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

No files, tests, or entry points are named. Review existing MISP object definitions and their conventions first; completion would require agreeing on the proposed fields and adding a log-entry object that supports an investigation timeline.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.