Data isolation
Sokendi is multi-tenant by design. Every customer organization gets its own Postgres schema, and row-level security is enforced at the database layer, so one customer's data can't leak into another's.
Your organization is identified from your verified sign-in, never from a value your browser sends. Plan limits and module access are checked by the API on every request, not hidden in the interface.
Public vulnerability data, such as the National Vulnerability Database and CISA's Known Exploited Vulnerabilities catalog, is downloaded once and shared across the platform because it is public. Nothing about your organization is stored with it or sent to fetch it.
Encryption and secrets
- All traffic to the dashboard and API is encrypted with TLS.
- Connections between our own services, such as to the database and the secrets manager, are encrypted with TLS too.
- Agents talk to the platform only over encrypted connections. The live connection that delivers commands to an agent uses mutual TLS: both sides prove their identity with certificates before anything is sent.
- Platform signing keys and secrets are held in HashiCorp Vault, not in plaintext on disk or in source code.
- Passwords are never stored. We store a one-way hash, using a deliberately slow algorithm designed to resist cracking.
Agent security
The Sokendi agent runs on your hosts, so it is built to be trustworthy there.
- Each agent enrolls with an enrollment token that expires within 24 hours and is single-use by default (your admins can issue a token for a set number of hosts). The agent then receives its own credentials. A revoked agent is disconnected at once and can no longer connect or send data.
- Every command sent to an agent is signed by the platform, and the agent verifies the signature before acting on it.
- Agent updates are signed and checksum-verified before they are installed. An update that fails verification is refused.
- An agent can only report for itself. Each report must carry the agent's own credential and a valid signature, and every record in it must name that agent and organization, so one host can't send data on behalf of another host or another organization.
- Remote actions on an agent, such as an on-demand scan, a query or a remediation step, only run if your organization's agent policy allows them and the person asking has the required role. Each one is recorded in your audit log.
Scan safety
- Active scans only run against domains your organization has verified it owns, by publishing a DNS record we check. Scans against anything else are refused by the platform.
- Each plan can verify a set number of domains, and only that many are scannable. Pro and higher plans also require business verification before any active scan runs: business details on file, a verified domain, and an admin who signs in with an email address on that domain.
- We re-check that DNS record every few days. If it can't be confirmed for 7 days, after at least two failed checks in a row, the domain is no longer treated as verified, and scans against it stop until you verify it again. This is recorded in your audit log.
- Scans are queued to a separate, sandboxed scan plane rather than running on the API server, so active and intrusive modules never share a host with your dashboard or your data.
- Some scan modules look up public threat intelligence (for example, vulnerability databases or known data breaches). Those lookups send only what the lookup needs, such as a vulnerability identifier, a product name, or an email address on one of your verified domains. Annex C of our Data Processing Agreement names each service.
Account security
- Sign-ins use short-lived access tokens. The longer-lived session token is kept in a secure, HttpOnly cookie that page scripts can't read, and it is replaced every time it is used. If an old session token is ever reused, the session is ended.
- After repeated failed sign-in attempts, sign-in for that account is paused for 15 minutes.
- You can protect your sign-in with two-step verification: a passkey or security key, or a code from an authenticator app, with single-use recovery codes as a backup. Some sensitive actions ask you to confirm it's you again.
- Changing your password, or deleting your organization, requires your current password. Changing or resetting your password ends every session: other devices are signed out within 15 minutes, when their short-lived access expires.
- Email verification and password reset links work once, expire (after 24 hours and 1 hour), and requesting a new link cancels the previous one.
- Live dashboard updates use a single-use ticket that is tied to your session and network address, and the connection closes when your session expires.
- Roles control what each team member can see and do, and are enforced by the API, not just the interface.
- Every request for your organization's data must carry a verified sign-in, or come from an enrolled agent using its own credentials. Sokendi doesn't issue shared or long-lived API keys.
Access to your data
Sokendi staff do not browse customer data. If our support team needs to view your organization to resolve an issue, that access is limited to platform administrators, uses separate temporary credentials, and is recorded in your organization's own audit log, so you can see when it started and ended. While viewing your organization, staff can't change your team members, their roles, or anyone's password.
Audit logging
Account and administrative actions are recorded to your organization's audit log, with who did them and from which address: for example team and role changes, password changes, enrollment tokens, agent revocation, remote actions on agents, and support access. Organization admins can review it from the dashboard and export it as a CSV file; each export is itself recorded in the log.
Audit log entries are kept from 90 days on Free up to 7 years on Enterprise, and never less than 90 days while your organization exists. The Sokendi application itself can add entries but can't change or delete them: this is enforced by the database, not just by our code. Only a separate, restricted retention process removes entries, once they are older than your plan's retention period.
Incident response
If we discover a security incident affecting your data, we will notify affected customers without undue delay, tell you what we know and what we are doing about it, and keep you updated until it is resolved. We report incidents to regulators where the law requires it.
Reporting a vulnerability
If you believe you have found a security issue in Sokendi, please email [email protected]. Include what you found, the steps to reproduce it, and its potential impact. We aim to acknowledge reports within 3 business days.
When testing, please:
- Only test against your own account and organization.
- Don't access, change, or delete data that isn't yours, and stop as soon as you reach someone else's data.
- Don't run denial-of-service, spam, or social engineering tests.
- Give us reasonable time to fix the issue before disclosing it.
We won't pursue legal action against researchers who follow these guidelines in good faith.