Introduction
Understanding organizationsUnderstanding componentsManage organizationsManage componentsManage component Jira integrations
Understanding users and teamsUnderstanding role-based access controlManage usersManage teamsConfigure role-based access controlRBAC permissions reference
Understanding authentication in CloudBees UnifyPersonal access tokensManage personal access tokensSet 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 application security posture managementUnderstanding Jira ticket creationUnderstanding security center workflowsConfigure security toolsConfigure implicit security analysisConfigure Jira ticketing for an applicationConfigure SBOM analysisDefine security SLAsTriage security findingsUse the organization security dashboardUse the component security centerUse the application security centerUse security overview
Get started with security scanningConfigure SAST scanningConfigure DAST scanningConfigure container scanningConfigure SCA scanningConfigure secret scanningConfigure IaC scanningVerify CloudBees action image signatures and SLSA attestationsSecurity scanner referenceSecurity findings taxonomy
Introduction
Actions catalog
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
View pending approval tasks in your inboxMonitor 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
Introduction
Understanding feature managementUnderstanding Configuration as CodeGet started with feature managementCreate and manage feature flagsConfigure feature flag targetingOrganize feature flagsImplement feature flag governanceEnable secret modeConfiguration 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 reference
Backend SDK referenceGo SDK referenceJava SDK referencePython SDK referenceRuby SDK referencePHP SDK reference.NET/C# (server-side) SDK referenceNode.js SDK referenceMobile SDK referenceAndroid SDK referenceiOS/tvOS SDK referenceObjective-C SDK referenceSwift SDK referenceReact Native SDK referenceWeb SDK referenceJavaScript (browser) SDK referenceJavaScript SSR SDK referenceClient SDK referenceJava client SDK reference.NET/C# (client-side) SDK referenceC (server-side) SDK referenceC++ (server-side) SDK referenceC (client-side) SDK referenceC++ client SDK reference

Use the organization security dashboard

3 minute read
How-to guide— Task-oriented: directions to achieve a specific goal.

The organization level security dashboard enables you to understand application security posture across the entire organization and its child organizations in a single, centralized view.

To access the security dashboard:

  1. Select an organization from the organization selector.

  2. Select Security  Dashboard.

The Dashboard tab displays security issues and occurences for selected organization and all its child organizations in scope. This includes applications, components, and branches belonging to these organizations.

Security dashboard
Figure 1. Security dashboard

Use the filters to scope the dashboard to specific applications, components, or default branches. Not all available branches are displayed by default. To view other branches, select them manually. The filters dynamically update the dashboard to reflect the selected scope.

Applications and components support multiple selections. The branch filter supports a single selection for each component, allowing you to select one branch per component.

  • Selecting an application filters the available components and default branch associated with that application.

  • Selecting a component will show all the branches but only the default branch is selected after selecting a component.

Review dashboard filters

Use the following filters to scope the security issues and their occurrences from the most relevant and recent risk signals:

  • Severity: The risk rating reported by the security tool that discovered the issue.

  • Tools: The security tool, or tools, that reported the issue.

  • Status: The triage status of the occurrences.

  • First identified: The date range in which the issue was first identified.

You can combine multiple filters. Clear an individual filter, or reset all filters, to return to the unfiltered table.

When you change a filter, the table data gets refreshed to match the selected scope.

Review the header summary

The header summary gives you a high-level view of your organization’s security posture for the current scope. The header summary includes:

  • Open issues and open occurrences, showing the total count for the current organization and its child organizations.

  • A severity breakdown of open issues, split into Critical, High, Medium, and Low.

  • Resolved issues, showing the count of issues resolved for the current organization and its child organizations. An issue is marked as Resolved only when all its occurrences are resolved. If any occurrence remains unresolved or is in progress, the issue is not considered resolved.

Review security issues and occurrences

The dashboard displays security issues and its occurrences from multiple security tools, pipelines, and applications, giving you a trusted place to assess the overall risk and decide where to focus the remediation effort.

  • Issue Name/Code: The name or identifier of a security issue reported by a security tool.

  • Occurrences: The individual instances of a security issue reported in a branch, file, or code location.

  • Severity: The rating reported by the security tool when discovering an issue.

  • First seen: The time when the issue was first detected.

You need the View findings by triage status permission to access the organization security dashboard. For permission details, refer to RBAC permissions reference.

Review issue occurrence details

The Issue occurrences table lists the occurrences of an issue for the selected scope.

  • File name: The name of the issue.

  • Tool: The security tool that reported the occurrence.

  • Status: The current triage status of the occurrence. For details on each status, refer to Triage security findings.

  • SLA due: The date by which the occurrence must be resolved, based on the SLA defined for the organization. For more information, refer to Define security SLAs.

For code findings, select the occurrence to open the file in the connected source code management system. Where supported, CloudBees Unify highlights the relevant line in the file.

Related pages

Triage security findings
Use the component security center