Manually Closing of Configuration Compliance Test Results
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2024 12:22 PM
Hi,
We have recently implemented Configuration Compliance with a couple integrations: Qualys Policy Compliance as well as Prisma Cloud.
There are times when we want to be able to manually close Config Test Results, however, unlike Vulnerability Response, the STATE field is 'grayed out', thus not allowing us to manually close Test Results. I understand that we can likely change the Roles/ACL to allow the STATE field to be 'changeable'. However, my guess is that they made the STATE field unchangeable by default for a reason. Is there something we should be concerned about if we decide to change the ACL/Roles to allow us to change that field? I just don't want to change it and not know the ramifications if we do that.
Like I said, we are able to manually close VITs in Vulnerability Response, but Config Test Results don't allow us to.
Let me know your thoughts. Thanks.
Kevin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2025 05:54 AM
Ideally, the entire workflow should be through remediation tasks, a VIT is a very small unit to be working on. You could create a group and then resolve the entire group to close.