It provides excellent documentation to integrate the tool within the workspace easily. I believe this is great when it comes down to containers specifically, as it looks in the skeleton of the image and a runtime scan. Review collected by and hosted on G2.com.
I believe the downside of the Lacework comes from its offering of infrastructure as code scanning. It is not context aware thus when you use your IaC code with imported modules, it won't understand what you are importing from those modules thus won't give you a concrete dataflow. Review collected by and hosted on G2.com.
Thank you for the detailed update of your review, Aleskandr. We're thrilled to hear that Lacework has enhanced your observability and incident response capabilities. It's fantastic to know that our solution is simplifying forensic investigations and improving your container traffic flows. We appreciate you sharing about the IaC challenges you’re experiencing; our team suggests scanning the code in your CI/CD pipeline (instead of in the code repos) with a "terraform plan" file. This file resolves the nested set of files (these are places where one IaC file calls another) and generates a single file to analyze. I hope this suggestion is helpful, or if I can connect you directly with the team to chat more, please send me a note at emily.chin@lacework.net and I would be happy to facilitate.