01
Identity-aware industrial access
Associate each authenticated user and live session with the equipment, points, commands, and values they reach.
User · session · access domainRaymon 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 accessProtocol-aware enforcementIndustrial microsegmentationStateful protection
Industrial decision context LIVE
IDENTITYField engineerAuthenticated session
↓TARGETSubstation RTU · AI:30DNP3 control point
↓OPERATIONOperate · value 131.25SBO sequence verified
POLICY DECISIONALLOWApproved sequence · within profile · evidence retained
The control gap
A permitted connection is not necessarily a permitted operation.
Industrial decisions require context that conventional network controls cannot provide: who acted, which equipment and point were involved, what the decoded operation requested, and whether its value and sequence were expected.
01Authenticated user→
02Live session→
03Industrial equipment→
04Decoded operation→
05Record · Allow · Block
Observe safelyEstablish industrial visibility before enforcement.
Enforce preciselyControl the actual operation, value, target, and sequence.
Explain every decisionRetain evidence readable by industrial teams.
One industrial control plane
Security built around equipment and operations
Raymon combines secure access, deep industrial inspection, policy engineering, stateful control, and operational evidence. The capabilities work together; they are not isolated dashboards.
02
Protocol-aware enforcement
Evaluate decoded industrial operations—not only addresses and ports—and record, allow, or block them with an explicit reason.
Function · object · point · value03
Industrial microsegmentation
Constrain North–South and East–West activity by identity, protected access domain, equipment, operation, and process context.
Zone · identity · equipment · operation04
Stateful process protection
Correlate authorization, command, response, feedback, timeout, and replay across multiple messages and sessions.
Sequence · timing · prerequisite05
Equipment-centric policy
Manage industrial equipment, points, operating limits, safety profiles, reusable templates, and site-specific policy profiles.
Asset · point · limit · safety profile06
Operational evidence
Translate protocol detail into readable industrial events with category, severity, tags, session context, and decision evidence.
Normalize · explain · retainIndustrial use cases
Controls that map to real operational work
Start from the maintenance task, protected equipment, and expected process behavior—not from a generic list of blocked ports.
01Power & Utilities
Validate a DNP3 control sequence
SITUATION
A remote engineer initiates a control operation against an RTU point.
RAYMON CONTROL
Confirm Select-Before-Operate order, object and point consistency, timing, user session, and approved maintenance scope.
OPERATIONAL OUTCOME
Permit the expected operation; block a direct, expired, mismatched, or replayed operate; retain the complete decision trail.
02Manufacturing
Constrain vendor access to a PLC cell
SITUATION
A vendor needs diagnostics without unrestricted access to the production network.
RAYMON CONTROL
Place the session in a dedicated access domain and permit approved read operations only for assigned equipment.
OPERATIONAL OUTCOME
Keep unrelated cells unreachable and identify every attempted write, stop, download, or out-of-scope operation.
03Water & Process
Protect an operating limit
SITUATION
A command proposes a value outside the equipment safety profile.
RAYMON CONTROL
Evaluate the decoded target and value against the managed point definition, permitted range, identity, and process prerequisite.
OPERATIONAL OUTCOME
Block the unsafe request at the managed enforcement path and produce evidence meaningful to operations and engineering.
From packets to operational evidence
An event an industrial team can act on
Raymon preserves protocol facts while presenting the event in operational language. The same record supports live operations, investigation, policy review, and audit.
- Equipment, point, operation, and requested value
- Authenticated identity and session context
- Category, severity, tags, and readable description
- Policy decision, matched protection, and reason
CONTROL OPERATIONALLOWED
DNP3 operate accepted for an approved analog output
Field engineer requested 131.25 on RTU-07 / AI:30. The Select-Before-Operate sequence was complete, the value was within the assigned safety profile, and the maintenance session was authorized.
- Identity
- field.engineer-17
- Session
- Maintenance · Substation West
- Equipment
- RTU-07
- Point
- AI:30 · Setpoint
- Sequence
- Select → Operate · 1.8 s
- Decision
- ALLOW
Deployment without policy fragmentation
Place enforcement where the industrial path requires it
Use session-aware control for authenticated remote work, independent services at industrial boundaries, or both. The inspection, policy, stateful protection, and evidence model remains consistent.
L2Proxy Connect
Inspect and enforce industrial policy inside the authenticated access path, preserving user and session context with every decision.
Standalone L2Proxy Service
Run isolated service instances with dedicated policy profiles at transparent, routed, bridged, or protected industrial boundaries.
North–South access control+East–West industrial enforcement+Per-session operational evidence
Review deployment and assurance choices →Continue with the evidence
Evaluate Raymon against your industrial requirements.
The complete product catalog provides operational examples, policy workflows, normalized events, deployment choices, qualification guidance, and clearly stated product boundaries.
Customer publications
Download the printable catalogs
Share A4 PDFs with embedded diagrams for meetings, reviews, and offline distribution.