fort

Key Features

• •Automated auditing: Runs 15+ security checks including disk encryption, firewall, screen lock, SSH, Gatekeeper, and automatic updates in under 3 seconds, showing current vs expected state for each control.
• •One-command fixing: Automatically remediates vulnerable security settings like enabling the firewall, disabling guest account, and setting screen lock delay with a single `--fix` command. Use `--dry-run` to preview all changes before applying them, ensuring safe and informed hardening.
• •Compliance reporting: Generates a self-contained HTML report with machine identity, serial number, timestamp, and per-check results. Each check maps to SOC 2, ISO 27001, NIST CSF, and CIS controls. Print to PDF in one click for auditor evidence.
• •Zero telemetry: fort makes zero network calls during audits, ensuring complete privacy. It reads local system state using documented macOS APIs and exits immediately. No account, telemetry, or background process ever runs.
• •Claude Code integration: Use fort inside Claude Code to audit your Mac from a conversation. Ask 'is my Mac secure?' and it runs the audit, explains each finding, and fixes only what you approve. Read-only until you give permission.
• •macOS compatibility: Works on macOS 12 Monterey through the latest release, on both Apple Silicon and Intel Macs. Single binary, no prerequisites except Homebrew or direct download.

Use Cases

• •A developer before a business trip runs `fort --fix` to ensure their Mac has disk encryption enabled, firewall active, and remote login disabled. Outcome: a hardened machine that meets company security policy in seconds, even without IT involvement.
• •A security consultant uses fort to audit multiple client Macs without enrolling them in MDM. They run `fort --report` after each audit and collect HTML reports as evidence for compliance assessments. Outcome: fast, repeatable, and independent of client infrastructure.
• •A small team with no IT department uses fort to ensure all members' Macs have consistent security settings. They run `fort` weekly and check reports. Outcome: baseline security maintained with minimal overhead.
• •A privacy-conscious user periodically runs `fort` to verify no sharing services are enabled, guest account is disabled, and automatic login is off. Outcome: peace of mind knowing the Mac is secure against physical and network threats.
• •A company preparing for SOC 2 compliance uses fort to generate evidence of security controls on all employee Macs. The `--report` output maps directly to required controls. Outcome: auditor-ready documentation without purchasing enterprise software.

Who is this for?

Fort is designed for developers and power users who want to lock down their personal Macs quickly without installing agents or signing up for services. It also serves privacy-conscious individuals who need a transparent, zero-telemetry tool to periodically check and harden their security settings. Small teams and consultants benefit from a repeatable, scriptable way to audit multiple Macs without enrolling them in MDM. Additionally, compliance officers and IT administrators can use fort to generate evidence for SOC 2, ISO 27001, NIST, and CIS audits by producing self-contained HTML reports that map directly to controls.