Book a demo
See Red Kite on your own perimeter.
Pick a time that suits your team. After a first meeting, we run Red Kite on part of your perimeter, then walk you through what we found in a demo.
What to expect
Pick a time
Book a slot for a first meeting to get to know each other and talk about your needs. You’ll get a calendar invite right away.
We map your perimeter
After that first meeting, we run Red Kite’s discovery on part of your attack surface: the same reconnaissance an attacker would do, like finding hosts, open ports and services. We don’t try to exploit anything.
We show you what we found
In the demo, we walk you through the platform with your own assets and answer your questions.
Discovery call
Prefer that we reach out?Leave your work email and we’ll get in touch to find a time.
Red Kite adapted easily to our organisation’s needs and helped us automate the monitoring of our external perimeter. We’ve been astonished by its level of customisation.
Frequently asked questions
We already have an EASM tool. How is Red Kite different?
Red Kite was built by offensive security professionals, and it goes beyond discovery: it checks every asset against best practices, rechecks fixed issues to make sure they don’t come back, and lets you add your own test cases. Every finding shows how it was obtained, so your team can verify it. The best way to compare is to bring your current results to the demo and compare them with what Red Kite finds.
Who should join our discovery call?
We recommend inviting whoever is responsible for securing your external attack surface, whether that falls to offensive security, vulnerability management or another team, and one person who would use Red Kite day to day.
Do we need to install anything?
No. Red Kite works from the outside, the way an attacker sees you. There is no agent or appliance to install, and nothing to set up on your side for the demo.
What do you do with our data after the demo?
We only use it to prepare and run your demo, and we never share it. Once the demo is over, we delete it.