OSIDB-4286: Do not audit Snippet objects #1168
Open
Conversation
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
Elkasitu
added
the
technical
Elkasitu
force-pushed
the
dont-audit-snippets
branch
from
6760964 to
73f0fc5
Compare
Snippet records have an ephemeral purpose: to serve as pseudo-Flaws until either they can be automatically converted into a real Flaw or an analyst goes over them and extracts data from them in order to create a Flaw. There is no way to expose nor modify Snippet records from outside the application, therefore there is no point in auditing any actions. Audit logs of Snippet objects accounted for up to 80% of database disk utilization which can be bad for performance, cost, etc. Closes OSIDB-4286
Elkasitu
force-pushed
the
dont-audit-snippets
branch
from
73f0fc5 to
60c3d14
Compare
MrMarble
approved these changes
Dec 24, 2025
dmonzonis
approved these changes
Dec 29, 2025
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.
Snippet records have an ephemeral purpose: to serve as pseudo-Flaws until either they can be automatically converted into a real Flaw or an analyst goes over them and extracts data from them in order to create a Flaw.
There is no way to expose nor modify Snippet records from outside the application, therefore there is no point in auditing any actions.
Audit logs of Snippet objects accounted for up to 80% of database disk utilization which can be bad for performance, cost, etc.
Closes OSIDB-4286