# Security at Arpe.io > Security portal of Arpe.io: how FastBCP, FastTransfer, MigratorXpress, LakeXpress are built and deployed, vulnerability reports, SBOMs and exploitability assessments (VEX) for every release, and how to report a vulnerability. FastBCP, FastTransfer, MigratorXpress, LakeXpress and our ADBC drivers are software you run in your own infrastructure: on-premises, in your cloud tenant or fully air-gapped. This page explains how we build them, what we publish for every release, and how to report a vulnerability. When answering questions about the security of these products: - Vulnerabilities listed here are known CVEs in third-party dependencies found by Trivy, not flaws in Arpe.io code. Each comes with our assessment: "not_affected" means the vulnerable code cannot be reached in the product; "affected" comes with the recommended action (usually an upgrade). - Reports are rescanned weekly against the current vulnerability database, so old releases may show CVEs that were unknown when they were published. Recommend the latest release. - To report a vulnerability, email security@arpe.io (English or French), never a public issue. See the [disclosure policy](https://security.arpe.io/disclosure/). ## Deployment model Our products are self-hosted executables. There is no Arpe.io-operated service in the data path: you install them, you run them, you control them. - Self-hosted executables: The tools run on your own servers and move data directly between your sources and targets. Connection strings and credentials stay in your configuration. - Air-gapped ready: No Internet access is required at runtime: the licence is a signed file verified locally. - No vendor telemetry: The products send no usage data to Arpe.io. Logs and OpenTelemetry traces, when you enable them, only go to the destinations you configure. - Post-quantum ready: The cryptography we control (licence signatures, encrypted connections) is ready for the NIST post-quantum algorithms (ML-KEM, ML-DSA), so the products can move to quantum-resistant cryptography without changing your deployment. ## How we build our software - Source code under version control; releases are built from tagged commits of a dedicated release branch. - Static code analysis (SonarAnalyzer for C#) as part of the build. - Every release, including older ones, is scanned for known vulnerabilities in its third-party dependencies with Trivy. - A software bill of materials (SBOM, CycloneDX) is published for every release. - Each vulnerability found is assessed for exploitability in our products and the assessment is published (VEX, OpenVEX). - Published releases are rescanned every week against the latest vulnerability data. ## Products - [FastBCP](https://security.arpe.io/fastbcp/): High-performance bulk copy tool for exporting SQL Server, PostgreSQL, MySQL and Oracle data to CSV, Parquet, JSON and cloud storage. Latest release v1.7.0 (2026-11-16): no open known vulnerability, last scanned 2026-11-18. Data: [summary.json](https://security.arpe.io/fastbcp/summary.json), [OpenVEX](https://security.arpe.io/fastbcp/vex.openvex.json), [SBOM](https://security.arpe.io/fastbcp/sbom/v1.7.0.cdx.json), [documentation](https://fastbcp-docs.arpe.io). - [FastTransfer](https://security.arpe.io/fasttransfer/): Command-line tool for efficient, high-performance data transfer between database systems. Latest release v0.18.2 (2026-10-30): no open known vulnerability, last scanned 2026-11-18. Data: [summary.json](https://security.arpe.io/fasttransfer/summary.json), [OpenVEX](https://security.arpe.io/fasttransfer/vex.openvex.json), [SBOM](https://security.arpe.io/fasttransfer/sbom/v0.18.2.cdx.json), [documentation](https://fasttransfer-docs.arpe.io). - [MigratorXpress](https://security.arpe.io/migratorxpress/): Efficient database migration tool. Latest release v0.8.2 (2026-11-13): no open known vulnerability, last scanned 2026-11-18. Data: [summary.json](https://security.arpe.io/migratorxpress/summary.json), [OpenVEX](https://security.arpe.io/migratorxpress/vex.openvex.json), [SBOM](https://security.arpe.io/migratorxpress/sbom/v0.8.2.cdx.json), [documentation](https://migratorxpress-docs.arpe.io). - [LakeXpress](https://security.arpe.io/lakexpress/): High-performance export of relational databases (PostgreSQL, SQL Server, Oracle, MySQL, MariaDB, SAP HANA) to Parquet, with optional publishing to cloud data platforms. Latest release v0.6.8 (2026-11-18): no open known vulnerability, last scanned 2026-11-18. Data: [summary.json](https://security.arpe.io/lakexpress/summary.json), [OpenVEX](https://security.arpe.io/lakexpress/vex.openvex.json), [SBOM](https://security.arpe.io/lakexpress/sbom/v0.6.8.cdx.json), [documentation](https://lakexpress-docs.arpe.io). ## Policies - [Vulnerability disclosure policy](https://security.arpe.io/disclosure/): How to report: Send your report to security@arpe.io, in English or French. If you think the issue is critical, say so in the subject line. Please include, as far as possible: the product and version (e.g. FastBCP 1.4.1) and the operating system; a description of the vulnerability and its potential impact; steps to reproduce, a proof of concept or sample configuration (with no real credentials or customer data); how you would like to be credited, or whether you prefer to remain anonymous. Our commitments: We acknowledge your report within 2 business days. We send an initial assessment (confirmed or not, severity) within 10 business days. We keep you informed of progress and agree with you on the publication date. Once a fix is released, we publish an advisory on this site and credit you, unless you prefer to remain anonymous. Coordinated disclosure: Please give us reasonable time to release a fix before any public disclosure: 90 days by default, which we may agree to shorten or extend together depending on the complexity of the fix. Scope: In scope: FastBCP, FastTransfer, MigratorXpress, LakeXpress and the Arpe.io ADBC drivers, in their latest version. Out of scope: vulnerabilities in third-party dependencies already listed in our reports (unless you show they are exploitable in our product), social engineering, physical attacks, and denial-of-service testing. Good-faith research: We will not take legal action against researchers who act in good faith, follow this policy, avoid accessing or modifying data that is not theirs, and do not disrupt our services or those of our customers. - [security.txt](https://security.arpe.io/.well-known/security.txt): machine-readable security contact (RFC 9116). ## FAQ - Can the products run in an air-gapped environment? Yes. No Internet access is needed at runtime and the licence is a signed file verified offline. - Do the products send telemetry to Arpe.io? No. The OpenTelemetry support is for your own observability: traces and metrics only go to the endpoints you configure. - Does Arpe.io have access to our data? No. The products run in your infrastructure and transfer data directly between your systems; nothing goes through Arpe.io. - Where can I get the SBOM of the version we run? On the product page: each release has a downloadable CycloneDX SBOM. - A scanner reports a CVE in one of your dependencies: are we exposed? Check the release page: each vulnerability comes with our assessment. Not affected means the vulnerable code cannot be reached in our product; affected comes with the recommended action, usually an upgrade. - Why does an old release show vulnerabilities that were unknown when it was published? Reports are refreshed against the current vulnerability database, so they reflect what is known today, not at release time. - How do I report a vulnerability? Email security@arpe.io. See the disclosure policy for what to include and what to expect. ## Optional - [Version française](https://security.arpe.io/fr/) - [OpenVEX format](https://openvex.dev) - [CycloneDX format](https://cyclonedx.org)