Jira Integration
Automated ticket creation and lifecycle management in Jira Cloud and Jira Data Center. Piscium creates detailed remediation tickets with exposure evidence, affected asset inventory, fix recommendations, and SLA deadlines. Ticket status changes in Jira automatically update remediation tracking in Piscium, and resolved tickets trigger verification re-scans.
What You Get
Automated ticket creation and lifecycle management in Jira Cloud and Jira Data Center. Piscium creates detailed remediation tickets with exposure evidence, affected asset inventory, fix recommendations, and SLA deadlines. Ticket status changes in Jira automatically update remediation tracking in Piscium, and resolved tickets trigger verification re-scans.
Why Jira?
Remediation fails when it lives outside the tools teams already use. By pushing validated exposures directly into Jira with full context, Piscium ensures that engineering and OT teams receive actionable tickets — not vague vulnerability reports — in the workflow they already follow.
Example Scenario
Piscium validates that a default SNMP community string on an OT network switch allows unauthorized read-write access to the management plane. A Jira ticket is automatically created in the OT Infrastructure project with severity Critical, assigned to the network engineering team, and tagged with the affected switch hostname, VLAN, and Purdue Level. When the engineer updates the SNMP configuration and transitions the ticket to Done, Piscium triggers a verification scan and confirms the exposure is closed.
Implementation Notes
Supports Jira Cloud (via Atlassian Connect) and Jira Data Center 9.x+ (via REST API with personal access token). Requires a dedicated Jira project or configured issue type for Piscium remediation tickets. Custom field mapping is configurable in the Piscium connector settings. Supports bi-directional status sync with configurable state mappings.
Webhook Payload Example
{
"event": "remediation.status_changed",
"timestamp": "2026-03-12T11:20:00Z",
"remediation_id": "REM-2026-00198",
"exposure_id": "EXP-2026-00334",
"status": "resolved",
"assignee": "carlos.r@corp.local",
"jira_issue_key": "OTSEC-1142",
"resolution": "fixed",
"verification_scan_scheduled": "2026-03-12T23:00:00Z"
}Ready to Connect Jira?
See the integration running live in your environment.