FIG. 14 User guide

Everything you need to run IronCastle.

From agent install to incident response to compliance evidence. Updated every release. If something is missing, email [email protected] and we'll add it.

§ 01 Topics

Pick a section.

Twelve guides. Each one a focused 5-15 minute read. Anchored to the in-product UI, so screenshots stay accurate.

01 · Onboarding

First 24 hours

From signed contract to first event ingested. Tenant setup, named-analyst introduction, what to expect in the first week.

02 · macOS agent

Install the macOS agent

Signed .pkg install with full-disk access and LaunchDaemon registration. Verifies in < 60 seconds.

03 · Windows agent

Install the Windows agent

Authenticode-signed MSI. Group Policy / Intune-ready. Runs as SYSTEM with anti-tamper protection.

04 · Portal tour

Customer portal walkthrough

Home, incidents, assets, reports, settings. Owner view vs. analyst view. The five things you should check weekly.

05 · Incident flow

During an incident

What happens when AI Guardian fires. How the auto-cascade works. How to read the audit log. How to pause auto-response.

06 · Integrations

Connect your stack

Connect your identity, cloud, and SaaS sources via OAuth — no API keys to manage. New sources added on request.

07 · MSSP / partner

Run your own SOC

For MSPs and resellers. Partner portal setup, tenant onboarding, white-label branding, analyst seats.

08 · Compliance

Evidence on demand

Pull SOC 2, ISO 27001, HIPAA, CIS evidence directly from the portal. Auditor share-link with read-only scope.

09 · API

REST API + webhooks

Pull incidents, push custom events, hook your SIEM. Tokens scoped per tenant. Rate-limit-friendly.

10 · Detection tuning

Tune your tenant

Suppress known-good actors, add custom Sigma rules, manage the hash blocklist, allowlist exec paths.

11 · Quarantine vault

Quarantined files

View quarantined binaries, inspect VirusTotal / MalwareBazaar verdicts, release if false positive, delete forever.

12 · Admin ops

Org administration

User management, SAML / SCIM, RBAC, audit log, billing, data residency, data export, account deletion.

01 · First 24 hours.

What happens after you sign

Within 4 business hours, your named analyst introduces themselves over email and books a 30-minute kickoff. We provision your tenant on the region you selected (UAE / AU / EU) and send you the portal invite.

Single-tenant data isolation is enforced at the database row level — no shared infrastructure between you and any other customer.

Day 1 checklist

1. Sign in to portal.ironcastle.io with the invite link.
2. Enable MFA on your owner account.
3. Add 2-3 admins from your IT team.
4. Connect M365 or Google Workspace (5-minute OAuth).
5. Deploy the agent to one pilot endpoint to verify telemetry.

Day 6 milestone

By the end of day 6, you should have: all endpoints covered, identity + cloud connected, the first weekly digest in your inbox, and the security score at 70+. If you're below 70, your analyst will reach out with a specific list of items to close.

02 · macOS agent.

What it is

A Rust binary signed with Permus's Apple Developer ID and notarised by Apple. Runs as a LaunchDaemon under root with Full Disk Access. Approximately 9 MB on disk, < 90 MB RAM idle, < 0.5% CPU under normal load.

Install

Download the signed .pkg from the portal (Settings → Agents → Download). Double-click. Approve the system extension prompt. The agent registers within 30 seconds.

# Headless install (MDM)
sudo installer -pkg IronCastle-Agent-0.1.17.pkg -target /
# Verify
sudo launchctl list | grep io.ironcastle.agent

Tamper protection

The agent runs with KeepAlive=true on the LaunchDaemon, plus an internal watchdog heartbeat. Attempts to pkill, launchctl unload, or remove the plist will respawn the agent within 1-2 seconds and emit a critical incident with the attacker's PID and command line.

05 · Incident response.

The five layers

Every event runs through five detection layers in series: Sigma rules → threat intel → hash blocklist → YARA scan → AI Guardian. A critical match triggers the auto-cascade: kill the process, quarantine the file, tenant-wide blocklist the SHA256, isolate the host. All four actions execute within seconds.

The "What we did for you" panel

Every incident in the customer portal has a transparency panel that logs every analyst and AI action with timestamp and actor. The 🤖 AI Guardian icon attribution means an autonomous action was taken; a named analyst means a human action.

Pausing auto-response

Settings → Response → Auto-cascade has a single switch. Disabling it queues critical actions for analyst approval instead of auto-executing. Used during change windows, pen-tests, or when you want a tighter human-in-the-loop.

Still stuck? Real humans answer.

Email your named analyst, or write to support — 4-hour response during business hours, 30 minutes on Keep, 5 minutes on Citadel.

Contact support →