Introduction
Understanding organizationsUnderstanding componentsManage organizationsManage componentsManage component Jira integrations
Set up your first organizationUnderstanding users and teamsUnderstanding role-based access controlManage usersManage teamsConfigure role-based access controlRBAC permissions reference
Understanding authentication in CloudBees UnifySet up multifactor authenticationConfigure SAML single sign-onConfigure OIDC authenticationConfigure network security policiesNetwork security reference
Understanding platform configurationUnderstanding environmentsManage properties and secretsManage environmentsTrack environment inventoryConfigure containersSet up preconfigured actionsConfigure notificationsSet up Slack webhook notifications
Accessibility policy referenceShared responsibility model referenceSubscription and services agreementSupport policiesSupported browsers and external tools
Introduction
Understanding feature managementUnderstanding Configuration as CodeGet started with feature managementCreate and manage feature flagsConfigure feature flag targetingOrganize feature flagsImplement feature flag governanceConfiguration as Code reference
Understanding flag impressions and activity statusUnderstanding flag healthUnderstanding code referencesReview and clean up feature flagsSet up code references
Understanding Jira integration for feature flagsSet up the Jira integrationLink Jira tickets to feature flags
Understanding multiple SDK keysBuild your first mobile app with feature flagsBuild your first feature-flagged web applicationBuild your first feature-flagged backend serviceInstall client-side SDKsInstall server-side SDKsConfigure multiple SDK keysFlag implementation referenceMobile SDK referenceWeb SDK referenceBackend SDK referenceClient SDK reference
Introduction
Understanding CI workflowsUnderstanding custom actionsCreate a build workflowCreate a custom actionCreate and manage workflowsCreate reusable workflowsTest and validate containers in workflowsCheck out source codeTrigger workflows remotelyWorkflow syntax referenceJobs syntax referenceSteps syntax referenceServices syntax reference
Monitor workflow runsView test results in runsView evidence in runsView deployments in runsManage workflow artifactsPublish test resultsPublish evidence itemsGenerate a software bill of materialsManage ServiceNow change requests
Configure workflow credentialsConfigure AWS credentialsConfigure container registry credentialsConfigure Git credentialsIntegrate CyberArk Conjur secrets
Understanding GitHub Actions integrationSet up GitHub Actions integrationDisplay GitHub Actions workflows and runsRegister GHA build artifactsPublish GHA deployed artifactsPublish GHA test resultsPublish GHA evidence itemsTrigger CloudBees workflows from GitHub ActionsScan with GitHub Actions
Understanding CloudBees CI and Jenkins® integrationConnect CI and Jenkins controllersMonitor CI and Jenkins buildsRegister CI build artifactsRegister CI deployed artifactsPublish CI test resultsConfigure CI security scanningCI and Jenkins integration reference
Build and publish container imagesUnderstanding external CI/CD integrationsRun external CI/CD jobsExternal CI/CD action reference
Introduction
Understanding release orchestrationManage applicationsCreate deployer workflowsCreate staged workflowsCreate and manage releasesOrchestrate multi-workflow releasesRelease management reference
Understanding artifact managementRegister and track artifactsStore and retrieve artifactsPromote artifactsGenerate a software bill of materialsArtifact management reference
Deploy with HelmDeploy to KubernetesContainer deployment reference
Deploy to AWSAWS deployment reference
Deploy with enterprise platformsExecute remote deployment commandsEnterprise deployment reference
Verify deployments with New RelicDeployment verification reference

Understanding Jira ticket creation

2 minute read

CloudBees Unify creates a Jira issue when a security finding is triaged to Fix Required. Each issue is created in the Jira project configured for the application, using the configured work type, and includes the following information from the security finding:

  • Finding name and vulnerability code (CVE or CWE).

  • Severity rating.

  • Affected asset name and type.

  • Security tool that identified the finding.

  • Link back to the finding in the CloudBees Unify Security Center.

For more information about Jira ticketing for applications, refer to Configure Jira ticketing for an application

When a Jira issue is created for a security finding, its priority is automatically set to match the severity of the finding in the CloudBees Unify Security Center.

The Jira issue includes a link to the corresponding finding in the CloudBees Unify Security Center. Selecting the link opens the Security Center with the specific finding prefiltered and its details displayed.

Similarly, the CloudBees Unify Security Center displays the Jira issue reference as a link. Selecting the link opens the corresponding Jira issue in a new browser tab.

Only one Jira issue is created per unique finding. If the same finding is detected in a subsequent scan, the existing Jira issue is updated rather than a new one being created.
Jira issue creation only applies when a Jira integration has been configured for the application. Findings triaged to Fix Required without a configured Jira integration are tracked in CloudBees Unify only. For the full triage procedure, refer to Triage security findings.

Understand bidirectional status sync

Status changes in either CloudBees Unify or Jira are synchronized based on the configured status mappings.

This ensures that security teams working in CloudBees Unify and developers working in Jira always have an accurate view of remediation progress without manual updates in both tools.

CloudBees Unify to Jira: When a security finding status changes in CloudBees Unify, the corresponding Jira issue status updates to the mapped Jira status.

Security finding status sync with Jira
Figure 1. Security center findings mapped to Jira ticket

Jira to CloudBees Unify: When a Jira issue changes to a status mapped to a CloudBees Unify finding status, the corresponding finding status in CloudBees Unify is updated only if the Jira issue is in the In Progress state. Changes to Jira issues in any other status do not update the finding status in the CloudBees Unify Security Center. CloudBees Unify receives these updates via the webhook configured during the organization-level Jira integration setup.

Jira ticket mapped to Security center finding
Figure 2. Jira ticket details mapped to Security center finding
Status sync only applies to findings that have a corresponding Jira issue. Findings not yet triaged to Fix Required do not have a Jira issue and are not synced.
Understanding application security posture management
Understanding security center workflows