InnerWeb
Skip to main content

PERA diagram for a location and access control system

A one-page PERA diagram with levels 0-6 and DMZ 3.5 lets a power plant assess its location and access control system before anyone decides whether it is an IT or an OT system. The integrator draws the server, gateway, receivers and KD gate on it, marks firewalls and traffic directions, and gives the IT and automation department one document for the discussion.

0-6
PERA model levels, with DMZ 3.5
Source: card
5
OT architecture rules to show on the diagram
Source: card

Why draw the diagram before the IT or OT classification

The dispute over whether a location and access control system belongs to IT or OT usually ends with the request being passed from one department to another. The PERA diagram turns that dispute into a discussion of specifics: where the server stands, which devices talk to which, and through which firewall.

What the diagram decides and what it does not

The diagram does not replace the buyer's security policy. It shows which connections the designed system needs and whether any of them breaks the rules the buyer applies to its network. The classification decision is taken by the department responsible for the network, but on the basis of the drawing, not a verbal description.

Why one page

A one-page drawing can be printed, placed on a table and discussed in a single meeting. Multi-page architecture documentation gets lost in mailboxes, and the IT department's questions come back a week later. One page forces a decision on what to show and what to leave in the attachments.

What we draw: levels 0-6 and DMZ 3.5

The architecture of the system in the OT network is presented in the PERA model, where levels 0-6 correspond to successive layers from process to business, and DMZ 3.5 is the buffer zone between the OT network and the higher levels. The buyer usually has its own layout of levels, so the integrator asks about it at the start rather than drawing on assumptions of its own.

Elements of the system on the drawing

The diagram places four kinds of elements: the application server, the gateway, the signal receivers and the access control gate. Each gets a level, an address in a VLAN and a description of the direction of connections.

  • application server in the OT network, at the buyer's site
  • gateway collecting data from the receivers
  • receivers (antennas) in buildings and on the site
  • access control gate with the client's KD reader

KD gate: what the system supplies and what stays with KD

InnerWeb does not manufacture access control readers and does not sell KD cards. On the diagram the reader and KD controller are an element of the client's system, and the arrow to the InnerWeb server is the card swipe event sent by webhook. Such a drawing shows the IT department at once that no new type of reader is appearing on the network.

Elements of the system on the diagram by type (illustrative example)

Elements of the system on the diagram by type (illustrative example)Illustrative chart: one server, two gateways, four receiver groups and three KD gates on a sample diagram.01234elementsApplication serverApplication server: 1 elements1GatewayGateway: 2 elements2Receivers (groups)Receivers (groups): 4 elements4KD gatesKD gates: 3 elements3
Source: Sample calculation: assumed number of elements on an illustrative one-page diagram

Rules the diagram must meet

The energy sector buyer checks the drawing against several rules. Their fulfilment is visible on the diagram without reading the description, and a missing element is often the reason for a return for correction.

  • OT network separated by firewalls from higher levels
  • no hosts with interfaces in two levels
  • separate VLANs for management, backup and monitoring
  • logs sent to a SIEM
  • remote access through VPN with 2FA and a jump host in the OT DMZ

Why a host with two interfaces in different levels is a problem

A host with interfaces in two levels works like a bridge that bypasses the firewall. That is why the diagram shows the server as one device in one level, and routes communication with other levels through the firewall and, where needed, through DMZ 3.5.

What about outbound traffic

When the client's network blocks all outbound traffic from the application host, alarm webhooks are saved in a persistent queue, and an external poller collects them through an inbound channel. On the diagram this is drawn as an inbound arrow, not an outbound one, which the buyer sees at once.

Audit evidence and the buyer's requirements

The energy sector buyer may require the system to work locally in the OT network without a connection to the vendor, frames signed with the buyer's keys, and a device trust procedure. The diagram is the natural place where these requirements meet: it shows that the server is local, not in the vendor's cloud.

For an auditor, the value of the diagram is that it can be compared with reality: the firewall configuration, the list of VLANs and the log forwarding settings. A discrepancy is then caught at acceptance, not after an incident.

Checklist

Video

Frequently asked questions

Why a one-page diagram when technical documentation exists?

One page lets the IT and automation department discuss the architecture in one meeting. The full documentation stays as an attachment, and the diagram is the starting point for the classification decision.

Does InnerWeb supply readers for the KD gate?

No. Readers and controllers belong to the client's KD system. InnerWeb receives card swipe events through a webhook.

What about remote access to the server in the OT network?

The diagram shows access through VPN with 2FA and a jump host in the OT DMZ, not a direct connection from higher levels.

Who decides whether the system is IT or OT?

The department responsible for the buyer's network. The diagram gives it the facts for that decision.

Let's draw the diagram for your network

We will prepare a one-page PERA diagram with the server, gateway, receivers and KD gate, according to your layout of levels. Tell us when to meet with IT and automation.

Let's talk