Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compiler Execution Within Kubernetes Containers #4880

Closed
wants to merge 6 commits into from

Conversation

signalblur
Copy link
Contributor

Summary of the Pull Request

I've created a new detector based on research done by Datadog based on compiler execution within a container. I believe I saw a tweet a few years back from Florian suggesting to avoid regex to make understanding logic a bit easier, but on the off chance it's preferred over the below I believe this should work:

.*(\-|\_| )?(gcc|g\+\+|clang|javac|make|nasm|yasm)(\-|\_| )?.*

This shouldn't happen legitimately (according to best practices) as builds should be immutable. I've set the priority on this to low as even though that is a recommended best practice, I'm sure there will be FP's in reality.

Changelog

new: Compiler Execution Within Kubernetes Containers

Example Log Event

Fixed Issues

N/A

SigmaHQ Rule Creation Conventions

  • If your PR adds new rules, please consider following and applying these conventions

@github-actions github-actions bot added the Rules label Jun 16, 2024
@signalblur signalblur changed the title K8s compiler Compiler Execution Within Kubernetes Containers Jun 16, 2024
…xecution_in_container.yml

Co-authored-by: frack113 <62423083+frack113@users.noreply.github.com>
@nasbench
Copy link
Member

Since the PR #4881 contains the rule you submitted here (i'll handle both of them there).

@nasbench nasbench closed this Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants