> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/deploying-lineaje/hybrid-deployment/prerequisites/network-configuration.md).

# Network Configuration

Configure the network access that SCA360 needs to run, such as outbound ports, runtime privileges, and external domains used for analysis, uploads, and report downloads. Allow only the services that apply to your environment and enabled features.

### Security and Firewall Requirements

<table><thead><tr><th width="154">Port</th><th>Usage</th></tr></thead><tbody><tr><td>TCP/443</td><td>SCA360 uses this port to connect to the SBOM360 backend and fetch data from public repositories.</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 runs as a regular user. Root or sudo privileges are not required. The user must have a valid home directory.</td></tr><tr><td>Network access</td><td>SCA360 requires access to external networks on the ports listed in the Firewall Requirements table. Depending on the configuration, SCA360 may also require access to internal source and package repositories.</td></tr><tr><td>Execution access</td><td>SCA360 executes the following: third-party tools shipped in the <code>third_party</code> folder, and the <code>git</code> client to clone source code.</td></tr></tbody></table>

### Domains Requiring Access

Configure this only if the firewall does not allow outgoing HTTPS connections 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 <strong>OR</strong></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>Upload SBOM metadata</td><td>https://us-east-1-commercialprod-veedna-opa.s3.amazonaws.com/*</td></tr><tr><td>Download reports</td><td>https://us-east-1-commercialprod-veedna-sbomreport-bucket.s3.amazonaws.com/*<br><br>https://us-east-1-commercialprod-veedna-datapipeline.s3.amazonaws.com/*</td></tr><tr><td>Local Vulnerability Lookup</td><td><p>https://*.anchore.io <strong>OR</strong></p><p>https://toolbox-data.anchore.io/<br>https://grype.anchore.io</p></td></tr><tr><td>Malware Lookup</td><td>https://data.reversinglabs.com</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</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>Packagist Repository</td><td>https://packagist.org</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>Ubuntu Container</td><td><p>https://*.ubuntu.com <strong>OR</strong> https://archive.ubuntu.com</p><p>https://security.ubuntu.com</p><p>https://old-releases.ubuntu.com</p></td></tr><tr><td>Debian Container</td><td>https://*.debian.org <strong>OR</strong><br>https://ftp.de.debian.org</td></tr><tr><td>Red Hat Container</td><td><p>https://*.redhat.com <strong>OR</strong><br>https://sso.redhat.com</p><p>https://api.access.redhat.com</p><p>https://cdn-ubi.redhat.com</p></td></tr><tr><td>Alpine Container</td><td><p>https://*.alpinelinux.org <strong>OR</strong><br>https://build.alpinelinux.org</p><p>https://dl-cdn.alpinelinux.org</p></td></tr><tr><td>Amazon Linux Container</td><td>https://*.amazonlinux.com <strong>OR</strong><br>https://cdn.amazonlinux.com</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.veedna.com/deploying-lineaje/hybrid-deployment/prerequisites/network-configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.