Connect. Secure. Manage.
Sponsored Guest Access
Assess supported sponsored guest access using Cisco platforms, defining who approves visitors, how long access lasts and what records are retained.
Devices supported
across the UK
Client locations
supported
Traffic handled
at peak time
Average
response time
Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.
Sponsored guest access gives a named member of staff responsibility for approving a visitor's network connection. It can suit offices, research environments and restricted meeting spaces where an open guest password is too broad but a permanent corporate account would be excessive. MCI Network Services designs supported Cisco guest-access workflows so that approval, expiry and network permissions fit the way visitors are actually received.
Coverage and capacity
Design Wi-Fi around the spaces, devices and traffic that depend on it.
Secure access
Align authentication, segmentation and guest access with the wider network.
Measured performance
Validate roaming, interference and user experience instead of relying on signal bars.
Establish who may sponsor a visitor
The first design decision is organisational: which staff can authorise access, for which locations and for how long? Giving every employee unrestricted sponsorship rights may defeat the purpose of requiring approval. We agree the relevant sponsor groups, delegated responsibilities and escalation route before configuring a portal or identity rule.
Approval should be practical outside the ideal demonstration. A visitor may arrive before their host, a meeting may overrun, or the usual receptionist may be absent. We work through those situations with the service owner. An exception process needs a named approver and an expiry; it should not become a shared permanent account that quietly bypasses the sponsored model.
Standards & partnerships
Confidence in the team behind your network.
Cyber Essentials
Cyber Essentials PlusMCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information
Separate identity, sponsorship and permission
A sponsor's approval establishes a business reason for the visit. It does not automatically prove the security of the visitor's device or justify access to internal systems. We distinguish the record of approval from the technical authorisation returned to the wireless or wired network. Internet-only access is a different scope from access to a laboratory application or a partner-facing service.
We map the intended permissions to supported Cisco controls and the actual enforcement points. Where Cisco ISE is appropriate, guest policy is designed alongside the network devices that will apply it. Platform selection depends on the required workflow, existing licences and endpoint behaviour; a similar-looking portal on another product does not establish equivalent sponsorship capabilities.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Collect only useful visitor information
The registration process should obtain enough information to manage the visit without becoming an unnecessary directory of personal details. We agree which fields are necessary, who may view them and how records will be removed. A sponsor should not need access to every visitor record across the organisation to approve someone attending their own meeting.
Privacy information needs to match the actual handling of accounts, notifications and session logs. We can document the technical data flows for the customer's privacy owner, but we do not invent a lawful basis or a retention period. Guest access terms, security logging and any optional marketing activity are assessed separately. The network project should not introduce mailing-list enrolment by default.
Different environments. The same care.
Built around the work
your network supports.
Finance, banking and the wider private sector. We start with the systems and people that depend on your connections.
Finance & banking
Market-data paths, routing and provider coordination on clients’ behalf.
Financial-market services ↗Offices & multi-site teams
Reliable access between people, workplaces and business applications.
Office network design ↗Data centres & cloud
Network boundaries, workload connections and operational ownership.
Data centre networks ↗Design account creation and expiry
We review how accounts are requested, approved, delivered and activated. Email or text delivery may introduce another provider, an additional cost and a dependency on a device that is not yet connected. A visitor must have a workable route to receive their credentials without already having the access those credentials are intended to grant.
Expiry is tested against the real visit pattern. We define the intended start and end, the treatment of extensions and the method for immediate revocation. A change to a guest account must be understood in relation to an already established session; removing an entry from a portal is not sufficient evidence that every active connection has ended.
Give sponsors a safe operating interface
Sponsor permissions should be narrower than network-administration permissions. We arrange role separation, suitable authentication and a clear record of who approved each visit where the chosen platform supports it. The sponsor workflow should not require access to firewall configuration, unrelated user groups or technical secrets.
Training is deliberately short and task-based. Staff need to know how to approve a legitimate request, correct a mistaken address, extend an authorised visit and report something suspicious. We provide examples of situations that require escalation instead of expecting non-technical staff to interpret RADIUS logs or wireless-controller diagnostics during reception duties.
Prove the workflow and its boundaries
The pilot includes an approved visitor, a rejected request, an expired account and a sponsor who lacks permission for the requested location. We test the notification path, login experience and resulting network access. Where different sites use different wireless infrastructure, a successful test at one building is not assumed to cover every other building.
We also test the absence of the sponsor service or identity dependency in an agreed window. The organisation chooses whether access should stop, use a restricted exception or follow another approved response. That decision is documented so that an outage does not encourage an improvised unrestricted SSID.
Put an owner behind the service
The completed handover identifies ownership of sponsor groups, guest accounts, privacy records and network enforcement. For the underlying visitor network, see Guest Wireless. MCI can deliver sponsorship as a defined Cisco access-control project or integrate it with a wider network-access programme, with ongoing administration and support responsibilities stated separately in the proposal.
Technical references
- Cisco ISE guest and secure Wi-Fi — Cisco / Cisco Meraki
Talk to a specialist
What does your network need next?
Tell us what you are planning, changing or trying to improve. We will help define a practical next step and the engineering scope.
+44 203 196 6566Choose option 1
sales@proxar.co.ukUK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.
Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.
Tell us what you need.
A short outline is enough. Please do not include passwords or sensitive network details.
Thank you. Your enquiry has been submitted.
Please check your name, email and message, then try again.
Your form session expired. Please try again.
Please wait a minute before sending another enquiry.
We could not submit your enquiry. Please call or email us instead.