---
title: Security Overview
description: "Effective date: January 1, 2026 [Accept Mission](https://www.acceptmission.com/pt/encyclopedia/accept-mission/) is an AI powered innovation management platform built for companies and innovation teams. Security is a core part of how we design, build, and operate the platform. ## 1) Security principles We focus…"
url: "https://www.acceptmission.com/pt/knowledge/security-overview/"
updated: "2026-10-16"
category: "Security & Trust"
---

# Security Overview

Effective date: January 1, 2026

[Accept Mission](https://www.acceptmission.com/pt/encyclopedia/accept-mission/) is an AI powered innovation management platform built for companies and innovation teams. Security is a core part of how we design, build, and operate the platform.

## 1) Security principles

We focus on protecting customer data through:

- Strong access control and secure authentication
- Tenant isolation
- Monitoring and incident response readiness
- Encrypted data storage and encrypted data transfer
- Secure development and fast patching
- Backups and disaster recovery planning

## 2) Hosting, region, and high-level architecture

### Cloud hosting

[Accept Mission](https://www.acceptmission.com/pt/encyclopedia/accept-mission/) runs on Microsoft Azure infrastructure and is hosted on infrastructure we control via Microsoft Azure Kubernetes.

### Default data region

Standard hosting is in West Europe. Enterprise customers can choose to place their database server in another location worldwide.

### Network and environment design (high level)

- Customer clusters and databases are hosted in a private network environment.
- Internet-bound traffic flows through a controlled NAT path.
- Access to infrastructure is restricted and managed through controlled administrative access.

## 3) Authentication and authorization

### Authentication

We support secure Single Sign-On (SSO). Workspace admins can enable SSO with options such as SAML, Azure B2B, and OpenID, including integrations with third-party identity providers.

### Authorization

Access is governed through role-based permissions and controlled visibility. Organizations can define who can view, edit, evaluate, or manage ideas, initiatives, and data across the platform.

## 4) Access control and tenant isolation

### Tenant isolation

Enterprise customers are isolated with their own database and unique credentials. Customers are isolated inside their own namespace within Kubernetes, with network policies and role controls designed to ensure tenant separation.

### Operational access controls

Infrastructure access is limited to designated authorized operations team members, protected by strong authentication and restricted access paths.

## 5) Encryption and data protection

Data is encrypted at rest.

Data transfer uses TLS, including TLS v1.3 for encrypted communication in the default configuration.

## 6) Monitoring, detection, and incident response

### Service monitoring

We proactively monitor the service with dashboards and alerts to detect unusual behavior or reliability issues.

### Suspicious behavior detection

Unusual network patterns and suspicious behavior are monitored. Azure infrastructure uses intrusion detection and prevention systems (IDS/IPS) to identify patterns aligned with known attack methods.

## 7) Secure development and vulnerability management

We audit changes throughout the development lifecycle through architecture reviews and automated and manual code review processes.

We keep the software up to date with fast patching timeframes for critical and high vulnerabilities, and regular update cycles.

We use third parties to perform application security assessments and conduct annual vulnerability assessment and penetration testing.

## 8) Backups, business continuity, and disaster recovery

The platform uses redundancy to support high availability.

We keep continuous encrypted backups on Azure and can restore organizational data from backups if primary data stores are lost.

In a region-wide outage, we can bring up a duplicate environment in another Azure region while respecting agreed data location.

Recovery targets: RPO 24 hours and RTO 72 hours.

## 9) Contact

For security questions, contact: security@acceptmission.com.

## Configure Single Sign-On

For the complete customer setup instructions, see [Configure Single Sign-On with Accept Mission](https://www.acceptmission.com/knowledge/configure-single-sign-on-with-accept-mission/).