Arnica Documentation
  • Introduction
  • Getting Started
    • 🔑Sign Up
    • ▶️SCM Integrations
      • Azure DevOps
      • Bitbucket Cloud
      • Bitbucket Server & Datacenter
      • Github
        • GitHub Audit Logs
        • Github App Permissions
      • Gitlab
    • 📤ChatOps
      • Microsoft Teams
      • Slack
        • Adding Arnica to a New Channel
        • Interacting With the Arnica Slackbot
    • 🎫Ticket Management
      • 🐛Jira Integration
      • 📋ADO Boards Integration
    • 🧠Artificial Intelligence
      • Azure OpenAI
      • OpenAI ChatGPT
    • 🏨On Premise Integrations
  • Inventory
    • 💼Identities, Repositories & Organizations
    • 📇Software Bill of Materials (SBOM)
    • 🦄Prioritization & Product Ownership
  • Hardcoded Secrets
    • 🕵️Secret Detection
    • ⏪Realtime Secret Mitigation
    • 🥕Secrets Policy Settings
  • Code Risks
    • 🎼Static Application Security Testing (SAST)
      • Custom SAST Rules
    • 🧩Software Composition Analysis (SCA)
    • 🔡3rd Party Package Licenses
      • Override License Classifications
    • 🤹3rd Party Package Reputation
      • Identifying Low Rep Packages
      • How to Find Alternative Packages
    • ⛅Infrastructure as Code Security (IaC)
    • 🤖Code Risk Policy Settings
      • Developer Feedback On Push
      • Require Review Before Dismissal
      • 0 New High Severity Vulnerabilities
      • Enforce Remediation SLA
    • 🪄Code Risk Magic Links
    • 📦Code Risk Language and Framework Support
  • Platform Operations
    • 🚪Joining an Existing Org
    • ❌Deleting a Tenant
    • 🫂How do I invite members to my tenant?
      • New User Invitations
    • 👥Users & Roles
    • 🔇Deleting Integrations
    • ⌛Scheduled Jobs
      • How often do Jobs run?
    • 💸Billing
  • Security
    • 🎮Role Based Access Control (RBAC)
    • 🛡️Data Handling
    • 🏛️SSO Integration
      • Okta Integration
      • Entra ID Integration
Powered by GitBook
On this page
  • SaaS
  • Ingress traffic
  • Egress traffic
  • On-premise

Was this helpful?

  1. Getting Started

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.

On-premise

PreviousOpenAI ChatGPTNextIdentities, Repositories & Organizations

Last updated 13 days ago

Was this helpful?

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

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

🏨
Data Handling page
contact us