Skip to main content

Manufacturing & Critical Infrastructure

Keep the World Running.

As AI enters operational environments, evidence must account for equipment, processes, vendors, cyber-physical dependencies and real-world effects.

Where the risk sits

Where operational AI needs evidence.

AI that plans, schedules or advises in operational settings brings IT-style risk close to physical processes.
  • 01

    Operational data and tools

    AI with access to maintenance, scheduling or supplier systems.

  • 02

    Vendor AI

    Supplier tools inside operations that change on the supplier’s schedule.

  • 03

    Authority versus safety

    Having permission to act is not the same as being safe to act — the two need separate evidence.

  • 04

    Hand-offs to people

    Recommendations that operators may follow without the context behind them.

  • 05

    Downtime and resilience

    The cost of an AI-driven mistake in a process that has to keep running.

What we do here

Evidence for the IT side of operations.

Mythos AI Security assesses AI workflows, data access and vendors — not live control systems, and not physical safety.
  • Athena

    Maps the data, systems and vendors an operational AI workflow can reach.

    Example output · Access and dependency map

  • Achilles

    Tests the workflow’s permissions and recommendations in a test environment.

    Example output · Findings with evidence

  • SPINE

    Keeps conclusions tied to versions, and reopens them when a vendor or model changes.

    Example output · Claims and change records

Business impact

What we would expect to measure.

Agreed with your operations and security owners.
  • Hypothesis

    Known dependencies

    Data, systems and vendors in scope mapped and evidenced.

  • Hypothesis

    Bounded authority

    What the AI can do, tested in a safe environment.

  • Hypothesis

    Vendor visibility

    Supplier changes tied to what they affect.

  • Hypothesis

    Clear hand-offs

    Operator decisions recorded with their evidence.

Control alignment

Referenced, never certified.

Operational and safety standards that apply to you are identified during scoping, so evidence can support the reviews they require.
  • NIST SP 800-53Mapping builtFindings are tagged to the controls they touch.
  • OWASP Top 10 (2021)Mapping builtWeb application risks, tagged to findings.
  • OWASP Top 10 for LLM Applications (2025)Mapping builtUsed as threat coverage for testing.
  • General AI packMapping builtAI governance controls, layered on the core map.
  • Your safety and OT security standardsReferenced in scopingIdentified with your team; physical safety stays with your safety owners.

A walkthrough

A maintenance planner, start to finish.

How one scoped engagement would run, entirely outside production.

A manufacturer wants an AI assistant to draft maintenance plans from equipment history and supplier bulletins. It asks what the assistant can reach and whether a bulletin could steer it.

Illustrative scenario · synthetic data
  1. Scope agreed

    test environment onlyScoped

    Data, systems and limits are written down; no live control systems are touched.

  2. Reach mapped

    AthenaObserved

    The assistant can also write to the work-order system — not in the design.

  3. Behavior tested

    AchillesFinding

    Text inside a supplier bulletin makes the assistant draft an out-of-schedule work order.

  4. Fix retested

    same scenariosVerified

    Write access removed; drafts go to a planner for approval.

  5. Decision

    your operations ownerHuman decision

    Approved for drafting only, with retest on the next supplier update.

A first conversation

What we would ask first.

Typical starting point: Assessment of one high-risk AI system

  1. 01Which AI workflow touches operations, and in what role?
  2. 02What systems and vendors can it reach, and can it write to any of them?
  3. 03What test environment can we use so production is never touched?
  4. 04Who owns safety decisions, and how should our evidence reach them?

Mythos AI Security

Start with one operational workflow.

A scoped assessment in a test environment, with evidence your operations and security teams can use.