> 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-operations-and-responsibilities.md).

# Security operations & responsibilities

### Sub-processors

Infotopics uses trusted sub-processors to deliver services securely.

| Sub-processor   | Purpose                                   |
| --------------- | ----------------------------------------- |
| Microsoft Azure | Hosting of segregated SaaS environments   |
| TransIP         | Infrastructure services                   |
| HubSpot         | CRM and customer communications           |
| Sentry          | Application monitoring and error tracking |

Sub-processors are reviewed regularly, and material changes are communicated to customers.

***

### Vulnerability management

Infotopics follows a proactive vulnerability management approach:

* Continuous dependency monitoring
* OWASP Top 10 awareness
* Independent penetration testing
* Timely patching and remediation

Security updates are applied as part of normal operations for Share deployments.

***

### Incident and data breach handling

In the event of a security incident:

* Impact is assessed immediately
* Customers are notified without undue delay
* Mitigation actions are applied
* Incidents are documented and reviewed

Incident response procedures align with ISO-aligned security practices.

***

### Customer responsibilities

Customers are responsible for:

* Managing Tableau user access and permissions
* Applying workbook-level security
* Governing data content and sensitivity
* Securing infrastructure in Enterprise deployments

Infotopics cannot override Tableau’s permission model or customer infrastructure controls.

***

### Best practices

We recommend following the additional [data security guidelines](https://help.tableau.com/current/server/en-us/dashboard_extensions.htm) provided by Tableau regarding Tableau Dashboard Extensions. These guidelines offer valuable insights and best practices to enhance the security posture of Tableau deployments while utilizing Extensions effectively. We offer support options to assist customers in resolving any data security concerns or technical issues. Whether utilizing on-premises solutions or SaaS deployments, customers can reach out to our [support](https://appsfortableau.infotopics.com/support/contact-support/) team to address their specific needs promptly.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
