[BUG] Baked-in fapolicyd rules for the AWS CLI (v2) are at wrong tier
Open
Beginner friendly
Nobody has claimed this yet.
bug
- Dominant language
- Shell
- Stars
- 10
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
The current placement, at tier "30", causes the exceptions for the AWS CLI (v2) to be inserted before "Core ELF rules" (in tier "40") as well as the scripted-languages rules (at tier "70"). The rule-group should be moved to tier "80" to make resulting systems more secure.
From the vendor documentation for fapolicyd:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the repository for the AWS CLI (v2) fapolicyd rule group and its current tier 30 assignment. Change that assignment to tier 80, then inspect the surrounding rule definitions or validation checks to confirm the generated ordering places it after the core ELF and scripted-language rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100