Trust / Security
Security at CyberOwl
The controls the platform enforces, and how to tell us if you find a weakness in it.
In force since
In short
CyberOwl holds the weaknesses of our customers' systems, so it is built to be a hard target itself. This page lists what the platform enforces today, not what we intend to do. If you find a way around any of it, tell us.
01
Accounts and sign-in
- Passwords are stored only as scrypt hashes with a per-password salt, and must be at least twelve characters long.
- Two-factor authentication with an authenticator app is available on every account that signs in with a password, and is required by default for administrators and technical leads. Recovery codes are stored as hashes and work once.
- Google sign-in can be linked to an existing account. It cannot create one. An account linked to Google signs in only through Google, so its second factor is whatever that Google account enforces.
- Rate limits apply to sign-in, registration, password reset and two-factor verification, per account and per address. Repeated failures lock the account temporarily.
- New accounts confirm their email address before they can sign in, and a new customer organization is reviewed before it gets access.
02
Sessions
- Sessions are kept on the server. The browser holds only a random identifier, in a cookie that scripts cannot read, that is sent only over HTTPS, and that is not sent with requests made from other sites except when you follow a link to the platform.
- A session expires after 30 days unless the platform administrator sets a shorter or longer limit.
- Signing out ends that session. Deactivating an account or changing its role ends all of its sessions.
- When an administrator acts on behalf of a user for support, that session lasts at most one hour.
03
Access control and separation between customers
Access is checked against the organization you belong to and the role you hold. Roles can be granted for the whole platform, for one organization or for one campaign, so a tester sees the work they are assigned to and a customer sees only their own organization.
- Each role maps to an explicit list of permissions, and administrators can review the full matrix.
- Customer organizations have their own roles for administrators, managers and read-only viewers.
- API keys carry only the scopes chosen when they were created, never more than their creator has. They are stored as hashes; the full key is shown once.
04
Protecting what is stored and sent
- In transit: the site is HTTPS only, with strict transport security.
- Secrets: integration credentials, authenticator secrets and webhook signing secrets are encrypted with AES-256-GCM before they reach the database.
- Evidence and reports live in private file storage. Downloads go through the application, which requires a signed-in session and permission for the campaign the file belongs to.
- Webhooks are signed with HMAC-SHA256, so the receiver can verify a delivery came from CyberOwl.
- Browser protections: a content security policy that only runs scripts carrying a per-request nonce, a ban on framing the site, MIME sniffing disabled, a strict referrer policy, and camera, microphone and location turned off.
05
Uploaded files
Evidence is, by nature, material taken from systems under test. Every upload is scanned for malware before anyone can download it. A file that fails the scan is blocked, and a file whose scan has not finished is held back until it does.
Uploads are limited to an allowlist of file types, with a size limit per type and a limit on how many files one finding can carry.
06
Audit trail
Actions in the platform are recorded with the person who took them, what they affected, the IP address, the browser and the time. The record is append-only: the database itself rejects edits and deletions of its entries, so the application cannot rewrite it.
07
How we build and release it
Every proposed change is scanned for secrets. A change to the application's own code also has to pass:
- static analysis and a dependency audit;
- type checking, linting and the unit test suite;
- a database migration and restore check.
A release adds its own:
- the application images are built from the exact reviewed commit, scanned for high and critical vulnerabilities that have a fix available, and shipped with a software bill of materials;
- they are signed, and production verifies the signature and the commit before running them;
- the built images are exercised by the full end-to-end test suite before they can be promoted;
- a deployment takes a backup of the database and file storage first, applies migrations, checks the result, and only then exposes the new version. If a step fails before that point, it restores the backup and the previous release.
Dependencies are checked for updates every week.
08
AI features
AI features are off unless the platform administrator turns them on. When they are on, the text a feature works on is sent to a language-model provider to produce a suggestion or an answer; evidence files are not sent. Suggestions are advisory, and a person decides what happens to a finding. The privacy policy lists what each kind of feature sends.
09
The organization behind it
CyberOwl is built and operated by Nexa, whose information security management system is certified under ISO/IEC 27001.
10
What you can turn on today
- Two-factor authentication for every member of your organization, from each person's settings.
- Narrow API keys: one key per integration, with only the scopes it needs and an expiry date.
- Webhook verification: check the signature header on every delivery before acting on it.
- The right roles: give read-only access to people who only need to follow progress, and remove members who leave.
- Dedicated test accounts for our testers, rotated when the engagement ends.
11
Report a vulnerability
No system is perfectly secure. If you find a weakness in CyberOwl, write to [email protected] with “security” in the subject. English and Spanish are both fine.
What helps us act on it quickly:
- the address or feature affected, and the account role you used, if any;
- the steps to reproduce it, with the requests or a short recording;
- what an attacker could reach with it.
While you look, please:
- use only accounts you own, and stop as soon as you can see data that is not yours;
- do not degrade the service, send bulk traffic or run automated scans against production;
- do not use social engineering or physical access against our people or our customers;
- give us the chance to fix it before you tell anyone else.
This page covers the CyberOwl platform and its public site. The systems of our customers are not in scope: they are tested only under an agreement with their owner, as the terms of use explain.
12
Questions
For a security questionnaire, or anything this page does not answer, write to [email protected]. Related pages: the privacy policy, which explains what personal data the platform holds, and the terms of use.