-
Notifications
You must be signed in to change notification settings - Fork 140
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
Add evidences to Compliance Finding #1157
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks straightforward, but can you please make sure to update the CHANGELOG.md? Thanks.
Sorry, added |
For this one, we should probably change the dictionary definition of
|
e35d89c
to
616fc2b
Compare
I feel as if |
When reporting Compliance Finding, we want to specify which File, API or Device caused us to trigger the finding.
Signed-off-by: Rajas <89877409+floydtree@users.noreply.github.com>
When reporting Compliance Finding, we want to specify which File, API or Device caused us to trigger the finding. For example, if we have a terraform file which creates an AWS ec2 instance with public 22 port, we want to point to the file where we found the issue.
Description of changes: