Vulnerability relationship mapping

---
title: Vulnerability relationship mapping
description: Use many-to-many \(M2M\) relationship records to map connections between vulnerabilities and other entities.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/threat-intelligence-security-center/tisc-vul-relationship-map.html
release: australia
product: Threat Intelligence Security Center
classification: threat-intelligence-security-center
topic_type: concept
last_updated: "2026-09-10"
reading_time_minutes: 1
keywords: [vulnerability relationship mapping, Vulnerability Products, Vulnerability CWEs, many-to-many relationships]
breadcrumb: [TISC Library Repository, Threat Intel Library, Use, Threat Intelligence Security Center, Security Operations]
---

# Vulnerability relationship mapping

Use many-to-many \(M2M\) relationship records to map connections between vulnerabilities and other entities.

-   **Vulnerability Products**: maps vulnerabilities to products with a status field indicating the relationship \(for example, **Known Affected**, **Fixed**, **Under Investigation**\).
-   **Vulnerability CWEs**: maps vulnerabilities to CWEs. No status field is required for this relationship.

Bulk delete operations are available for all M2M relationship records from the related list view.

**Parent Topic:**[TISC Library Repository](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/threat-intelligence-security-center/tisc-ioc.md)

**Related topics**  


[Observables]()

[Indicators]()

[Threat Entities]()

[Other Objects]()

[Vulnerability Artifacts]()

[View RSS Feeds]()

[Working with Reports in TISC]()

[MITRE-ATT&CK repository]()

[Relationships Objects]()

[Potential Relationships]()