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 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 keysMobile SDK referenceWeb SDK referenceBackend SDK referenceClient SDK referenceFlag implementation reference
Introduction
Understanding CI workflowsCreate a build workflowCreate 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 external secret providers
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

Get started with continuous security

2 minute read

Create your first component with automatic security scanning to see how CloudBees Unify analyzes code and dependencies for vulnerabilities. This walkthrough shows you the basic continuous security workflow using an existing repository.

Prerequisites

Before you begin, ensure you have:

  • A CloudBees Unify organization with component creation permissions.

  • A GitHub or Bitbucket repository with code to scan.

  • Admin access to the repository for integration setup.

For complete technical requirements, refer to CloudBees Unify technical requirements reference.

Create your first security-scanned component

  1. Integrate your SCM provider with CloudBees Unify.

    Navigate to Configurations  Integrations and create an integration for your GitHub or Bitbucket account. For detailed steps, refer to the platform integration documentation.

  2. Enable security scanning for your organization.

    Enable implicit security assessment and the code scanners you want to use. If your workflows register or publish binaries, also enable binary analyzers to scan them.

    Enable security scanning before you create your component, so that scanning triggers automatically when the component is created.

    For detailed steps, refer to Configure implicit security analysis.

  3. Create a component linked to your repository.

    Navigate to Software Delivery  Components and create a new component. Select your integrated repository during component creation. This enables automatic security scanning whenever code changes occur.

  4. Trigger initial security scans by pushing code changes.

    Make any change to your repository and push it to the main branch. CloudBees Unify automatically initiates comprehensive security analysis including static code analysis, dependency vulnerability scanning, and secret detection.

  5. Review security findings in CloudBees Unify security views.

    Navigate to the security dashboards to review scan results:

    • Use the Security Center for component-level security findings and triage workflows.

    • Access the Security Overview for application-level security posture management.

    • Check Security Insights for organizational security metrics and trends.

Your component now has continuous security scanning active. CloudBees Unify will automatically scan every future code push, providing ongoing security analysis.

What you accomplished

You’ve experienced the basic continuous security workflow:

  • Component-based security activation that requires no pipeline configuration.

  • Automatic trigger scanning on code changes.

  • Integrated security findings in CloudBees Unify security views.

  • Multi-scanner analysis including code analysis, dependency scanning, and secret detection.

This foundation enables you to explore advanced security features like policy configuration, triage workflows, and organization-wide security posture management.

Related pages

Connect your CI tool
Get started with DevOps analytics