Data Storage
Nextedy Apps store 100% of their data in Polarion’s existing storage layer. This includes Polarion’s SVN repository (for document and work item versioning) and the relational database (for structured queries and indexing). Nextedy Apps do not:- Create or use separate databases
- Write data to the local filesystem outside of Polarion’s storage
- Transmit data to external services, APIs, or cloud endpoints
- Maintain caches or data stores outside of Polarion’s JVM
What Data Do Apps Modify?
Nextedy Apps read and write standard Polarion data objects within the authenticated user’s permission scope:| Data Type | Examples | Storage Location |
|---|---|---|
| Work item fields | Risk severity, occurrence, detection ratings | Polarion database + SVN |
| Work item links | Trace links between requirements and risks | Polarion database + SVN |
| Custom fields | Product-specific fields (e.g., ASIL level, risk class) | Polarion database + SVN |
| Document structure | LiveDoc section ordering, table layouts | Polarion SVN |
| Configuration | Sheet layouts, column definitions, model YAML | Polarion SVN (.polarion/ directory) |
Encryption in Transit
All communication between the user’s browser and the Polarion server uses HTTPS with TLS 1.2 or higher. This encryption is configured and managed at the Polarion platform level (or by the infrastructure provider for Polarion X). Nextedy Apps do not establish separate network connections. All data flows through Polarion’s existing HTTPS endpoint.Encryption at Rest
Encryption of data at rest is the responsibility of the infrastructure owner:- On-premise — The customer manages disk encryption, database encryption, and SVN repository encryption according to their own security policies.
- Polarion X — Siemens manages encryption at rest as part of the Polarion X infrastructure.
Data Isolation
Polarion provides project-level access control. Each Polarion project has its own set of roles, permissions, and membership. Nextedy Apps respect this isolation:- Users only see data from projects they have been granted access to.
- Cross-project queries are filtered by Polarion’s permission engine before results reach the app.
- Sheet configurations and model definitions are scoped to individual projects.