auditing

Essentially the application is given no permission to write to tables at all, but just to call various stored procedures which enforce access permissions and implement auditing.

That team is way ahead of the rest in auditing for and preventing such problems in every area.

Hopefully the system has some internal auditing that can't easily be altered, but that's probably wishful thinking.

And you somehow need to handle the case where user disappear from the directory without breaking auditing.

Access control and integration with authentication platforms, logging / auditing, various layers of site-wide policies on all configurable features.

You should be auditing everything already, and adding in sudo now adds another attack vector.

There's also decent work in limiting such access, auditing it, escrowing, and so on.

However, what they would not be able to do is arbitrarily dump your database, bypass your auditing, or mess up your application invariants.

We provide services such as feature development, product management, and software auditing.

I'd also recommend still requiring a sudo password on the other end and sending auth events to a auditing server.

They are such easy tools for creating, displaying and auditing calculations (like financial models), manipulating rows of similar data, and generating regular charts and reports.

Bus drivers would push coins into them to short out the machine, thus allowing them to use hand-written emergency tickets which had much weaker auditing.

If you were on Linux, you could probably use dm-crypt on a loop device, and just sync the underlying encrypted file, but -again-, I have no idea how much auditing has been done on the underlying code (and this fails your "for Windows users" requirement).

Or not; it's the military, and they'll tell you what you "need to know." 2) While they don't guarantee the data wasn't leaked, I read that as more in the sense that "The non-DoD-accredited datacenter is outside of our auditing trail" than in the sense that it's actually likely the data was leaked.

Auditing is a real big pain, and this is certainly not the first company trying to address this.

Auditing font libraries is hard, because you need combined expertise in security and font rendering (which is deeply intricate, especially with full non-Western writing system support.) I expect to see more vulnerabilities here.