-
Notifications
You must be signed in to change notification settings - Fork 83
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
feat: application level encryption #157
feat: application level encryption #157
Conversation
…pplication-level-encryption-missing-on-data-category
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.
Looking great already! Some comments
Conflicts: pkg/commands/process/settings/settings.go pkg/report/output/output.go pkg/report/output/policies/policies.go
…tion-missing-on-data-category
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.
I don't see the policy using this info. Is that coming in a separate PR?
yeah something is wrong my branches got mixed. fixing it. |
…g-on-data-category' of github.com:bearer/curio into AMA-3158-use-case-2-application-level-encryption-missing-on-data-category
…pplication-level-encryption-missing-on-data-category
Description
This Pr adds verified by, It adds risk type and adds support for rego policies as processor step between detectors and dataflow.
To dataflow report it adds non mandatory field encrypted, and non mandatory field verified by.
example output
Related
https://bearer.atlassian.net/browse/AMA-3230
https://bearer.atlassian.net/browse/AMA-3231
https://bearer.atlassian.net/browse/AMA-3232
https://bearer.atlassian.net/browse/AMA-3233
https://bearer.atlassian.net/browse/AMA-3234
Checklist