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

Unable to manage risk #479

Closed
mutilator opened this issue Jan 31, 2024 · 4 comments
Closed

Unable to manage risk #479

mutilator opened this issue Jan 31, 2024 · 4 comments
Labels
stale This has become stale due to inactivity

Comments

@mutilator
Copy link

I was able to utilize the exception list functions for the legacy scanning engine but I'm not seeing a way to manage the new engine risk acceptance.

  • sysdig_secure_vulnerability_exception_list
  • sysdig_secure_vulnerability_exception
  • sysdig_secure_scanning_policy
  • sysdig_secure_scanning_policy_assignment

Is this a coming feature? Can the new risk acceptance even be managed in a similar fashion where we have specific policies and risk lists per container/base-container?

Copy link

github-actions bot commented Apr 1, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale This has become stale due to inactivity label Apr 1, 2024
@mutilator
Copy link
Author

Still an issue

@github-actions github-actions bot removed the stale This has become stale due to inactivity label Apr 2, 2024
Copy link

github-actions bot commented Jun 1, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale This has become stale due to inactivity label Jun 1, 2024
Copy link

github-actions bot commented Jun 9, 2024

This issue has been closed due to inactivity.

@github-actions github-actions bot closed this as completed Jun 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale This has become stale due to inactivity
Projects
None yet
Development

No branches or pull requests

1 participant