Update built-in-rules.json to Support BPF Enforcer Behavior Modeling Data #260
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
…erate policy template
Danny-Wei
changed the title
Danny-Wei
changed the title
UgOrange
approved these changes
Sep 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What this PR does
Modifies the
built-in-rules.jsonfile used by Policy Advisor to add BPF enforcer-compatible permission aliases (e.g.,write,append) to file rulepermissionsfields. This enables the Policy Advisor to correctly parse behavior data collected by the BPF enforcer with the BehaviorModeling mode, ensuring it can generate valid policy templates.Key Features Added
Updated file rule
permissionsarrays inbuilt-in-rules.jsonto include both AppArmor-style abbreviations and BPF-compatible full names.