InnerWeb
Skip to main content

OHS system supplier risk assessment: questions for the plant IT department

The plant's IT department receives a system that is to run on the network, see people and generate alarms. We have compiled the questions worth asking the supplier before accepting a pilot: about ports, network zones, logs, SSO, tokens, vulnerabilities and data isolation. The supplier's answers should be in writing, using the same numbering as the questions.

5
zones in the architecture model for the IT department
Source: offer card
0
inbound ports in the plant network
Source: offer card
3-4 days
working days to fix critical and high vulnerabilities in sample platform requirements for suppliers
Source: IT supplier requirements of a large platform

Who this list is for and how to use it

The list is for the IT and information security department that assesses an OHS or location system supplier before a pilot. The supplier should answer the questions in the same numbering in which they were asked. The buyer's IT security department, which asked 12 questions about the reporting system, expected exactly this format and a demonstration environment equivalent to production.

The questions do not replace an audit, they set its order. An incomplete answer is information in itself: it shows which area requires a conversation or a document before anyone installs the first element.

1. Architecture: zones, ports and direction of traffic

Start with the question about zones. The architecture model for the IT department that we use has 5 zones: the plant site, users, the plant network, the customer's systems and the cloud in the EU. For each zone the supplier should indicate what runs in it and what leaves it.

No inbound ports are opened in the plant network, and outbound traffic is limited to HTTPS 443 to the instance address. Ask the supplier whether its system has the same assumptions, and request a list of destination addresses and protocols so that a firewall rule can be built.

  • which inbound ports the system requires to be opened in the plant network
  • which addresses and protocols are required for outbound traffic
  • whether the system runs in a demilitarised zone (DMZ) or in the production network
  • whether the OT and IT networks are separated, and how the system crosses between them

Remediation window for critical and high vulnerabilities (working days)

Remediation window for critical and high vulnerabilities (working days)Bar chart: the required time to fix a vulnerability ranges from 3 to 4 working days.01234daysLower limit: 3 days3 daysLower limitUpper limit: 4 days4 daysUpper limit
Source: Sample security requirements of a large platform for IT suppliers

2. Data isolation and hosting model

Ask whether the data of our plant is separated from the data of other customers. Each of our customers has an isolated instance with its own database and its own mail system. The instance can run in Docker containers on the customer's server (on-premise), and some environments run on Kubernetes.

The question about data location is just as important: in which country, in which cloud service, who has administrative access and how that access is recorded. An answer such as "the data is safe" is not an answer.

3. Working with blocked outbound traffic

In many plants the network blocks outbound traffic from the application host. Ask what happens to alarms in such a situation. In our solution, alarm webhooks are stored durably in a queue and are picked up by an external poller through a working inbound channel.

Note the caveat: delivery depends on the polling frequency. This limitation should be recorded in the pilot documentation, because it affects how quickly an alarm about motionlessness or SOS arrives. A supplier who does not mention the limitation is hiding a fact that matters for people's safety.

4. Vulnerabilities, cryptography and tokens

Large purchasing platforms set specific requirements for IT suppliers, and they can be used as a template for questions. An example set includes fixing critical and high vulnerabilities within 3-4 working days, OWASP ASVS level 2, tokens with at least 128 bits of entropy, a ban on RC4, DES, MD5, SHA1, TLS 1.0 and 1.1, and audits from the last 12 months.

Ask the supplier which of these requirements it meets, how it confirms this and when the last audit or penetration test was performed. A request for a dated document is justified: a requirement without evidence is a declaration.

  • how long the supplier takes to remove critical and high vulnerabilities
  • which OWASP ASVS level the application meets and who assessed it
  • what the entropy of session tokens and integration tokens is
  • whether obsolete algorithms and TLS versions are disabled
  • when the last audit or penetration test was performed

5. Login, SSO and permissions

Ask how users log in to the system and how the plant removes an account when an employee leaves. If the plant has a directory service, the question is whether the system supports single sign-on and how it synchronises the list of people. In the architecture model this point stays open until the site inventory, because it depends on the plant's environment.

The second block concerns logs: what is recorded (logins, permission changes, permits, alarms), how long it is kept and in what form it can be exported to the plant's system. For IT what counts is whether the supplier provides evidence for an audit, not only a declaration.

6. Demonstration environment and access to the showcase version

Ask for a demonstration environment equivalent to production. An IT department that cannot check the settings has no way to assess the risk. Ask whether the demo environment has the same safeguards and whether demo data is clearly separated from the plant's data.

This question is linked to the quality of the demo: an environment with a history of gate passages and a training cycle shows the system's behaviour under conditions close to real ones.

7. Recommendation: how to assess the answers and decide on a pilot

Assess the answers in three categories: closed (a written answer with evidence), open (the answer requires an inventory of the site) and rejected (the supplier does not meet the requirement). Before the pilot, the closed category should cover ports, isolation, cryptography and logs, while open items may concern SSO and IP addressing.

A pilot can be accepted with open questions if it has a set deadline for closing them and limits the data to the minimum needed in the pilot.

Video

Frequently asked questions

Must an OHS system supplier have a security audit?

Buyers often require audits from the last 12 months. If the supplier has no audit, it should indicate the scope of testing and the date of the nearest one, and the pilot can be limited to the minimum data.

What to do when the network blocks outbound traffic?

Ask about the alarm queue and pickup by a poller through an inbound channel. Record in the documentation that delivery time depends on the polling frequency.

Can the instance run on our server?

Yes. The instance can run in Docker containers on the customer's server, and some environments run on Kubernetes. The scope of hosting is set during the pilot.

Sources

Need answers to the IT department's questions?

Send us the list of questions in your numbering. We will answer in writing and show the demonstration environment.

Let's talk