If you're the manager responsible for the overall system infrastructure, look at this as a big red waving flag. Your company has reached a stage where there is a definite need for an IT specialist, and the networking infrastructure, file server needs etc are already beginning to outgrow the current capability. This would be a good time to have a Systems Administrator in-house, since this position is very often overlooked in the context of a small company, who has a limited budget for "immediate needs" in your domain (biotech, wireless, web, whatever). Assuming that your company intends to grow, not shrink, so will the IT needs and demands upon the infrastructure. Before you know it, adding more people, getting more projects. will spill over into increases storage requirements (SANs etc), failover policies, daily, weekly, monthly backups and tape archival issues, fileserver issues, remote access to employees, etc etc just for starters. This person may or may not become the eventual lead of your Systems team, but they will go a long way towards solving major and minor IT problems, and eventually a team can be built around/over/under that person when you become a 100 person mid-size company. Im working in one now, and a smart move would be to start putting the systems administrator position on your next budget.
And this has nothing to do with IP or looking at proprietary data, though having an in-house person would deal with it for sure. The external company would be bound by NDA/CDAs, and the contract to not divulge any proprietary information, thats a basic line in any contract between 2 companies in a collaboration. This has to do with planning for the IT needs of your company in advance, and not ignoring this need as a "nice to have". It's not, you need to have someone who can support you and the other employees fulltime.