Security

The defences that work before anyone has posted: turn away throwaway accounts, ride out a raid, make newcomers solve a captcha, stop an admin who starts deleting everything, and keep a copy of your roles and channels.

Dashboard

Safety › Security

Naeris needs

Kick Members · Ban Members · Manage Roles · Manage Channels · Manage Server · View Audit Log

Alerts

Blocked arrivals, raids and anti-nuke actions are reported in the Alerts channel. Empty, they go to the mod-log. Pick a channel your staff actually reads: these are the messages you want to see quickly.

Arrival filter

Turn on Filter arrivals to refuse accounts that look like bots or throwaways the moment they join. Each check is optional:

• Minimum account age (days): accounts younger than this are refused. 7 days stops most spam accounts; 0 accepts any age.
• Require a profile picture.
• Refuse names with an invite link: a classic for advertising bots.
• Refuse names with a blocked word: uses the automod's blocked words.

What happens to a refused account: kick, ban, or a 24-hour timeout. They get a private message saying why, so a real person knows what to fix. Add trusted people to Always let in (user IDs), for a friend with a brand-new account.

Raids

Turn on Watch for raids and set what counts as one: so many Arrivals within (seconds), like 10 in 30. When that happens, Naeris posts an alert and, until 10 minutes after the last spike:

• Just alert: nothing more, your staff decides.
• Kick newcomers: everyone who joins during the raid is kicked.
• Raise verification: the server's verification level goes to the highest (verified phone number), then back to what it was once the raid is over.

Captcha

Newcomers type the code shown in an image before getting access. It stops bots that join to spam, which can't read the image.

1. Create a role, say Verified, and give it access to your channels. Take that access away from @everyone.
2. Make a verification channel that @everyone can see.
3. Turn on Ask for a captcha, pick the Verification channel and the Role given once verified, save, then click Post the verification message.

Members click the button, get a private image, and type the code in a small form. Another image draws a new one if it is hard to read. A code is valid for 5 minutes.

• Kick unverified members after (minutes): members who never verify are kicked after that long. 0 never kicks.
• Kick after 3 wrong codes.

Naeris needs Manage Roles, with its role above the verified role.

WARNING

If you also give a role on join, make sure that role doesn't open your channels, or newcomers walk past the captcha. The verified role should be the one that gives access.

Anti-nuke

The worst raid is the one from inside: a moderator's account gets hacked, or an admin leaves on bad terms and starts deleting channels. Anti-nuke watches destructive actions in the audit log: channels and roles deleted or created, bans, kicks, prunes and webhooks created.

When someone does more than so many Actions within (seconds) (3 in 10 by default), Naeris stops them with the Sanction you chose: Remove their roles, kick or ban. With Put things back on, it then recreates the channels and roles they deleted, lifts the bans they gave and removes what they created.

The server owner and Naeris are always trusted. Add the others under Trusted people (user IDs), for a bot that legitimately creates channels, for example.

Only the server owner can change these settings, from the dashboard. Naeris needs View Audit Log, and its role must be above the roles of the people it may have to stop.

Backups

A backup is a copy of your roles and channels with their permissions. Messages, members and threads are not in it.

• Daily backup makes one every day. The 5 most recent are kept.
• Back up now makes one on the spot, before a big reorganisation for instance.
• Restore missing recreates the roles and channels from the backup that no longer exist, with their permissions, and changes nothing else. A deleted category comes back with its channels under it. Restoring a backup, or deleting one, needs the Administrator permission.

Commands

Security is set up from the dashboard only. In Discord, /channel lockdown locks every channel where members can write during a raid, and /massban bans a list of IDs: see Moderation.