# START — Bring us an adversarial scenario that can't be left to chance.

> INTRUSIVE.AI works with AI security testers, red teams, and application builders on high-consequence evaluation problems. Start a technical conversation about the target, the behavior you need to investigate, and the evidence that would make the result useful.

- Status: technical conversations, engineering services and product access.
- Document version: 1.0
- Last reviewed: 2026-10-05
- Intended audience: security practitioners, authorized red teams, and application owners.
- Related products: all four suite components.
- Canonical URLs: [website section](https://intrusive.ai/#start), [this document](https://intrusive.ai/content/start.md).

## How to start

Contact [hello@intrusive.ai](mailto:hello@intrusive.ai). Describe the application, the authorized testing scope, its tools and dependencies, the boundary you want to test, and the effects you need to observe. Indicate model-provider and deployment constraints, relevant synthetic-data requirements, and what would establish a useful result. An architecture summary and minimal synthetic example are sufficient for an initial conversation; do not send credentials or customer data.

You can also start independently with the [Operator Sandbox](https://github.com/intrusiveai/operator_sandbox), [Attack Harness](https://github.com/intrusiveai/attack_harness), and [Interceptor Sandbox](https://github.com/intrusiveai/interceptor_sandbox) repositories. Use [releases.intrusive.ai](https://releases.intrusive.ai/) for matching artifacts and compatibility information. Operator accepts objectives and optional user-authored scenarios without requiring ITI; Interceptor can be used directly.

## Engineering services and ITI

Engineering services cover implementations of the suite, customized adaptations of the open-source components, and customized threat-intelligence adaptations of Intrusive Threat Intelligence. Engagement details are established through the technical conversation. ITI is subscription software for scenario planning and campaign assessment; its license is separate from the three AGPL-3.0-only components. This website does not specify a support SLA or promise a particular engagement outcome.

## Appropriate use and prerequisites

Use the suite for authorized security validation, red-team experiments, application evaluation, defensive research, and remediation testing. Establish permission for each target and each real external integration. Review application images, environment blueprints, fixed destinations, credentials, model-provider terms, and campaign stopping limits before execution. Replace business data and operational identities with synthetic fixtures wherever feasible.

Do not use the suite to target systems without authorization, obtain or disclose other people's private data without permission, or exceed an agreed scope. These are INTRUSIVE.AI's engagement and recommended-use expectations; they do not amend the rights or terms of the open-source licenses. A configured HTTPS target may have real effects, so authorization remains necessary even when the attack harness itself is contained.

## Report a security finding

Use the relevant component's GitHub Issues:

- [Operator Sandbox issues](https://github.com/intrusiveai/operator_sandbox/issues)
- [Attack Harness issues](https://github.com/intrusiveai/attack_harness/issues)
- [Interceptor Sandbox issues](https://github.com/intrusiveai/interceptor_sandbox/issues)

Give the affected release/platform, observed behavior, expected boundary, and a minimal synthetic reproduction. Issues are public; exclude credentials, customer data and private infrastructure details. Use the business contact for ITI inquiries or questions that do not map to an open-source component.

## Practitioner benefits, limitations and sources

A concrete target and evidence goal make it easier to choose suitable onboarding, simulation surfaces, scenario guidance and scope. Initial contact does not require handing over production access. Consult [system architecture](https://intrusive.ai/content/system.md), [open-source inspection](https://intrusive.ai/content/open-source.md), and [trust model](https://intrusive.ai/content/trust-model.md) before selecting a deployment. The [website privacy policy](https://intrusive.ai/privacy_policy.txt) describes how website visits and email inquiries are handled.
