🏛️ SEC Item 1.05 disclosure workflow · SOC 2 Type II · FedRAMP Moderate roadmap · SSO/SAML/SCIM · Private IR Brain corpus
For Enterprise
Book a Walkthrough
⚡ For Fortune 1000 Public Companies, Multi-BU & Critical Infrastructure

One incident command surface across every business unit.

IR-OS gives the Global CISO a unified command view across every subsidiary, region, and operating company — while each business unit keeps day-to-day autonomy. Powered by a private IR Brain trained on your own tabletops, AARs, and incident history. Built for SEC Item 1.05 public-company disclosure, NERC CIP, TSA, CIRCIA, DORA, and every other regulator you can't afford to get wrong.

Infrastructure
SOC 2 Type II
Supabase + Cloudflare
Federal roadmap
FedRAMP Moderate
In progress
Identity
SSO / SAML / SCIM
Okta, Azure AD, Ping
Defensible record
SHA-256 hash chain
FRE 901 ready

Multi-business-unit hierarchy from day one.

Most CIRM platforms were built for a single tenant. IR-OS was built for the Fortune 500 CISO who has six business units, four insurance panels, three legal jurisdictions, and one board that wants a unified view.

Parent
Global CISO · Unified View
BU 1
Manufacturing
EMEA · own IRC
own insurer
BU 2
Financial Svcs
Americas · own IRC
SEC Item 1.05
BU 3
Retail
Global · own IRC
PCI DSS scope
BU 4
Tech / SaaS
Global · own IRC
GDPR + SOC 2

Each BU runs its own IRC teams, incidents, and tabletops under its own jurisdictions. The parent sees a unified view for board reporting, regulatory aggregation, and cross-BU threat correlation. Shared policies cascade down. Private evidence stays local.

The Global CISO's hardest problem

When a threat actor lateral-moves across your business units, you end up with four incident commanders arguing about authority while the SEC Item 1.05 clock runs. IR-OS was designed from the ground up to solve exactly this.

Built for people like
Dr. Evelyn Hartwell
Global CISO · Fortune 500 Manufacturing (public, NYSE) · 42,000 employees · 28 countries · 6 BUs · SEC Item 1.05 registrant

"We're a public company so SEC Item 1.05 four-business-day disclosure applies the moment my disclosure committee determines materiality. My board wants 'one view' of cyber readiness across all six business units and I can't give it to them today. When a threat actor lateral-moves across BUs, I have four incident commanders arguing about who's in charge while the clock runs. That can't happen at our scale."

SEC Item 1.05 disclosure workflow

For public registrants: the 4-business-day clock auto-starts from the moment your disclosure committee determines materiality. Every decision is timestamped in the hash-chained ledger. Legal, CFO, CISO, IR head, and Comms route through a pre-defined disclosure committee workflow with AI-drafted 8-K language and a regulator-ready audit trail.

Parent + BU hierarchy

Parent tenant for the Global CISO with read access across every BU. Each BU runs its own incidents, tabletops, and IRC rosters under its own RLS boundary. Evidence stays where regulators expect it; reporting rolls up automatically.

SSO / SAML / SCIM

Okta, Azure AD, Ping Identity, OneLogin, Google Workspace. Auto-provision and deprovision users via SCIM. Enforce MFA, session policies, and least-privilege role mappings at enterprise scale. Your identity team owns IR-OS access the same way they own everything else.

Private IR Brain corpus

Your own historical incidents, tabletops, and AARs ingested into a private pgvector corpus on top of the public IR Brain (NIST, ISO 27035, SEC, GDPR, CISA, MITRE). Every AI suggestion is grounded in your organization's own hard-won history. No model training — retrieval only, your data stays yours.

Critical infrastructure is its own beast. We speak OT.

If you run generation, transmission, distribution, pipelines, rail, water, or any other covered critical infrastructure, your regulatory surface is larger than any single framework. IR-OS ships with compliance mapping for every one of them.

Built for people like
James Okafor
VP Cyber Risk & Resilience · Fortune 100 Utility · 5 operating companies

"OT/IT convergence means incidents now span SCADA and corporate networks. My regulatory matrix is NERC CIP-008-6, TSA SD02C, five state PUCs, CIRCIA 72-hour, DHS. Any incident triggers six regulators in parallel and I have to prove 'we followed our documented plan' to auditors. Last audit we couldn't because the plan was in a shared drive."

SEC 8-K Item 1.05
4 business days from materiality determination (public companies)
GDPR Article 33
72 hours from awareness of personal data breach
NERC CIP-008-6
Cyber security incident reporting for the bulk electric system
TSA SD02C
Pipeline and rail cyber security directive
CIRCIA
72-hour covered cyber incident reporting to CISA
EU DORA
Major ICT incident reporting for financial entities
EU NIS2
24h early warning + 72h full notification
CMMC / DFARS
Defense industrial base cyber incident reporting
FedRAMP (roadmap)
1h Category 1-2 / 72h Category 3 reporting
Federal Banking
36-hour OCC/FDIC/Fed notification rule

OT-aware runbooks

SCADA, DCS, PLC, historian, HMI — IR-OS ships with OT-specific incident playbooks mapped to NERC CIP-008-6 and TSA SD02C. The IRC Recommender understands the difference between OT and IT roles and routes accordingly.

Regulator-ready audit evidence

Every action is recorded in a SHA-256 hash-chained ledger with attribution, timestamp, and cryptographic integrity. Export a complete audit package — timeline, decisions, notifications, evidence — in the format your auditor expects.

Splunk + ArcSight integration

Inbound webhooks from your SOC stack and outbound event mirroring so your SIEM has a record of every IR-OS decision. Correlate incidents across OT and IT without duplicating data stores.

Regional IRC teams, federated authority

Geographic region-specific IRC rosters with region-appropriate authorities and state-law mappings. Your Midwest operating company runs its incident under Midwest rules while the parent sees the unified view.

Before IR-OS vs. enterprise with superpowers

Fortune 500 CISOs and critical infrastructure VPs don't buy IR-OS for novelty. They buy it because the drudgery at enterprise scale is ten times worse — and so are the consequences.

Before — the drudgery at scale

  • Six BUs running incidents in six different tools with six different timelines
  • Four incident commanders arguing about authority when a threat lateral-moves
  • Board asks "are we ready?" and nobody can aggregate across subsidiaries
  • Audit finds "ineffective IR process"; plan was in a SharePoint nobody opened
  • NERC/TSA/CIRCIA clocks tracked in a grid somebody updates manually
  • Five years of tabletop learnings locked in PDFs no model can read
  • 6-month procurement cycle just to buy the tool that runs the tool

After — enterprise superpowers

  • One command surface, parent view across all 6 BUs, RLS-isolated evidence
  • Pre-authorized authority matrix resolves the "who decides?" question before the incident
  • Unified board readiness dashboard aggregates all BUs in real time
  • Hash-chained ledger proves you followed your documented plan to FRE 901 standard
  • All compliance clocks auto-tracked per BU per regulator in parallel
  • Your 5 years of AARs ingested into a private IR Brain that grounds every AI suggestion
  • Procurement: SOC 2 Type II infrastructure today, FedRAMP Moderate on the roadmap, MSA in hand

Enterprise pricing — built for procurement

Transparent starting price, custom annual contracts. Procurement-friendly: published MSA available, standard DPA, SOC 2 Type II report under NDA, security questionnaire pre-answered. No 6-month sales dance.

Enterprise
Starting at $2,499/month
Custom annual contracts · volume-based multi-BU pricing · GSA and cooperative options
  • Unlimited users
  • Unlimited IRC teams across BUs
  • Unlimited incidents + tabletops
  • Multi-BU parent hierarchy + unified view
  • SSO / SAML / SCIM provisioning
  • Unlimited IR Brain queries
  • Private IR Brain corpus (your AARs, tabletops, incidents)
  • NERC CIP + TSA + CIRCIA + DORA mapping
  • OT-aware runbooks and playbooks
  • Splunk + ArcSight + SIEM integrations
  • API access, webhooks, custom integrations
  • Dedicated Customer Success Manager
  • 24×7 support with named engineers
  • SLA guarantees + uptime credits
  • SOC 2 Type II report under NDA
  • FedRAMP Moderate roadmap on request
Book a Walkthrough

Pre-answered security questionnaire · standard MSA available · 30-day pilot for qualified enterprises.

Enterprise FAQ

How does the private IR Brain corpus work?

During onboarding, you provide IR-OS with your historical tabletops, after-action reviews, incident records, and any other IR documentation you want the AI to learn from. We ingest it into a pgvector-backed private corpus scoped to your tenant only. Every AI suggestion in your environment retrieves from your private corpus first, then the public IR Brain (NIST, ISO 27035, SEC, GDPR, CISA, MITRE) as fallback. No model training — retrieval augmentation only. Your data stays yours, never goes to OpenAI/Anthropic for training, and can be deleted on request.

What's the FedRAMP status?

IR-OS is in the FedRAMP Moderate Ready phase. Our underlying infrastructure (Cloudflare, Supabase) is FedRAMP-authorized. Contact [email protected] for the current detailed roadmap under NDA — we can typically share a target authorization date and our sponsoring agency.

How does multi-BU hierarchy work with RLS?

Each business unit is its own tenant with row-level security enforcement at the database level. Users belong to a BU and can only see their BU's incidents, IRCs, and evidence. Parent tenants (Global CISO) have explicit read-only policies granting cross-BU visibility for aggregated reporting — no BU's private evidence is exposed to another BU. The architecture is designed for M&A scenarios, divestitures, and carve-outs: a BU can be moved between parents or become its own parent with full data portability.

Can we self-host IR-OS on our own infrastructure?

Not today. IR-OS is a multi-tenant SaaS running on Cloudflare Workers + Supabase. For enterprise customers who need in-region data residency or single-tenant isolation, we offer a dedicated single-tenant deployment option on AWS GovCloud or Azure Gov with a longer-term commit. Contact [email protected] to discuss.

What SOC 2, ISO 27001, or other certifications do you have?

IR-OS runs on SOC 2 Type II certified infrastructure (Supabase + Cloudflare). IR-OS's own SOC 2 Type II audit is in progress with completion targeted for Q3 2026. ISO 27001 is on the 2027 roadmap. Enterprise customers can receive a letter of engagement from our auditors under NDA and our pre-answered CAIQ / SIG security questionnaire on request.

How do we procure — we need a signed MSA, DPA, and BAA

We publish a standard MSA, a GDPR-compliant DPA, and a HIPAA BAA. All three are available on request before you start the trial, so your legal team can review in parallel with your technical evaluation. Our enterprise procurement cycle is typically 30–45 days from first call to signed contract.

Your board wants one view. Your regulators want one record.

Unify incident command across every business unit, every jurisdiction, every clock. Let AI run the room while your practitioners run the response.

Book a Walkthrough