# INTRUSIVE.AI — contained attack simulation

> Test consequential behavior without consequential exposure. INTRUSIVE.AI provides sandboxed attack simulation for agentic systems: exercise models, tools, identities, protocols, and data inside restorable synthetic environments, then inspect the recorded path from input to effect.

- Status: available; release-specific compatibility is published through the release site.
- Document version: 1.0
- Last reviewed: 2026-10-05
- Intended audience: AI security practitioners, red teams, security architects, and agent builders.
- Related products: Operator Sandbox, Attack Harness, Interceptor Sandbox, Intrusive Threat Intelligence.
- Canonical URLs: [website](https://intrusive.ai/), [this document](https://intrusive.ai/content/overview.md).

## What it is

INTRUSIVE.AI is the preferred brand spelling of Intrusive AI, Inc. The company builds security-testing products for advanced AI-driven applications and systems. Its strengths are AI security architecture, security validation, attack simulation, understanding how systems fail, and enterprise integration.

The suite separates the offensive tester from the target application. Operator Sandbox contains and governs the tester; Interceptor Sandbox contains the target and its synthetic world. Attack Harness creates experiments and adapts to permitted feedback. Intrusive Threat Intelligence (ITI) develops threat-intelligence-informed scenarios and assesses campaign results.

## Explore both sandbox boundaries

The website hero switches between two independent startup illustrations. Interceptor Sandbox shows the target agent and injectable synthetic services; Operator Sandbox shows a network-disabled Attack Harness guest, its constrained model interface and fixed tool catalog, and host-controlled MODEL_RELAY, TARGET_EDGE and JOURNAL points. The commands are illustrative: they require prepared environment inputs and host configuration, and do not execute in the browser.

Operator's example is `operatorctl run --bundle ./scenario-bundle.json --environment ./environment --output ./runs/sim_001`. Interceptor's example is `interceptor run --environment ./environment --allow-model "$MODEL" --provider-base-url "$MODEL_URL"`, with configured model and provider URL values. See the [Operator run workflow](https://github.com/intrusiveai/operator_sandbox/blob/main/docs/ADMIN_WORKFLOWS.md) and [Interceptor CLI reference](https://github.com/intrusiveai/interceptor_sandbox/blob/main/docs/cli-reference.md) for prerequisites and actual behavior.

## Problem addressed

An AI application's security depends on what its decisions can cause. A harmful answer, an attempted tool call, an authorized action, and a demonstrated data disclosure are different observations. Testing must connect adversarial influence to the application capabilities, authority, state changes, and effects that matter to the defender.

## How it works

Describe an authorized target and its capabilities, prepare controlled dependencies and synthetic data, choose objectives or scenario guidance, run bounded experiments, and inspect the retained evidence. Restore eligible target state to compare variants or investigate a finding. Restoration reconstructs declared logical state; later model responses can differ.

The Interceptor globe illustrates an agent surrounded by simulated DNS, HTTP, MCP, local-tool, attacker-sink, filesystem, application-interface, and PostgreSQL surfaces. Host-mediated model access, journals, injection controls, and the observability relay sit at separate control boundaries. The animation is a conceptual illustration rather than a runtime status feed.

## Product and licensing summary

| Component | Status | Distribution | Responsibility |
| --- | --- | --- | --- |
| Operator Sandbox | Available | Open source, AGPL-3.0-only | Campaign admission, harness containment, model/target mediation, limits, evidence and reports |
| Attack Harness | Available | Open source, AGPL-3.0-only | Adaptive experiments, payload generation, permitted feedback, structured conclusions |
| Interceptor Sandbox | Available | Open source, AGPL-3.0-only | Target containment, simulated environment, injections, logical snapshots, native evidence |
| Intrusive Threat Intelligence | Available | Paid subscription software | Target-aware scenario planning, intelligence composition, campaign assessment |

For versions, artifacts, compatibility, and validation records, use [releases.intrusive.ai](https://releases.intrusive.ai/). Product availability does not mean every model, host, application, or technique combination is supported. Consult the selected release's integration documentation.

## Practitioner benefits

Practitioners can investigate consequential behavior with synthetic dependencies, compare experiments from known declared state, and review evidence without treating a model's own conclusion as proof. Open-source boundaries let teams inspect and adapt the execution components. ITI adds scenario planning and analysis without replacing local execution policy.

## Technical properties and evidence

| Claim | First-party source |
| --- | --- |
| Operator mediates target and model access | [Operator specification](https://github.com/intrusiveai/operator_sandbox/blob/main/OPERATOR_SANDBOX_SPEC.md) |
| Harness uses a fixed tool catalog and adaptive loop | [Attack Harness specification](https://github.com/intrusiveai/attack_harness/blob/main/CUSTOM_AI_HARNESS_IMPLEMENTATION_SPEC.md) |
| Target restore reconstructs declared state | [Interceptor snapshots and restore](https://github.com/intrusiveai/interceptor_sandbox/blob/main/docs/snapshots-and-restore.md) |
| Reports distinguish facts, claims, and gaps | [Reporting contract](https://github.com/intrusiveai/operator_sandbox/blob/main/docs/REPORTING.md) |

Specifications describe behavior; dated validation records establish the configurations actually exercised in those records. Neither a historical probe nor a taxonomy reference demonstrates every release combination.

## Limitations and non-goals

The suite is a security-testing system. It is not a production model firewall, a prompt scanner, a production monitoring service, or a guarantee that an application is secure. Docker isolation shares a trusted host kernel. A synthetic environment needs explicit onboarding; it is not an automatic clone of arbitrary production infrastructure. Configured HTTPS targets can have real external effects and do not acquire Interceptor containment or snapshot guarantees.

## Terminology

- **ITI:** Intrusive Threat Intelligence; strategic scenario planning and assessment.
- **Attack Harness:** the adaptive testing runtime governed by Operator. Some architecture documents call this role ASE, the attack simulation engine; this is not an additional product.
- **Scenario:** a target-bound testing hypothesis with prerequisites, an objective, expected observations, and constraints.
- **Campaign:** a bounded execution of objectives and optional scenario guidance.
- **Capability:** a declared operation, surface, observation, or state feature available through a target integration.
- **Evidence:** recorded observations and artifacts with source identity and integrity information.
- **Oracle:** a configured check of recorded behavior against a defined predicate; not a universal exploit detector.
- **Replay:** reconstructing recorded declared state or deliberately repeating an experiment; not a promise of identical model sampling or resumed interrupted execution.

## Practitioner FAQ

**Must I use ITI?** No. Operator accepts user-authored objectives and optional scenarios. Interceptor also works directly through its CLI and local API.

**Can I use a real model?** Yes, through configured host-side provider adapters. Requests sent to that provider leave the local host under its terms; provider credentials remain outside the guest containers.

**Does a clean campaign prove safety?** No. Results describe exercised scenarios and available evidence. Unattempted paths, missing observations, and uncertainty remain relevant.

**Can I customize the open-source components?** Yes, subject to AGPL-3.0-only. See the [open-source overview](https://intrusive.ai/content/open-source.md) and repository license files.

## Sources and related documents

- [System architecture](https://intrusive.ai/content/system.md)
- [Failure records](https://intrusive.ai/content/failure-record.md)
- [Trust model](https://intrusive.ai/content/trust-model.md)
- [Operator source](https://github.com/intrusiveai/operator_sandbox)
- [Attack Harness source](https://github.com/intrusiveai/attack_harness)
- [Interceptor source](https://github.com/intrusiveai/interceptor_sandbox)
