BoomiSight Security Policy
Last updated: 2026-07-14 Owner: BoomiSight Security Applies to app: BoomiSight for Confluence Review cadence: Quarterly and before Marketplace submission Status: Publication-ready for Marketplace submission
Security Model
Section titled “Security Model”BoomiSight is an Atlassian Forge app. Atlassian hosts the app runtime, storage, user interface, and Rovo action surfaces. BoomiSight stores app configuration and bounded cached facts in Forge-managed storage, stores Boomi API tokens in Forge-managed secret storage, and sends configured backend requests only to the Boomi REST API.
Controls
Section titled “Controls”| Control | Implementation |
|---|---|
| Authentication | Forge invokes app functions in authenticated Atlassian contexts. |
| Authorization | Admin mutations use trusted Forge space context and space-admin checks. Page and space facts use trusted current Confluence context rather than caller-supplied routing identifiers. |
| Licensing | Paid product features check the Atlassian Marketplace license context before returning functionality. |
| Secret storage | Boomi API tokens are stored in Forge-managed secret storage and are not returned to the browser after saving. |
| Least privilege | App permissions are limited to app storage, Confluence space read/write for trusted context and the configured-space marker, and page read for page-local context and explicit bounded scans. BoomiSight does not request page-write access. |
| Egress | Backend fetch is limited to https://api.boomi.com. |
| Retry/backoff | Boomi API requests use bounded retry behavior for throttling and transient upstream failures. |
| Data minimization | UI and Rovo projections exclude raw property values, XREF rows/cells, credentials, source payloads, and internal identifiers. Documentation Health keeps compact findings rather than full page bodies. |
| Navigation | Process Property and XREF links use a dedicated validated HTTPS Boomi Build route on the exact platform.boomi.com host; arbitrary URLs and caller-supplied account routing fail closed. |
| Vulnerability management | CI runs lint, tests, forge lint, npm audit, and weekly CycloneDX SBOM generation. |
| Logging | Operational errors are logged without intentionally emitting Boomi API tokens. |
Vulnerability Reporting
Section titled “Vulnerability Reporting”Report suspected security issues to security [at] flowdence.io. Include the affected site, app surface, reproduction steps, and any relevant timestamps. Do not include secrets in the report.
Assurance Summary
Section titled “Assurance Summary”| Area | Public assurance |
|---|---|
| Platform hosting | BoomiSight runs on Atlassian Forge, using Atlassian-managed runtime and storage services. |
| Customer credentials | Boomi API tokens are stored with Forge-managed secret storage and can be rotated or removed by customers through app configuration. |
| External data access | The app sends configured Boomi API requests to https://api.boomi.com and does not use a Flowdence-hosted backend for product data processing. |
| Access boundaries | Configuration, maintenance, current-page context, current-space facts, scans, and refresh actions are scoped from trusted Forge context. Page reads do not grant page-edit behavior. |
| Cached and Rovo output | Cached views and Rovo answers use bounded safe projections and report stale, partial, unknown, or truncated states rather than widening scope silently. |
| Vulnerability management | Flowdence uses automated CI checks, dependency review, Forge validation, npm audit, and SBOM generation as part of release readiness. |
| Incident handling | Security reports are triaged through Flowdence support and security processes, with customer communication based on severity and impact. |