search

falcosecurity / rules

Falco rule repository
https://falcosecurity.github.io/rules/
Apache License 2.0
89 stars 64 forks source link

Container information #184

Closed ajinkya1986 closed 3 months ago

ajinkya1986 commented 8 months ago

Currently all the rules in falco have %container.info field in the output parameters, which populates only limited container information. Is it possible to add more container information for the rule which require them. Like container.image, container.image.id, container.type, container.image.tag etc

incertum commented 8 months ago

See https://falco.org/docs/rules/style-guide/ string search for %container.info to find the relevant paragraph.

Since you have this question I am wondering how we can improve the documentation in this regards. Would you have ideas?

ajinkya1986 commented 8 months ago

This refers to creating new rules and adding container information. But how can we add more container information in the existing rules without creating custom rules.

incertum commented 8 months ago

Hi @ajinkya1986 no worries. The formatting guidelines apply to any rules you pass to Falco.

Have you tried https://falco.org/docs/outputs/formatting/?

Alternatively (if the special %container.info placeholder is not ideal for your use case) you can manually change the output yaml property in the existing rule(s) files and specifically define any field you want to be in the logs https://falco.org/docs/reference/rules/supported-fields/#field-class-container.

poiana commented 5 months ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

poiana commented 4 months ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

poiana commented 3 months ago

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community. /close

poiana commented 3 months ago

@poiana: Closing this issue.

In response to [this](https://github.com/falcosecurity/rules/issues/184#issuecomment-2005701684): >Rotten issues close after 30d of inactivity. > >Reopen the issue with `/reopen`. > >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Provide feedback via https://github.com/falcosecurity/community. >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.