kics VS ZAP

KICS (stands for "Keeping Infrastructure as Code Secure"): Owner/Maintainer: Checkmarx Age: First released on GitHub on November 30th, 2020 License: Apache License 2.0

The ones I remember being alright from a bunch of trials/PoC we did at my job were Snyk https://snyk.io/product/infrastructure-as-code-security/ and The one Gitlab Ultimate uses, https://github.com/Checkmarx/kics

KICS – Scan for Infrastructure-as-Code vulnerabilities

Checkov, Terrascan, and Kics can be used to scan our Infrastructure code. It supports Terraform, Cloudformation, and Azure ARM resources.

kics: https://github.com/Checkmarx/kics

Cost:

Details about the meeting on this thread: https://github.com/Checkmarx/kics/discussions/5675

We have a request in KICS (Keep IaC secure, https://github.com/Checkmarx/kics) to support AWS 4.0 provider and I wondered how fast did people adopt it and did the required changes.

I use ZAP [1] with the OAST add-on for this at the moment. I admit the UX isn't perfect, but it serves my purpose.

If I also want control over the responses (e.g. return a 401 status code for every fifth request), I have a custom extender script [2] for that.

[1]: https://www.zaproxy.org/

Implement tools like Burp Suite or OWASP ZAP for in-depth security scanning of your APIs.

OWASP ZAP

The use of capital punctuation implies a warning? an alert? Would this same response be warranted for Burp which is also a commercial, closed source product?

If this is an issue for some, then ZAP being open source[1] maybe favourable.

That said, Burp is the defacto tool for a reason - it's best in class. Every pentester I know, including myself, has a paid subscription. The fact that it's closed source hasn't been an issue.

[1] https://github.com/zaproxy/zaproxy

Briefly reviewed your product. Seems like OWASP ZAP is your competition: https://www.zaproxy.org/

It runs entirely in the browser so it uses the browser "native" frameworks.

Dynamic analysis involves testing your application while it's running. Tools like OWASP ZAP and Burp Suite can help identify vulnerabilities like SQL injection or Cross-Site Scripting by sending malicious requests to your application and analyzing the responses.

> Lying is not an embellishment or puffery, it's a lie. Engaging a company for a 3 day pen test that's totally insufficient, that would be an embellishment.

I agree, but if the RFP question was phrased "have you done penetration testing?" then that leaves a lot of room for embellishment. If the question is "do you have SOC2 certification?" and you answer "yes" untruthfully, then that is a lie. If they ask for the SOC2 or pentest report and you give them a falsified document, that's where you're (probably) committing fraud.

> One of the most important part of pen tests is that they are external.

AWS/Google/etc have internal security teams doing their pen tests, so no, this isn't true.

> Just doing your job as an engineer and looking for bugs is not a pen test.

What about an engineer spending an afternoon running ZAP[0]?

> It's like saying, "what is an audit really? We have accountants and they check our books for anomalies."

Yeah, which is why you don't just ask a company "do you keep track of your finances?" if you're investing in them, you request external auditors.

[0] https://www.zaproxy.org/

In addition to manual security reviews, you can also implement DevSecOps practices to automate security checks. For example, you can set up a CI/CD pipeline to run static code analysis tools like CodeQL and automatically run penetration tests using tools like OWASP ZAP.

OWASP ZAP (open source)

I would start by installing Burp Suite or OWASP Zap and seeing what the actual messages look like