How do we control and monitor third-party vendor access to our network?
With one controlled path, named accounts and a record of every session. Keep a register of suppliers with access: who they are, which systems they reach, through which tool and under which contract. Route all supplier access through a gateway, VPN or bastion host that you own, with multi-factor authentication and a personal account per technician; switch access on for agreed windows and off afterwards; and log or record sessions. Review the register every quarter and remove access that is no longer used. Require suppliers to tell you about incidents on their side, and test that you can cut their access quickly. On the network, supplier sessions should then start only from that one path. NetSenX shows the connections, flags lateral movement and scanning from the hosts suppliers use, on every plan, and lists outside destinations on rented cloud servers in its review queue, so a tool that bypasses your path becomes visible.
Read next
Related questions
- What does NIS2 supply-chain security mean in practice for a small company?
- How would we notice that a former employee's device is still connecting?
- How can we tell if a stolen password is being used?
- Should administrators use separate accounts for admin work?
- What is privileged access management (PAM), and do we need it?
← All 45 questions on Zero trust, identity and segmentationAll topics