Open yi2020 opened 3 years ago
@owenrumney @ismailyenigul @kaplanlior @JamesWoolfenden - as you all have engaged with this repo, would love to hear your thoughts. Anyone else is also welcome to jump in on this conversation.
Update to this issue: The best idea I have for this is to create an AWS account (and later azure, etc.) and then:
NOTE: Write credentials to the AWS account and the various tools will be saved in the secrets of this repo, accessible only to those individuals who are designated (ideally, one representative from each tool).
If anyone has feedback on this approach, would love to hear it :)
This also makes me wonder - some of the open source tools don't yet look at live accounts, so need to think of how to separate the measurement between those that do and those that don't.
Over the past year, infrastructure-as-code security began to evolve to look beyond just the code itself. We've seen this with Accurics, Bridgecrew, Fugue and Indeni Cloudrail's offerings. We also saw this recently with driftctl's launch.
An IaC security tool comparison needs to take this into account. This means we need to create a staging AWS environment that can be used in conjunction with the IaC security scans to show the capabilities beyond just static analysis.
We should figure out a way to pull this information into this tool-compare repository in a manner that's reproducible to anyone who seeks to do so.