Security Actions & Security Operation Handling#48
Merged
Conversation
BrianSipos
reviewed
Aug 12, 2025
Collaborator
BrianSipos
left a comment
There was a problem hiding this comment.
Specific comments about OPLIST validity and extension. I can touch these up if it helps.
This was
linked to
issues
Aug 12, 2025
BrianSipos
approved these changes
Aug 12, 2025
BrianSipos
reviewed
Aug 12, 2025
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.
Notable Changes
Creates singular
Actionstructure, containing ordered list of SecOps.ActionSets now contain (not-necessarily ordered) list ofActions.Actionhave their parameters checked to determine order - for example, if a new SecOp(tgt=payload, ctx=BIB, role=ACCEPT), it should be added after SecOp(tgt=payload, ctx=BCB, role=ACCEPT).Adds conclusions to SecOps
Copied from other open PR for clarity