A security-assurance company must build securely and transparently.
This page documents Oxygenn security principles. Before production access to customer systems, data flows, roles, subprocessors and contractual foundations are defined transparently.
Microsoft Tenant
7 findings
Least Privilege
Integrations should receive only the permissions necessary for the agreed control scope.
Data Minimization
Only evidence and metadata necessary for the service should be processed; sensitive raw data is avoided where unnecessary.
Secure Development
Code review, dependency management, secrets management, logging and change control are part of the development model.
Tenant Isolation
Customer data and permissions are logically separated; production architecture documentation will be provided before enterprise rollout.
Auditability
Administrative actions, evidence changes and relevant exceptions should be traceably logged.
Responsible Disclosure
Security findings can be reported to customer@oxygenn.de; a dedicated security channel will be added before public SaaS launch.