LogoLogo
WebsitePricingBlog
  • Debricked Documentation
  • Overview
    • Getting started
      • Create a OpenText Core SCA account
      • Running OpenText Core SCA
    • Help
      • Frequently asked questions (FAQ)
      • Upgrade your account
      • Get help in OpenText Core SCA tool
    • Language support
      • C# - Nuget, Paket
      • CycloneDX SBOM
      • Go - Go Modules, Go Dep, Bazel
      • Java & Kotlin - Gradle, Maven, Bazel
      • JavaScript - NPM, Yarn, Bower
      • Objective-C - CocoaPods
      • PHP - Composer
      • Python - Pip, Pipenv
      • Ruby - RubyGems
      • Rust - Cargo
      • Swift - CocoaPods
      • Linux package managers
      • Scala - SBT
    • Security overview
  • Product
    • Vulnerability management
      • Security terms
      • Data sources
      • See your data
      • Pull Requests (PR)
        • Enable Pull Request support
        • Solve vulnerabilities using Pull Requests (PR)
        • Solve vulnerabilities using Pull Requests (PR) via API
      • Set a review status
        • Snooze or pause a review status
      • Reachability Analysis
        • Set up Reachability Analysis for Java
        • Set up Reachability Analysis for Go
      • Solve vulnerabilities manually with root fixes
    • License risk management
      • Licence families
      • License risks
      • Set up a use case
        • Set up a use case using API
      • Proxy non-standard license identifiers
    • Project health
      • Contributors
      • Popularity
      • Security
    • Open source select
      • Search projects
      • Compare projects
      • View more details
      • Start left policies
      • OpenText Core SCA Select Browser Extension
      • End of Life (EOL)
    • Automation
      • Create an automation rule
      • Edit an automation rule
      • Default automation rules
      • Set up webhooks
      • Policies
      • Monitoring
    • Exporting or SBOM
      • Overview
      • License export
      • Vulnerability export
      • SBOM export
        • CycloneDX SBOM export
        • SPDX SBOM export
    • Administration
      • Generate access token
      • Account
        • Change your password
        • Delete your account
        • Delete company account
      • Billing
        • Manage contributing developers
        • Manage billing frequency
        • Manage payment methods
        • Access invoices
        • Manage your subscription
      • Settings
        • Enable and disable snoozing vulnerabilities
        • Supported language for Debricked tool
        • View logged events
        • Two-Factor Authentication (2FA)
      • Users
        • User roles (freemium and premium)
        • Role-Based Access Control (Enterprise)
        • Manage users
          • Add a new user
      • Repositories
        • Default Branch
        • Repository groups
        • Manually upload a dependency file
        • Manage your commits
  • Tools & Integrations
    • Command Line Interface (CLI)
      • Debricked CLI
        • High performance scans
        • File fingerprinting
      • Legacy CLI
    • CI/CD integrations
      • GitHub
      • CircleCI
      • BuildKite
      • GitLab
      • Bitbucket
      • Azure DevOps
      • Argo workflows
      • Travis CI
      • Jenkins
      • Bamboo
      • TeamCity
    • Fortify on Demand (FoD)
    • Fortify Software Security Center (SSC)
    • Debricked APIs
      • Open source select API
    • Integrated Development Environments (IDEs)
    • Single Sign-On (SSO)
      • Single Sign-On (SSO) through Okta
      • Single Sign-On (SSO) through Microsoft Entra ID
      • Single Sign-On (SSO) through JumpCloud OIDC
      • Single Sign-On (SSO) through GitHub
  • Tips & Tricks
    • Debricked CLI migration guide
    • Workarounds
      • Scanning Conan (C++) projects
      • Scanning a repository with different services
      • Scanning Docker images
      • Automations: Do not fail on found CVE lacking a fix
Powered by GitBook
LogoLogo

Company

  • Pricing
  • Blog

Support

  • Privacy Policy
  • Terms & Conditions
  • Service Status

Resources

  • Vulnerability DB
  • Open Source Select

© 2018-2024 | Open Text

On this page
  • Set a rule as a default rule
  • Remove a rule as a default rule
  • Disable default automation rules using API

Was this helpful?

Export as PDF
  1. Product
  2. Automation

Default automation rules

Find default automation rules already in place and learn how to customize or remove them.

Last updated 3 days ago

Was this helpful?

To make things easier for you, OpenText Core SCA has created a set of default rules that are activated on your first scan and applicable to all of your repositories. As an administrator, you are also able to disable existing default rules and can assign new rules to be added to integrated repositories by default.

Keep in mind that once a rule is marked as default, it will be enabled for new repositories, even if it was disabled for existing repositories.

Set a rule as a default rule

  1. Go to Automation on the left side menu. Here, you can , as well as the existing rules

  2. Click Default rule.

  3. In the confirmation modal, select whether the rule should be activated for only newly integrated repositories or existing repositories as well.

  4. Click Confirm. From now on, only newly integrated repositories will be affected by your default rule.

This can also be done when creating or editing an automation rule:

  1. Click New+ to create a rule OR Edit rule in an existing rule.

  2. Tick the Default rule checkbox.

  3. Click Save. From now on, newly integrated repositories will be affected by your default rule.

Remove a rule as a default rule

  1. Go to Automation on the left side menu. Here, you can , as well as the existing rules.

  2. Click Default rule.

  3. On the confirmation modal, click Go ahead. From now on, newly integrated repositories will no longer be affected by your default rule.

Disable default automation rules using API

You can disable these rules through our API to create your own custom policy.

The default rules can be accessed through the endpoint:

api/1.0/open/admin/user/default-rules-enabled

You can check the current status of your default rules:

curl -X 'GET' \  'https://debricked.com/api/1.0/open/admin/user/default-rules-enabled' \  -H 'accept: */*' \  -H 'Authorization: Bearer <token>'

The response will show you “true” if the default rules are enabled and “false” if they are disabled, e.g.:

{    "defaultRulesEnabled": true}

You can change the current status using “enabled”:true and “enabled”:false. Here’s an example of how to disable it:

curl -X 'PATCH' \  'https://debricked.com/api/1.0/open/admin/user/default-rules-enabled' \  -H 'accept: */*' \  -H 'Authorization: Bearer <token>' \  -H 'Content-Type: application/json' \  -d '{  "enabled": false}'

Once you disable the default rules using the API, the automation rules will not trigger when a new repository is added to your account. Remember to set up your own rules to optimize your use of OpenText Core SCA tool.

create new automation rules
edit
create new automation rules
edit