# Safety

## Responsibility

See [#responsibility](https://malix.gitbook.io/administration/discord/management#responsibility "mention")

## Philosophy

The safeness of a community is what gives it its quality

It doesn't mean that its safety setup should be constraining, but rather that it should be hermetic

For these purposes, the best ones are based on [the zero trust security model](https://en.wikipedia.org/wiki/Zero_trust_security_model)

## Issues

<table data-view="cards" data-full-width="false"><thead><tr><th align="center"></th><th></th></tr></thead><tbody><tr><td align="center"><h3>Spam</h3></td><td>The most common safety issue<br>It might sometimes even be unintentional<br><br>Common spam actions are about sending numerous useless or unrelated content<br><br>Its proportion is often correlated with the quality and engagement of its respective community</td></tr><tr><td align="center"><h3>Nukes</h3></td><td><p>Events that consist of rogue actions that are done by members with privileged permissions</p><p></p><p>These members are either trusted staff, or non-staff that has been assigned privileged permissions<br></p><p>Common rogue actions are mass ban, role and channel deletions, and vanity invite link theft</p></td></tr><tr><td align="center"><h3>Raids</h3></td><td><p>Events that consist of coordinated server incursion for the purpose of harassing their members</p><p></p><p>Common harassments are mass pinging, and channel &#x26; DM spamming<br><br>The most sophisticated ones prepare by discreetly filling over time the target server with many raiders</p></td></tr><tr><td align="center"><h3>Self-bots</h3></td><td><p>A type of bot that runs on a user account instead of a bot account</p><p></p><p>They are most of the time used for rogue purposes.<br><br>Common rogue purposes are advertising <a href="#issues">spams</a>, mass DM scams and <a href="#raids">Raids</a></p></td></tr></tbody></table>

{% hint style="danger" %}
**Those are** [**forbidden by Discord's Trust and Safety terms**](https://support.discord.com/hc/en-us/articles/115002192352-Automated-user-accounts-self-bots-)\
**The guilty risk getting perma-banned and the targeted servers deleted if too much damage has been done&#x20;*****(see*** [#responsibility](#responsibility "mention")***)***
{% endhint %}

## Solutions

<table data-view="cards"><thead><tr><th align="center"></th><th></th></tr></thead><tbody><tr><td align="center"><h3>Restrictive Permissions</h3></td><td><p><a href="#issues">Admin safety issues</a> can come from the staff or those who has been assigned privileged permissions by them</p><p></p><p>Most of <a href="#issues">these issues</a> can be prevented by applying restrictive (but not constraining) permissions<br>For that, read <a data-mention href="../native/permissions">permissions</a> and follow <a href="https://en.wikipedia.org/wiki/Zero_trust_security_model">the zero trust security model</a></p></td></tr><tr><td align="center"><h3>Moderation</h3></td><td><p>Mandatory (see <a data-mention href="#responsibility">#responsibility</a>)</p><p></p><p>Most of it is done manually<br>However, automatizing it is easy and time-saving<br><br>The native AutoMod has easy to setup auto-moderation features that also contributes to anti-<a href="#issues">spam</a><br>For an in-depth setup, use dedicated bots (such as <a href="../bots/wick">Wick</a>)</p></td></tr><tr><td align="center"><h3>Setup Security Culture</h3></td><td><p>Staff account authentication security is primordial for a server to ensure its security integrity</p><p></p><p>To enforce that, it is recommended to setup a security culture in the server</p><p></p><p>Send this page to your staff and enable the "Require 2FA for moderator actions" setting</p></td></tr><tr><td align="center"><h3>Verification</h3></td><td><p>A verification system is a security feature intended to restrict the normal access to a server using a <a href="../../native/permissions#verification">verified</a> or <a href="../../native/permissions#verification">unverified</a> role, most of the time to block <a href="#issues">self-bots</a>, or <a href="#issues">raids</a><br></p><p>To manage it, it can either be manual or automated with <a href="../bots/bots">bots</a> (we recommend <a href="../bots/wick">Wick</a>)</p></td></tr><tr><td align="center"><h3>Backup</h3></td><td><p>When a role, channel, or message is deleted, the only way to get them back is to restore a backup<br></p><p>Some services might only save server settings, such as the native "server template" feature, but other can also restore its deep content (such as <a href="https://xenon.bot/premium">the premium version</a> of <a href="https://xenon.bot/">xenon</a>)</p></td></tr></tbody></table>
