Security and operations: where Ovenca runs and who has access
You decide where Ovenca is operated and where your procurement and supplier data resides: as a private cloud in a data centre in Germany or in your own infrastructure. In both cases Onveda deploys and maintains the application.
This page summarises for information security, data protection and IT operations what applies to both operating models: responsibilities, access, support with response times, target values for availability and backup, and the evidence for your review.
- Your infrastructure (e.g. Azure)
- Your data centre or your own cloud environment
- Private cloud
- Separate instance in a data centre in Germany
- Single sign-on
- Sign-in through your identity provider with SAML 2.0 or OpenID Connect, tested with Microsoft Entra ID.
- Multi-factor authentication
- TOTP via an authenticator app.
Operating models and responsibilities
Both models use the same software. They differ in who operates the instance and where the data resides.
| Criterion | Your infrastructure (e.g. Azure) | Private cloud |
|---|---|---|
| Location of the instance | Your data centre or your own cloud environment | Separate instance in a data centre in Germany |
| Operation of the instance | Onveda deploys and maintains the application; infrastructure with you | Onveda |
| Availability | 99.5% per year as a target for the application; the availability of your infrastructure is your responsibility | 99.5% per year as a target, excluding planned maintenance windows |
| Technical and operational control | Infrastructure with you, application with Onveda | With Onveda, on an instance operated for you alone |
| Data residency | Entirely within your infrastructure | In Germany |
| Interfaces to the ERP | Run within your infrastructure between Ovenca and your ERP | Run between the private cloud instance and your systems. The connection path is defined during the evaluation. |
| Data protection agreement | Data processing agreement under Art. 28 GDPR with Onveda for operating and maintaining the application | Data processing agreement under Art. 28 GDPR with Onveda |
In both models Onveda handles maintenance, updates and support.
Access control
Roles determine who may see and change what. Sign-in runs through your identity provider.
- Roles and permissions
- Permissions are granted per role, separately for read, create, update and delete.
- Objects and relations
- Permissions apply per object, such as suppliers, catalogs or products, and per relation between objects.
- Legal entities and plants
- Legal entities and plants are part of the permission structure and reflect your organisation.
- Single sign-on
- Sign-in through your identity provider with SAML 2.0 or OpenID Connect, tested with Microsoft Entra ID.
- Multi-factor authentication
- TOTP via an authenticator app.

- Four permissionsRead, create, update and delete are granted individually.
- Object or relationEach row is marked as an entity or a relation.
- OrganisationLegal entities and plants appear as relations of their own.
View from the product: permissions of a role in the Admin Area.
Traceability
Changes to catalogs, approvals and users are logged in the audit trail.
- Catalogs
- Changes to catalogs are logged. In Catalog Management each catalog has its own history.
- Approvals
- Approval decisions are logged.
- Users
- Changes to users are logged.
Data protection and data residency
The place of processing follows the operating model you choose.
- Data processing
- Onveda concludes a data processing agreement with you under Art. 28 GDPR, in the private cloud as well as for operation in your infrastructure.
- Data location
- In your infrastructure or in the private cloud in Germany.
- Separate instance
- In the private cloud, Ovenca runs for you as a separate instance.
- Transport encryption
- TLS for the web interface and the interfaces.
Support by the developers
Support is provided by the Onveda developers who build and operate Ovenca. The first response depends on the priority of the ticket.
| Priority | Description | First response |
|---|---|---|
| P1 critical | Ovenca cannot be used, orders are not possible | 1 hour |
| P2 high | An essential function is impaired, for example approvals or the handover to the ERP | 4 hours |
| P3 medium | A single function is restricted and a workaround exists | Next working day |
| P4 low | Questions, minor bugs and change requests | 2 working days |
- Service hours
- Working days from 8:00 to 17:00 CET. The first response times apply within service hours.
- On-call service
- Available as an option for P1 tickets outside service hours.
Availability, backup and recovery
The following values are targets and apply to both operating models. Binding values are set out in the contract.
- Availability
- 99.5% per year, excluding planned maintenance windows
- Backup
- Depending on the operating environment continuously in real time, plus daily; retention 30 days
- Recovery point (RPO)
- 24 hours
- Recovery time (RTO)
- 8 hours
Your data
Data export during the term and handover at the end of the contract.
- Data export
- Possible at any time.
- End of contract
- Onveda hands over your data in full.
Evidence for your review
For information security, data protection and co-determination we provide the documents your review requires.
- ISO 27001
- Onveda aims to be certified to ISO 27001 by the second quarter of 2027 at the latest.
- Data processing
- Data processing agreement under Art. 28 GDPR, in the private cloud as well as for operation in your infrastructure.
- Works council and DPIA
- Information for works council co-determination and for your data protection impact assessment is available on request.
- Penetration tests
- Carried out by Onveda, comprehensively on request. The team has more than ten years of experience with penetration testing.
- Updates and patches
- Applied by Onveda in both operating models.
- Security questionnaire
- We answer it in writing for the operating model you are assessing.
Related pages
Platform
Integration and architecture
Order flow, punchout, interfaces and the connection to SAP and other ERP systems.
Reference
LANXESS case study
In use worldwide, working together since 2014, with SAP contracts and material numbers in product search.
Send your security questionnaire or request a technical discussion
Send your security questionnaire to info@ovenca.com or announce it through the form. Three details help us place your request.
- Preferred operating model: private cloud in Germany or your own infrastructure
- Identity provider and protocol for single sign-on
- Internal requirements on data residency and data processing