mirror of
https://github.com/hanzoai/team.git
synced 2026-09-30 01:57:35 +00:00
b5f007d35e
* docs: resolve cross-file anchor mismatches from RST-to-MDX migration
The Sphinx-to-Docusaurus migration converted `:ref:`/`{ref}` links using
naive text-slugification, so anchors that pointed to headings in a
different file (e.g. release-summary tables linking into their
respective changelog pages) were emitted as same-page fragments and
silently resolved to nothing.
Built a label registry from the original Sphinx `.. _label:` / `(label)=`
targets to recover the true source file for each cross-reference, then
rewrote the affected links to point at the correct file + heading
anchor. Fixes 282 broken cross-file anchors, primarily in the mobile/
desktop/server release-summary pages, plus assorted same-page anchor
mismatches caught by re-auditing after the prior admonition/anchor fix.
* docs: manually resolve remaining anchor mismatches after cross-file audit
Hand-verified fixes for anchors that fuzzy-matching alone couldn't
safely resolve (confirmed against actual heading text/context, and in a
few cases against the original RST source, before applying):
- Typos and dropped words carried over from the original Sphinx docs
(e.g. "bot-acocunts", "auto-follow-all-new-channel-threads" ->
"follow-all-new-channel-threads").
- Sphinx auto-generated duplicate-heading IDs (#id1/#id3/#id4) resolved
to their real target headings.
- Numbered-step TOC links in enterprise-roll-out-checklist.mdx that
dropped the leading "N. " used in the actual heading slugs.
- Push-notification docs pointing at the wrong file entirely
(environment-configuration-settings instead of
push-notification-server-configuration-settings).
- SAML "saml-enterprise" label resolved to its true cross-file target
(authentication-configuration-settings#saml-2-0), recovered from the
original RST label definition that the automated registry missed
because it sat after an RST transition marker.
- sso-saml-technical references converted from broken same-page/
malformed-path anchors to correct page links.
* docs: fix SAML 2.0 anchor slug (saml-2-0 -> saml-20)
github-slugger strips periods rather than hyphenating them, so "SAML
2.0" slugifies to saml-20, not saml-2-0 as previously fixed.
* docs: fix broken path links found during docs/main migration cleanup
* docs: convert div.tab blocks to Docusaurus Tabs/TabItem components
* docs: restore missing Kubernetes deployment architecture diagrams
The RST-to-MDX migration never copied over the AWS/Azure/Oracle
architecture diagrams referenced by the deployment-architecture-at-scale
page, leaving broken images in each Tabs/TabItem.
* docs: fix 7 anchor mismatches from the fragment/heading audit
Covers three root causes from the anchor mismatch breakdown:
- Fragment repeated the target page's own title instead of a real
heading, so the link is simplified to point at the bare page.
- Heading exists verbatim but lives on a sibling settings page
(experimental-configuration-settings, push-notification-server-
configuration-settings) rather than environment-configuration-settings.
- A page path was mistakenly pasted into a same-page #fragment instead
of being used as a real cross-page link.
* docs: fix 8 anchor slugs that were close but didn't match the real heading
Repoints links whose fragment was a plausible guess (typo, reworded
heading, or wrong section) at the actual auto-generated slug of the
target heading, confirmed by inspecting each target page directly.
* docs: merge split Tabs blocks so tabs render horizontally
The div.tab conversion script split some sibling tab groups into
separate single-item Tabs blocks whenever a stray blockquote marker
sat between them, causing them to render stacked instead of as one
horizontal tab bar. Merges the MySQL/PostgreSQL and Team/Enterprise
Edition tab groups back into single Tabs blocks.
* docs: remove Azure tab and restore Kubernetes deploy content
The Mattermost Operator, Azure, and Oracle platform tabs on the
Kubernetes deployment guide were split across two separate Tabs
blocks (rendering stacked instead of as one tab bar) and all three
tab bodies were empty because the migration never flattened the
original RST include directives. Removes the unsupported Azure tab
and restores the Mattermost Operator and Oracle content from the
pre-migration RST sources as a single merged Tabs block.
* addresscoderabbitreview
* docs: unify Linux/Kubernetes/Containers deploy pages and fix FIPS/STIG placement
Kubernetes and Containers duplicated full install content across a top-level
page (Tabs) and orphaned sidebar subpages that nothing linked to. Reworked
both to follow the Linux page's pattern: shared content on the landing page,
platform-specific instructions live once in their own subpage.
Also removed configure-fips-at-install-time.mdx, which claimed FIPS is
available for native Linux installs — FIPS/STIG in Mattermost is a container
image property (Chainguard-based build), not available outside Docker/
Kubernetes. Consolidated all FIPS/STIG references onto
containers/fips-stig.mdx and pointed the Mattermost Operator subpage (not
Oracle OKE, which doesn't expose image selection) at it.
* docs: fix review findings — image alt text, Important callout markup, typo
- Replace generic alt="image" on scaling diagrams with descriptive text
identifying cloud provider and user scale.
- Convert raw div.important markup in deploy-containers.mdx to the
repo's <Important> component, matching usage elsewhere in the file.
- Fix "Matermost" typo in manage-your-display-options.mdx.
---------
Co-authored-by: Hanzo Dev <[email protected]>
125 lines
14 KiB
Plaintext
125 lines
14 KiB
Plaintext
---
|
||
title: "Zero Trust with Mattermost"
|
||
---
|
||
Mattermost helps organizations adopt and implement Zero Trust principles to safeguard their mission-critical communications and collaboration.
|
||
|
||
For security teams, Mattermost’s zero-trust-first approach ensures consistent compliance with organizational risk policies by automating key governance processes like incident response or data lifecycle management.
|
||
|
||
Unlike traditional security approaches, Zero Trust assumes every user and system may be a potential threat. Mattermost implements this paradigm by offering customizable, secure solutions that protect sensitive communication workflows from both internal and external risks.
|
||
|
||
This document outlines how Mattermost supports the core tenets of Zero Trust, for organizations of different sizes, including [Identity and access management](#identity-and-access-management), [Continuous monitoring](#continuous-monitoring), [Deployment and host control](#deployment-and-host-control), [Encryption](#encryption), [Micro-segmentation](#micro-segmentation), [Multi-factor authentication](#multi-factor-authentication-mfa), [Data management](#data-management), and [Incident response](#incident-response). Links to detailed documentation resources are provided below.
|
||
|
||
## Identity and access management
|
||
|
||
Mattermost integrates seamlessly with enterprise identity providers (IdPs), enabling strong identity verification and strict access control.
|
||
|
||
By using one of the secure identity mechanisms listed below and enforcing least-privilege access via roles and groups, Mattermost ensures that only verified individuals gain access to the platform and its resources:
|
||
|
||
- [SAML](/administration-guide/onboard/sso-saml): Enables seamless Single Sign-On, ensuring centralized authentication to continuously enforce user verification.
|
||
- [LDAP](/administration-guide/onboard/ad-ldap): Facilitates integration with enterprise directories to tightly control user access, adhering to granular identity verification.
|
||
- [OpenID Connect](/administration-guide/configure/authentication-configuration-settings#openid-connect): Provides secure, standards-based user authentication to verify identities and enforce secure access.
|
||
- [Session Management](/administration-guide/configure/environment-configuration-settings#session-lengths): Strengthens continuous authentication by controlling session lengths and automatically revoking sessions based on inactivity or policy violations, ensuring constant identity verification. By limiting session lifetimes and enforcing strict session policies, Mattermost mitigates the risk of stolen session tokens or extended unauthorized access.
|
||
|
||
Authorized users can seamlessly be added and removed from channels utilizing the native AD/LDAP integration based on group memberships:
|
||
|
||
- [LDAP Synchronized User Groups](/administration-guide/onboard/ad-ldap-groups-synchronization): Automates user management and access control by dynamically syncing with organizational directories to minimize risks and enforce policies.
|
||
|
||
## Continuous monitoring
|
||
|
||
Mattermost offers tools for monitoring activity, identifying suspicious behavior, session management, and real-time incident response. Audit trails and performance monitoring ensure the proactive detection of potential issues or breaches, delivering visibility into the activity across the platform.
|
||
|
||
- [Audit Logging](/administration-guide/manage/logging): Tracks detailed activity logs for monitoring and identifying real-time anomaly-detection use cases, such as detecting anomalous behavior from compromised accounts or insider threats, or responding to unusual file-sharing activity within sensitive channels.
|
||
- [SIEM Integrations](https://developers.mattermost.com/integrate/webhooks/): Streamlines monitoring within existing security systems to detect and respond to lateral movement threats or policy violations consistently.
|
||
- [Performance Monitoring](/administration-guide/scale/deploy-prometheus-grafana-for-performance-monitoring): Protects against potential threats by analyzing system and user behaviors via proactive monitoring.
|
||
|
||
## Deployment and host control
|
||
|
||
Flexibility and control to host Mattermost securely to minimize the risk of vulnerabilities, downtime, and unauthorized modifications by ensuring secure, efficient, and reliable deployment of applications while maintaining strict control over the hosting environment.
|
||
|
||
Mattermost's self-hosting enables tailored configurations for on-premises systems with specialized security needs, while cloud IP filtering ensures scalable control for remote or hybrid teams operating across distributed environments:
|
||
|
||
- [Self-hosting Mattermost](/deployment-guide/deployment-guide-index): Enforces stricter data sovereignty requirements, and complete control over deployment environments, enabling organizations to implement custom Zero Trust security measures.
|
||
- [Cloud IP Filtering](/administration-guide/manage/cloud-ip-filtering): Prevents untrusted entities from gaining initial access, restricting platform access to trusted network ranges, enforcing an evaluation of every connection.
|
||
|
||
## Encryption
|
||
|
||
Encryption protects both data at rest and data in transit, ensuring end-to-end security for sensitive communications. Encryption mitigates the risk of data theft in both storage and transfer, while granular permissions limit access to sensitive files and data to only authorized users.
|
||
|
||
- [Database Encryption](/deployment-guide/encryption-options#database): Protects user and organizational data at rest, safeguarding sensitive information from unauthorized access.
|
||
- [Transport Layer Security (TLS) Encryption](/deployment-guide/encryption-options#encryption-in-transit): Secures data in transit by encrypting communications.
|
||
- [Policy Enforcement](/deployment-guide/encryption-options#file-storage): Ensures strict compliance through automated enforcement, protecting data integrity.
|
||
|
||
## Micro-segmentation
|
||
|
||
Segmenting and isolating sensitive resources is vital in minimizing lateral movement during an attack. Mattermost supports micro-segmentation through its organizational and role-based capabilities. Micro-segmentation enables organizations to restrict access to sensitive conversations, ensuring secure communication channels tailored to individual teams or missions.
|
||
|
||
To achieve comprehensive micro-segmentation, the following areas of Mattermost functionality play a critical role.
|
||
|
||
### Access control and permissions
|
||
|
||
Ensure precise and role-based access to sensitive resources in order to minimize the risk of unauthorized access and potential data breaches:
|
||
|
||
- [Advanced Access Controls](/administration-guide/manage/team-channel-members#advanced-access-controls): Enforces specific permissions configurations to restrict access based on roles.
|
||
- [Playbook-Specific Permissions](/end-user-guide/workflow-automation/share-and-collaborate): Controls access to sensitive workflows, ensuring resources are available only to authorized team members.
|
||
|
||
### Organizational design and user management
|
||
|
||
Establish a structured and scalable framework for managing user identities, roles, and access workflows to ensure accountability, facilitate collaboration, and enforce security policies:
|
||
|
||
- [Teams](/end-user-guide/collaborate/organize-using-teams): Enables segmentation of access and collaboration, fostering compartmentalization and limiting exposure to unauthorized users.
|
||
- [Private Channels](/end-user-guide/collaborate/channel-types#private-channels): Restricts conversations to authorized participants, protecting sensitive data and adhering to need-to-know principles.
|
||
- [Guest Accounts](/administration-guide/onboard/guest-accounts): Enables secure, scoped access for external parties, ensuring least privilege principles are maintained.
|
||
- [Custom User Groups](/end-user-guide/collaborate/organize-using-custom-user-groups): Allows precise administrative control of access and permissions for specific user sets, enhancing access segmentation.
|
||
|
||
### Administrative controls
|
||
|
||
Enforce logical segmentation through team-level and group-level management, enhancing productivity and security by aligning user access with their specific roles:
|
||
|
||
- [Delegated Granular Administration](/administration-guide/onboard/delegated-granular-administration): Ensures operational security by enabling controlled management access based on responsibilities.
|
||
- [Custom Terms of Service](/administration-guide/comply/custom-terms-of-service): Requires users to acknowledge organization-specific Terms of Service before access ensures alignment with security policies and strengthens compliance, particularly in regulated industries where custom terms may reflect specific mandates.
|
||
- [Granular Permissions](/administration-guide/onboard/delegated-granular-administration): Facilitates precise control over user and system permissions, adhering to the principle of least privilege.
|
||
- [Read-Only Permissions for Files](/administration-guide/configure/site-configuration-settings#file-sharing-and-downloads): Limits file-sharing capabilities to safeguard sensitive information from unauthorized alterations.
|
||
|
||
### Security policies and tokens
|
||
|
||
Enhance security with tailored authentication tools to protect systems and data from unauthorized API usage and credential misuse by establishing and enforcing secure, consistent, and scalable authentication mechanisms:
|
||
|
||
- [Personal Access Tokens](https://developers.mattermost.com/integrate/reference/personal-access-token/): Enables secure API access with identity verification aligned to least privilege.
|
||
|
||
## Multi-factor authentication (MFA)
|
||
|
||
Mattermost supports MFA to strengthen authentication practices by adding an extra layer of protection for high-risk workflows beyond passwords:
|
||
|
||
- [MFA](/administration-guide/onboard/multi-factor-authentication): Enhances user identity verification by requiring multiple factors for authentication. MFA ensures that unauthorized users are denied access even if passwords are compromised, reducing the risk of account breaches.
|
||
|
||
Alternatively, often enforced through the identity provider (IDP).
|
||
|
||
## Data management
|
||
|
||
Data management directly addresses how sensitive information is managed, controlled, and safeguarded at every stage of the data lifecycle. Proper data retention practices ensure that data is not only securely stored but also that it is not retained longer than necessary, thereby reducing risks.
|
||
|
||
By retaining data only for the duration that it is needed and then securely disposing of it, the exposure to malicious activity or unauthorized access is significantly reduced. Even if attackers gain access, their exposure is minimized. The less data stored, the smaller the "footprint" for potential exploitation:
|
||
|
||
- [Data Retention Policies](/administration-guide/comply/data-retention-policy): Enforces strict retention controls to reduce data exposure and help comply with governance standards.
|
||
- [Compliance Export](/administration-guide/comply/compliance-export): Ensures data portability for audit and compliance purposes in a secure and controlled manner.
|
||
- [Compliance Monitoring](/administration-guide/comply/compliance-monitoring): Offers visibility into adherence to security and compliance policies, supporting compliance mandates.
|
||
- [E-Discovery](/administration-guide/comply/electronic-discovery): Boosts organizational oversight by ensuring discoverability of stored data for legal and compliance audits under secure protocols. E-Discovery capabilities help organizations meet compliance expectations for legal audits under frameworks like GDPR or HIPAA without sacrificing secure collaboration workflows.
|
||
- [Archiving Inactive Teams or Channels](/administration-guide/manage/team-channel-members#archive-a-team) & [Unarchive Channels](/end-user-guide/collaborate/archive-unarchive-channels): Reduces the potential attack surface by securely deactivating and storing inactive resources, minimizing both live data exposure and the likelihood of exploitation. This approach ensures adherence to security best practices while maintaining the ability to securely restore resources if needed.
|
||
|
||
## Incident response
|
||
|
||
Incident response ensures that organizations can effectively detect, investigate, and respond to security threats within a framework that assumes no entity, whether inside or outside the network, should be trusted by default. Incident response is the operational arm that ensures that organizations are vigilant, prepared, and capable of protecting themselves in a dynamic and evolving threat landscape.
|
||
|
||
Mattermost Playbooks reduce the time to respond to threats and ensure compliancy-aligned documentation through automated incident notifications by empowering organizations to predefine and automate incident response workflows, ensuring that responses are consistent, documented, and transparent:
|
||
|
||
- [Incident-Specific Channels for Secure Collaboration](/end-user-guide/workflow-automation/work-with-playbooks#actions): Maintains secure collaboration workflows across broader incident response workflows involving external tools, enforcing a centralized control model for operational continuity during incidents. Incident-specific channels reduce the time to assemble expert response teams, ensuring faster mitigation of active threats like phishing or ransomware attacks.
|
||
- [Automated Incident Notifications](/end-user-guide/workflow-automation/notifications-and-updates): Streamlines response workflows with authenticated alerts.
|
||
|
||
Enhance learning from incidents, ensure historical accountability, reduce future attack surfaces, and meet compliance expectations by securely centralizing documentation to improve future response processes:
|
||
|
||
- [Post-Incident Documentation](/end-user-guide/workflow-automation/metrics-and-goals): Enables secure storage and access for learnings, ensuring compliance with attack surface minimization principles.
|
||
|
||
By embedding Zero Trust principles across access, monitoring, data management, and incident response, Mattermost equips organizations with the tools needed to safeguard collaboration workflows in today's evolving threat landscape.
|
||
|
||
Discover how Mattermost can transform your Zero Trust strategy today. Book a live demo with a [Mattermost Zero Trust Expert](https://mattermost.com/contact-sales/) to explore tailored solutions for your organization’s secure collaboration needs.
|