SaaS

Customers with on-premise SCM deployments that can allow network traffic between Arnica's SOC2 Type 2 certified environment and the SCMs can use this option.

Ingress traffic

Arnica ingests data from SCMs via API and git commands - all over TLS 1.2 and above. The following source IP addresses need to be able accessing the SCMs:

18.221.115.1

3.14.104.231

3.14.211.193

3.23.28.237

13.58.11.157

3.143.46.92

18.221.211.0

3.23.227.208

Egress traffic

In order to enable real-time scanning capabilities, all traffic to https://api.app.arnica.io/ needs to be allowed over TLS 1.2 and above.

On Premise Integrations

Arnica provides 2 deployment options for on-premise SCMs.

SaaS

Customers with on-premise SCM deployments that can allow network traffic between Arnica's SOC2 Type 2 certified environment and the SCMs can use this option.

Ingress traffic

Arnica ingests data from SCMs via API and git commands - all over TLS 1.2 and above. The following source IP addresses need to be able accessing the SCMs:

18.221.115.1
3.14.104.231
3.14.211.193
3.23.28.237
13.58.11.157
3.143.46.92
18.221.211.0
3.23.227.208

Egress traffic

In order to enable real-time scanning capabilities, all traffic to https://api.app.arnica.io/ needs to be allowed over TLS 1.2 and above.

For more information about how Arnica handles your data, please visit the .

On-premise

Arnica supports on-prem deployments in Kubernetes. Please for more information.

PreviousOpenAI ChatGPT NextIdentities, Repositories & Organizations

Last updated 13 days ago

Was this helpful?