Lineaje Learning Center
  • About Lineaje
  • Lineaje Product Offering
  • Getting started
    • Create an account
      • Configure Azure AD for sso
      • Configure Okta for sso
    • Onboarding workflow
  • SBOM360, OSM
    • Generate an SBOM
      • Source Code Management (SCM) As Source
        • Public Code Repositories
        • Private Code Repositories
          • Configure GitHub credentials
          • Configure Bitbucket credentials
          • Configure Gitlab credentials
          • Configure Git credentials
          • Configure Azure Repo
        • Frequently Asked Questions
      • Container Image As Source
        • Public Container Image
        • Private Container Image
          • Configure AWS Elastic Container Registry
          • Configure Google Container Registry
          • Configure Docker Hub
          • Configure Generic OCI Registry
          • Configure Azure Container Registry
        • Frequently Asked Questions
      • Existing SBOM As Source
        • EO 14028 checks
      • Manifest file As Source
      • Android Package Kit (APK)
      • Using Lineaje CLI
    • Explore Your SBOM
      • Info
      • Attestation
      • IRL
      • Dependencies
      • Provenance
      • Vulnerabilities
      • Mitigations
      • Security Posture
      • Code Quality
      • Suppliers & Licenses
      • Findings
    • Manage Your SBOM
    • Dashboard
    • Search
    • Policies and Gates
    • Organization and User Management
      • Organization example
    • Lineaje AI
    • AI Plan and AI Remediate
      • JIRA Integration
  • SBOM360 Hub
    • My Products
    • My SBOMS
    • Find & Review SBOMs
    • Manage Your Repository
    • Request and Share SBOMS
    • Settings
    • User Roles
  • Lineaje CLI
    • System Configuration
    • Toolset Configuration
    • CLI Installation
    • CLI Usage
    • Troubleshooting CLI issues
    • Support matrix
  • Integration with CICD pipeline
    • Pre-Requisites
    • Generate Project from source code
      • Project creation using Lineaje cloud
  • Abbreviations and Descriptions
  • Release Notes
    • Unified Scanner for AWS
Powered by GitBook
On this page
  • Hardware
  • Operating System
  • Additional Software requirement
  • Security and Firewall requirements
  • Privileges configuration
  • Domains to which access is required
  1. Lineaje CLI

System Configuration

PreviousLineaje CLINextToolset Configuration

Last updated 1 month ago

System must meet specific hardware and software specification to install and use the CLI. Review the requirements before installing the CLI

Hardware

Component
Requirements

Processors

Intel x86_64 architecture-based processor

  • Minimum: 2 vCPU

  • Recommended: 4 vCPU

Memory

Minimum: 2 GB RAM

Recommended: 4 GB RAM

Disk space

Output Directory – Minimum 100 GB

“/tmp” Directory – Minimum 40 GB

“/home” Directory – Minimum 1 GB

Operating System

Ubuntu 22.04 LTS

Red Hat Enterprise Linux 8

Note: CLI cannot be run on 32bit platform

Additional Software requirement

CLI requires the following software to be available on the system

  • Git Client

For language decomposition, please refer .

Following software can also be installed to help in troubleshooting

  • unzip

  • strace

  • screen/tmux

  • gdb

  • wget / curl

  • vim

  • tcpdump

  • jq

Security and Firewall requirements

Port
Usage

TCP/443

CLI will use this port to connect to the SBOM360 backend

CLI will use this port to fetch data from public repositories

Privileges configuration

Privilege type
Usage

Regular User

CLI can be executed by a regular user. There is no need to provide root or sudo privileges to the user that will run the CLI. This regular user should have a proper home directory

Network access

CLI will require access to connect to external networks on the ports mentioned in the “Firewall requirements” table

Depending on the configuration, the CLI will also require access to connect to internal source and package repositories

Execution access

CLI will execute the following,

• Third party tools that the CLI ships internally inside the “third_party” folder • “git” client to clone source code

Domains to which access is required

This access is required to be configured only if the Firewall does not allow outgoing HTTPS connection by default.

Services accessed

Lineaje Backend Services

https://*.v2.prod.veedna.com

Maven and Gradle Package Repository

https://repo.maven.apache.org

https://repo1.maven.org

https://repo.spring.io https://oss.sonatype.org https://maven.google.com

NPM and JavaScript Package Repository

Python Package Repository

https://pypi.org

Rust Package Repository

https://crates.io

Ruby Package Repository

https://rubygems.org

Dotnet Package Repository

https://api.nuget.org

Go Package Repository

https://sum.golang.org https://proxy.golang.org https://golang.org https://google.golang.org https://pkg.go.dev

Source Repository

https://github.com

https://bitbucket.org

https://gitlab.com

Vulnerability Lookup

https://*.anchore.io

https://toolbox-data.anchore.io/

Lineaje AWS S3 location

https://us-east-1-commercialprod-veedna-opa.s3.amazonaws.com/*

Ubuntu Container

https://*.ubuntu.com

Debian Container

https://*.debian.org

Red Hat Container

https://*.redhat.com

Alpine Container

https://*.alpinelinux.org

Amazon Linux Container

https://*.amazonlinux.com

https://registry.npmjs.org

Toolset Configuration