Tenable Attack Surface Management
Browse all Tenable APIs63
AI ReadinessAI-Aware (B-)63/100
Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey74 EndpointsREST
For Agents
Programmatically download export, export assets in xlsx format. Covers 74 operations with apiKey authentication.
Use for: I need to download export, I want to export assets in xlsx format, Search for export assets in csv format, Find all export assets in json format
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Attack Surface Management API. The API exposes 74 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Attack Surface Management to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Attack Surface Management, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftenable.com%2Fattack-surface-management" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftenable.com%2Fattack-surface-management" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Attack Surface Management API.
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
Patterns agents use Attack Surface Management API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'download export', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
74 endpoints — attack surface management api.
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
Attack Surface Management
- AI-Aware (B-)63/100
99
Foundational Compliance72
Developer Experience & Jentic Compatibility44
AI-Readiness & Agent Experience90
Agent Usability50
Security61
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
95%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
72
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
16%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
71%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
44
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
49%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
74%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
51%
Summary Coverage
Coverage of summaries across operations/tags/info.
90
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
90%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
61
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
61%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Attack Surface Management API through Jentic.
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.
GET STARTED