CLI Commands
Packages and the standalone installer expose /usr/sbin/csm, which points to /opt/csm/csm. Commands that talk to the control socket require the daemon to be running; direct-store maintenance commands say explicitly when it must be stopped.
Global flags
csm rehash and csm capabilities reject missing option values before recording
hashes or printing output. csm capabilities accepts but does not read config paths.
| Flag | Description |
|---|---|
--config <path> | Override the main config path. Default: /etc/csm/csm.yaml, with fallback to /opt/csm/csm.yaml on legacy installs. |
--config-dir <path> | Override the conf.d directory. Default: /etc/csm/conf.d. Wins over CSM_CONFIG_DIR when both are set. Override paths must be absolute, trusted, and not group- or world-writable; loaded fragments must meet the same write-safety check. |
Daemon
| Command | Description |
|---|---|
csm daemon | Run as persistent daemon (fanotify + inotify + PAM + periodic checks). Signals systemd READY=1 after watchers attach and pings WATCHDOG=1 on the configured interval. The systemd notification variables are read once at startup and removed from the environment, so no command the daemon runs inherits them. |
Notification writes time out if systemd stops reading its socket, so they cannot block the daemon indefinitely. ModSecurity rule actions are checked every five minutes using file contents, including linked rule files. Unchanged rule trees skip parsing; empty or incomplete builds keep retrying, and platform detection resumes when the selected directories no longer yield rules. A temporarily empty tree keeps the last loaded actions until a replacement is available.
Checks
| Command | Description |
|---|---|
csm run | Run all checks now via the daemon, send alerts |
csm run-critical | Critical checks now via the daemon (the daemon also schedules critical checks internally every 10 min) |
csm run-deep | Deep checks now via the daemon (the daemon also schedules deep checks internally every 60 min) |
csm check | Run all checks via the daemon, print findings to stdout, no alerts / auto-response |
csm check-critical | Test critical checks only (dry-run via daemon) |
csm check-deep | Test deep checks only (dry-run via daemon) |
csm scan <user> [--alert] | Scan a single cPanel account (capped quick scan). --alert sends alerts for the findings. An account whose home is on an additional home partition is found through the cPanel account list and its passwd home. |
csm scan <user> --full [--wait] [--json] [--respect-ignores] [--quarantine] | Uncapped deep scan of one account, routed through the daemon (bypasses the per-account file cap). It also runs the YARA rules over the account’s document roots, one file at a time through the YARA worker; files over full_scan_max_file_mb are reported as not scanned, and image files are scanned after everything else so a scan that runs out of time has read the code first. It is report-only by default; --quarantine acts on critical file findings the way the scheduled auto-response does (WordPress core, plugin and theme files are cleaned in place unless cleaning would leave them empty or their release does not ship them; directories, symlinks and lower-severity findings are left for review); --wait polls to completion and prints the report, and exits with status 3 when the scan stopped early, was canceled or failed; --respect-ignores honors ignore_paths. |
csm scan --all --full [--wait] [--json] [--respect-ignores] | Server-wide uncapped full scan across every account. Quarantine per account after review (--quarantine is rejected with --all). |
csm scan --status [id] [--json] | List full-scan jobs, or show one job by id. |
csm scan --report <id> [--json] | Print the stored report for a completed full-scan job. Exits with status 3 when that scan did not cover everything. |
csm scan --cancel <id> [--json] | Cancel a running full-scan job. |
Exit status 3 means the scan did not cover everything: a check timed out or failed, a file was skipped as oversize or unreadable, the account was not found, or not every finding was stored.
Passwd home fallback accepts an account-named directory directly under a sibling
home volume, such as /home2, and rejects symlinked volumes and homes. Arbitrary
passwd locations outside this boundary are not used for account scans.
The full-account YARA pass does not follow tenant symlinks. It reports unreadable
or changed files and directories as coverage gaps, and keeps confirmed matches
if a later read or worker call times out. Large worker requests use a private
temporary snapshot in the daemon state directory, bounded by
full_scan_max_file_mb, which is removed after the request. Failure to create
or scan that snapshot is reported as incomplete coverage. The default account
scan still has no YARA pass.
Management
| Command | Description |
|---|---|
csm install | Deploy config, systemd, auditd rules, logrotate, WHM plugin |
csm uninstall [--purge] | Remove the executable and CSM-owned service, audit, logrotate, webserver, and ModSecurity integrations. Config, drop-ins, state, logs, signature rules, and quarantine data are preserved by default. --purge removes all CSM-owned data. Operator ModSecurity rules are never removed. |
csm baseline | Full server scan via the daemon, records current state for change tracking. Dangerous privileged accounts or WHM root tokens can still be reported on first scan. Takes 5-10 min on large servers. Required on first install. Add --confirm when existing history would be cleared. The daemon must be running. |
csm rehash | Re-record the binary, csm.yaml and conf.d hashes without scanning. Use once after editing restart-required config, changing a drop-in by hand, or replacing the binary; a stale hash makes the next restart refuse to start. It also applies integrity.immutable to the installed binary. csm rehash --fragment <file> re-records hashes only when the named conf.d files are the only change; see conf.d drop-ins for its exit codes. Unknown arguments are refused rather than ignored. |
csm status | Show current state, last run, active findings, and automation rollout state. Add --json for the full health snapshot (watchers, severity counts, store health, blocklist size, capabilities, version, hashes, automation). |
csm verify-release <key.pem> <file.sig> <file> | Verify a release artifact’s Ed25519 signature without OpenSSL; the supported verification path on EL8 and CloudLinux 8. |
csm systemd-roots | Print a validated systemd drop-in granting write access to configured account trees; see custom account roots. |
csm privileges [--json] [--markdown] | Print every operation that needs privilege beyond reading CSM’s own files, with what it writes and the config key that stops it. Reads nothing from the host, so it answers “what would this do to my server” before installing. See capability matrix. |
csm action show <id> | Print, as JSON, what the admission ledger recorded for one automatic response: the candidate with its state, reason and outcome, each attempt, and for a response refused because a block already enforced it, that block. <id> is a candidate ID or the action_id of an admission record. Asks the running daemon. See action log. |
csm actions [--since <when>] [--op <id>] [--limit N] [--json] | Print what CSM did to this host: quarantines, cleans, process kills and firewall changes, with the digest before and after a file change. Reads the log directly, so it answers after a crash. See action log. |
csm selftest [--json] | Scan a bundle of samples with known verdicts and report what the installed rules catch, including the gaps the bundle records. Reads no account data. See self-test. |
csm doctor | Config + integrity + daemon + watchers (including the YARA-X scanning worker, which fails while it is down or keeps crashing) + store sanity check, including service write access for custom account roots. Config checks include the firewall lockout warnings for inbound and outbound policy; the integrity check reports a binary, csm.yaml or conf.d hash mismatch before the next restart refuses to start, with the remedy. On CloudLinux with PHP Shield enabled it also reports whether the Shield event mount has been applied to the cages, names up to five missing cages, and gives per-account remount commands. Unresolved accounts appear as uid:N; resolve their account names before remounting. For more than five missing cages, it also offers a remount of all cages during a maintenance window. On Postfix hosts with Dovecot, the smtp auth logging line warns when Dovecot does not log rejected logins, which SMTP brute-force detection needs, logs their passwords, or its settings cannot be read. The correlation attribution line names the checks whose findings sit in the active set without a hosting owner (WARN) or confirms every eligible finding carries one (OK), with the cumulative count since start either way. The web client addresses line says whether the web server configuration sets no client address rewriting, replaces the logged client address (OK, naming the setting and its file; web findings then get no automatic response from admission), or cannot be read completely (WARN). It applies the loaded web_server: settings before reading the files. The configuration root selects Apache or nginx, including cPanel LiteSpeed’s Apache tree; LiteSpeed XML stays at its standard location. On Stalwart hosts the stalwart API key line says whether Stalwart accepts CSM’s API key from stalwart.api_key_file, and the stalwart setup lines check Stalwart’s settings, read-only, through that key. Without a working key doctor uses an admin login from STALWART_USER and STALWART_PASSWORD when both are set, and otherwise does not check the settings. The key is sent only to an API address on this host whose port belongs to root or Stalwart’s service user; for a remote address doctor uses the admin login only. csm doctor challenge checks challenge public URL, TLS, port gate, webserver snippets, configtest, and the live /challenge/gate endpoint. Add --json for machine-readable output. |
csm validate | Validate config (--deep for connectivity probes) |
csm config show [--no-redact] [--json] | Display the redacted config even when callback secrets are set only in the service environment. With --no-redact, a missing required callback secret stops the command before it prints the config. Use --json for JSON output. |
csm config schema | Print a JSON Schema reflected from the Config struct. Use for CI validation of conf.d drop-ins or panel-side editor schemas. |
csm config apply-immutability | Reapply integrity.immutable to /opt/csm/csm. Unsupported filesystems or missing tooling produce a warning and a successful exit; permission and other unexpected errors fail. Package transaction hooks use this after upgrades. |
csm verify | Verify binary and config integrity |
csm version | Version and build info |
csm capabilities | Print this build’s feature tokens, one per line; --json prints a JSON array. Needs no running daemon and no config, so an orchestrator can check a token before it writes a key that depends on it. Tokens for live BPF monitors appear only in the daemon’s GET /api/v1/capabilities. |
csm incidents ... | List, show, and update correlated security incidents (list, show <id>, status <id> <state>, bulk-status). See Incidents. |
csm forensic-snapshot <account> --out <archive.tar.gz> | Evidence archive for incident handoff (triggers, admins, sessions, file mtimes). |
csm webserver-integration <install|upgrade|status|validate|remove> | Install, upgrade, or remove the challenge reverse-proxy snippets for the detected web server. |
csm pam <install|uninstall|status> | Install or remove the pam_csm.so PAM hook (csm pam --help). |
csm report enroll | Generate an abuse-reporting node key pair. |
csm doctor also lists protection queue health:
waiting and running work, losses and lag. A sustained backlog or drop rate
fails the named queue check and includes recovery guidance. Queues whose work
is best effort warn instead of failing, so they never change the exit status.
While the firewall is disabled, queued automatic blocks pass the check, which
says the blocks are not applied and whether dry run is on.
The same evidence appears in csm status --json and the HTTP status response.
Each started live monitor also gets a backend: <feature> check naming the
backend it runs on, such as backend: placement. A monitor on none passes
when its detection.<feature>_backend is none and warns otherwise, with a
pointer to the startup log.
Backup & restore
| Command | Description |
|---|---|
csm backup <path> | Bundle csm.yaml, /etc/csm/conf.d/, the state directory and the antispam learning directory into a tar.gz at <path>. Runtime lock files, in-progress export staging, and unconfirmed firewall rollback artifacts are omitted. The daemon must be stopped; the command verifies both the control socket and state lock before reading data. |
csm restore <archive> [--force] | Validate and stage the complete archive before atomically replacing the live csm.yaml, conf.d, state directory and antispam learning directory; the replaced learning directory is kept aside and restored learning waits for confirmation. Restore rolls back failed replacements, removes stale state entries, and refuses a running or starting daemon. Stop the daemon first. |
csm store export / csm store import (below) is the lower-level alternative: tar+zstd, sha256-verified, finer-grained --only= flags. csm backup/restore is the convenience wrapper most operators want.
Restore and csm store import refuse an archive whose admission ledger is behind this host’s once the ledger has started live: the archive’s ledger never started live, or its clock is behind. Restoring it would spend an hour’s block budget twice and replay the live start from older blocks. --only=baseline is refused too when it carries the firewall state, because it puts that file beside the newer ledger; --only=firewall is not. A host whose ledger never started live, or that has none, is not subject to this comparison. A host ledger this build cannot read, including a truncated database, does not refuse, so a restore can repair it. Pass --force to either command to bypass this comparison.
csm store import rejects archives that place csm.db among state files; the database belongs only in bbolt.snapshot. A baseline import carrying firewall/state.json also verifies the snapshot’s checksum when the manifest provides one. --force does not bypass either format or checksum validation. Baseline imports without firewall state still ignore the unused snapshot.
Backup, export, import and restore check each database snapshot before reading or changing it and refuse a damaged one, including one with leaked pages. They make consistent backups, not salvage copies of damaged databases.
csm store import --only=firewall also checks the live database. When an archive contains antispam learning and omits state, restore checks the staged copy of the live database before replacing any files. Both operations refuse a damaged database or a broken database symlink and accept leaked pages in the live database.
Backup and restore use the state lock to exclude daemon access. Restore stages all data beside its destination before replacement, so validation failures leave the live installation unchanged. Uninstall is intentionally non-destructive unless --purge is supplied.
Restore accepts the format produced by csm backup: one tar archive in one gzip member, with no data or padding after the tar end markers and no trailing compressed bytes or additional members. It validates the gzip checksum and length before replacing any destination, and rejects corrupt or truncated archives.
Both commands stream file contents and limit the total uncompressed tar archive to 16 GiB by default, including headers, manifest, and padding. There is no separate limit on a state file. Use --max-bytes <positive byte count> on both commands to raise or lower the budget; restore also accepts older large backups when they fit the selected budget. An over-limit backup fails without replacing an existing archive. Restore keeps its manifest read limited to 64 KiB.
Backup checks space before copying the state database snapshot. Restore checks before each staged file and each replacement copy, including copies onto a different destination filesystem. These checks leave 64 MiB free beyond the file being copied. Allow space for the old installation, the full extracted archive, and a second copy of the restored files during replacement. Space checks cannot reserve storage against other writers; write failures still abort staging before live replacement. If a limit or space check fails, retain the original archive, provision enough storage, and retry with the same or a higher explicit budget.
Hardening
Operator-driven mitigations applied to the host. Run csm harden with no arguments to print the available subcommands on the current host (the audit detects kernel build, panel, and existing mitigations and only offers what’s relevant). Background, full list, and live-detection details: CVE Mitigations.
| Command | Description |
|---|---|
csm harden | Print the hardening menu for this host. |
csm harden --copy-fail | Apply the CVE-2026-31431 (Copy Fail) modprobe mitigation: blacklist algif_aead + af_alg, unload them. Refuses on built-in-AF_ALG kernels. |
csm harden --copy-fail-seccomp | Apply the CVE-2026-31431 seccomp mitigation: write systemd RestrictAddressFamilies=~AF_ALG drop-ins for LiteSpeed, Apache/Nginx, every PHP-FPM pool, cron, and mail units. The right path on built-in-AF_ALG kernels (typical cPanel/CloudLinux 8). |
The web UI’s Server Hardening page can also apply fixes one section at a time. A failing check that has a safe, mechanical fix shows an Auto-fix checkbox. Apply selected fixes changes only the checked items, then re-runs the audit. The page waits for the worker to finish. Only one hardening worker can run at a time, including across daemon restarts. It uses the daemon’s main configuration and drop-in directory. Applying fixes requires root and systemd-run.
- SSH
MaxAuthTries 4,X11Forwarding noandUseDNS nogo into a CSM block at the top ofsshd_config. The file is checked withsshd -tbefore sshd reloads, and restored if the check fails. The previous file is kept assshd_config.csm-bak. - Kernel settings are set with
sysctl -wand saved to/etc/sysctl.d/99-zz-csm-hardening.conf. A missing drop-in directory stops the fix before kernel settings change. /tmpand/var/tmpbecome1777owned by root./etc/shadowbecomes0600, or0640when the system shadow group owns it.- WHM tweak settings are changed through
whmapi1 set_tweaksetting, with 200 for max emails per hour. Compilers are restricted to root, and cPanel updates are set to daily. - PHP
expose_php,enable_dl, upload progress and fatal error backtraces are turned off inzz-csm-hardening.iniin each build’s scan directory, and in every SAPI’sconf.don Debian and Ubuntu. If a Debian or Ubuntu web SAPI cannot be updated, the CLI setting stays pending for retry. Linked or unreadable SAPI directories require manual changes. PHP-FPM restarts, Apache reloads when mod_php was changed, and LiteSpeed receives a fresh restart request on each apply.
SSH port, password and root login settings, disable_functions, allow_url_fopen, and the mail, web server and firewall checks stay manual.
Remediation
| Command | Description |
|---|---|
csm clean <path> | Clean infected PHP file (backs up original) |
csm db-clean --option <account> <option_name> [--preview] | Sanitize malicious WordPress option values (e.g. injected siteurl / home) |
csm db-clean --revoke-user <account> <user_id> [--demote] [--preview] | Revoke or demote a compromised WordPress admin and invalidate their sessions |
csm db-clean --delete-spam <account> [--preview] | Delete published posts whose title or content matches a high-confidence spam keyword. Matches are confirmed on a Unicode-aware word boundary, so a post is never removed for containing a keyword inside a longer word. Keywords that also occur in ordinary writing are reported by scans but never deleted. |
csm db-clean --drop-object <account> <schema> <type> <name> [--preview] | Drop a MySQL trigger / event / stored procedure / stored function, capturing its CREATE SQL into the db_object_backups bbolt bucket first. <type> must be trigger, event, procedure, or function. <schema> must match a database discovered for <account>. Daemon must be stopped. |
csm virtual-patch [--apply] | Re-scan web roots and preview reversible access-file deny rules. Requires root and manual or auto mode; a timed-out partial scan applies only findings already confirmed reachable and exits nonzero. |
csm enable --php-shield | Enable PHP runtime protection |
csm disable --php-shield | Disable PHP runtime protection |
Installing or enabling PHP Shield creates /opt/csm/shield.conf.php only
when it is missing, so your edits survive. Update its allowed IPs by hand
after changing infra_ips. Disabling keeps the file; uninstalling removes it.
A PHP pool with open_basedir must allow /opt/csm/, not just the shield
script, or the shield ignores /opt/csm/shield.conf.php and uses its
defaults. A .csm-shield-disable file only works where open_basedir
allows the account’s home folder.
State database
| Command | Description |
|---|---|
csm store compact | Reclaim unused space in the bbolt state file (atomic rename over the live DB). Requires the daemon to be stopped (systemctl stop csm) because bbolt holds an exclusive file lock while running. |
csm store compact --preview | Snapshot into a temp file next to the live DB and print src/dst sizes without replacing anything. Use to estimate reclaim before scheduling a maintenance window. |
csm store export <path> | Write a tar+zstd backup containing the bbolt store, the state directory, and the signature-rules cache. Private in-progress staging files and unconfirmed firewall rollback artifacts are omitted. A sibling <path>.sha256 companion file holds the archive hash for verification. Daemon must be running. |
csm store import <path> | Restore from a backup archive. Daemon must be stopped. Default restores everything; --only=baseline restores only state JSON files (file hashes); --only=firewall merges the firewall buckets into the existing bbolt in one transaction, where a durable firewall journal and its snapshot in the archive replace the target’s, and refuses while either side has a durable firewall action unresolved or its audit undelivered; --force-platform-mismatch allows restoring an archive captured on a different OS / panel / web server; --force allows an admission ledger behind this host’s live one (see Backup & restore). |
csm store reset-bot-verify | Drop cached bot PTR verification results and missing-PTR records so the next scan re-runs reverse DNS checks. Requires the daemon to be stopped because bbolt holds an exclusive file lock while running. |
csm export --since <when> | Dump audit-log events for SIEM backfill. <when> is RFC 3339 (2026-04-01T00:00:00Z) or a duration relative to now (24h, 7d). One JSON event per line on stdout, in the same v=1 schema the live audit_log sinks emit. Pipe to a file or directly into a log shipper. Daemon must be running. |
Updates
| Command | Description |
|---|---|
csm update-rules | Download latest signature rules |
csm update-geoip | Update MaxMind GeoLite2 databases |
csm update-bot-ranges | Refresh built-in AI-crawler IP ranges from vendor feeds |
PHP-relay (mail abuse, cPanel only)
Operator controls for the email PHP-relay detector. Talks to the daemon’s control socket; the daemon must be running. See Real-time detection for what the detector fires on, and Auto-response for the freeze action.
| Command | Description |
|---|---|
csm phprelay status | Print the detector’s current state as JSON: enabled, platform, effective dry-run + source (runtime/bbolt/csm.yaml), Path 2b effective account limit, scripts/IPs/accounts tracked, msgID-index size, active ignores. Use to confirm the watcher is wired on a fresh install. |
csm phprelay ignore-script <scriptKey> [--for-hours N] [--persist] [--reason ...] | Suppress every path for a host:/path scriptKey. Default TTL 168h (7d). --persist writes to the bbolt phprelay:ignore bucket so the suppression survives daemon restarts; without it the entry is in-memory only. <scriptKey> is the value the daemon prints in email_php_relay_abuse and email_php_form_relay_script findings (e.g. shop.example.com:/wp-admin/admin-ajax.php). |
csm phprelay unignore <scriptKey> [--persist] | Remove an active ignore. --persist also deletes the bbolt row. |
csm phprelay ignore-list | List all active ignores as JSON: scriptKey, expiresAt, addedBy, reason. |
csm phprelay dry-run on|off|reset [--persist] | Override the auto-freeze dry-run state at runtime. on = freeze findings emitted but no exim -Mf runs; off = live freezes; reset clears the runtime override and falls back to bbolt or csm.yaml. Precedence: runtime > bbolt > yaml. --persist writes the on/off choice to the bbolt phprelay:settings bucket so it survives restarts; on reset --persist the bbolt row is also deleted. |
csm phprelay thaw <msgID> | Manually thaw a frozen Exim message. Wraps exim -Mt with msgID validation (rejects anything that isn’t [A-Za-z0-9-]{16,32}) and writes a thaw entry to the auto-freeze JSONL audit at /var/log/csm/php_relay_audit.jsonl. |
Antispam learning (cPanel only)
Teaches or corrects learning from Spam folders. Runs as root against the running daemon while learning is enabled; observe mode refuses it.
| Command | Description |
|---|---|
csm antispam learn --spam <file>... | Learn each saved message as spam; every cluster it matches gains one operator mark. |
csm antispam learn --forget <file>... | Remove the learned clusters each message matches, including every account’s contribution to them. |
csm antispam learn --status [<request-id>...] | Show what the daemon recorded for request IDs, including clusters still publishing; without an ID, list unfinished requests. |
csm antispam learn --fresh-namespace | With learning disabled, move the learning keys and stored messages aside and empty the learning state; the next enable starts a new namespace. |
Each file gets a request ID, printed before it is sent; csm actions --op integrate.antispam_learn --json shows its recorded outcome and full digests. A lost or truncated reply is retried once with the same ID and snapshot. The exit status is 0 only when every file was learned, already learned, forgotten or matched nothing.
Stalwart
Prepares a Stalwart mail server for CSM through its admin API. See Preparing Stalwart.
| Command | Description |
|---|---|
csm stalwart setup [--dry-run] [--password-file PATH | --password-stdin] [--url URL] [--account-domain NAME] | Make Stalwart log failed logins and the mail its spam filter rejects or discards, end its bans with CSM’s blocks, and take webmail client addresses from the web server behind CSM’s port lock. Create the role CSM response, the service account csm-response and its API key, which works only from this host and is written to stalwart.api_key_file; the account has no password and can receive mail. A role that lacks CSM’s permissions is reset to CSM’s list, dropping permissions added by hand. Setup refuses an existing csm-response account that has a password or another sign-in credential, has sign-ins stopped, or holds keys without CSM’s role. --account-domain names the account’s domain on a server with several. On a server with tenant administrators, use a domain only the server administrator controls, since whoever can edit the account could give it a password. A key Stalwart accepts is kept while it is the account’s only key; to rotate it, delete the key file and run setup. The key steps run only when the API address is on this host. Also prints whether the spam filter is on and its scores. Adds the spam rule CSM_IP, which scores senders on CSM’s address list so more of their mail goes to Junk, or is rejected or discarded at the scores set in Stalwart; it is the one step that changes how mail is handled, and switching the rule off in Stalwart stops it. An unreadable spam filter status warns without stopping setup. Prints each step as name: state: detail. The admin login comes from STALWART_USER and STALWART_PASSWORD, or the first line of --password-file. --password-stdin reads the password from the first line of stdin instead, with the user from STALWART_USER or admin. On a terminal, setup prompts for missing values and hides password input even with --password-stdin. When you enter both values, the username is hidden too. Press Enter at the user prompt for admin. Ctrl-D at an empty prompt cancels setup. Without a terminal, setup reads stdin only with --password-stdin. --url overrides stalwart.api_url. Before sending the login to an address on this host it checks that root or Stalwart’s service user holds that port and owns each connected peer; unreadable ownership records stop the login. Exits 1 when a setting is unsafe, other Stalwart settings cannot be read, the key file cannot be used or checked, or a change failed. Exits 2 on a usage or config error, an API address that is refused, a missing or refused login, a port held by another user, or a host that is not a Stalwart host. |
Firewall
See Firewall for the full reference.
csm firewall status
csm firewall deny <ip> [reason]
csm firewall allow <ip> [reason]
csm firewall tempban <ip> <dur> [reason]
csm firewall deny-subnet <cidr> [reason]
csm firewall grep <pattern>
csm firewall flush
csm firewall apply-confirmed <minutes>
csm firewall confirm
csm firewall restart
csm firewall rollback status|confirm|revert
# ...
csm firewall apply-confirmed and csm firewall restart refuse a pending
CLI confirmation window and say whether waiting for its rollback still helps.
If startup cannot read its saved configuration, rollback restores the kernel
ruleset and state and the window stays pending; once that restore is
recorded, later restarts keep the blocks added since and apply the
configured settings. csm status and csm doctor show the window. Inspect
the current firewall before csm firewall confirm, which accepts the
current ruleset and engine configuration; it does not recover unreadable
settings. Or repair the saved configuration and restart the daemon, which
restores it and rebuilds the ruleset with the current blocks; removing it
does not end a recorded window, even one whose marker was empty or corrupt.
See CLI confirmation window. The
separate Web UI config timer uses csm firewall rollback.