1,002 Photos and videos
The way #ZeroTrust is implemented in IT does not translate directly to OT environments:
- Many industrial systems run on legacy hardware
- Devices cannot always be patched or modified
- Downtime may be unacceptable, even for maintenance
1/2
ALT "Person holding a child-sized high-visibility safety vest that is clearly too small to fit, illustrating why a one-size-fits-all Zero Trust approach designed for IT may not work in OT environments."
1
12
Applying IT security tools directly to these environments can introduce complexity without solving the real #remoteaccess control problem.
Read it here: secomea.com/blog/zero-trust/โฆ
#OTsecurity #secomea
2/2
13
"Most companies have their internal remote access processes under control. The real problem starts with third parties."
That was one of the key points discussed in Jesper's recent interview with @EEngineeringMag.
For many industrial organizations, employee access is
1/6
1
8
find themselves in a situation where employee access is tightly governed, while ๐๐ต๐ถ๐ฟ๐ฑ-๐ฝ๐ฎ๐ฟ๐๐ ๐ฎ๐ฐ๐ฐ๐ฒ๐๐ ๐ฟ๐ฒ๐บ๐ฎ๐ถ๐ป๐ ๐ณ๐ฟ๐ฎ๐ด๐บ๐ฒ๐ป๐๐ฒ๐ฑ across multiple systems, processes, and stakeholders.
Which brings us to another point from the interview:
5/6
1
2
"You either have control over access to your industrial equipment, or you don't. You either know who connected, what they did, and why, or you don't."
Read the full interview ๐
fineeng.eu/driving-industriaโฆ
#OTsecurity #remoteaccess #secomea
6/6
3
secure on its own. The real test is whether the entire system remains secure once everything is connected.
#OTsecurity #remoteaccess #secomea
P.S. This car analogy comes from Anette Svendsen's webinar on using "IEC 62443 as a common language for NIS2, CRA, and NIST CSF".
5/6
1
8
If you missed the session, you'll find the link to watch it on demand ๐
secomea.com/webinars/iec6244โฆ
6/6
9
If you've ever been on a troubleshooting call where five people are describing what they see to the one person who actually has #remoteaccess, you'll probably understand why we built ๐๐ผ๐ถ๐ป๐ ๐ฆ๐ฒ๐๐๐ถ๐ผ๐ป.
OT problems rarely belong to one team.
Maintenance, IT,
1/4
1
11
๐ป๐ผ๐ ๐ท๐ผ๐ถ๐ป ๐๐ต๐ฒ ๐๐ฎ๐บ๐ฒ ๐ฟ๐ฒ๐บ๐ผ๐๐ฒ ๐๐ฒ๐๐๐ถ๐ผ๐ป ๐ถ๐ป ๐ฟ๐ฒ๐ฎ๐น ๐๐ถ๐บ๐ฒ, enabling teams to collaborate directly rather than relay information through calls, screenshots, and status updates.
The result is faster troubleshooting, better knowledge sharing, and
3/4
1
11
greater visibility into remote work.
Because solving OT problems is often a team effort. Remote access should support that.
Head to your Prime platform to try it out, and read more about the Joint Session feature in our blog: secomea.com/blog/product-updโฆ
#OTsecurity #secomea
4/4
3
The #SANS #ICS ๐ฆ๐ฒ๐ฐ๐๐ฟ๐ถ๐๐ ๐ฆ๐๐บ๐บ๐ถ๐ ๐ฎ๐ฌ๐ฎ๐ฒ starts today in Orlando ๐
We'll be here over the next few days discussing a focus area that keeps coming up across industrial environments: managing third-party access to OT systems.
According to #secomea's 2026 State
1/3
1
38
of Industrial #remoteaccess Report, most organizations now manage 6-20 external vendors, while a significant number manage many more.
Every vendor, contractor, and service partner introduces additional access paths, credentials, and workflows that need to be controlled.
2/3
1
11
As these ecosystems grow, managing access centrally is becoming an operational necessity.
If you're attending the Summit and want to exchange perspectives on #ICSSummit, vendor access, and remote connectivity, stop by the #secomea booth and say hello. ๐
#OTsecurity
3/3
14