Skip to content
Context GRC

NERC CIP, Critical Infrastructure & Enterprise GRC

Continuous Compliance Engineering

Compliance programs fail between audits—especially in spreadsheets. Context GRC runs inside your network, using 14 drift engines to route deviations to the people who own them. Purpose-built for NERC CIP and critical frameworks, with automation where every AI-proposed change waits for a named, authenticated reviewer before it takes effect.

  • Named approver on every AI-proposed change
  • Approval states you can audit
  • Hash-chained audit trail
  • 40 frameworks
  • 15 NERC CIP standards
  • 14 drift engines
  • 7 modules
  • 5 policy channels
drift-engine console
  • positive_olir_driftRUN RECORDEDDaily @ 2:30 AM Local Context + on framework confirmation + on demand
  • positive_evidence_renewalDRIFT ROUTED (owners notified)Hourly at minute 30
  • positive_morning_briefingRUN RECORDEDDaily @ 7:00 AM Local Context
  • positive_policy_blast_radiusAWAITING HITL APPROVALHourly at minute 30 & Event-driven (Policy.Revised)Reviewer: named user, role-scoped
  • positive_ai_telemetry_flywheelRUN RECORDEDEvent-driven on HITL Action Review
Reads your existing logs and records. Zero active network scanning.

Platform

Why Existing Tools Fail Between Audits

Cloud SaaS requires surrendering your data. Enterprise suites take a year to configure. Spreadsheets break silently between audits. Here is how Context GRC closes the gap.

Runs fully on premises or air-gapped

Context GRCYes
Legacy enterprise GRC suite
Often
Workflow platform with a GRC module
Sometimes
Cloud compliance automation SaaS
Rarely
Federal authorization toolchain
Often
Spreadsheets & shared drives
Yes

Local AI with source citations

Context GRCYes
Legacy enterprise GRC suite
Rarely
Workflow platform with a GRC module
Rarely
Cloud compliance automation SaaS
Rarely
Federal authorization toolchain
Rarely
Spreadsheets & shared drives
No

Cyber-physical asset modeling (ESP, PSP, SCI)

Context GRCYes
Legacy enterprise GRC suite
Rarely
Workflow platform with a GRC module
Rarely
Cloud compliance automation SaaS
Rarely
Federal authorization toolchain
Sometimes
Spreadsheets & shared drives
Manual

NERC CIP content prepackaged

Context GRCYes
Legacy enterprise GRC suite
Sometimes
Workflow platform with a GRC module
Rarely
Cloud compliance automation SaaS
Rarely
Federal authorization toolchain
Rarely
Spreadsheets & shared drives
Manual

Continuous drift detection

Context GRCYes
Legacy enterprise GRC suite
Rarely
Workflow platform with a GRC module
Sometimes
Cloud compliance automation SaaS
Often
Federal authorization toolchain
Sometimes
Spreadsheets & shared drives
No

Offline license verification

Context GRCYes
Legacy enterprise GRC suite
Rarely
Workflow platform with a GRC module
Rarely
Cloud compliance automation SaaS
No
Federal authorization toolchain
Sometimes
Spreadsheets & shared drives
Not applicable

Auditors at no seat cost

Context GRCYes
Legacy enterprise GRC suite
Rarely
Workflow platform with a GRC module
Rarely
Cloud compliance automation SaaS
Rarely
Federal authorization toolchain
Rarely
Spreadsheets & shared drives
Yes

Named human approval recorded for AI-proposed changes

Context GRCYes
Legacy enterprise GRC suite
Varies
Workflow platform with a GRC module
Varies
Cloud compliance automation SaaS
Varies
Federal authorization toolchain
Varies
Spreadsheets & shared drives
Varies

This table reflects general market patterns and each organization's own evaluation will vary.

Platform Functions

Seven integrated modules on one data model

Every module shares one context-scoped data model, so a change in a policy, asset, framework, or piece of evidence surfaces everywhere it matters.

Curated frameworks & standards
40
NERC CIP standards (CIP-002 to CIP-015)
15
Canonical drift engines (6 positive / 8 negative)
14
Integrated platform modules
7
Prepackaged NIST crosswalks (69 mappings)
7
Policy ingestion channels
5

One shared surface across every module

Cmd+K
  • One shared data model

    Seven integrated modules share one data model, so a change in one module is visible in the others.

  • Universal Command Palette

    A universal Command Palette (Cmd+K on macOS, Ctrl+K elsewhere) jumps to any framework, requirement, policy, control, risk, action plan, action item, asset, or evidence artifact.

  • Declarative deep-link routing

    Declarative deep-link routing opens any record directly in a slide-out detail drawer across 10 entity types without losing workspace context.

Cyber-Physical Asset Graph

7 capabilities

Models what actually sits in your regulatory boundary, from facilities and perimeters to systems of systems.

  • 14 asset types, including facilities, electronic security perimeters, physical security perimeters, shared cyber infrastructure, and systems of systems
  • Parent and child asset hierarchies
  • 11 regulatory traits (such as ERC, ESP, PSP, EAP, TCA, and removable media) that tag each asset for the standards that care about it
  • Electronic access point and transient cyber asset populations derived from traits
  • Full ERT Level 1 population workbook (13 tabs) exported on demand
  • Uploaded ERT template compared against the live inventory to surface drift and gaps dynamically
  • Bulk import of CSV and Excel files with saved column mappings, and CSV export from any grid

Frameworks & Crosswalks

40 frameworks15 NERC CIP standards7 crosswalks69 mappings

Catalog groups

Electric & critical infrastructure

  • NERC CIP (CIP-002 to CIP-015)
  • AWIA Section 2013
  • FedRAMP Low / Moderate / High
  • CMMC Level 1 / Level 2

NIST

  • SP 800-53 Rev. 5
  • SP 800-171 Rev. 2
  • CSF 2.0
  • Privacy Framework
  • RMF (SP 800-37 Rev. 2)

Industry & international

  • ISO 27001 / 27002 / 27701
  • SOC 2
  • HIPAA Security Rule
  • PCI DSS 4.0
  • CIS Controls v8
  • GDPR
  • CCPA / CPRA

Prepackaged crosswalks

  • NIST 800-53 to AWIA20 mappings
  • NIST CSF to AWIA15 mappings
  • NIST 800-53 to ISO 2700110 mappings
  • NIST 800-53 to FedRAMP Moderate8 mappings
  • NIST 800-53 to SOC 27 mappings
  • NIST 800-53 to FedRAMP High5 mappings
  • NIST 800-53 to NERC CIP4 mappings
14 asset types11 regulatory traits

The prepackaged catalogs are curated working sets. They are not a substitute for the authoritative text of each standard.

Where to start, by sector

Electric: NERC CIP

Start with all 15 CIP standards in the catalog, then model BES Cyber Systems, ESPs, and PSPs inside your regulatory boundary.

  • Model BES Cyber Systems, ESPs, and PSPs in the cyber-physical asset graph
  • Generate 13-tab ERT Level 1 population workbooks from live inventory
  • Bring the ERT Level 2 overlay (v10.1) into audit preparation
  • Let the Drift Engine keep evidence and asset records current between audits

Water: AWIA Section 2013

The AWIA Section 2013 catalog and two prepackaged crosswalks (from 800-53 and from CSF 2.0) give risk and resilience assessment teams a starting structure.

  • Deploy the AWIA Section 2013 catalog
  • Apply the NIST 800-53 to AWIA and CSF 2.0 to AWIA crosswalks
  • Use quantitative loss modeling in the risk module to support board cost-of-impact discussions

Oil & Gas

Pair NIST 800-53 and CSF 2.0 with the cyber-physical asset graph to scope pipeline, terminal, and facility assets.

  • Deploy NIST SP 800-53 Rev. 5 and NIST CSF 2.0
  • Model pipeline, terminal, and facility assets in the asset graph
  • Add sector-specific content through your own policies and controls

Defense Industrial Base: CMMC

CMMC Levels 1 and 2 and NIST 800-171 Rev. 2 are in the catalog, while local AI and on-premises deployment keep controlled information inside your boundary.

  • Deploy CMMC Levels 1 and 2 and NIST SP 800-171 Rev. 2
  • Run local AI models inside your own management network
  • Keep controlled unclassified information within your boundary

Other sectors

SectorWhere to start
HealthcareHIPAA catalog plus ISO 27001 and SOC 2
Financial servicesPCI DSS 4.0, SOC 2, and NIST CSF 2.0
Federal contractorsFedRAMP baselines, 800-53, and 800-171
Commercial enterpriseISO 27001, SOC 2, GDPR, and CCPA

Context GRC is designed to support, and helps you prepare for, these programs; it is not itself certified, authorized, or accredited under any of them.

The 14 Canonical Drift Engines

Continuous, not periodic

Fourteen engines run in two families. Six positive engines build forward momentum. Eight negative engines protect against decay. Each context keeps its own settings and history.

  • Per-context toggles and Run Now for every engine.
  • Every run and every skip is recorded for the audit trail.
  • A 10-minute dispatcher sweep resolves each context's local timezone and uses day locks to prevent duplicate runs.
  • Each context clones its engine settings from the Global-Context baseline initially, saving you time,
  • and can be configured individually based on need.
positive_olir_driftPRODUCING_VALUE

Catalyst Beat OLIR Control Mapping Engine

Senses
Reads your active controls against NIST OLIR crosswalk data and the requirements of every framework deployed in a context.
Action
Stages mapping proposals for human approval in the Action Center; rejected suggestions are never re-suggested.
Cadence
Daily @ 2:30 AM Local Context + on framework confirmation + on demand

Framework-agnostic: engines read your own records in each context.

positive_evidence_renewalPRODUCING_VALUE

Evidence Renewal Lifecycle & 4-Tier Provenance Cascade

Senses
Reads each control's collection cadence and renewal milestones (30 days, 14 days, 7 days, due date, 7 days overdue).
Action
Sends renewal guidance to control owners, drawing on assessor notes, prior validation history, and sample metadata.
Cadence
Hourly at minute 30

Framework-agnostic: engines read your own records in each context.

positive_morning_briefingPRODUCING_VALUE

Context-Local Morning Delivery Briefing Engine

Senses
Gathers pending renewals, approaching policy reviews, and open action items for each context boundary.
Action
Delivers a single context-branded briefing with deep links at the start of the local business day.
Cadence
Daily @ 7:00 AM Local Context

Framework-agnostic: engines read your own records in each context.

positive_policy_blast_radiusPRODUCING_VALUE

Policy & Control Review Cadence + Revision Blast Radius Engine

Senses
Reads control review frequencies and counts the controls that depend on each governing policy.
Action
Notifies control owners with a dependency count when a governing policy is revised or a review comes due.
Cadence
Hourly at minute 30 & Event-driven (Policy.Revised)

Framework-agnostic: engines read your own records in each context.

positive_ai_telemetry_flywheelPRODUCING_VALUE

AI Telemetry & Continuous Learning Flywheel Engine

Senses
Watches human decisions on Action Center cards, alongside the AI suggestion each decision answered.
Action
Records originals and human overrides so later AI work in the same context reflects your corrections.
Cadence
Event-driven on HITL Action Review

Framework-agnostic: engines read your own records in each context.

positive_document_approval_driftPRODUCING_VALUE

Document Governance Approval & Review Acceleration Engine

Senses
Tracks draft policies in review, including those held in native and SharePoint document libraries, against a review SLA.
Action
Moves unreviewed Responsible contributors to Informed when the deadline lapses and stages approval triage for Accountable approvers.
Cadence
Hourly at minute 45 & Daily @ 7:30 AM Context-Local

Framework-agnostic: engines read your own records in each context.

Integrations & Extensibility

Centralized connectors, local by default

All connectors are administered in one place under System Administration. Domain modules reuse central settings so credentials are never scattered across screens.

Content & Policy Sources

4

Channels that ingest governing policies and procedures into the vault for AI control extraction and human review.

SharePoint On-Premises SE & Online

Shipping

Discovers policy libraries in SharePoint Subscription Edition and SharePoint Online, and ingests documents into the policy vault for review.

  • Library discovery scopes strictly to the sites and libraries administrators authorize
  • Ingested policies enter the same review, supersession, and drift-escalation workflow as native uploads
  • Document-ID URLs resolve directly to the intended file

Confluence Spaces

Shipping

Ingests policy pages from Confluence spaces you authorize, preserving page structure for review and control extraction.

  • Space-level scoping keeps ingestion limited to selected policy spaces
  • Page content enters AI control extraction staged for human approval

GitHub & GitLab Repositories

Shipping

Ingests versioned policy documents from GitHub or GitLab repositories so policy-as-code flows cleanly into the vault.

  • Repository and path scoping limits ingestion to authorized policy folders
  • Updates flow through standard revision tracking and blast-radius owner notifications

File / ZIP Upload & Document-ID URL

Built-in

Upload individual policy files or ZIP archives directly, or paste a document-ID URL when an external repository is not connected.

  • ZIP archives unpack into individual policy records for review
  • Works identically in completely air-gapped networks with no external connector

Identity & Directory Assurance

1

Directory services that authenticate platform users and collect scheduled directory-state evidence.

Active Directory (LDAP / LDAPS)

Auth + Evidence

Dual-role integration: serves as a platform sign-in provider and collects automated directory-state evidence on a schedule.

  • Multi-select security group filtering limits sign-in and account scope
  • Just-in-time (JIT) user provisioning and 15-minute directory sync keep access current
  • Automated directory-state evidence collection logs every run in the execution ledger

Device & OT Configuration Assurance

2

Read-only connectors to network and endpoint configuration systems that turn device state into control evidence.

SolarWinds NCM (SWIS REST)

Shipping

A strictly read-only connection to SolarWinds Orion and Network Configuration Manager turns device configuration state into evidence on a schedule you set per control.

  • Queries are checked to be read-only before running, and targets are validated to block loopback, link-local, and metadata addresses
  • Scoping restricts discovery to administrator-approved Orion Groups per compliance context
  • Captures vendor-normalized, secret-redacted running and startup snapshots for Cisco IOS/IOS-XE/NX-OS, Juniper JunOS, Fortinet FortiOS, and Palo Alto PAN-OS
  • Detects running-vs-startup and baseline drift with human-in-the-loop baseline sign-off

Configuration baseline compliance

Per device: whether an approved baseline exists, whether the latest running configuration matches it, and whether any drift findings are open.

  • NERC CIP-010 R1
  • NIST SP 800-53 CM-2
  • NIST SP 800-53 CM-6

Configuration change log

Per device: configuration changes captured in the look-back period, and whether any of them remain unreviewed.

  • NERC CIP-010 R2
  • NIST SP 800-53 CM-3

Tripwire Enterprise (REST)

API-Ready (Pending Live Console Validation)

A read-only Tripwire Enterprise REST connector that imports administrator-selected node groups, syncs file-integrity element versions and policy test results, and produces control evidence with human baseline approval.

  • The client exposes no write method at all, so a misconfiguration cannot change anything in Tripwire
  • Imports only administrator-selected node groups, with optional endpoint path overrides
  • Control evidence stores either a hash or the full configuration (screened and redacted), with human baseline approval

Built to Tripwire's published REST API; not yet validated against a live Tripwire console.

Platform Extensibility

3

Built-in administration, encrypted object storage, and opt-in customer-hosted AI inference controls.

Centralized Connector Administration

Built-in

All connectors are administered in one place under System Administration, so service credentials are never scattered across domain screens.

  • Connector credentials are encrypted at rest with Fernet, with a supplied key-rotation script
  • Outbound targets pass SSRF validation before requests are dispatched
  • Domain modules (Policies, Evidence Hub, Asset Inventory) reuse central settings automatically

S3-Compatible Object Storage (SeaweedFS)

Built-in

Stores evidence artifacts and sealed engagement manifests in S3-compatible object storage with volume encryption at rest.

  • Encrypted SeaweedFS volumes run inside your boundary by default
  • Supports requirement-level continuity retention and soft-delete restore without data loss

Customer-Hosted OpenAI-Compatible Endpoint

Built-in

Local models remain the default. Administrators who choose to can point the platform at an OpenAI-compatible inference endpoint hosted by your organization.

  • Local, DoD-favorable open-weight models run inside your boundary by default
  • External customer-hosted inference is an explicit administrator opt-in, never a silent fallback

Roadmap

2

Planned items. The following are direction, not commitments for a specific date.

Planned items. The following are direction, not commitments for a specific date.

Cloud Infrastructure & MDM Evidence Collectors

Roadmap

Automated evidence pulls from cloud infrastructure and mobile device management platforms.

  • Direction, not a commitment for a specific date
  • Cloud infrastructure and MDM collectors are not shipping today

Signed Offline Installers & Update Bundles

Roadmap

Verifiable offline installer and update packages for sites that move software across an air gap by hand.

  • Direction, not a commitment for a specific date
  • Today, releases deploy as containerized stacks with hash-pinned dependencies

Connector credentials are encrypted at rest, outbound targets pass validation before requests are dispatched, and every automated collection run is recorded in the execution ledger.

Catalyst AI

Sovereign, in-network intelligence

AI runs on local models by default, and binds to loopback only, and there are no runtime calls to public content networks. Pointing the platform at an inference endpoint is a deliberate administrator decision that belongs to your organization.

Six specialty personas

  • Policy Catalyst

    Draft, extract, and gap-analyze policies against active frameworks.

  • Audit Catalyst

    Review evidence readiness, workpapers, and finding summaries.

  • Risk Catalyst

    Surface, score, and prioritize operational and compliance risk.

  • Remediation Catalyst

    Generate corrective action plans with RACI assignments.

  • Crosswalk Catalyst

    Map and verify requirements across disparate frameworks.

  • Holistic Advisor

    End-to-end guidance spanning policy, audit, risk, and remediation.

Local, DoD-favorable model roster

  • IBM Granite 4.2 (8B / 30B) Primary reasoning and draftingApache-2.0
  • Phi-4 14B Reasoning, selectable by hardware tierMIT
  • Mistral-Nemo 12B Reasoning, selectable by hardware tierApache-2.0
  • Granite Guardian 4.1 (8B) Independent Context Guardian judgeApache-2.0
  • nomic-embed-text Local embeddings for retrievalApache-2.0

Each model is verified against its manifest family, not just its tag, so a renamed model cannot slip into a runtime pipeline. Model, threads, and context window adapt to host hardware.

Workspace

  • Dual-mode workspace: edge drawer and full-screen /catalyst
  • Persistent session history and shareable deep links
  • Dual-pane Policy Canvas for live side-by-side drafting
  • Per-boundary AI Context Profiles describing each facility
  • Model-aware thinking depth (off, low, full) with automatic chain-of-thought stripping

Real outputs

  • Cited answers with a provenance panel
  • 5-Why root cause analysis, then Apply to Action Center
  • Mitigation suggestions, then Apply to Risk Register
  • Policy Draft Canvas, then Export to Vault
catalyst / Audit CatalystIllustrative transcript

Justify deferring the monthly patch cycle for the relay gateways under CIP-007 R2.

1. Bottom lineA deferral can be supported only if the 35-day patch evaluation and mitigation plan are documented for each affected asset.

2. Context-bound analysisYour Patch Management Procedure (POL-4) requires a mitigation plan when a security patch cannot be applied within the evaluation window.

3. Remediation stepsRecord the vendor advisory, attach the compensating controls, and route the plan to the Accountable approver.

4. Next questionDo you want a draft mitigation plan staged in the Action Center for approval?

Citation POL-4: Patch Management Procedure
Section:
Section 4.2, Deferral and mitigation
Excerpt:
“Where a patch cannot be applied within the evaluation window, a dated mitigation plan shall be recorded and approved.”
Cosine similarity:
0.91

What does our policy say about satellite clock sources?

Zero-trust abstention

No active records cover satellite clock sources in this context yet. I will not infer an answer. Would you like help drafting a net-new policy record?
Illustrative transcript. Answers are grounded in the live records of the active context.

Context Guardian: independent AI-on-AI verification

A single-model assistant grades its own confidence. Context GRC adds an independent local judge, IBM Granite Guardian (granite4.1-guardian:8b), so the model that drafts an analysis is not the model that clears it.

  • Groundedness verification

    Checks drafted controls, root cause analyses, and crosswalk deltas against source documents before they are rendered or applied.

  • Compliant substitution

    When a proposal breaks an organizational rule, such as external cloud MFA, Guardian substitutes the approved alternative, such as on-premises RADIUS or TACACS+ MFA, and de-duplicates sibling options.

  • Two-Key evidence gate

    Evidence is never auto-accepted on one model's score. It needs the primary pass confidence and a clean Guardian groundedness verdict; otherwise it is staged for human review.

  • Protection scorecard

    A four-KPI banner tracks outputs screened, disallowed controls substituted, ungrounded outputs intercepted, and unsafe queries blocked.

Apply to Action Center or Risk Register is an explicit click by a named person; nothing is applied on the model's say-so.

Five placements: Chat input screening, Retrieval output groundedness, Extraction validation, Egress screening, Agentic function calls. Guardian is an administrator-enabled capability.

Human-in-the-Loop Approval

Every AI proposal waits for a named person.

Before an audit, you will be asked who authorized a change. Context GRC stages AI-proposed work for review and records the reviewer's decision against an authenticated account.

  1. Step 1AI_PROPOSES

    AI proposes

    A local model drafts a control, mapping, mitigation, or action.

  2. Step 2PENDING_REVIEW

    Waits in review

    Nothing changes your data. The item is staged in the Action Center.

  3. Step 3APPROVED | REJECTED

    Named reviewer decides

    An authenticated user with a role in that context approves or rejects.

  4. Step 4LEDGER_ENTRY

    Decision recorded

    Actor, role, context, timestamp, and outcome land in the audit ledger.

  • Who

    Approvals are attributable to a named, authenticated user: PBKDF2 credentials, TOTP multi-factor authentication, and per-context roles.

  • What state

    AI-proposed items stay pending until a person acts on them. Rejected suggestions are not suggested again.

  • Lineage

    The reviewer's decision, with the original AI output beside any human edit, is recorded. The audit ledger is hash-chained and tamper-evident, and auditors can search the audit trail.

action center / approval recordIllustrative record
Proposed by
Local model (Catalyst)
Reviewer
j.alvarez
Role
COMPLIANCE_OFFICER
Decision
Approved
Context
Generation-North
Timestamp
2026-03-12 14:07 UTC
Ledger entry
Recorded in hash-chained audit ledger
Illustrative record. Names and values are examples, not customer data.

Guardrails around the approval

  • Two-Key evidence gate

    Evidence is not auto-accepted on one model's score. Administrator-enabled.

  • Guardian screening

    An independent local judge checks groundedness. Administrator-enabled.

  • Role-scoped routing

    Unassigned items go only to administrator and compliance roles in that context.

Designed to support your audit evidence; it does not confer certification.

Continuous Evidence & Cryptographic Assurance

Collect, steward, seal

A hash-chained audit ledger makes after-the-fact edits detectable, so an auditor can trust the trail as well as the artifacts.

  1. Collect

    Evidence and policy content flow in from the connectors your administrators configure.

    • Active Directory (LDAP/LDAPS) collector, with an execution ledger for every run
    • SolarWinds NCM device configuration collector, scoped by Orion group and bound to individual controls
    • SharePoint on-premises and Online, Confluence, and GitHub/GitLab policy ingestion
    • All connectors administered in one place under System Administration
  2. Steward

    Evidence is stored, tracked, and recoverable.

    • S3-compatible storage encrypted at rest
    • Expiry tiers: active, expiring within 30 days, expired (control moves to EVIDENCE_EXPIRED)
    • Recycle bin with restore; context-scoped access through row-level security
    • Provenance types: DIRECT, CONTROL_SYNC, AI_EXTRACTED, CONTINUITY_RETAINED
  3. Seal

    One-click cryptographic sealing of an engagement packet.

    • A SHA-256 evidence manifest is computed at seal time
    • Best-effort S3 object lock on sealed artifacts
    • An AUDIT_PACKET_SEALED entry lands in the same hash-chained, tamper-evident ledger that records approval decisions
Explore all content, identity, and device configuration connectors in Integrations & Extensibility

Requirement-level binding

Artifacts map directly to regulatory requirements as well as controls. CONTINUITY_RETAINED keeps evidence on the requirement when a control is unmapped or retired.

Evidence inheritance across crosswalks links proof to equivalent controls without duplicating files.

Audit Portal

  • Five auditor views: engagement builder, matrixed mandates, overlay catalog, evidence vault, audit trail
  • NERC ERT Level 1 workbook export (13 tabs) and ERT Level 2 overlay v10.1: 170 requests, 71 sample sets, 21 standards
  • Unlimited free auditor seats for your assessors (WECC, SERC, Texas RE, MRO, NPCC, ReliabilityFirst, and 3PAOs)

Utility Architecture

Everything runs inside your boundary

Context GRC deploys as a containerized stack on premises or in a private cloud. Connectors and an optional inference endpoint sit outside the boundary and are administrator-controlled.

  • Run it entirely inside a management network adjacent to your OT systems. The front end makes no calls to public content networks.
  • The model, thread count, and context window adapt to the host hardware, from Apple Silicon to NVIDIA GPUs to CPU-only edge hosts.
  • Roadmap: cloud and device-management evidence collectors are not yet shipping integrations.

Request a Pilot

See Context GRC in your environment

Built for electric utilities and bulk electric system entities. Context GRC does not have reference customers yet, so pilot participants work directly with the engineer building it. Tell us where compliance work slows you down and we will follow up.

  • Architecture deployment workshop and on-prem hardware sizing for your environment
  • Early evaluation of the 14 drift engines and Catalyst AI in your own contexts
  • Custom baseline integration with the frameworks and standards you already track
  • Direct engineering advisory channel

Pricing starts at $20,000 per year.

Teams can be productive in as little as a week, depending on scope and integration needs. Implementation services are available.

Optional. Used only to follow up via your preferred return contact method.

See our Privacy Policy and Terms & Conditions.

Primary regulatory drivers

Select up to 3.

Trust & Security

Built to be inspected

Designed to support your programs. It does not confer certification.

  • Air-gap ready

    Containerized on-prem or private cloud. Every front-end library is vendored locally with documented licenses and SHA-256 manifests, so there are no runtime CDNs.

  • Credentials & MFA

    PBKDF2-HMAC-SHA256 at 600,000 iterations, a NIST SP 800-63B passphrase policy, and TOTP multi-factor authentication.

  • Secrets

    Integration credentials are Fernet-encrypted with a rotation script. Secrets are injected through Docker secrets.

  • Transport & ledger

    TLS between services and a hash-chained, tamper-evident audit ledger of recorded actions.

  • Worker isolation

    Ed25519-signed task envelopes, a least-privilege worker database role under row-level security, pre-persistence DLP screening, and fenced untrusted document text in prompts.

  • Access control

    Role-based access with per-context role grants, and context-scoped views and roles.

  • Supply chain

    177 exact-pinned packages with about 3,000 SHA-256 hashes. CI gates: Bandit, TruffleHog, pip-audit --strict, a copyleft license gate, and Trivy.

  • Attributable approvals

    AI-proposed controls, mappings, and actions are staged for a named, authenticated reviewer to approve across four triage touchpoints, with the decision recorded. Cmd+K opens the command palette.

Licensing

  • Licenses are Ed25519-signed tokens verified locally, with no phone-home.
  • Tiers are set by the number of contexts and internal users.
  • Free Auditor: auditor accounts never consume a seat.
  • After a 14-day grace period the platform moves to a read-only archive. It never locks you out of your records.