Guide/Protect your server/Security setup checklist

Discord Server Security Checklist (Step by Step)

The ordered list to lock a server down properly, with the command for each step and why it matters.

Quick answer

The whole list as commands

!security alerts #security-alerts @Staff high
!security quarantine @Quarantined
!security lockdown staff_role:@Staff member_role:@Member
!antinuke enable
!security set antinuke.strictPrivileged on
!antinuke permrole role:@Mods actions:ban,kick,timeout,purge limit:5 window:10
!whitelist add bot 123456789012345678 antinuke
!security automod sync
!backup schedule on hours:24 keep:7
!security audit

Ask the guide

Step by step

In short

Ten steps, in order. Flash does the first six for you; the rest take five minutes.

1Put the bot's role at the top. Server Settings → Roles → drag {bot} above every human role. Anti-nuke cannot ban anyone whose top role sits at or above the bot's. Nothing else on this list works without this.
2Give it View Audit Log. Administrator covers it. Without it the bot cannot see who did something.
3Alerts channel and staff role. !security alerts #security-alerts @Staff high. Every critical event pages this role.
4Quarantine role. !security quarantine @Quarantined (a role with no permissions). Used by anti-raid, heat, join gate and moderator limits.
5Lockdown roles. !security lockdown staff_role:@Staff member_role:@Member, so a lockdown also silences the member role and never locks staff out.
6Anti-nuke on, strict. !antinuke enable then !security set antinuke.strictPrivileged on.
7Permission grants for every moderator role. !antinuke permrole role:@Mods actions:ban,kick,timeout,purge limit:5 window:10. Repeat per role with the actions that role actually needs. A role without a grant is banned on its first destructive action — that is the point, but it means every moderator role needs one before you turn strict mode on.
8Whitelist bots, not people. !whitelist add bot <id> antinuke for trusted bots (Dyno, MEE6…). Keep humans on permission grants, which have limits; the plain whitelist has none.
9Edge blocking and backups. !security automod sync and !backup schedule on hours:24 keep:7; !backup create "baseline" messages:true once.
10Audit and drill. !security audit grades what is still open; !raid drill shows what your raid settings would do. Re-run both after any change.

Test strict mode with an alt account that has a moderator role but no grant: delete a test channel with it. You should see "⚡ Non-whitelisted action stopped" within a second, the alt banned, and the channel back. Then give that role a grant, unban, and try again — nothing should happen.

Copy and try

The whole list as commands

!security alerts #security-alerts @Staff high
!security quarantine @Quarantined
!security lockdown staff_role:@Staff member_role:@Member
!antinuke enable
!security set antinuke.strictPrivileged on
!antinuke permrole role:@Mods actions:ban,kick,timeout,purge limit:5 window:10
!whitelist add bot 123456789012345678 antinuke
!security automod sync
!backup schedule on hours:24 keep:7
!security audit

Good to know

Turn strict mode on only after every moderator role has a grant.
Test with an alt that has a moderator role and no grant: it should be banned on its first destructive action, and unbanned after you add the grant.

Still stuck? Ask in the support server.