Secomea vendor access needs site-by-site expiry evidence

Create one entitlement per site and purpose

The direct control is a site-scoped entitlement record. Identify the person, employer, vendor contract, internal sponsor, physical site, process area, asset group, approved applications or protocols, requested privilege, business purpose, support case or service class, allowed schedule, issue and expiry dates, authentication method, credential custody, required supervision, and accountable approvers. A vendor company, shared support account, global group, or active contract is not sufficiently precise to establish who may reach which industrial system.

Separate employment and contract validity from technical access. A technician can remain employed while the project, warranty, maintenance window, site sponsorship, qualification, or local need has ended. Conversely, an urgent operational need does not automatically authorize a dormant identity. Preserve requested, approved, provisioned, used, suspended, expired, revoked, and recertified states with effective times and reasons. Unknown ownership or missing sponsor should close the entitlement path, not become a permanent exception.

Recertify standing access without preauthorizing work

A periodic review should give each site owner a complete population of vendor identities, groups, privileges, target assets, last use, pending support cases, expiry, exceptions, and credential health. Reviewers need enough operational context to remove obsolete access and narrow excess scope. Record each disposition, reviewer role, evidence date, changes, unresolved item, and follow-up. Aggregate active-user counts cannot show whether access is still needed or correctly bounded at a particular facility.

Entitlement is only one gate. Even a current, least-privilege account does not authorize a particular remote task, configuration change, command, restart, patch, bypass, or return-to-service decision. Those actions require their own site work authority, safe process state, engineering procedure, supervision, change control, rollback, and closure evidence. Keep lifecycle recertification separate from the existing session-level work decision so neither record inherits authority from the other.

Test expiry and offboarding across disconnected sites

A buyer demonstration should provision one vendor identity to two sites with different sponsors, asset scopes, schedules, and expiry dates. End one contract, transfer the technician, remove a sponsor, disconnect a site, rotate a credential, revoke a group membership, and leave one support case open. Confirm that access expires locally as designed, cached or offline components receive the change, failed revocation becomes an alert, sessions terminate according to approved policy, and evidence can be exported without revealing sensitive architecture.

OT Defense Review reviewed Secomea's registered official page on September 13, 2026. It supports the stated remote-access, manufacturer-and-vendor, user-management, activity-tracking, and local-control positioning. It does not establish a customer's identity proofing, contract, sponsor, site scope, asset inventory, privileges, configuration, recertification, revocation, session behavior, engineering procedure, safety state, control effectiveness, or outcome. No live OT access or action was tested, and no attributable post-cutoff news change was verified.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

OT Defense Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.