Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #1294: Add a generic event class for each category #1295

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rmouritzen-splunk
Copy link
Contributor

Related Issue:

#1294

Description of changes:

A generic event class for each category is helpful when mapping existing event logs to OCSF in situations where the category of an event is clear but the work to fully map events is not yet complete.

The alternative is loss of fidelity or just dropping the raw event (not mapping it at all while running in production), neither of which is desirable. The loss of fidelity arises from the use of the Base Event class instead of a generic category-specific class, and thus losing both the category and activity IDs for the generic class.

There should be a warning in the event class descriptions of these generic classes saying exactly why they exist, and steering people away from their use a final solution. The same warning should be added to Base Event.

Delete once you have confirmed the following:

  1. Did you add a single line summary of changes to Unreleased section in the CHANGELOG.md file?
    TBD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant