[New] DaC VCS Sync Workflow - #29
Open
eric-forte-elastic wants to merge 2 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Adds a new workflow called
dac-vcs-rule-sync, Detection-as-Code sync to version control. With this enabled, rules tagged withvcsin a configurable space, defaulting todevare exported through a detection-rules fork and opened as pull requests against main, with unit tests reported on the PR.This would be used in a Kibana as authoritative or a dual sync governance model.
Given the added complexity and requirements of having a fork of detection rules with a custom rules config setup, a direct setup guide is added in the file
examples/security/detection/dac-vcs-rule-sync/DEPLOY_AND_TEST.mdSee example PRs generated from this workflow:
Note
DaC workflows in general are somewhat restricted in that they cannot interact with Github Action workflows directly as these are not present in the current version of the Github Connector. If support for these are added, the workflow can be notably simpler with a similar result.