Security
Advanced protection and incident response migrating from PulseGuard.
Start here
Configure security without unexpected punishments
PulseOne → Dashboard → select your server → Modules → Security
Choose the server → Modules → Security. At the top, check whether the button says Pause runtime or Enable runtime.
Review Protection level. A preset only fills the form; it does not change active behavior until you press Save configuration.
Inspect the Contain members automatically... anti-raid toggle, coordinated-message protection and any configured quarantine actions. Disable the exact action you do not want.
Scroll to the bottom and press Save configuration. Check for success feedback, then refresh to confirm the saved settings.
To stop the Security runtime, press Pause runtime. Note the page documents that owner-accessible /security lockdown and audit tools can remain available even while paused.
For Member verification, configure the role below PulseOne's Discord role and post an enabled gate using /security verify-post only after testing.
Practical example
Coordinated anti-raid protection can time out accounts that post the same message within seconds. Turning off AutoMod does not necessarily disable that separate Security feature.
Before you begin
- No module dependency listed.
- Discord bot permissions for the operational slice: ViewAuditLog, ManageRoles, ViewChannel.
- Review staff roles and channel access in your server before using the feature.
Overview of the setup
Before you begin
Review detection modules and decide whether to start with a monitored/no-action mode.
Configure
Configure anti-raid, anti-nuke, phishing and verification policies, keeping staff bypasses explicit.
Test and verify
Simulate a policy breach in a controlled server, inspect evidence and practice the recovery/unlock workflow.
Features explained
What each feature does and what to check before publishing or installing the result.
Anti-raid, anti-nuke, and phishing detection
Anti-raid, anti-nuke and phishing rules catch distinct classes of abuse; tune each independently.
Member verification and quarantine review
Verification and quarantine protect new joins but need staff-reviewed recovery paths.
Durable incident evidence and investigation timeline
Incident history should retain only necessary evidence and affected actions.
Channel lockdown and verified recovery workflows
Lockdown should be reversible and not strand staff without access.
PulseGuard configuration and state imports
Legacy PulseGuard imports require an explicit review of migrated settings before enforcement.
If it still does not work
- If a member is punished unexpectedly, check Discord Server Settings → Audit Log first, then review the individual Security feature and the module’s runtime badge.
- Saving a preset or changing an input without Save configuration does not apply it.
- Pausing the runtime does not automatically reverse an earlier timeout, ban, quarantine or lockdown. Review active Discord state separately.
Troubleshooting and safety checks
- Legitimate member blocked? Use staff review and recovery rather than disabling every security policy.
- If a capability is unavailable in the UI, check the module's current rollout/availability instead of assuming every roadmap item is live.