Cisco XDR Reputation API
The Reputation API from Cisco XDR — 1 operation(s) for reputation.
The Reputation API from Cisco XDR — 1 operation(s) for reputation.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/cisco-xdr-reputation-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: IROH-INT Enrich Reputation API
version: 1.0.107
license:
name: All Rights Reserved
url: https://www.cisco.com
contact:
name: Cisco Security Business Group -- Advanced Threat
email: cisco-intel-api-support@cisco.com
description: 'IROH Integrations: configure and query Threat Response modules'
x-provenance:
method: harvested
authored_by: Cisco XDR
harvested_by: API Evangelist
harvested_on: '2026-08-19'
first_party: true
note: Published by Cisco. Retrieved unmodified except for this x-provenance block.
provider_published: true
x-evidence:
- type: source
url: https://visibility.amp.cisco.com/iroh/iroh-enrich/index.html
- type: raw
url: https://visibility.amp.cisco.com/iroh/iroh-enrich/swagger.json
servers:
- url: https://visibility.amp.cisco.com/
security:
- iroh: []
- AuthorizationHeader: []
- oauth2:
- telemetry
- integration
- private-intel
- admin
- cognitive
- profile
- inspect
- asset
- event
- feedback
- sse
- registry
- users
- investigation
- invite
- casebook
- orbital
- enrich
- oauth
- vault
- response
- notification
- global-intel:read
- webhook
- ao
tags:
- name: Reputation
paths:
/iroh/iroh-enrich/reputation/observable:
get:
x-no-doc: false
tags:
- Reputation
description: '[required scopes](/iroh/doc/iroh-auth/#scopes): `enrich/observables/reputation:read`
This route queries intel modules with supplied `Observable` in order to calculate its `Reputation`'
responses:
'200':
description: Reputation verdict calculated for given observable
content:
application/json:
schema:
$ref: '#/components/schemas/EnvelopedReputation'
application/x-yaml:
schema:
$ref: '#/components/schemas/EnvelopedReputation'
application/edn:
schema:
$ref: '#/components/schemas/EnvelopedReputation'
application/transit+json:
schema:
$ref: '#/components/schemas/EnvelopedReputation'
application/transit+msgpack:
schema:
$ref: '#/components/schemas/EnvelopedReputation'
'401':
description: A `NormalizedError` including a `trace_id`
content:
application/json:
schema:
$ref: '#/components/schemas/NormalizedError-401'
application/x-yaml:
schema:
$ref: '#/components/schemas/NormalizedError-401'
application/edn:
schema:
$ref: '#/components/schemas/NormalizedError-401'
application/transit+json:
schema:
$ref: '#/components/schemas/NormalizedError-401'
application/transit+msgpack:
schema:
$ref: '#/components/schemas/NormalizedError-401'
'500':
description: A `NormalizedError` including a `trace_id`
content:
application/json:
schema:
$ref: '#/components/schemas/NormalizedError-500'
application/x-yaml:
schema:
$ref: '#/components/schemas/NormalizedError-500'
application/edn:
schema:
$ref: '#/components/schemas/NormalizedError-500'
application/transit+json:
schema:
$ref: '#/components/schemas/NormalizedError-500'
application/transit+msgpack:
schema:
$ref: '#/components/schemas/NormalizedError-500'
parameters:
- in: query
name: type
description: The type of observable.
required: true
example: ip
schema:
type: string
enum:
- file_path
- mac_address
- trend_micro_id
- cybereason_id
- process_args
- s1_agent_id
- device
- hostname
- certificate_common_name
- serial_number
- meraki_network_id
- url
- jamf_management_id
- certificate_serial
- intune_id
- meraki_org_id
- cisco_cm_id
- registry_key
- process_path
- darktrace_id
- process_username
- cortex_agent_id
- orbital_node_id
- process_uid
- ngfw_name
- user
- certificate_issuer
- ipv6
- email
- cisco_uc_id
- cvm_id
- sha256
- crowdstrike_id
- google_cloud_id
- google_chromebook_id
- acudid
- sha1
- registry_name
- md5
- service_now_id
- ip
- domain
- email_subject
- imei
- ngfw_id
- amp_computer_guid
- ms_machine_id
- secure_access_id
- mutex
- processor_id
- swc_device_id
- registry_path
- odns_identity
- odns_identity_label
- cisco_mid
- process_name
- pki_serial
- meraki_node_sn
- email_messageid
- imsi
- user_agent
- process_hash
- file_name
- in: query
name: value
description: The value of the observable.
required: true
example: 1.2.3.4
schema:
type: string
- in: query
name: mids
description: Use this parameter to query only some Modules passing their Ids
required: false
example:
- a78f09b4-16fa-4617-8bbf-f6044284ec0f
- 36716d80-2bd7-47fc-a179-cde2a0a8c5fe
style: form
explode: true
schema:
type: array
items:
type: string
summary: Enrich Observable Reputation
components:
schemas:
Technology:
example:
prevalence: Often
name: string
type: object
properties:
prevalence:
example: Often
description: Defines the different regularities that guide the applicability of platforms.
type: string
enum:
- Undetermined
- Sometimes
- Often
- Rarely
name:
example: string
description: Technology name (Web Server, Web Client)
type: string
additionalProperties: false
required:
- prevalence
ValidTime:
example:
start_time: '2016-01-01T01:01:01.000Z'
end_time: '2016-01-01T01:01:01.000Z'
description: The time range during which this Indicator is considered valid.
type: object
properties:
start_time:
example: '2016-01-01T01:01:01.000Z'
description: If not present, the valid time position of the indicator does not have an upper bound.
type: string
format: date-time
end_time:
example: '2016-01-01T01:01:01.000Z'
description: If end_time is not present, then the valid time position of the object does not have an upper bound.
type: string
format: date-time
additionalProperties: false
ExternalReference:
example:
source_name: string
description: string
url: string
hashes:
- string
external_id: string
description: External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.
type: object
properties:
source_name:
example: string
description: The source within which the external-reference is defined (system, registry, organization, etc.)
type: string
description:
example: string
description: Markdown string with at most 5000 characters.
type: string
url:
example: string
description: A URL reference to an external resource.
type: string
hashes:
example:
- string
description: Specifies a dictionary of hashes for the contents of the url.
type: array
items:
type: string
external_id:
example: string
description: An identifier for the external reference content.
type: string
additionalProperties: false
required:
- source_name
DeliberateEnvelopedObserveBundleDataDataRelationships:
type: object
properties:
count:
type: number
format: double
docs:
type: array
items:
$ref: '#/components/schemas/Relationship'
uniqueItems: true
additionalProperties: false
required:
- count
- docs
DeliberateEnvelopedObserveBundleDataDataIdentityAssertions:
type: object
properties:
count:
type: number
format: double
docs:
type: array
items:
$ref: '#/components/schemas/IdentityAssertion'
uniqueItems: true
additionalProperties: false
required:
- count
- docs
RegistryRenameType:
example:
time:
start_time: '2016-01-01T01:01:01.000Z'
end_time: '2016-01-01T01:01:01.000Z'
process_id: 10
process_name: string
process_guid: 10
process_username: string
registry_key: string
type: RegistryRenameEvent
registry_old_key: string
type: object
properties:
time:
$ref: '#/components/schemas/ObservedTime'
process_id:
example: 10
type: integer
format: int64
process_name:
example: string
description: String with at most 1024 characters.
type: string
process_guid:
example: 10
type: integer
format: int64
process_username:
example: string
description: String with at most 1024 characters.
type: string
registry_key:
example: string
description: String with at most 1024 characters.
type: string
type:
example: RegistryRenameEvent
type: string
enum:
- RegistryRenameEvent
registry_old_key:
example: string
description: String with at most 1024 characters.
type: string
additionalProperties: false
required:
- time
- process_id
- process_name
- registry_key
- type
- registry_old_key
HTTPType:
example:
process_guid: 10
traffic:
destination_host_name: string
protocol: 10
source_ip: string
destination_subnet: string
destination_ip: string
source_subnet: string
destination_port: 10
direction: incoming
source_port: 10
method: CONNECT
time:
start_time: '2016-01-01T01:01:01.000Z'
end_time: '2016-01-01T01:01:01.000Z'
type: HTTPEvent
host: string
process_name: string
process_id: 10
process_username: string
query: string
encrypted: true
url_port: 10
type: object
properties:
process_guid:
example: 10
type: integer
format: int64
traffic:
$ref: '#/components/schemas/Traffic'
method:
example: CONNECT
type: string
enum:
- OPTIONS
- PATCH
- TRACE
- HEAD
- POST
- CONNECT
- GET
- PUT
time:
$ref: '#/components/schemas/ObservedTime'
type:
example: HTTPEvent
type: string
enum:
- HTTPEvent
host:
example: string
description: String with at most 1024 characters.
type: string
process_name:
example: string
description: String with at most 1024 characters.
type: string
process_id:
example: 10
type: integer
format: int64
process_username:
example: string
description: String with at most 1024 characters.
type: string
query:
example: string
description: String with at most 5000 characters.
type: string
encrypted:
example: true
type: boolean
url_port:
example: 10
type: integer
format: int64
additionalProperties: false
required:
- traffic
- time
- type
- host
- process_name
- process_id
Identity:
example:
description: string
related_identities:
- identity: string
confidence: High
information_source: string
relationship: string
description: Can contain information such as the name of the attacker, the group or organization they belong to, or any other identifier that can help in the attribution process.
type: object
properties:
description:
example: string
description: Markdown string with at most 5000 characters.
type: string
related_identities:
example:
- identity: string
confidence: High
information_source: string
relationship: string
description: Identifies other entity Identities related to this Identity.
type: array
items:
$ref: '#/components/schemas/RelatedIdentity'
additionalProperties: false
required:
- description
- related_identities
Weakness:
type: object
properties:
description:
example: string
description: Should be short and limited to the key points that define this weakness.
type: string
background_details:
example: string
description: Information that is relevant but not related to the nature of the weakness itself.
type: string
paradigms:
example:
- prevalence: Often
name: string
description: Applicable paradigms.
type: array
items:
$ref: '#/components/schemas/Paradigm'
abstraction_level:
example: Base
description: Refers to the level of abstraction or granularity used to describe the weakness. It helps to categorize the vulnerability based on the level of detail provided.
type: string
enum:
- Variant
- Class
- Base
- Compound
architectures:
example:
- prevalence: Often
name: string
class: Embedded
description: Applicable architectures.
type: array
items:
$ref: '#/components/schemas/Architecture'
schema_version:
example: 1.3.30
description: CTIM schema version for this entity.
type: string
revision:
example: 10
description: A monotonically increasing revision, incremented each time the object is changed.
type: integer
format: int64
alternate_terms:
example:
- term: string
description: string
description: Indicates one or more other names used to describe this weakness.
type: array
items:
$ref: '#/components/schemas/AlternateTerm'
likelihood:
example: High
description: Likelihood of exploit.
type: string
enum:
- Medium
- Info
- Unknown
- None
- High
- Low
type:
example: weakness
description: The fixed value weakness
type: string
enum:
- weakness
created:
type: string
format: date-time
source:
example: string
description: Represents the source of the intelligence that led to the creation of the entity.
type: string
external_ids:
example:
- string
description: "It is used to store a list of external identifiers that can be linked to the incident, providing a reliable and manageable way to correlate and group related events across multiple data sources. It is especially useful in larger organizations that rely on multiple security information and event management (SIEM) systems to detect security incidents. For instance, it can be used to track events across different network sensors, intrusion detection and prevention systems (IDPS), or log management platforms. \n The field can also be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. It can be used to cross-reference with other external tools such as threat intelligence feeds and vulnerability scanners."
type: array
items:
type: string
modified:
type: string
format: date-time
short_description:
example: string
description: A single line, short summary of the object.
type: string
title:
example: string
description: A short title for this object, used as primary display and reference value.
type: string
external_references:
example:
- source_name: string
description: string
url: string
hashes:
- string
external_id: string
description: "Specifies a list of external references which refers to non-CTIM information.\n\nSimilar to `external_ids` field with major differences:\n\n- `external_ids` field is used to store a list of external identifiers that can be used to link entities across different data sources. These identifiers are typically standardized and well-known, such as CVE IDs, US-CERT advisories, or other industry-standard threat intelligence feeds. The `external_ids` field can be used to facilitate automation and orchestration workflows, where additional information can be shared among incident management systems. \n\n- `external_references` field, on the other hand, is used to provide a more general mechanism for linking entities to external sources of information. The `external_references` field can include references to blog posts, articles, external documents, threat intelligence reports, and other sources of information that may not have a standardized format or identifier."
type: array
items:
$ref: '#/components/schemas/ExternalReference'
functional_areas:
example:
- Authentication
description: Identifies the functional area of the software in which the weakness is most likely to occur.
type: array
items:
type: string
source_uri:
example: string
description: URI of the source of the intelligence that led to the creation of the entity.
type: string
modes_of_introduction:
example:
- phase: Architecture and Design
note: string
description: Information about how and when a given weakness may be introduced.
type: array
items:
$ref: '#/components/schemas/ModeOfIntroduction'
structure:
example: Chain
description: Defines the structural nature of the weakness.
type: string
enum:
- Chain
- Simple
- Composite
language:
example: string
description: 'The `language` field is used to specify the primary language of the affected system or the target of an attack. It can be used to provide additional context and information about the entity. The primary purpose of this field is to help analysts filter and prioritize entities based on their knowledge and expertise of different languages.
For example, if an incident involves an attack on a system in a country where a specific language is predominant, the `language` field can be used to indicate that language, which can help analysts to quickly identify and respond to incidents that may be geographically or culturally relevant. This information can be used to prioritize incidents based on their potential impact. The `language` field can also be used to help with correlation of incidents across different systems and regions, as well as to help with data analysis and reporting.'
type: string
id:
example: string
description: Globally unique URI identifying this object.
type: string
notes:
example:
- type: Applicable Platform
note: string
description: Provides any additional comments about the weakness.
type: array
items:
$ref: '#/components/schemas/Note'
common_consequences:
example:
- scopes:
- Access Control
impacts:
- Alter Execution Logic
likelihood: High
note: string
description: Refers to the typical or expected negative effects that can result from exploiting the weakness. This could include anything from unauthorized access to data, denial of service, system crashes or other things.
type: array
items:
$ref: '#/components/schemas/Consequence'
tlp:
example: green
description: 'TLP stands for [Traffic Light Protocol](https://www.us-cert.gov/tlp), which indicates precisely how a resource is intended to be shared, replicated, copied, etc.
It is used to indicate the sensitivity of the information contained within the message. This allows recipients to determine the appropriate handling and dissemination of the information based on their clearance level and need-to-know.
For example, an entity containing information about a critical vulnerability in a widely-used software might be marked as `red`, indicating that it should only be shared with a small group of highly trusted individuals who need to know in order to take appropriate action. On the other hand, a message containing more general information about security threats might be marked as `amber` or `green`, indicating that it can be shared more broadly within an organization.'
type: string
enum:
- white
- green
- red
- amber
detection_methods:
example:
- method: Architecture or Design Review
description: string
effectiveness: High
effectiveness_notes: string
description: Identifies methods that may be employed to detect this weakness, including their strengths and limitations.
type: array
items:
$ref: '#/components/schemas/DetectionMethod'
operating_systems:
example:
- prevalence: Often
name: string
version: string
cpe_id: string
class: Android
description: Applicable operating systems.
type: array
items:
$ref: '#/components/schemas/OperatingSystem'
client_id:
type: string
affected_resources:
example:
- CPU
description: Identifies system resources that can be affected by an exploit of this weakness.
type: array
items:
type: string
languages:
example:
- prevalence: Often
name: string
class: Assembly
description: Applicable Languages.
type: array
items:
$ref: '#/components/schemas/Language'
timestamp:
example: '2016-01-01T01:01:01.000Z'
description: The time this object was created at, or last modified.
type: string
format: date-time
potential_mitigations:
example:
- description: string
phases:
- Architecture and Design
strategy: Attack Surface Reduction
effectiveness: Defense in Depth
effectiveness_notes: string
description: Describes potential mitigations associated with a weakness.
type: array
items:
$ref: '#/components/schemas/Mitigation'
technologies:
example:
- prevalence: Often
name: string
description: Applicable technologies.
type: array
items:
$ref: '#/components/schemas/Technology'
additionalProperties: false
required:
- description
- schema_version
- type
- id
DeliberateEnvelopedObserveBundleDataDataCampaigns:
type: object
properties:
count:
type: number
format: double
docs:
type: array
items:
$ref: '#/components/schemas/Campaign'
uniqueItems: true
additionalProperties: false
required:
- count
- docs
ModeOfIntroduction:
example:
phase: Architecture and Design
note: string
type: object
properties:
phase:
example: Architecture and Design
description: Identifies the point in the software life cycle at which the weakness may be introduced.
type: string
note:
example: string
description: Provides a typical scenario related to introduction during the given phase.
type: string
additionalProperties: false
required:
- phase
ColumnDefinition:
example:
name: string
type: integer
description: string
required: true
short_description: string
type: object
properties:
name:
example: string
type: string
type:
example: integer
type: string
enum:
- url
- string
- observable
- number
- integer
- markdown
description:
example: string
description: Markdown string with at most 5000 characters.
type: string
required:
example: true
description: If `true`, the row entries for this column cannot contain `nulls`. Defaults to `true`.
type: boolean
short_description:
example: string
type: string
additionalProperties: false
required:
- name
- type
OpenC2COA:
example:
type: structured_coa
id: string
action:
type: alert
target:
type: acudid
specifiers: string
actuator:
type: endpoint
specifiers:
- string
modifiers:
response: acknowledge
method:
- acl
additional_properties:
context: string
time:
start_time: '2016-01-01T01:01:01.000Z'
end_time: '2016-01-01T01:01:01.000Z'
frequency: string
duration: '2016-01-01T01:01:01.000Z'
source: string
search: cve
option: string
id: string
location: internal
delay: '2016-01-01T01:01:01.000Z'
destination: copy-to
type: object
properties:
type:
example: structured_coa
type: string
enum:
- structured_coa
id:
example: string
description: String with at most 1024 characters.
type: string
action:
$ref: '#/components/schemas/ActionType'
target:
$ref: '#/components/schemas/TargetType'
actuator:
$ref: '#/components/schemas/ActuatorType'
modifiers:
$ref: '#/components/schemas/ModifierType'
additionalProperties: false
required:
- type
- action
RegistrySetType:
example:
process_guid: 10
registry_data: string
time:
start_time: '2016-01-01T01:01:01.000Z'
end_time: '2016-01-01T01:01:01.000Z'
type: RegistrySetEvent
registry_data_length: 10
registry_value: string
registry_key: string
process_name: string
process_id: 10
process_username: string
type: object
properties:
process_guid:
example: 10
type: integer
format: int64
registry_data:
example: string
description: String with at most 5000 characters.
type: string
time:
$ref: '#/components/schemas/ObservedTime'
type:
example: RegistrySetEvent
type: string
enum:
- RegistrySetEvent
registry_data_length:
example: 10
type: integer
format: int64
registry_value:
example: string
description: String with at most 2048 characters.
type: string
registry_key:
example: string
description: String with at most 1024 characters.
type: string
process_name:
example: string
description: String with at most 1024 characters.
type: string
process_id:
example: 10
type: integer
format: int64
process_username:
example: string
description: String with at most 1024 characters.
type: string
additionalProperties: false
required:
- time
- type
- registry_value
- registry_key
- process_name
- process_id
RelatedIdentity:
example:
identity: string
confidence: High
information_source: string
relationship: string
description: Describes a related Identity
type: object
properties:
identity:
example: string
description: The reference (URI) of the related Identity object.
type: string
confidence:
example: High
description: Specifies the level of confidence in the assertion of the relationship between the two objects.
type: string
enum:
- Medium
- Info
- Unknown
- None
- High
- Low
information_source:
example: string
description: Specifies the source of the information about the relationship between the two components.
type: string
relationship:
example: string
type: string
additionalProperties: false
required:
- identity
Verdict:
type: object
properties:
valid_time:
$ref: '#/components/schemas/ValidTime'
observable:
$ref: '#/components/schemas/Observable'
type:
example: verdict
type: string
enum:
- verdict
created:
type: string
format: date-time
modified:
type: string
format: date-time
disposition:
example: 1
description: Numeric verdict identifiers.
type: integer
format: int64
enum:
- 1
- 4
- 3
- 2
- 5
disposition_name:
example: Clean
description: 'The disposition_name field is optional, but is intended to be shown to a user. Applications must therefore remember the mapping of numbers to human words, as in: {1 "Clean", 2 "Malicious", 3 "Suspicious", 4 "Common", 5 "Unknown"}'
type: string
enum:
- Common
- Unknown
- Suspicious
- Malicious
- Clean
client_id:
type: string
judgement_id:
example: string
description: A URI leading to a judgement.
type: string
additionalProp
# --- truncated at 32 KB (311 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/cisco-xdr/refs/heads/main/openapi/cisco-xdr-reputation-api-openapi.yml