canonical: https://jentic.com/apis/tenable.com/attack-surface-management

# Tenable Attack Surface Management

Attack Surface Management API. The API exposes 74 endpoints secured with apiKey authentication.

## For AI agents

Programmatically download export, export assets in xlsx format. Covers 74 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Download export
- Export assets in XLSX format
- Move or copy specific assets
- Query and filter Attack Surface Management records by parameters
- Monitor Attack Surface Management operational status and events

## Use cases

### Developer Tools Operations

Use the Attack Surface Management to perform developer tools operations programmatically. The API provides 74 endpoints covering core functionality including download export, export assets in xlsx format, export assets in csv format.

Example prompt: Call POST /export/download to download export

### Automated Tags Management

Automate tags operations by combining multiple Attack Surface Management endpoints. Agents can export assets in xlsx format and then export assets in csv format in a single workflow.

Example prompt: Call POST /assets/export/xlsx to export assets in xlsx format, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Attack Surface Management endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'download export', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /export/download | Download export |
| POST | /assets/export/xlsx | Export assets in XLSX format |
| POST | /assets/export/csv | Export assets in CSV format |
| POST | /assets/export/json | Export assets in JSON format |
| POST | /sources/export/csv | Export source list in CSV format |
| POST | /sources/export/xlsx | Export source list in XLSX format |
| POST | /asset/bulkmove | Move or copy specific assets |
| POST | /asset/bulkmovefilter | Move or copy filtered assets |

## Key resources

- **Tags** — Interact with tags.
- **Sources** — Access source lists and results.
- **Assets** — List assets with IP address, hostname, port and unique hash.
- **Assets Bulk Operations** — Operations related to Assets Bulk Operations
- **Alerts** — Get alerts for subscriptions.

## Why Jentic

- **Setup:** Wiring Tenable Attack Surface Management by hand means learning its API-key header auth against the asm.cloud.tenable.com host and handling export and bulk-move calls yourself. Through Jentic you install once, import Attack Surface Management from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Attack Surface Management targets travel in request bodies and query filters rather than a resource id in the URL path, so limit the agent to the operations it needs, such as exporting assets or downloading a report. You choose the operations it may call, so bulk-move operations are not included unless you add them.
- **Credential handling:** Your Attack Surface Management API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'export assets to CSV' or 'download a source report', and Jentic returns the matching Attack Surface Management operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Attack Surface Management use?

The Attack Surface Management uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I download export with the Attack Surface Management?

Yes. Use the POST /export/download endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Attack Surface Management?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I download export through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'download export'. Jentic returns the matching Attack Surface Management operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Attack Surface Management have?

The Attack Surface Management exposes 74 endpoints covering tags, sources, assets operations.

### Can I limit what my agent is allowed to do with the Attack Surface Management API?

Yes. Because you run Jentic One yourself, you decide which Attack Surface Management operations your agent may call and which API key it uses, so you can allow read-only work like exporting assets to CSV, XLSX, or JSON and downloading source reports while excluding everything else. Since this API carries its targets in request bodies and query filters rather than in the URL path, the boundary is the set of operations you approve, and destructive bulk-move actions such as POST /asset/bulkmove and POST /asset/bulkmovefilter stay off unless you add them. Your API key is injected at execution time under your own rules and never enters the agent's prompt, logs, or context.