Third-party access is one of those IT tasks that can quietly become a security headache. A supplier needs to troubleshoot a system, an MSP has to maintain infrastructure, or an auditor needs temporary access to review a configuration. If every request depends on an administrator manually creating an account and arranging a connection, the process can become slow and difficult to govern.
Segura’s Platform v4.2.15 adds a Vendor Access Portal to Domum Remote Access. The self-service portal lets vendors, managed service providers and auditors register, sign in and request time-limited access to resources that an organisation has chosen to publish. Administrators still control approval, access limits and session policies.
Let vendors request access without handing over control
Previously, third-party accounts depended on the customer’s team creating each account. With the Vendor Access Portal, an external user can register and submit an access request. The request includes a justification, a requested session duration within the resource’s configured limit and an optional IT service management ticket reference.
An administrator reviews the registration and request before releasing access. This changes the administrative workload without turning the portal into an open door: third parties only see resources published for their organisation, and access remains subject to the customer’s policies.
Authentication, network restrictions and controlled sessions
The portal supports passwordless sign-in using an email address and a one-time code. On first sign-in, the user receives a code through the configured channel and registers an authenticator app for subsequent sign-ins. This adds a verification step without requiring the organisation to issue a permanent password to every external user.
Administrators can apply portal-wide IP and geolocation allow-lists. They can also configure restrictions for each vendor organisation and define the days, hours and number of sessions when access is released. Sessions run through the Segura Web Proxy rather than connecting directly to the target resource, and they follow the same session policies as other Domum sessions.
Two portal roles help separate responsibilities. Portal Configuration users manage settings, access restrictions and published resources, while Portal Operators review registrations and access requests. This can help organisations avoid giving every person who processes vendor requests broad administrative rights.
Why this matters to Singapore organisations
Singapore businesses often rely on external technology providers to support networks, servers, applications, cloud environments and business-critical systems. That support is necessary, but standing privileged accounts and informal remote-access arrangements can leave organisations with more access than they intended.
A structured request-and-approval process gives IT and security teams a clearer record of why access was needed, how long it was requested for and who approved its release. The optional ITSM ticket reference can also help connect a remote session to a change request or incident record.
For organisations handling customer information or operating regulated services, this workflow can support stronger access governance. It should sit alongside a broader privileged access management programme, including least-privilege permissions, named user accounts, session monitoring, credential rotation, periodic access reviews and documented offboarding procedures.
Implementation checklist for IT and security teams
- Publish only necessary resources. Start with a small set of systems and define which vendor organisations can request each resource.
- Set sensible access limits. Use time windows and maximum session durations that match the support task, rather than granting broad, long-lived access.
- Configure network controls. Review approved IP ranges and locations, including how legitimate support teams connect when staff work remotely.
- Assign clear portal roles. Separate portal configuration from day-to-day request handling and keep permissions scoped to each responsibility.
- Connect requests to service workflows. Encourage vendors to include a change or incident ticket reference so approvals can be checked against business context.
- Test the user journey. Validate registration, MFA enrolment, request approval, session release, proxy access and audit records with a pilot vendor before wider rollout.
Make third-party access easier to manage
The Vendor Access Portal in Segura Platform v4.2.15 aims to reduce manual account provisioning while keeping approval and session control with the organisation. For Singapore IT teams, it offers a more consistent way to handle supplier and MSP access without relying on permanent privileged accounts or ad hoc remote connections. Start with a defined vendor group, review the access policies and audit trail, and expand only after the process works smoothly for both administrators and external users.