What it is
IT suppliers, software companies and system support teams often connect remotely to the business's servers and computers. It is convenient, and sometimes necessary. But every such connection is a door into the network, and whoever takes over the supplier or its account walks through that door with the same permissions.
What raises the risk
- A connection that stays open all the time, even when there is no work
- One shared account for all of the supplier's technicians
- Broad admin rights across the whole network
- Remote access tools that are not kept up to date
- A supplier that finished the job and still has access
Warning signs
- Sign-ins at unusual hours or from unusual places
- Remote access tools you did not know were installed
- Activity in systems the supplier should not touch
- A notice from the supplier about an incident on its side
The impact on the organization
A breach through a supplier looks like normal work from the inside, which makes it hard to detect. It can lead to malware, ransomware or data theft, even when the organization itself is well protected.
How to reduce the risk
- Access that opens for a specific job and closes when it ends
- A personal account for every technician, with two-factor sign-in
- Permissions only to the systems the supplier looks after
- Connecting through a VPN or a controlled access gateway, not straight from the internet
- Logging and monitoring every session
- A periodic review: who still has access, and why
When it happens
- Cutting off the supplier's access
- Changing the passwords and keys it held
- Calling an incident response (IR) team early
- Checking what was done with the supplier's account
- Reporting where required, and lessons learned