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

accumulative profile #54

Open
itaysk opened this issue Sep 2, 2023 · 0 comments
Open

accumulative profile #54

itaysk opened this issue Sep 2, 2023 · 0 comments
Assignees

Comments

@itaysk
Copy link
Contributor

itaysk commented Sep 2, 2023

Currently we alert any profile deviation as suspicious. This approach is noisy and possibly overly protective. I suggest we change the behavior to alert only if something that was previously unknown is now added to the profile.
For example, consider a case that the pipeline connected to domainX.com, tracee-action detected it and admin acknowledged it. Now domainX.com is in the dns profile. Then in a subsequent run, the pipeline did not connect to domainX.com for whatever reason. Today, we alert this, and this issues propose to ignore this specific case.
The rational is that pipelines can be inconsistent by design, and that the profile should be essentially a list of trusted/allowed interactions as opposed to exact interactions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant