Recording is the default. Enforcement is opt-in.

ENGINEERING AUTHORIZATION FOR INDUSTRIAL ENVIRONMENTS

Govern the engineering session, not only the workstation.

EWSP is an evidence and authorization layer for privileged industrial engineering activity. On a Windows engineering workstation it records which process opened a connection to which controller, on which port and protocol, and when, for the destinations you configure it to watch. It checks that session against the project baseline where integrity monitoring is configured, and against a policy of approved destinations. It can deny a new connection that policy does not permit. By default it blocks nothing, and it may send a read-only identity query to the controller. Enforcement is a separate step you turn on deliberately.

Records by default Policy-based authorization Opt-in local enforcement A record of observed sessions

THE PROBLEM

A network path is not an engineering authorization.

Industrial organizations already protect networks, endpoints, identities and remote access. Segmentation, firewalls, EDR, application allowlisting, PAM, remote access controls and OT network monitoring each answer an important question. Privileged engineering work raises another one: what is trusted engineering software actually authorized to do to an industrial asset?

CONNECTIVITY

Can this system reach that asset?

A network path being available does not by itself establish authorization for a particular engineering activity.

ENGINEERING AUTHORIZATION

Is this activity permitted for this asset, in this context?

A trusted workstation or application does not by itself establish authorization for every industrial engineering action.

THE MISSING SECURITY BOUNDARY

The layer between a trusted workstation and an industrial asset.

NetworksWhat can communicate
EndpointsWhat is trusted
Identities and remote accessWho can obtain privileged access
Engineering authorization EWSPWhat privileged engineering activity is authorized for this asset, in this engineering context

EWSP addresses this authorization boundary.

WHAT EWSP DOES

One authorization boundary for privileged engineering activity.

EWSP evaluates the context, decides, enforces locally and keeps the evidence, so engineering authorization no longer depends on assumption.

RECORDS BY DEFAULT

It records by default, and acts only if you turn that on

A new installation observes connections to the destinations you configure and does not enforce anything. It records the workstation, the application, the destination and port, the time, and the project baseline it was checked against where project integrity monitoring is configured. It does not block an edit and does not change how engineers work. For sessions to the controller's standard engineering port, it also opens its own connection and sends a read-only identity request; the answer is not authenticated. Enforcement is a separate step that you turn on deliberately. The record identifies the workstation and the application; it does not identify the individual engineer or tie a record to a single controller session.

ENGINEERING CONTEXT

Understands the activity around the connection

EWSP evaluates the context it can observe: the workstation, the process and executable that opened the connection, the destination address and port, the time, and the project baseline where integrity monitoring is configured. Where the controller answers a separate read-only query, it records the identity the controller reports, which is not authenticated. It does not identify the individual engineer, and it does not decode the engineering protocol.

AUTHORIZATION

Policy-based, explainable decisions

EWSP applies explicit policy to engineering context and produces an explainable authorization decision, and can incorporate scoped authorization evidence into that decision.

ENGINEERING OPERATION CONTEXT

Operation evidence, without overstating it

EWSP can incorporate explicit evidence about the requested engineering operation into authorization decisions, while distinguishing reported operation evidence from evidence considered sufficient for authorization. EWSP does not assume every requested engineering operation can currently be identified from every industrial engineering tool.

LOCAL ENFORCEMENT

Decisions that take effect

EWSP can enforce the resulting decision at the engineering workstation before protected communication reaches the target asset. Enforcement applies to new connections: when a permit expires, a change that was already made is not reversed and a session that is already open is not reset.

IF THE AGENT STOPS

EWSP fails open

EWSP's enforcement filters belong to the agent's own process. When that process ends, its filters are removed with it, and new connections are no longer blocked until the agent is running again. This is deliberate: a stopped agent does not leave an engineer unable to reach a controller. A stop the agent did not get to record leaves a gap in its local record, not a closing entry.

EVIDENCE

A record that explains itself

EWSP preserves an explainable record of the context, the authorization decision, the enforcement result and available operational evidence.

INTEGRITY

Project file changes are noticed

EWSP watches the protected project file on the workstation and compares it with the approved baseline. When the file changes, it flags the change and, where enforcement is on, withdraws its approved-destination permits so new connections are denied. It does not read the controller. An edit made online to a running controller does not change the project file until someone saves it, so EWSP does not see that edit, and it cannot compare the file with what is running in the controller.

RECOVERY AND INVESTIGATION

Context that survives the event

EWSP preserves engineering activity context to support investigation, reconciliation and recovery workflows.

HOW EWSP WORKS · HIGH LEVEL

Context, decision, enforcement, evidence.

A conceptual view of where EWSP sits. It is not a description of the software’s internal components.

Engineer or engineering team
Engineering workstationApplication · Project · Engineering context
EWSPEngineering Authorization
ContextPolicyDecision
PERMIT
Industrial asset
DENY / WITHHOLD
Protected communication does not proceed
Engineering evidenceContext, decision, enforcement result and observed outcome
Failure behavior. EWSP separates authorization failures, evidence uncertainty and enforcement failures so unavailable evidence is not silently treated as authorization. That describes how it decides while it is running. It does not mean EWSP blocks traffic when it is not running. EWSP fails open: its filters belong to the agent’s own process, so when that process stops, crashes or is stopped, new connections are no longer blocked until it runs again. EWSP tests failure and recovery behavior rather than assuming it. See Current Product Status for what has been measured to date.

SEE EWSP DECIDE

An unapproved destination denied, an approved one permitted.

A connection to a destination outside the approved policy is denied before it connects. A connection to an approved destination is permitted. Recorded on 12 August 2026 from the EWSP Console, on an earlier build than the current release, with a PC connecting to a simulated controller running in a virtual machine. It does not show a real controller or real engineering software.

HOW EWSP FITS WITH EXISTING OT SECURITY

EWSP complements existing OT security.

It is designed to sit alongside the controls an industrial organization already relies on, not to replace them.

OT network securityhelps determine what can communicate.
Endpoint securityhelps determine whether a workstation or application is trusted.
PAM and remote access controlshelp govern who can obtain privileged access.
EWSPfocuses on the engineering authorization context surrounding privileged activity against industrial assets.

Endpoint trust can contribute to engineering authorization. It does not replace engineering authorization.

BROWNFIELD BY DESIGN

Designed for the industrial environments that already exist.

EWSP is built around brownfield plants, where existing engineering tools, networks and controllers stay in place.

  • Local Windows deployment on the engineering workstation.
  • Designed so the current enforcement model does not require redesigning the controls network.
  • No PLC logic modification is required for current workstation-side enforcement.
  • Existing engineering tools remain the engineering tools.
  • EWSP is not inserted into the process-control loop.
  • Adoption can begin without immediately enforcing blocks.
Does it replace my firewall, EDR or PAM?

No. It complements them.

Can we begin without blocking engineers?

Yes. Observation and review come before selective enforcement, where supported by the current product.

Compatibility with particular engineering tools and controllers is established during validation, not assumed. EWSP does not claim universal compatibility.

EVIDENCE AND GOVERNANCE

An explainable record of what was evaluated and what happened.

EWSP is designed to preserve a local record so an engineering decision can be understood and reviewed afterward. The record is stored on the workstation and is not protected against alteration or reading by a local account that can reach it.

Recorded

  • Engineering context
  • Authorization decision
  • Policy result
  • Enforcement outcome
  • Project or artifact evidence, where available
  • Industrial asset evidence, where available
  • Operational outcome, where observed
  • Recovery and reconciliation evidence, where available

Read-only integration interfaces can expose governed engineering evidence to approved enterprise workflows.

EWSP may generate evidence that is useful to governance and compliance workflows. It does not provide certification, and it does not by itself establish compliance with IEC 62443, NERC CIP, or any other framework.

CURRENT PRODUCT STATUS

Working software. Controlled validation. Pilot next.

An honest view of maturity, so a reader knows exactly what exists today.

WORKING SOFTWARE

Built

A native Windows engineering authorization and local enforcement platform.

CONTROLLED VALIDATION

Lab validated

Authorization, enforcement, evidence and selected governance capabilities demonstrated in controlled test environments.

NEXT MILESTONE

Pilot validation

Industrial design partner and pilot validation using real engineering workflows and industrial assets.

  1. Built
  2. Lab validated
  3. Pilot validated next
  4. Production validated not yet

EWSP has not yet been validated in production plants, across the range of vendor engineering tools, or at PLC scale.

LOW-RISK ADOPTION

Begin with evidence. Add enforcement deliberately.

OBSERVE
REVIEW
SELECTIVELY ENFORCE
VALIDATE

You are not expected to install EWSP and immediately start blocking engineers. Observation and review come first; enforcement is added only where you choose.

VALIDATION AND PROOF

Demonstrated in controlled environments.

  • Authorization decisions on observed sessions demonstrated
  • Authorized and unauthorized communication demonstrated
  • Local enforcement demonstrated
  • Engineering project integrity monitoring demonstrated
  • Explainable evidence and audit records demonstrated
  • Controlled backup and recovery behavior demonstrated

Controlled technical validation is not production deployment. Detailed validation results are shared privately during technical diligence and pilot discussions.

DESIGN PARTNERS AND PILOTS

Validate the engineering authorization boundary in a real workflow.

EWSP is seeking industrial operators, OT cybersecurity teams, automation organizations and experienced design partners to validate the engineering authorization boundary in real engineering workflows.

contact@ewsp.org