Sken vs StackHawk

Sken adds capabilities above and beyond what StackHawk provides.

StackHawk and Sken offer different capabilities for application security testing.

StackHawk is focused on run-time application security testing through DAST, and provide no coverage for source code or open-source dependency checks.

Sken.ai uses a combination of known vulnerability data, source code scanning for dependencies, code scanning for bugs and run-time web application scanning for a comprehensive view of application security.

Sken also correlates across these different application security testing methods to weed out false positives and identify real issues that have an impact on the security posture of the application.

StackHawk Provides:

Dynamic scanning of deployed/production applications with DAST

StackHawk does not (while Sken does) provide:

Finding vulnerabilities introduced by your dev team with SAST
Understanding of known vulnerabilities based on a set of rules
Understanding of unknown security issues, including OSS, application code and third-party interfaces.
Lower false positives via correlation of source code scanning and run-time application security testing