Vectice Docs
API Reference (Latest)Vectice WebsiteStart Free Trial
Latest
Latest
  • 🏠Introduction
    • Vectice overview
      • Autolog
      • Next-Gen Autolog [BETA]
      • AskAI
      • Vectice for financial services
  • 🏁Quickstart
    • Getting started
    • Quickstart project
    • Tutorial project
    • FAQ
  • ▶️Demo Center
    • Feature videos
  • 📊Manage AI/ML projects
    • Organize workspaces
      • Create a workspace
      • Workspace Dashboard
    • Organize projects
      • Create a project
      • Project templates best practices
    • Invite colleagues
    • Define phase requirements
    • Collaborate with your team
  • 🚀Log and Manage Assets with Vectice API
    • API cheatsheets
      • Vectice Python API cheatsheet
      • Vectice R API cheatsheet
    • Connect to API
    • Log assets to Vectice
      • Autolog your assets
      • Log datasets
      • Log models
      • Log attachments and notes
      • Log code
      • Log a custom data source
      • Log assets using Vectice IDs
      • Log dataset structure and statistics
      • Log custom metadata in a table format
      • Log MLFLow runs
    • Retrieve assets from app
    • Manage your assets
    • Manage your iteration
    • Preserve your code and asset lineage
  • 🤝Create Model documentation and reports
    • Create model documentation with Vectice Reports
    • Streamline documentation with Macros
    • Auto-document Models and Datasets with AskAI Prompts
    • Document phase outcomes
  • 🗂️Admin Guides
    • Organization management
    • Workspace management
    • Teams management
    • User management
      • User roles and permissions
      • Update a user role in your organization
      • Activate and deactivate users
      • Reset a user's password
    • Manage report templates
  • 🔗Integrations
    • Integrations Overview
    • Integrate Vectice with your data platform
  • 💻IT & Security
    • IT & Security Overview
    • Secure Evaluation Environment Overview
    • Deployment
      • SaaS offering (Multi-Tenant SaaS)
      • Kubernetes self-hosted offering
        • General Architecture & Infrastructure
        • Kubernetes on GCP
          • Appendices
        • Kubernetes on AWS
          • Appendices
        • Kubernetes on Azure
          • Appendices
        • GCP Marketplace deployment
        • On premise
        • Configuration
      • Bring Your Own LLM Guide
    • Data privacy
    • User management
    • SSO management
      • Generic SAML integration
      • Okta SSO integration
    • Security
      • Data storage security
      • Network Security
        • HTTPS communication
        • Reverse proxy
        • CORS/CSRF
        • VPC segregation
      • Sessions
      • Secrets and certificates
      • Audit logs
      • SOC2
      • Security updates
      • Best practices
      • Business continuity
    • Monitoring
      • Installation guide
      • Customizing the deployments
    • Maintenance & upgrades
    • Integrating Vectice Securely
  • ⭐Glossary
    • Concepts
      • Workspaces
      • Projects
        • Setup a project
      • Phases
      • Iterations
        • Iterative development
      • Datasets
        • Dataset resources
        • Dataset properties
        • Dataset lineage and versions
      • Models
      • Reports
  • 🎯Release notes
    • Release notes
  • ↗️References
    • Vectice Python API Reference
    • Vectice R API Cheatsheet
    • Notebooks and code samples
    • Vectice website
Powered by GitBook
On this page
  • Securing external communications
  • Securing internal communications

Was this helpful?

  1. IT & Security
  2. Security
  3. Network Security

HTTPS communication

PreviousNetwork SecurityNextReverse proxy

Last updated 1 year ago

Was this helpful?

Securing external communications

At Vectice, we understand the importance of safeguarding your data when you use our software. That's why we prioritize secure communication through HTTPS encryption.

For self-hosted Vectice deployments, we recommend using a DNS provider such as with secured certificates. Our SaaS offering comes pre-configured with this setup.

  • Cloudflare certificates: We utilize high-quality SSL/TLS certificates from Cloudflare for our vectice.com domain. These certificates encrypt all communication between your web browser and our servers. This encryption scrambles the data, making it unreadable to anyone who might try to intercept it as it travels across the internet.

  • Cloudflare protection: In addition to the certificates, we benefit from Cloudflare's industry-leading security expertise. CloudFlare acts as an extra shield in front of our infrastructure, filtering out malicious traffic and further safeguarding your connection.

This combined approach with Cloudflare certificates and protection offers robust encryption and an additional layer of security for your data transmitted to and from vectice.com.

Securing internal communications

Understand more about .

We take secure communication within our system very seriously. Here's how we achieve this:

  • Automated certificate management: We utilize cert-manager, a powerful tool within our Kubernetes cluster. This tool automates the entire lifecycle of SSL/TLS certificates for our internal services.

  • HTTPS encryption: With these certificates in place, all application instances within the cluster can communicate with each other securely using HTTPS encryption. This encryption safeguards your data by scrambling it during transmission, making it unreadable to anyone who might intercept it.

  • Streamlined certificate handling: Cert-manager obtains, renews, and deploys certificates automatically. This ensures our certificates are always valid and readily available, minimizing the risk of expired certificates interrupting communication.

By prioritizing secure communication within our infrastructure, we foster a robust and trustworthy internal network for your data.

💻
Cloudflare
cert-manager mechanisms