add PagerDuty to Downstream Connections reference and vendor lists

Author: paulOsinski

docs/content/connections/downstream/about.md

@@ -17,6 +17,7 @@ Supported Downstream Connections:
 - GitHub
 - GitLab Boards
 - Jira
+- PagerDuty
 - ServiceDesk Plus
 - ServiceNow
 - Shortcut
@@ -81,6 +82,7 @@ For the complete list of requirements, please open the vendor specific pages bel
 - [GitHub](/connections/downstream/downstream_toolreference/#github)
 - [GitLab Boards](/connections/downstream/downstream_toolreference/#gitlab)
 - [Jira](/connections/downstream/downstream_toolreference/#jira)
+- [PagerDuty](/connections/downstream/downstream_toolreference/#pagerduty)
 - [ServiceDesk Plus](/connections/downstream/downstream_toolreference/#servicedesk-plus)
 - [ServiceNow](/connections/downstream/downstream_toolreference/#servicenow)
 - [Shortcut](/connections/downstream/downstream_toolreference/#shortcut)

docs/content/connections/downstream/downstream_toolreference.md

@@ -539,3 +539,44 @@ A few Zendesk-specific behaviors to be aware of:
 - The ticket description is the first comment in Zendesk and cannot be edited after creation, so pushing an updated Finding will sync the ticket's subject, priority, and status, but not description changes.
 - Tickets are marked `solved` rather than deleted when a Finding is removed; Zendesk closes solved tickets automatically after a period of time.
 - `closed` is a final status - closed tickets cannot be updated at all, and pushing a Finding whose ticket has closed will report an error.
+
+## PagerDuty
+
+The PagerDuty Integration allows you to push DefectDojo Findings and Finding Groups as PagerDuty Incidents on a Service of your choice.
+
+### Instance Setup
+
+- **Label** should be the label that you want to use to identify this integration.
+- **Location** should be set to your regional PagerDuty REST API base URL: `https://api.pagerduty.com` for US accounts, or `https://api.eu.pagerduty.com` for EU accounts.
+- **API Token** should be set to a PagerDuty REST API key.  An administrator can create one in PagerDuty under **Integrations > API Access Keys**.
+- **From Email** should be the email address of a valid PagerDuty user on the account.  PagerDuty requires it when creating or updating incidents.
+
+### Issue Tracker Mapping
+
+- **Service ID** should be the ID of the PagerDuty Service that Incidents will be created on (e.g. `PXXXXXX`).  You can find it in the URL while viewing the Service.
+
+### Severity Mapping Details
+
+By default this maps to the Incident **Urgency** field, which accepts `high` and `low`:
+
+- **Severity Field Name**: `Urgency`
+- **Info Mapping**: `low`
+- **Low Mapping**: `low`
+- **Medium Mapping**: `low`
+- **High Mapping**: `high`
+- **Critical Mapping**: `high`
+
+Alternatively, set **Severity Field Name** to `Priority` and use your account's Incident Priority names (e.g. `P1` - `P5`) as the mapping values.  Priority names are resolved against the priorities configured on your PagerDuty account; an unknown name will report an error on push.
+
+### Status Mapping Details
+
+- **Status Field Name**: `Status`
+- **Active Mapping**: `triggered`
+- **Closed Mapping**: `resolved`
+- **False Positive Mapping**: `resolved`
+- **Risk Accepted Mapping**: `acknowledged`
+
+A few PagerDuty-specific behaviors to be aware of:
+
+- PagerDuty has no incident deletion - removing a Finding resolves its Incident instead.
+- Incident links open the Incident's web URL as returned by PagerDuty, so they work regardless of region.

docs/content/connections/issue_tracking.md

@@ -15,7 +15,7 @@ The DefectDojo issue tracking integrations connect your vulnerability management
 | Edition      | Supported Issue Tracking Integrations |
 |--------------|---------------------------------------|
 | Community Edition  | * [Jira](/connections/os_jira/os__jira_guide/)                          |
-| Pro          | * [Jira](/connections/downstream/downstream_toolreference/#jira) ([legacy guide](/connections/downstream/pro__jira_guide/))<br>* [Azure DevOps](/connections/downstream/downstream_toolreference/#azure-devops-boards)<br>* [Bitbucket](/connections/downstream/downstream_toolreference/#bitbucket)<br>* [Freshservice](/connections/downstream/downstream_toolreference/#freshservice)<br>* [GitHub](/connections/downstream/downstream_toolreference/#github)<br>* [GitLab Boards](/connections/downstream/downstream_toolreference/#gitlab)<br>* [ServiceDesk Plus](/connections/downstream/downstream_toolreference/#servicedesk-plus)<br>* [ServiceNow](/connections/downstream/downstream_toolreference/#servicenow)<br>* [Shortcut](/connections/downstream/downstream_toolreference/#shortcut)<br>* [Zendesk](/connections/downstream/downstream_toolreference/#zendesk) |
+| Pro          | * [Jira](/connections/downstream/downstream_toolreference/#jira) ([legacy guide](/connections/downstream/pro__jira_guide/))<br>* [Azure DevOps](/connections/downstream/downstream_toolreference/#azure-devops-boards)<br>* [Bitbucket](/connections/downstream/downstream_toolreference/#bitbucket)<br>* [Freshservice](/connections/downstream/downstream_toolreference/#freshservice)<br>* [GitHub](/connections/downstream/downstream_toolreference/#github)<br>* [GitLab Boards](/connections/downstream/downstream_toolreference/#gitlab)<br>* [PagerDuty](/connections/downstream/downstream_toolreference/#pagerduty)<br>* [ServiceDesk Plus](/connections/downstream/downstream_toolreference/#servicedesk-plus)<br>* [ServiceNow](/connections/downstream/downstream_toolreference/#servicenow)<br>* [Shortcut](/connections/downstream/downstream_toolreference/#shortcut)<br>* [Zendesk](/connections/downstream/downstream_toolreference/#zendesk) |
 
 
 When enabled, DefectDojo can create issues automatically, or selectively from Products or Engagement. As Findings are updated in DefectDojo—resolved, mitigated, or reactivated—the corresponding issues can be kept in sync, ensuring both systems reflect the current state of risk.

docs/content/get_started/about/defectdojo_versions.md

@@ -22,7 +22,7 @@ weight: 1
 | Import enhancements | ❌ Standard imports only | ✔️ Background imports, Smart Upload, Universal Parser, CLI uploads |
 | Tool integrations | ❌ Manual/API-driven | ✔️ Built-in **Upstream Connections** (API Connectors) for popular AppSec and cloud tools |
 | Jira integration | ✔️ Included | ✔️ Included |
-| Project management integrations | ❌ Not included | ✔️ **Downstream Connections** to **Jira**, **Azure DevOps**, **GitHub**, **GitLab**, **ServiceNow**, **Bitbucket**, **Shortcut**, **Zendesk**, **ServiceDesk Plus** and **Freshservice** |
+| Project management integrations | ❌ Not included | ✔️ **Downstream Connections** to **Jira**, **Azure DevOps**, **GitHub**, **GitLab**, **ServiceNow**, **Bitbucket**, **Shortcut**, **PagerDuty**, **Zendesk**, **ServiceDesk Plus** and **Freshservice** |
 | Finding enhancements | ❌ Not included | ✔️ Automatic KEV, EPSS scoring and Ransomware tracking |
 | SOC & AppSec unification | ❌ AppSec-focused only | ✔️ Unified AppSec and SOC findings |
 | AI & next-generation features | ❌ Not included | ✔️ AI-assisted workflows, reporting and MCP support |