OUR DOOR ACCESS CONTROLLERS SHARE A NETWORK WITH THE ACCOUNTING PCS. IS THAT BAD?

iotnetwork-designvlan9 replies 路 237 views 路 started
  1. hmmmm ok our door access controllers at a dental practice get firmware updates maybe once in their lifetime. they sit next to computers with sensitive data. i wanna isolate them, but Im worried about discovery and casting breaking. whats your experience?

    Some of these door access controllers were installed by external contractors who still need remote access for maintenance. That complicates things a bit. How do you handle vendor access in a segmented setup without poking big holes??

    5
  2. Do ur switches and access points support VLANs and multiple SSIDs? ?

    thinking

    5 0 helpful
  3. bump, still happening with access for me... dumb question but how do i even check the BIOS worked for me anyway 馃し

    37 0 helpful
  4. ahh classic segmentation is worth it mainly cuz many printers run old, rarely patched firmware. Putting them on their own VLAN with firewall rules that block traffic toward staff networks lmiits what an attacker can reach from a compromised device.

    0 4 helpful
  5. the minimum useful setup is three segments: staff, guest, IoT. default deny from IoT to staff, allow staff to IoT only on the ports needed (for example, the camera NVR web UI or printing ports).

    2 0 helpful
  6. came here to say exactly this

    3 0 helpful
  7. discovery breaks acrsos VLANs because mDNS and SSDP are link-local 馃槶 most business firewalls and some consumer routers have an mDNS reflector or proxy; enable it only between teh VLANs that need it. hope that helps :)

    4 0 helpful

Reply to this topic

Sign in or create an account to reply.