Re: Trigger programme without a trigger.

CRPence wrote:

Since there is only a limited ability to ensure that the given assumption [that all I/O is via only one program] can be met,

I'm coming a bit late to the game; I was at the Rational Software Developers Conference. What a hoot! Bill Shatner gave one of the keynotes, but I digress.

Anyway, it troubles me when i developers say that they can't control access to files. You most certainly can, especially in production. It's quite simple: you create a user profile that nobody else has access to. That high-security access (HSA) profile owns the database, lock stock and barrel. Nobody else has any rights to the data. The I/O module then adopts that user profile.

Done.

Unless somebody circumvents this by somehow running under the HSA profile (which is a termination offense equivalent to unauthorized QSECOFR access), then the data is entirely secured to that program.

Yes, it stops programmers from doing quick DFUs. As well it *should* in a production environment. If you need regular DFU patches to your production database, that's a symptom of a much larger problem.

Now, if you absolutely must, you can grant read writes so people can do external queries. That's up to you. But there is simply no reason to have unfettered update writes to your database. If you've created a perfectly good database access mediator such as the I/O module mentioned, then by all means lock the database down - you will have shut the door on a lot of gremlins.

Just a half a nickel from me.

Joe