The rules for using the CyberOwl site and platform, and what a penetration test does and does not tell you.
In force since
In short
Use CyberOwl to test systems you are entitled to test, and treat what it shows you as confidential. A penetration test is a point-in-time assessment: findings are leads to fix and verify, and a clean result is not proof that nothing is wrong. Where your organization has a signed agreement with Nexa, that agreement governs the work and comes first.
01
What these terms cover
CyberOwl is a penetration testing platform operated by Nexa. These terms apply to the public site at nx-cyberowl.com, to the platform behind it, to its API and to the reports it produces. By creating an account or using the platform you accept them.
The testing itself is delivered under an agreement between your organization and Nexa: a services agreement, a statement of work, or an accepted proposal. Where that agreement and these terms differ, the agreement prevails.
02
Your account
Register with accurate details and an email address you control; you confirm it before the account becomes active.
A new organization is reviewed by Nexa before it gets access. Members join an existing organization by invitation from its administrator.
Each account is for one person. Do not share it, and keep your password and recovery codes to yourself.
You are responsible for what happens under your account. If you think someone else has used it, tell your administrator and write to us.
An organization's administrators decide who its members are and what role each one holds.
03
Authorization to test
A penetration test is only lawful when the owner of the system has agreed to it. When your organization requests a campaign, it confirms that:
it owns every asset placed in scope, or has written permission from the owner to have it tested;
where an asset runs on infrastructure operated by someone else, that operator's testing rules allow it;
the people requesting the work are entitled to authorize it.
Nexa tests what is in the agreed scope, during the agreed window, under the agreed rules of engagement. Tell us before work starts about anything that must not be touched, and tell us at once if scope changes.
04
How you may and may not use the platform
The platform exists so weaknesses can be found and closed. Using it for anything else is out of bounds:
Do not put systems in scope that you are not entitled to test.
Do not use a finding to attack anything. A finding describes how a weakness was reached so it can be fixed, not so it can be used again.
Do not try to reach another organization's data, go around the role you were given, or get past rate limits.
Do not upload anything unlawful. Evidence that contains malicious code belongs only in the finding it documents; uploads are scanned and infected files are blocked.
Keep API keys on your servers, out of browser code and public repositories, and revoke one as soon as it is exposed.
Do not resell access, copy the platform, or use it to build a competing service.
Actions in the platform are recorded with the user, the address and the time. Misuse is traceable, and it is grounds for suspending access.
05
Findings are confidential
Findings, evidence and reports describe how to break into real systems. Inside the platform they are visible to the members of the organization they belong to, to the testers assigned to that work and to the Nexa staff who run it.
Share reports and exports only with people who need them, and store them as the sensitive material they are.
Evidence can contain personal data from the tested system. Handle it under your own data protection obligations.
Nexa does not share an organization's findings with other customers and does not publish them. The providers that help run the platform, and what each one receives, are listed in the privacy policy.
06
What a penetration test is, and what it is not
It is a point-in-time assessment. It reflects the system as it was during the testing window. A change deployed the next day is not covered.
It is bounded by scope and time. Testers look where the agreement says, for as long as it says. What was out of scope was not assessed.
A clean result is not proof of security. Not finding a weakness does not mean none exists.
Severity is a judgment. Scores and impact ratings rank what to fix first. They are inputs to your own risk decisions, not a substitute for them.
A retest verifies a specific fix. It confirms the reported weakness is closed; it is not a new assessment of the whole system.
AI suggestions are advisory. Where AI features are on, they propose; a person decides.
Fixing is yours. We describe the weakness and recommend a correction. Deciding, implementing and deploying it is the responsibility of the system's owner.
07
Your content and ours
What your organization puts into the platform stays yours: its scope, its assets, its comments and its remediation notes. The platform, its software and its design stay Nexa's. Who owns the reports and other deliverables, and how they may be used, is set out in your agreement with Nexa.
08
Availability and changes to the service
We work to keep the platform available, and we take it offline briefly to deploy new versions. Features change as the product develops. Any commitment about availability or support hours is the one in your agreement; these terms do not add one.
09
Integrations and third-party services
The platform can be connected to other tools: webhooks, an issue tracker, a chat channel, or your own code through the API. What those tools do with the data they receive is governed by your arrangement with them, and you are responsible for the destinations you configure.
10
Suspension and closing an account
We can suspend an account or an organization that breaks these terms, that puts other customers at risk, or whose credentials appear to be compromised. Where we can, we tell the organization's administrator first.
You can ask us to close your account at any time. The privacy policy explains what is removed and what is kept when that happens.
11
No warranty and limitation of liability
The platform and its findings are provided for authorized security assessment purposes only. They are based on what could be observed during the assessment and may not reflect every weakness in a system. They are provided as-is, without warranty of accuracy, completeness, timeliness or fitness for a particular purpose.
Recipients are responsible for validating findings and for implementing remediation in line with their own security frameworks and regulatory obligations. To the extent the law allows, Nexa assumes no liability for actions taken on the basis of findings or reports. Where your organization has a signed agreement with Nexa, the liability terms of that agreement apply instead of this section.
12
Not legal or compliance advice
The platform reports what our testers observed. Decisions about incident response, notification duties, regulatory compliance and remediation belong to your organization and its own legal and security advisors. Nothing here is legal advice, and a report is not a certification.
13
Changes to these terms
When these terms change we publish the new version here and update the date at the top of the page. Material changes are announced to customer organizations. Continuing to use the platform after a change means you accept the new version.
14
Contact us
Questions about these terms: [email protected]. Related pages: the privacy policy, which explains what personal data the platform holds, and the security page, which lists the controls the platform enforces and how to report a weakness.