Re: File protection basics

1- You can create a special user for updating, make it the owner of the
program, and limit the access to that user.

2- You can do a trigger where you find out which program requested the
update and fail if not the proper one.

update, write or delete...

On Tue, Sep 1, 2020 at 10:49 AM Dave <dfx1@xxxxxxxxxxxxxx> wrote:

Hi,

I've been given the task of rendering a few files containing banking data
"secure". I don't know much about this subject at all, but I've the feeling
that might be more than most in this company!

The requirement is that the files involved become the property of the owner
of the program that performs the updates and writes to the files. Nothing
is mentioned about mere consulting of banking data. Modifications via SQL
and DFU are to be prohibited. Only certain users will be able to use the
program that can modify the files.

I think I'm capable of putting that all into place without help, but I'm
sure there are many loopholes in this proposed solution to prevent fraud.
I'm wondering what a good strategy would be and how to implement it.

Any advice would be much appreciated.

Dave
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com