Regression testing
Fixed once. Fixed for good.
Red Kite turns every finding you fix into a test case that keeps running, and alerts you as soon as an issue comes back.
Exposed Remote Desktop (RDP) server
remote.example.com:3389
Detected
Mar 3
Found during continuous discovery.
Fixed
Mar 5
Port closed by the infrastructure team.
Verified
Mar 6
Re-checked and confirmed closed.
Reappeared
Jun 12
Server rebuilt from an old image.
Finding reopened · team alerted
Every fix becomes a test
Regression testing means rechecking the issues you’ve already fixed, so a configuration change, a redeploy or a restored backup can’t quietly bring them back.
- 01
Fix the issue
Your team closes a finding: a port is closed, a service is patched, a page is taken down.
- 02
Red Kite keeps checking
The same test case keeps running on that asset, and on any new asset like it.
- 03
Catch it if it comes back
If the issue reappears, the finding reopens and your team is alerted.
Why fixed issues come back
A fix only lasts until the next change.
Redeployments undo fixes
A server rebuilt from an old image or template brings back the configuration you fixed.
Changes happen outside security
A firewall rule opened for a test, a vendor update, a rollback: your perimeter changes without security knowing.
Processes depend on people
Change management, hardening checklists, decommissioning: each relies on someone doing every manual step right, every time. One missed step and the issue is back.
Retesting is manual
Checking every past finding by hand takes time nobody has, so it doesn’t get done.
Make your fixes count
Every vulnerability you fix is time and money invested. Regression testing protects that investment.
Protect your remediation work
Make sure the effort spent fixing issues isn’t lost at the next change.
Catch issues early
Know when an issue returns instead of discovering it at the next audit.
Prove issues stay fixed
Show auditors and leadership what was fixed, and that it stayed fixed.
When nobody checks twice
Without regression testing, every fix is temporary until proven otherwise.
Without regression testing
- Fixed issues quietly come back after a change
- The same findings reappear in every pentest report
- You learn about a regression from an attacker or an auditor
- No record of when an issue came back, or for how long
With Red Kite
- Every fix becomes a test case that keeps running
- Regressions reopen the finding and alert your team
- Issues are caught before the next pentest or audit
- A full history of each finding, from detection to fix
Regression testing on your whole perimeter
Rechecking fixes works best on top of a complete, always up-to-date view of what you expose.
Covers assets you don’t know about
Test cases also run on newly discovered assets and shadow IT, not only on the ones in your inventory.
Your test cases, your rules
Turn any finding, including those from your pentest reports, into a test case that keeps running.
Fixes are verified, not assumed
A closed ticket doesn’t mean the issue is gone. If a fix didn’t work, Red Kite finds the issue again the next time the test case runs and flags it as a regression.
Fits your workflow
Regressions go straight to your service desk, where your team already works.
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
How long does onboarding take?
Onboarding is simple: all we need is an email address, and nothing else is required on your side. You can start using Red Kite within an hour.
Can I integrate Red Kite with enterprise software?
Red Kite integrates natively with many enterprise tools, such as SSO and SIEM platforms. It can also connect to any in-house application through custom integrations.
Does Red Kite provide an API or an MCP server for my automations and agents?
Yes. Red Kite has a robust, well-documented API to integrate with your tools, and an MCP server to connect it to your AI agents.
Start with a proof of value.
We scope a short pilot on one or two entities, compare what we find against what you already know, and then you decide.
Week 0
Scope
Together, we pick one or two entities and the domains and IP ranges to start from.
Week 1
Discover
Red Kite maps those perimeters and keeps them under continuous watch.
Weeks 2–4
Review together
We walk your team through the findings, including the assets nobody had on their list.
Week 4
Decide
You compare what we found with what you already knew, and decide whether to continue.
4 weeks from kickoff to decision.