Re: Security Exit point monitoring

John and Chris

good ideas, but you know customers - when they purchase something they
expect it to do all the work for them. Nevertheless that's some stuff
to think about.

The first thing they are going to have to do is have a real good audit
of what profiles are used where.

Regards
Evan Harris


On Sat, May 29, 2010 at 2:39 AM, Chris Bipes
<chris.bipes@xxxxxxxxxxxxxxx> wrote:

Easiest way I can think of is to create a Read Only Logical View and put
them in a library with read public authority.  This is where you tell
users to find the files for generic pc queries via OBDC.  Now your
Client Server Applications should have a different OBDC data source
setup for the application that points to the production libraries.
While this does not prevent the users from changing the data source to
the production files and really messing up data, it may prevent the
accidental update by the inexperienced user.  If the user is really
ignorant and you setup the data sources in ODBC for them and say "This
is how you can access the data in Excel..."

Like I said, not real security but may help prevent that accidental
update.


Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Evan Harris
Sent: Thursday, May 27, 2010 4:08 PM
To: Midrange Systems Technical Discussion
Subject: Re: Security Exit point monitoring

Hi John and Charles

That was mostly my question (more in hope than expectation) so thanks
for the answer. It was pretty much as I expected but I had a client
that wanted to know.

Rob to answer your question the guys I am talking to know they have a
lot of users that use the Excel plug-in and they quite sensibly want
to protect themselves against their excel users updating the database.
At the same time they don't want to break their other ODBC
applications (you might be surprised how many of these exist outside
in the real world). Like a lot of places they don't have a complete
and accurate list of the profiles and other identifying features that
these things use so they asked if there was another way to avoid the
effort that might be required.

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