> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.method.security/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.method.security/_mcp/server.

# Run your first Operation

> Launch an internet-based investigative Operation using Method-maintained resources

This guide walks you through launching your first Operation for an internet-based investigation. Operations can be investigative or offensive in nature. The steps below focus on an investigative workflow to get you started.

---

## Prepare your Environment

We recommend creating a dedicated Environment for this and other tutorials to keep your tutorial data separate from production data. See how to do so by following the [Create an Environment](/guides/platform-setup/create-a-new-environment#create-a-tutorials-environment) guide.

## Start an Operation

From the left sidebar, click **Operations** to open the Operations homepage.

Alternatively, click the **lightning bolt** icon in the left sidebar and select **Start an Operation**.

![Quick-action menu showing the Start an Operation option](/_fern-files/_img/58f5104cd00d61ff0b21373076c8299c6ec8a700795bf5575469ca0d4bbd99e8.webp)

From the Operations homepage, you can view all active Operations across your organization. Click any row to jump into a live Operation, or filter by user and Environment to find a specific session. Use the tabs to browse Operation Plans, Reports generated in the platform, Adversaries, and Completed Operations.

The **Suggested targets** panel on the right surfaces validated targets from Method Agents, so you can start an Operator session with a pre-selected starting point.

![Operations page showing active sessions and suggested targets](/_fern-files/_img/77ba0b19b3b84c97c4d216697addbeb844c03593b20d57db1e1cbada46e9e59d.webp)

## Begin a new Operation

Click **New** in the top-right corner of the Operations homepage to open a fresh Operator workspace.

![New Operation form showing Details, Entry point, Intelligence, Rules of Engagement, and Object Watch steps](/_fern-files/_img/0c4bf8999d9001c02c35b418db930a9e5501154a9a05b1f4c3fdb8ec1d2531e6.webp)

## Configure your Operation

The following example walks through an internet-based reconnaissance and investigation of several web services.

1. Name your Operation: `<yourname>-first-tutorial`
2. Provide an **Objective**: `Discover and enumerate web and network resources under wayneindustries.xyz`

![Operation setup form with name, mode, and objective fields](/_fern-files/_img/4eab7fce3ea8354721d31ed944bf6bd0ebad8713f33802f219ec16d969656a7e.webp)

3. Specify the **Entry point**:

   a. **Environment**: `<yourname>-first-tutorial`
   b. **Access vector**: Cloud Agent
   c. **Starting points**: with `FQDN` selected, add `wayneindustries.xyz`

![Entry point configuration with Environment, access vector, and starting points](/_fern-files/_img/0b72205811209c171f47b489bc9e4109bb3828fc063a3e2a5d09732adf74bed8.webp)

4. Skip the **Intelligence**, **Rules of Engagement**, and **Object Watch** sections.

5. Click **Begin Operation**.

## Run your first Tools

1. Run the **Passive Subdomain Discovery** Tool to enumerate `wayneindustries.xyz`'s subdomains. Select it from the search box and click **Run**.

2) Next, run a **Port Scan** against the discovered subdomains.

   Before executing, configure the Tool by selecting the input Object type (CIDR Range, IP Address, or FQDN), choosing a source for input Objects (Full Lineage, Parent only, Filtered set, or Manual), and setting optional parameters like specific ports to scan.

   The execution count shows how many times the Tool will run based on your selected inputs, so you can verify the scope before clicking **Run**.

![Port Scan configuration panel showing input object type, source, and optional parameters](/_fern-files/_img/493f6089f413f592f2ae99f86e63bc5b719499dfcb67b8a5e46f3984953e1867.webp)

3. Once a Tool completes, click the node to review the Objects created, any Findings surfaced, and the knowledge graph. You can also inspect raw execution details if you want to dig deeper.

![Tool execution results showing created Objects](/_fern-files/_img/91c5b07cac6f9c09756d2faac99d099991babb62b115f1725142b4aed4932e28.webp)

4. Continue by picking your next Tool. Click the arrow on any completed node and select **Choose next tool**. Configure parameters if needed, then click **Run**. Repeat this cycle to build out your Operation graph and expand your investigation.

## Next steps

This tutorial covered the basics of running an investigative Operation in Operator. Continue the Operation against these cloud-hosted resources, start a new one against new targets (for example, a new FQDN, IP, or CIDR), or deploy a [Jackal](/guides/platform-setup/install-a-jackal) and launch an Operation from an installed access vector.