Home Platform Services Industries Resources Company Schedule a Demo

EZTRAK Security & Access Architecture

See how EZTRAK minimizes the systems, credentials, connections, and trust relationships required to deploy turnaround software — without requiring ERP credentials, inbound firewall access, or OT connectivity.

IT teams are right to scrutinize every external application introduced into a refinery environment. This paper gives your team a clear view of what EZTRAK needs to operate and where the customer remains in control.

What access does EZTRAK require?

EZTRAK is designed to minimize the systems, credentials, connections, and trust relationships required to deploy turnaround software. It does not require ERP credentials, inbound firewall access, or connectivity to OT systems.

  • No ERP credentials required. Customers decide what approved information is exported and imported.
  • No inbound firewall access. EZTRAK does not require an inbound connection into the customer network.
  • No OT connectivity. EZTRAK remains separate from process control and safety instrumented systems.

What is covered in the paper?

The paper walks through the access boundary and the controls your team can evaluate, including identity and authentication, role-based access, tenancy, encryption, audit trails, vulnerability management, backups, and hosting.

It is written for the IT, security, and operations stakeholders who need enough detail to review the architecture before approving a new turnaround application.

Join our weekly newsletter

Field-level insights into how turnarounds, shutdowns, and outages actually run. No product announcements.

Give your IT team the details they need.

Review the architecture, access boundaries, and controls directly before you make a decision.