Security

Security at 1Security

How we certify, host and encrypt the 1Security service, and how to report a vulnerability to us.

Last updated November 5, 2026

Diese Seite ist nur auf Englisch verfügbar. Verbindlich ist die englische Fassung.

Certified

ISO/IEC 27001:2022 information security management system.

Hosted in the EU

Microsoft Azure, Sweden Central region.

Encrypted

AES-256 at rest and TLS 1.2 or later in transit.

Certification

1.Security sp. z o.o. operates an information security management system certified to ISO/IEC 27001:2022 (certificate number 30954151 ISMS22), issued by the accredited certification body DQS GmbH.

Hosting and data residency

  • The 1Security Cloud (SaaS) service runs on Microsoft Azure in the Sweden Central region, in the European Union.
  • Every connected tenant gets its own dedicated database. A query for one tenant cannot reach another tenant’s data.
  • Database backups are kept for 14 days, encrypted and stored in the same region.
  • Customers whose rules require data to stay in their own environment can run 1Security in their own Azure subscription (BYOC) or on their own hardware (On-Premise).

Encryption

  • At rest: databases, disks, the container registry and backups are encrypted with AES-256 by the Azure platform.
  • In the application: the most sensitive values, such as tenant database credentials and session refresh tokens, are additionally encrypted with AES-256 before they are written to the database.
  • In transit: all traffic to the service uses HTTPS with TLS 1.2 or TLS 1.3. Plain HTTP is redirected to HTTPS. Calls to Microsoft APIs use TLS, and traffic between the application and its databases stays on a private Azure network.

Access to your Microsoft 365 tenant

  • Users sign in with Microsoft Entra ID only. 1Security stores no passwords, and your organization’s MFA and Conditional Access policies apply at every sign-in.
  • The service connects to Microsoft Graph with application permissions authenticated by a certificate, not a shared client secret.
  • The base installation reads your tenant. Write permissions are granted only if you enable an optional remediation module.
  • File and email content is analysed in memory during classification and is not stored.
  • AI assistants you connect use read-only OAuth access, which you can revoke at any time in Authorized apps.

Report a vulnerability

If you believe you have found a security vulnerability in 1Security, email adamzaczek@1security.ai. You can write in English or Polish. We do not run a bug bounty programme.

Please include:

  • a description of the issue and its potential impact;
  • the affected URL, endpoint or component;
  • the steps needed to reproduce it, with any proof-of-concept code or screenshots;
  • how we can reach you for follow-up questions.

While you investigate, please:

  • test only against your own account and tenant, and do not access, change or delete data that belongs to others;
  • do not run denial-of-service, spam or social-engineering tests;
  • give us reasonable time to fix the issue before you disclose it publicly.

We confirm that we received your report, keep you informed while we investigate, and tell you when the issue is fixed.

The same contact is published in /.well-known/security.txt.

Documents

We do not run a separate trust centre. This page and the documents below are what we publish.

A data processing agreement (DPA) is available on request: write to privacy@1security.ai.

For security questionnaires and other questions, contact support@1security.ai or use our contact page.