Automatically built, prevents loading of unauthorized executables
Application whitelisting is not a new idea in security, and in a confined application the “known good” list is a very effective security against dropper attacks.
Hackers looking to upload new scripts, binaries or libraries into memory will be blocked as the whitelisting in comparing, in runtime, between each executable and the authorized list.
Karamba's secret sauce is the automatic process to map and build this whitelist. In very large applications with thousands of executables, only an automatic and granular building of the whitelist is practical to protect the code.
Given the dynamic nature of the supply chain Karamba XGuard Whitelisting has a built-in mechanism to allow external signed binaries from 3rd party as well as update diff from the image authority.
What is autonomous security and how does it provide superior runtime integrity protection? In this white paper, we explain how deterministic methods harden the runtime environment to prevent system hacking.
Karamba’s platform features CFI, whitelisting, on-premise or cloud-based management, customizable reporting and forensics. Plus it’s easy to deploy, and supports almost any platform, build environment, and architecture.
How does Karamba prevent hacking attempts? See a diagram of connected systems cybersecurity. Learn how Karamba eliminates the risks of false positives, performance drag, and security gaps.
41000 Woodward Ave
Building East, Suite 350
Bloomfield Hills, MI 48304
Tel: +1 248-574-5171
24 HaNagar Street
Tel: +972 9 88 66 113
Landstr. 264, Munich
Tel: +49 151 1471 6088