-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
docs(misconf): Add reference info on internals of Trivy IaC scanning #8272
base: main
Are you sure you want to change the base?
Conversation
|
||
![misconfig-code-org](../../imgs/misconfig-code-org.jpg) | ||
|
||
Trivy is able to obtain input from both IaC and Live Clouds when it comes to misconfiguration scanning. |
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.
Is the term Live Clouds
common?
![misconfig-code-org](../../imgs/misconfig-code-org.jpg) | ||
|
||
Trivy is able to obtain input from both IaC and Live Clouds when it comes to misconfiguration scanning. | ||
In the case of IaC scanning, language models such as Terraform and CloudFormation are used to build the common model. |
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.
language models
can be confused with LLM :)
Left a couple of comments. BTW, why did this document become necessary? |
as discussed, since this isn't user-facing documentation, I suggested to put this (and other developer-facing documentation) either in raw readme files in relevant places in the source code, and link to them from ARCHITECUTRE.md in the root (like TOC), or to move this to the "contributing" section of the docs |
Description
Add reference info on internals of Trivy IaC scanning
Checklist