Detect → audit → harden → report
You don't hand-edit sysctl, sshd or PAM files one server at a time. Run RCW-NixFort from Windows against any Linux host: it fingerprints the OS (Ubuntu, RHEL, Debian, Rocky, Alma, Amazon Linux…), selects the matching CIS benchmark profile (Level 1 / Level 2), and evaluates filesystems, kernel, services, network, logging, auditd, PAM, sudo and SSH controls.
Then harden. Every change is shown first, backed up on the server, and reversible by run id:
Reports you can hand to an auditor
Every run exports a self-contained HTML dashboard (filter by status, search evidence) plus JSON, CSV and Markdown — with the detected distro, applied benchmark, per-control evidence, what was fixed, and the rollback run id.
How it works
- Install nothing — copy the exe to any Windows 10/11 machine and open cmd/PowerShell. The target server just needs SSH and a sudo-capable user (or root).
- Audit first:
RCW-NixFort.exe scan --host 10.0.0.51 --user admin --askpass— detects the distro, runs the CIS control set and exports the report. - Preview or apply: add
--dry-runto see every planned fix, or runapplyand typeHARDENat the confirmation. Scope with--profile 2,--families network,access,--controls 5.6.6,--exclude. - Undo anything:
RCW-NixFort.exe rollback --host 10.0.0.51 --user admin --latestrestores files, permissions, sysctls, services and packages from the server-side journal.
What it hardens
- ✓Filesystem mount options (nodev / nosuid / noexec)
- ✓Kernel module blacklists (cramfs, usb-storage, DCCP, SCTP…)
- ✓Core dumps, ASLR, AppArmor / SELinux
- ✓Unwanted services removed or flagged (X11, NFS, Samba, FTP…)
- ✓Firewall enabled — SSH allowed first (ufw / firewalld)
- ✓Full CIS sysctl network parameter set
- ✓auditd + CIS audit watch rules (identity, sudoers, deletions)
- ✓rsyslog & persistent, compressed journald
- ✓Password policy: pwquality, aging 365/7/7, faillock
- ✓sudo use_pty + logfile, cron/at restrictions, TMOUT, umask 027
- ✓19 sshd directives (PermitRootLogin, MaxAuthTries, ciphers…)
- ✓/etc/passwd, shadow & group integrity + permissions
Safety model
- ✓Two-phase apply — audit first, fix list shown, explicit HARDEN confirmation
- ✓Every file change backed up server-side before modification
- ✓sshd changes validated with sshd -t, auto-restored if invalid, re-verified after reload
- ✓Risky items (bootloader password, repartitioning, IPv6 disable) stay MANUAL with guidance