Guidant AI Product Security Information
How to report a vulnerability, security advisories, support periods and software bills of materials. Published under the EU Cyber Resilience Act (CRA); all documents keep their previous versions.
1.Reporting a security vulnerability
If you find a security vulnerability in Guidant AI, email:
This mailbox is read and answered by security staff; it is not an automated form. If mail can't be delivered, write to billows@billows.com.tw or call +886 2 2562 3952 with the subject "Security vulnerability report." We accept Traditional Chinese and English.
If your report contains directly exploitable details, send a first message without them and we'll reply with a secure way to send the rest.
Please include: Affected version and component, vulnerability type, steps to reproduce, your severity estimate, whether exploitation is known, your contact details and whether you'd like to be credited. Don't include personal or customer data that isn't your own.
Our commitments
| Stage | Timeline |
|---|---|
| Acknowledgement | Within 3 to 5 working days, with a tracking number |
| Progress updates | About every 2 to 4 weeks while in progress |
| Fix targets | Critical 1–2 weeks, high 1–2 months, medium 3–6 months |
| Disclosure | Security advisory published after the fix ships; default coordinated disclosure window 90–120 days from acknowledgement |
| Credit | Named in the advisory with your consent |
Good-faith research: Test only in environments you own or are authorized to use, don't access others' data, no denial of service or social engineering, give us reasonable time to fix, don't disclose before publication, and don't make publication conditional on payment. Within those bounds, we commit not to pursue legal action for your research. We don't currently run a bug bounty program.
Full documentVulnerability Disclosure Policy: v1.1 (2026-10-19)Previous versions
No previous versions yet
2.Security advisories
One advisory per fixed vulnerability, numbered GAI-SA-<YYYYMM>-<sequence>, shipped with the corresponding security update and emailed to customer administrators.
| ID | Date | Title | Severity | Affected versions | Fixed in |
|---|---|---|---|---|---|
| (No advisories yet) |
Each advisory expands to show: description, affected products and versions, impact, severity (CVSS), fix or mitigation, credits.
3.Support period
Every version is supported for at least 5 years from the date it is first made available in the EU. A major version series ends on the latest end date of any version in it.
| Series | Supported at least until |
|---|---|
| 1.x | 2031-12-31 (extends with new releases) |
- Security updates are free during the support period, with no maintenance contract required.
- Customers are notified at least 6 months before support ends, with the upgrade path.
- Security updates ship as complete new installer packages applied by the customer's administrator; the product does not download or install updates itself (it runs in customer-managed environments where downtime and database upgrades are the customer's call).
- Every security update remains available for at least 10 years after release.
Full documentSupport Period Statement: v1.1 (2026-10-19)Previous versions
No previous versions yet
4.Software Bill of Materials (SBOM)
Every version ships with a CycloneDX SBOM covering backend application dependencies and five container images (backend, sandbox, frontend, database init, error tracking).
| Version | Release date | SBOM |
|---|---|---|
| 1.26.0 | 2026-10-08 | CycloneDX JSON |
Before every release and at least monthly, the SBOM is checked against known-vulnerability databases; anything affecting the product is handled under the Vulnerability Disclosure Policy.
5.Product security guidance
Security information for customer administrators: intended use, secure operating environment, key security features, configurations that create serious risk, and what to watch at first start-up and decommissioning.
Summary
- A single external entry point (HTTPS) at the frontend; the database and internal services are not exposed.
- Tenant data isolated at the database layer; internal connections encrypted; scanning agents connect over mutual TLS.
- Backend containers run read-only with privileges dropped; evidence files are unpacked in a sandbox with no internet access.
- The installer verifies every file against a bundled SHA-256 manifest; at startup the service verifies the vendor signature and locks itself if tampering is detected.
- Don't: expose ports other than the frontend, keep default passwords, keep using the product after support ends, or remove container security settings.
- Not provided by the product: disk encryption, scheduled backups, protection from volumetric denial-of-service — handle these at the host and network layer.
Full documentProduct Security Guidance: v1.1 (2026-10-19)Previous versions
No previous versions yet
Full documentSecurity Update and Decommissioning Procedure: v1.1 (2026-10-19)Previous versions
No previous versions yet
6.Declaration of conformity
Guidant AI is a default-category product under the CRA, assessed under Module A (internal production control). The EU declaration of conformity will be prepared and signed before the product is first made available in the EU, then published here and shipped with the installer.
7.Manufacturer
- Manufacturer
- Billows Technology Co., Ltd.
- Address
- 6F, No. 129, Songjiang Rd., Zhongshan Dist., Taipei City 104074, Taiwan
- Phone
- +886 2 2562 3952
- General contact
- billows@billows.com.tw
- Security reports
- security@billows.com.tw
- Website
- https://www.billows.tech
Last updated 2026-10-21. Document versions are kept for at least 10 years at stable URLs.