> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/deployment-and-licensing/security-and-data-protection/security-overview-and-certifications.md).

# Security overview & certifications

Infotopics Apps for Tableau are built with security by design and follow internationally recognised standards to protect customer data, infrastructure, and operational processes.

This documentation is intended for:

* IT administrators
* Security and compliance teams
* Architects and procurement reviewers

Security responsibilities vary depending on the **deployment model (Share or Enterprise)** and the **product used**, but the same core security principles apply across all Apps for Tableau.

***

### ISO/IEC 27001:2022 Certification

Infotopics | Apps for Tableau is **ISO/IEC 27001:2022 certified**, the globally recognised standard for Information Security Management Systems (ISMS).

This certification confirms that Infotopics:

* Identifies and manages information security risks
* Applies formal security controls and policies
* Continuously monitors and improves security practices
* Is independently audited on a regular basis

<figure><img src="https://1734369479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJjt7zXdgUjvEf9GT1Q3y%2Fuploads%2FLlsYPIwiHQGAlwwMlEX9%2Fimage.png?alt=media&amp;token=530fa5ba-1b4d-44d5-8241-842b7dd43271" alt=""><figcaption></figcaption></figure>

The ISO certification applies particularly to **Share (SaaS) deployments**, where Infotopics operates and secures the hosting environment on behalf of customers.

***

### Security governance

Infotopics maintains a structured security governance framework that includes:

* Documented security and access policies
* Role-based access control
* Secure development lifecycle practices
* Incident detection and response procedures
* Regular internal and external security reviews

Security is treated as an ongoing process, not a one-time activity.

***

### Secure-by-design approach

All Apps for Tableau are designed to:

* Minimise data exposure
* Respect Tableau’s security model
* Avoid unnecessary data storage
* Operate transparently within customer environments

### Security whitepaper

Infotopics provides a detailed **Security Whitepaper** that explains how Apps for Tableau are designed, deployed, and operated securely.

The whitepaper covers:

* Security architecture and principles
* Tableau Extensions security model
* SaaS (Share) and Enterprise deployment security
* Data protection and operational safeguards

The document is intended for IT, security, and compliance reviews.

[Download the Security Whitepaper](https://indd.adobe.com/view/841678f9-7b3b-433e-bed8-305e16710048)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infotopics.com/deployment-and-licensing/security-and-data-protection/security-overview-and-certifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
