# System Configuration

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

### Hardware

<table><thead><tr><th width="198">Component</th><th>Requirements</th></tr></thead><tbody><tr><td>Processors</td><td><p>Intel x86_64 architecture-based processor</p><ul><li>Minimum: 2 vCPU</li><li>Recommended: 4 vCPU</li></ul></td></tr><tr><td>Memory</td><td><p>Minimum: 2 GB RAM</p><p>Recommended: 4 GB RAM </p></td></tr><tr><td>Disk space</td><td><p>Output Directory – Minimum 100 GB </p><p>“/tmp” Directory – Minimum 40 GB </p><p>“/home” Directory – Minimum 1 GB</p></td></tr></tbody></table>

### 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 [Toolset Configuration](/sca360-secure-deployment-for-restricted-environments/toolset-configuration.md).

Following software can also be installed to help in troubleshooting&#x20;

* unzip&#x20;
* &#x20;strace
* screen/tmux
* gdb&#x20;
* wget / curl
* vim
* tcpdump
* jq

### Security and Firewall requirements

<table><thead><tr><th width="154">Port</th><th>Usage</th></tr></thead><tbody><tr><td>TCP/443</td><td><p>SCA360 will use this port to connect to the SBOM360 backend </p><p>SCA360 will use this port to fetch data from public repositories</p></td></tr></tbody></table>

### Privileges configuration

<table><thead><tr><th width="154">Privilege type</th><th>Usage</th></tr></thead><tbody><tr><td>Regular User</td><td>SCA360 can be executed by a regular user. There is no need to provide root or sudo privileges to the user that will run SCA360. This regular user should have a proper home directory</td></tr><tr><td>Network access</td><td><p>SCA360 requires access to connect to external networks on the ports mentioned in the “Firewall requirements” table </p><p>Depending on the configuration, SCA360 will also require access to connect to internal source and package repositories</p></td></tr><tr><td>Execution access</td><td><p>SCA360 will execute the following, </p><p>• Third party tools that SCA360 ships internally inside the “third_party” folder • “git” client to clone source code </p></td></tr></tbody></table>

### 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.

<table><thead><tr><th width="336.727294921875">Services accessed</th><th></th></tr></thead><tbody><tr><td>Lineaje Backend Services</td><td><p>https://*.v2.prod.veedna.com OR</p><p>https://data-service-v2-apigw.v2.prod.veedna.com<br>https://notification-service.v2.prod.veedna.com</p><p>https://lineaje-gpt-service.v2.prod.veedna.com</p><p>https://lineaje-identity-service.v2.prod.veedna.com</p><p>https://scim-service.v2.prod.veedna.com</p></td></tr><tr><td>Maven and Gradle Package Repository</td><td><p>https://repo.maven.apache.org</p><p>https://repo1.maven.org</p><p>https://repo.spring.io</p><p>https://oss.sonatype.org</p><p>https://maven.google.com<br>https://dl.google.com</p></td></tr><tr><td>NPM and JavaScript Package Repository</td><td>https://registry.npmjs.org<a href="https://registry.npmjs.org
">
</a></td></tr><tr><td>Python Package Repository</td><td>https://pypi.org</td></tr><tr><td>Rust Package Repository</td><td>https://crates.io</td></tr><tr><td>Ruby Package Repository</td><td>https://rubygems.org
</td></tr><tr><td>Dotnet Package Repository</td><td>https://api.nuget.org</td></tr><tr><td>Go Package Repository</td><td>https://sum.golang.org
<br>https://proxy.golang.org
<br>https://golang.org
<br>https://google.golang.org
<br>https://pkg.go.dev</td></tr><tr><td>Source Repository</td><td><p>https://github.com </p><p>https://bitbucket.org </p><p>https://gitlab.com</p></td></tr><tr><td>Vulnerability Lookup</td><td><p>https://*.anchore.io </p><p>https://toolbox-data.anchore.io/</p></td></tr><tr><td>Lineaje AWS S3 location</td><td>https://us-east-1-commercialprod-veedna-opa.s3.amazonaws.com/* </td></tr><tr><td>Ubuntu Container</td><td>https://*.ubuntu.com</td></tr><tr><td>Debian Container</td><td>https://*.debian.org</td></tr><tr><td>Red Hat Container</td><td>https://*.redhat.com</td></tr><tr><td>Alpine Container</td><td>https://*.alpinelinux.org</td></tr><tr><td>Amazon Linux Container</td><td>https://*.amazonlinux.com</td></tr><tr><td>Packagist</td><td>https://packagist.org</td></tr></tbody></table>

###


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.veedna.com/sca360-secure-deployment-for-restricted-environments/system-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.