Acceptable Use Policy

Tyrian provides isolated, self-contained laboratory environments for the purpose of authorized security training, detection engineering, and purple-team exercises. Every lab is a synthetic environment provisioned by Tyrian for your account.

You may only conduct offensive actions against assets that exist inside your own Tyrian-provisioned lab. Before any lab launches, you must attest that you will only target lab-owned assets. This consent is recorded with your identity and a timestamp.

You must not use Tyrian, its tooling, or any output from it to do any of the following:

• Target, scan, exploit, or attack any system, network, account, or asset you do not own or lack explicit written authorization to test — including systems outside your Tyrian lab.
• Attempt to defeat, bypass, or disable the platform's isolation, egress controls, tenant boundaries, or audit logging.
• Use lab-hosted command-and-control, tooling, or infrastructure to reach, relay to, or affect the public internet or any third party.
• Exfiltrate, stage, or transmit real production data, personal data, or another party's confidential information into or out of a lab.
• Develop, stage, or distribute malware, ransomware, or exploits for use outside the contained lab environment.
• Conduct denial-of-service activity against any target other than a designated in-lab asset, or attempt to cause harm to shared platform infrastructure.
• Resell, sublicense, or provide range access to third parties except as expressly permitted by an MSSP or reseller agreement.

Tyrian enforces containment at the infrastructure level so that misuse is structurally difficult, not merely discouraged:

• Default-deny WAN egress on every lab subnet, with only an explicit allowlist permitted.
• Command-and-control callbacks resolve exclusively to in-lab redirectors and never touch the public internet.
• Scenarios that require 'the internet' are served by simulated services, never live egress.
• Each session, virtual machine, subnet, and evidence object is scoped to a single tenant and cannot reach another tenant's resources.

Tyrian's golden images include only open-source or freely redistributable tooling. Commercial tools are bring-your-own-license and are installed via a post-boot license-injection step. You are responsible for holding valid licenses for any commercial software you introduce and for complying with its terms.

Platform actions — provisioning, connections, snapshots, teardown, and interactive sessions — are logged immutably, and remote sessions may be recorded for evidence and audit. We may review this data to investigate suspected violations of this policy.

We may suspend or terminate access, tear down running labs, and preserve relevant logs where we reasonably believe this policy has been violated. Serious violations may be reported to the appropriate authorities. Violation of this policy is a material breach of the Terms of Service.

If you become aware of misuse of the platform, or discover a security vulnerability, please contact us immediately at security@tyrian.io. We investigate all good-faith reports.