Notifications
Clear all
Topic starter
09/07/2026 3:19 pm
TL;DR: Manufacturing IT teams are being pushed to centralise asset visibility, automate routine service work, and tighten auditability across IT and OT environments, according to Efecte. The practical issue is not automation itself but whether access, workflow, and change control remain governable when service desks handle production-critical systems.
NHIMG editorial — based on content published by Efecte: Jak działy IT w produkcji mogą odzyskać kontrolę i czas dzięki narzędziom Matrix42
By the numbers:
- Only 5.7% of organisations have full visibility into their service accounts.
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools.
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface.
Questions worth separating out
Q: How should manufacturing IT teams govern access when service desks automate resets and provisioning?
A: They should treat the workflow itself as a governed access path.
Q: Why does asset visibility matter so much for IAM in manufacturing environments?
A: Because access governance depends on knowing what exists, who owns it, and which systems depend on it.
Q: What do security teams get wrong about low-code apps in industrial IT?
A: They often treat low-code apps as lightweight productivity tools instead of governed systems that can influence access, incidents, and operational change.
Practitioner guidance
- Map production assets to identity owners Inventory shop-floor endpoints, scanners, printers, MES connections, and IoT devices alongside the human and non-human identities that can reach them.
- Bind workflow approvals to lifecycle rules Require reset, provisioning, and access-request workflows to inherit expiry, revocation, and reviewer ownership from the underlying identity record.
- Review low-code apps as governed assets Classify operational apps that handle faults, requests, or access decisions as control-bearing systems.
What's in the full article
Efecte's full article covers the operational detail this post intentionally leaves for the source:
- Practical examples of how manufacturing teams structure service desk automation around internal processes.
- The specific ways the platform ties asset inventory, workflow, and compliance reporting together.
- How the article positions low-code app creation for operational support teams.
- The vendor's own framing of time savings, deployment speed, and day-to-day IT administration in production settings.
👉 Read Efecte's article on manufacturing IT automation and control →
Manufacturing IT automation: what changes for identity and access teams?
Explore further
09/07/2026 3:37 pm
Manufacturing IT automation is an identity governance problem, not just an efficiency project. The article focuses on saving time, but the underlying change is that more access decisions are being expressed through workflows rather than direct human action. That shifts control risk into provisioning logic, approval routing, and asset visibility. Organisations that treat the service layer as a convenience layer miss the fact that it now governs who and what can operate production systems.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools.
A question worth separating out:
Q: How can organisations reduce the risk of stale access in automated service workflows?
A: Use time-bound entitlements, explicit revocation steps, and periodic recertification for any automated path that creates access. The key is to prevent workflow convenience from turning into persistent authority. When a process can provision quickly, it should also be designed to cleanly remove access when the task ends.
👉 Read our full editorial: Automation in manufacturing IT: identity control, access, and auditability
