Security

Security & Data Ownership

This page answers the questions a technical evaluator asks before installing KEEP on a live network: what data stays on your own infrastructure, what KEEP as a vendor ever sees, who is responsible for backups, and how to remove an evaluation deployment if you decide not to continue.

What data remains local

The software KEEP installs at a client site keeps no database of its own. It discovers and polls devices on that network, then sends what it finds to your own Hub — the central server your organization runs. Nothing meaningful is retained on the client-site device itself between polling cycles. (Source: KEEP architecture documentation)

Your Hub's database is the system of record for everything KEEP discovers about your clients' networks — device inventories, incidents, scan results — and it runs on infrastructure you control, not on servers KEEP operates. (Source: KEEP architecture documentation)

If you manage more than one client site, each site reports only to your own Hub — never to KEEP directly, and never to another organization's Hub. (Source: KEEP architecture documentation)

What reaches the Control Plane

KEEP's Control Plane — the service that handles evaluation access, accounts, and licensing — is designed to receive only account, licensing, and deployment-identity information. It does not receive the operational data your network monitoring produces: no device inventories, no incidents, no scan results. (Source: KEEP Control Plane architecture documentation)

Where setting up a deployment requires network configuration details, those details are used only to prepare your installation package and are not retained afterward. (Source: KEEP Control Plane architecture documentation)

Authentication and trust boundaries

Every device that joins your network is explicitly authorized by your own administrator before it can connect — KEEP's Control Plane has no ability to authorize a device on your network by itself. (Source: KEEP architecture documentation)

Your team signs in through your own identity provider — Active Directory, LDAP, or single sign-on — or through a KEEP-native account. Multi-factor authentication is available for KEEP accounts. (Source: KEEP application security architecture)

Data storage responsibilities

Your Hub's database is backed up automatically, and backups are encrypted so that only you — or whoever you designate — can decrypt them. KEEP does not hold a copy of your backups and plays no role in your disaster recovery. (Source: KEEP backup and disaster recovery architecture)

You are responsible for securely storing your own recovery key and for keeping a copy of your backup somewhere other than the Hub itself. (Source: KEEP backup and disaster recovery architecture)

Evaluation removal process

If you decide not to continue after evaluating KEEP, a complete removal procedure exists for the software and data on your own infrastructure, and it has been verified against a real evaluation installation. (Source: KEEP Evaluation Program documentation)

Evaluation Considerations

Continue to Capabilities

For what KEEP does today, grouped and labeled Current, Planned, or Unknown, see Capabilities.