I have Tenable network security documentation explaining how bidirectional ticketing available but i think it only works for JIRA SERVER. Could someone confirm that and if this same bidirectional ticketing or a variation of is available for Jira cloud? If so, could someone please forward the documentation
Details below:
Solution Overview
Tenable Network Security offers a flexible solution that not only provides incident notification and alerting, but also integration with service desk and ticketing systems for tracking by appropriate response and remediation teams. This ensures a closed-loop management and automated workflow for processing security incidents and tracking their status throughout the mitigation process.
Unlike other solutions, the Tenable architecture also validates the effectiveness of response actions, such as the patching of vulnerabilities, via subsequent scan results. This ensures that issues are indeed resolved before tickets are closed.
How it Works
As an example, the integration with JIRA allows bi-directional communications for a complete view of detection, remediation, and verification of security issues within the organization. This takes place in three phases: Import, Rescan, and Close.
Phase 1: Import
1. SecurityCenter CV performs security assessment to detect
vulnerabilities on systems (endpoints, servers, databases, web
applications, etc.).
2. The integration script queries SecurityCenter CV for vulnerable hosts.
For each vulnerable host a parent ticket is created in JIRA and a
subtask is created for each vulnerability identified on the host.
Phase 2: Rescan
1. Resolved tickets are placed in the “fixed” state within JIRA.
2. The integration script identifies all tickets in “fixed” state and
initiates re-scans for them on a pre-defined schedule (for example,
every night).
Phase 3: Close
1. For each “fixed” ticket in JIRA the integration script queries
SecurityCenter CV to verify the vulnerability is mitigated.
2. If the vulnerability is mitigated, the JIRA ticket is moved to the
closed state.
3. If the vulnerability is not mitigated, the JIRA ticket is moved to the
“unfixed” state.
4. All “unfixed” tickets remain open and should be investigated by IT
team to determine root cause.
The above illustrates the integration and workflow between
SecurityCenter CV and JIRA. Tenable Professional Services can develop
a custom integration for other ticketing systems.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.