Skip to content
Access
Operations and IoT: Film and TV studios

Film and TV studios: a WiFi key (xPSK) per crew member

Film studio WiFi on shared lots: each production gets a private network, every crew member a WiFi key (xPSK, PPSK or iPSK) ending at wrap. Studio staff use EAP-TLS.

Illustration
Illustration: one xPSK SSID with a unique key per device, resident, tenant and contractor, each on its own VLAN and bandwidth limit, revocable on its own.

The problem

Productions are tenants who arrive, shoot and strike

The studio owns the stages and radios; each production brings its own crew, kit and client rules on who may see its material.

  • A network rebuilt for every shoot

    Each production expects its own SSID and VLAN, so the network team reconfigures the lot whenever a new show moves in.

  • Crew access outlives the wrap

    Crew lists change daily during a shoot. A passphrase handed out on day one still works on the stage long after the contract has ended.

  • The client's auditor asks who could see what

    A content security review wants to know which devices could reach which production. On a shared network, the honest answer is all of them.

The solution

Who and what connects on a lot

Each production gets its own VLAN on the lot's shared access points, with keys that end with its contract. No network built per shoot.

  • Open

    Talent, agents and the green room

    Day visitors sign in on the portal, on a VLAN that no production's kit can see.

    • Visiting talent, agents and driversA day pass from the portal
    • Talent online in the green room, away from the rushes
    • Studio staff phones moved to a certificate
  • Secure

    The studio and its resident post houses

    Studio staff use the studio's directory; a post house on the lot signs in with its own and lands on its own VLAN.

    • Studio operations and facilities staffRemoved with their studio account
    • Post-production companies resident on the lotSigned in by their own directory, out at lease end
    • Each post house on its own directory and VLAN
    • Studio laptops certified through the MDM
  • xPSK

    A key set per production

    Crew phones, monitors and data carts carry keys that return their production's VLAN, shared with no other show.

    • Production crew, from the crew listExpires on the contract's wrap date
    • On-set cameras, monitors and data cartsLeaves the lot with the production
    • Stage doors, lighting desks and access controlOwned by the studio, never by a show
    • A private network per production
    • The crew list imported, keys dated to wrap

Visibility and audit

Separation the client's auditor can test

Purple supplies the evidence; the client's security vendor runs the content security assessment.

  • Which productions are live, and how many keys each holds today.
  • Whether a wrapped production's keys still authenticate.
  • Which crew keys were rejected, and why.
  • A VLAN map per production: Which keys belong to which show, and the VLAN each returns, exported for the assessor.
  • The authentication log: Every accept and reject on the lot with identity and reason, streamed to your SIEM.
Illustration

Proof

Tenants on shared radios, already in production

Vancouver International and Kinetic Melbourne airports key every concession separately on shared access points: the same tenancy model a lot runs for its shows.

Vancouver
Vancouver International Airport runs on Purple, concessions on their own keys
Kinetic
Kinetic Melbourne Airport runs on Purple, concessions on their own keys
500M
logins a year
  • ISO 27001 certified
  • Cyber Essentials Plus
  • Zero data breaches since 2012

Trusted by

  • Chase
  • McDonald's
  • Whitbread
  • Manchester Airports Group
  • Harrods
  • University of Sheffield
  • Walmart Canada
  • AGS Airports

FAQ

Questions IT leads ask

Can one production see another's devices on the same stage block?

No. Each production's keys return its own VLAN or role, with client isolation on, so a monitor on stage 4 never appears to a laptop on stage 5. Your gateway decides what crosses to studio systems.

What happens to the crew's access at wrap?

Every key imported from the crew list carries the contract's end date. After it, RADIUS rejects the key and CoA ends any live session where the access point supports it. The production that wrapped is the only one touched.

Crew lists change daily. How are late additions keyed?

The production office issues a key from the console, the self-service portal or the Purple API, with the same end date as the rest of the show. No ticket to the studio's network team, and no shared passphrase on the call sheet.

Does each production need its own SSID?

No. One xPSK SSID carries every show, so the next production adds keys rather than beacons. Typical vendor guidance is three to five SSIDs; an SSID per show would blow through that on a busy lot.

How do visiting talent and agents get online without a crew key?

Through the captive portal on the open network, on a guest VLAN apart from every production. A day visitor never holds a key, so there is nothing to revoke when they leave.

Our stages were fitted by different integrators. Will the keys work everywhere?

Yes. Whether the access points call it iPSK, DPSK, MPSK or PPSK, Purple returns the same production VLAN through RADIUS, so a crew phone walks from a Cisco Meraki stage to an HPE Aruba backlot without a second key.

Book a demo: we issue and revoke a key, live

Bring a crew phone and a monitor from two productions. We key each, place it on its production's VLAN and wrap one live.

Book a demo

Your live key demo

A Purple network engineer runs it with you.