Repository navigation
Add a MISP 3.0 event-template usage and authoring guide - #329
Merged
Merged
Conversation
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add Event Templates under Using MISP, with a complete reporter workflow and visual-authoring walkthrough for MISP 3.0. The practical email-intake example creates a case reference, email/file objects, a
has-attachmentrelationship and two Event Reports. Include ten fresh screenshots and a downloadable, validated JSON template that starts inactive and organization-only.Explain required/repeated fields, object-template dependencies and minimum versions, generated titles and event defaults, preview/version behavior, permissions, import/export/duplication, library management and Draugnet exposure. Link the chapter from Using the System, General Layout and MISP Objects. Instructions and captures follow
3.0_wipat99ebee729702c560528f9788953719bda68aa1c1; the provenance manifest records source pins, runtime checks and limits.The chapter documents two checked-branch limitations: advanced event defaults require validated JSON/API editing, and some object values without explicit category metadata can be dropped during instantiation. The example uses fields verified in the saved event, and emphasizes inspecting generated data. No MISP application code was patched to produce the screenshots.
Validation:
The fixture's original empty template catalogue was restored after removing only task-created library/example/probe rows. Exercise events remain private, unpublished and IDS-off; the three task-started fixture containers were stopped. Tag/galaxy pickers, malware-sample uploads and external Draugnet reporting were not exercised end to end.