Threatrix Documentation
Threatrix
  • Getting Started
  • Developer Quick Start
  • SecureShip
    • Artifactory Scanning
    • ThreatAgent Scanning
  • Threat Center
    • Creating Account
      • OAuth Login
    • Entity Dashboard
    • User Profile
  • AICertify
    • Reviewing Results
  • codecertify
    • Quick Start
    • Project Summary Tab
    • Components Tab
      • Custom Components
        • Adding
        • Editing
        • Important Notes
      • Header Panel
      • Module Tree Panel
      • Results Panel
        • Card View
        • Risk Graph View
      • Audit History
    • Assets Tab
      • Custom Asset Matches
        • Adding Asset Match
  • securecore
    • Project Dashboard
    • ThreatScan
    • Scan Results
  • Threat Agent
    • Threat Agent Overview
    • Threat Agent - Installation & Scanning
    • Scan Summary Reports
    • Resolving Errors
    • Scanning Container Images
  • Integrations
    • Dependency Managers
      • RENV
    • Build Integrations
      • AWS CodeBuild
      • Azure DevOps
      • Bitbucket Pipeline
      • CircleCI
      • GitHub Action
      • GitLab Pipeline
      • Jenkins Pipeline
    • SCM Integrations
      • GitLab
      • Bitbucket
    • Issue Management
      • Jira
    • Notifications
  • Policy Management
    • Policy Overview
    • Creating Policies
    • Policy Conditions
    • Policy Actions
    • Policy Scopes
  • Administration
    • User Management
    • Organization Settings
      • Organization Knowledge Base
      • Integration
        • Slack Integration
        • Jira Integration
        • Service Keys
    • RBAC
    • Entity Management
    • Okta
      • Okta Org2Org Integration
  • GraphQL API
    • API Overview
  • Resources
    • Dependency Managers
      • PIP
    • Dictionary
    • Licenses
    • Security & Privacy
    • Binary File Support
  • Hybrid / On Premise
    • Getting Started
    • Installation
    • Upgrade
    • Setup
    • Cloud Data Disclosure
    • Troubleshooting
Powered by GitBook
On this page
  • Eligibility
  • Creating a custom component
  • Important Notes

Was this helpful?

  1. codecertify
  2. Components Tab
  3. Custom Components

Adding

PreviousCustom ComponentsNextEditing

Last updated 3 months ago

Was this helpful?

Eligibility

Only unmatched components are edible for assignment of a custom component. An unmatched component is one that was not found in our database using available matching techniques.

Creating a custom component

Custom components can be created from the Components tab by selecting an unmatched component and then clicking Add Component in the compont details window, on the right side.

This opens the "Add Component" window from which you can provide a the necessary meta data for your new component. Available fields are:

  • Component Name: The name of the component

  • Namespace: The namespace, if known

  • Version: The version, if known

  • PURL Type: This refers to the Ecosystem from which the component originated. Select NON_PURL if the component is not from a known ecosystem, or UNKNOWN if you don't know from which ecosystem this component originated.

  • License(s): One ore more license scan be applied to the component. When you being typing, both the Threatrix knowledge base and your organizations license knowledge base will be searched for based on the value you've entered.

  • Copyrights: The free form copyright field allows you to add 1 or more copyrights to the component

  • Internal: Checking this box indicates that this is a proprietary, internal component and not open source or not 100% open source.

When you're done filling in the meta data details, simply click "Add Component" and the new component will be created in your organizations Component knowledge base and automatically associated with the unmatched component, as shown below:

Important Notes

Please read and understand some regarding the creation, administration and application of Custom Components.

Important Notes