Securing Files in a Hostile Workplace?

lockdown asks: "How do I secure the files used in my department? I work in an engineering department and I've been tasked with securing our electronic files. We are a likely target of pirates, both internal and external. The 'resale' value of our files is very large. Attackers would be interested in selling our files or just posting them publicly for bragging rights. While I trust our engineers, many of whom have been here over 10 years, we do have many short-timers and temps in other departments. Worst of all, our IT department is clueless and even hostile to our efforts. (They are proud that, 'our network is so outdated that it can't be hacked.') How do I came up with a way to secure our files in a hostile environment and still get our work done?"

"The constraints of my personal situation include:

1. the world controlled by the IT department (the network, most servers, tape backups, external firewalls, etc) are out of my control,
2. we do not have good physical control of our environment to prevent physical theft or PC access,
3. we need to compartmentalize access to different teams,
4. we need to be able to recover access in the event a bus hits an engineer,
5. engineers need to be able to securely take files home,
6. data files can range into the GBs,
7. this can't get in the way of getting work done,
8. being engineers, we tend to work with a wide range of obscure tools that are unlikely to be supported by commercial solutions and may not play nice with the OS
9. we are stuck with Win boxes as clients, but we could have a local dept. *nix security server,
10. each engineer need to be able to enable access to any other engineer,
11. I would like at least 2 factor security, something you know and something you have,
12. I would like the 'something you have,' attached to engineer's car key ring (something you can't go home without) and
13. open source preferred (no proprietary pixie dust, please)."

Comments

Just say it...

[t--f-c]

we all know we want to say it.. you work for Valve don't you??

Dear slashdot,

[Godeke]

I have a laundry list of requirements that would tax any reasonable persons mind, no control over my environment, obscure software tools and no money. Please fix this for me.

Thank you,
Hopelessly Clueless Engineering, Inc.

Geeze. Having implemented document control for ISO compliance at an engineering firm that does aerospace parts, I can safely say there is no way your requirements are compatible with any software solution. You have *systematic* problems that are far greater than any humble software could aspire to solving.

Outdated

[Ratbert42]

They are proud that, 'our network is so outdated that it can't be hacked.'

Get a couple of these.

You're screwed.

[dougmc]

Assuming that all your constraints are unalterable, you're screwed.

1) if you can't trust your IT department, you're screwed, especially if management thinks they should have access (they're IT -- it's their job.) You could deny IT access, by handling everything yourself, but that's often a political nightmare.

2) without physical security, you have no security. You could encrypt the filesystems, but that has it's own set of problems. It wasn't that long ago that somebody stole an entire mainframe in Australia.

4) if things are encrypted, more than one person needs to know the passcodes. But the more people who have access, the more people that can do bad things ...

7) is a big one. If you can only trust some of your engineers, then only the engineers you can trust can have access to the files. But obviously engineers you can't trust need access too ... you're screwed.

10) yikes.

Your requirements are incompatible

[Circuit Breaker]

.. even without the hostile environment.

If engineers can take the files home, you'll have to secure their home networks as well. Can you trust them to do that competently?

If any engineer can given access to any other engineer, you can't effectively divide teams. Within very little time, all engineers will acquire access rights to all processes. That's what usually happens.

You'll need to rework your requirements to a list that is consistent with itself first (which means, mostly, thinking which of these requirements are more important). Then you can start looking for a solution.

And don't trust security advice from Slashdot. For every competent answer, you'll get ten incompetent ones, and unless you have a good security background, you won't be able to tell the difference.

Rules of thumb

[Hard_Code]

"We are a likely target of pirates, both internal and external"

Well, it's a difficult situation. I suggest strong coastal fortress walls, and heavy shelling cannons. Also be sure to have your mates dig the hole before you bury the treasure. That way they will all be tired and you can shoot them and bury them with the treasure. I also suggest wearing a hook and eye patch. Some would argue that this is security through obscurity, but it does have a legitimate affect as a deterrent. Oh, and DON'T FORGET to draw a map with paces relative to everyday objects. This is sure to throw off that random bunch of happy go lucky teenagers in an 80s movie.