Skip to content

Raymon Industrial Security Platform

Control industrial operations—not just network connections.

Connect authenticated users and sessions to the equipment, commands, values, and operational sequences they use—then record, allow, or block each activity with evidence that operations, engineering, and OT security teams can understand.

Identity-aware access · Protocol-aware enforcement · Industrial microsegmentation · Stateful protection · Operational evidence

Explore the Platform View Industrial Solutions

Start with the path that fits your role

You do not need to read this catalog from beginning to end. Plant leadership can begin with outcomes and solutions; operations can follow remote work and evidence; engineers can follow equipment, policy, and protection; evaluators can go directly to capability status and acceptance criteria.

Read the Executive Summary Choose a Reading Path

Control the industrial operation—not only the connection

Traditional network controls can allow or deny an IP address and port. Industrial operations need more context: Which protocol function was requested? Which RTU, PLC, point, register, or control target was involved? Was the operation expected at this stage of the process?

L2Proxy connects authenticated access, industrial protocol inspection, equipment knowledge, explainable policy, and operational evidence. It can determine who introduced an operation, which asset and point were involved, whether the action was permitted, and why the resulting decision was made.

Authenticated user → Live session → Industrial equipment → Operation → Record / Allow / Block

The platform can:

  • record an observation without interrupting production;
  • allow an explicitly permitted operation;
  • block traffic that violates an approved policy.

Stateful protection can also correlate events across multiple messages. This enables DNP3 Select-Before-Operate validation, command-to-status verification, controlled maintenance authorization, restart recovery tracking, alarm lifecycle monitoring, and replay-resistant one-time transitions.

Identity-aware industrial accessAssociate authenticated users and live sessions with the industrial activity they introduce.
Industrial microsegmentationLimit communication by protected access domain, identity, session, equipment, operation, and process context.
Protocol-aware protectionEvaluate decoded functions, objects, points, values, commands, endpoints, and sequences—not only ports.
Equipment-centric policyBuild protection around plant assets, points, normal states, operating limits, and approved commands.
Explainable decisionsRecord why an operation was observed, permitted, or blocked using reviewable industrial policy.
Industrial-language visibilityTranslate protocol details into equipment, operation, severity, category, tags, and readable descriptions.
Stateful protectionCorrelate authorization, command, response, feedback, timeout, replay, and process prerequisites.
Guided engineeringCreate policies faster with managed equipment knowledge, templates, contextual help, autocomplete, and validation.
Operational evidenceRetain session context, decoded protocol facts, decisions, and normalized events for audit and investigation.

Two complementary enforcement choices

                                  ┌─ L2Proxy Connect
Approved industrial policy ──────┤  Inside the authenticated session path
                                  │
                                  └─ Standalone L2Proxy Service
                                     At an independent industrial boundary

L2Proxy Connect provides user- and session-aware enforcement for authenticated remote industrial access. Standalone L2Proxy Service protects transparent, routed, or isolated industrial paths under an independent service lifecycle. Both use the same industrial inspection, policy, stateful protection, and evidence capabilities and can operate together at one site.

Together they support North-South access control and East-West enforcement wherever traffic crosses a managed L2Proxy path. See Industrial Segmentation and Microsegmentation.

A practical remote-maintenance outcome

An authenticated transformer-service engineer connects during an approved maintenance period. L2Proxy Connect associates the user and session with each industrial operation, permits approved diagnostic reads, evaluates an OLTC request against the assigned equipment policy, blocks an out-of-range or incorrectly sequenced command, and retains the complete decision trail for operations and investigation.

A staged OT adoption model

  1. Observe — establish protocol and asset visibility using passive or offline traffic.
  2. Normalize — translate protocol detail into device, asset, operation, and severity context.
  3. Model — describe permitted sequences, timing, identities, and process prerequisites.
  4. Validate — replay representative PCAPs and test normal, abnormal, timeout, and replay paths.
  5. Enforce — enable narrowly scoped blocking policies after operational approval.
  6. Audit — retain structured evidence for operations, engineering, and incident response.

Explore the platform

Catalog area Start here
Overview Industrial Security Platform and Industrial Outcomes
Solutions Industrial Solution Portfolio
Secure Access Secure Industrial Access, L2Proxy Connect, and Industrial Segmentation
Policy Engineering Industrial Policy Engineering
Protection & Evidence Industrial Protection and Evidence
Deployment & Assurance Deployment and Assurance

A control platform, not a replacement for process safety

L2Proxy evaluates network-carried industrial activity. It does not replace a safety instrumented system, PLC interlocks, engineering procedures, or endpoint authorization. Network loss, asymmetric capture, local operation, encryption, and incomplete protocol parsing must be considered when a policy is designed.