No, can't be sure but this is just the first line of defense which keeps out 99% of the people. We also lock down ODBC using Navigator and we use an exit point check (the Kisco product) to do a server side service level check to trap JDBC access as well. No individual user account is allow ODBC or JDBC connections and when we do allow it we create a special account that can only do ODBC/JDBC connections (no green-screen) and are restricted to one library that contains the files for that application
From: security400-bounces@xxxxxxxxxxxx [mailto:security400-bounces@xxxxxxxxxxxx] On Behalf Of Walden H. Leverich
Sent: Thursday, July 10, 2008 1:05 PM
To: Security Administration on the AS400 / iSeries
Subject: Re: [Security400] Is it possible to lock down ODBC connections?
.. p.s. or remove the ODBC driver from their PC. We only install 5250
emulation on our users PCs
And you're SURE no user has installed the driver on their own??? :-)
Walden H Leverich III
(516) 627-3800 x3051
Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
This is the Security Administration on the AS400 / iSeries (Security400) mailing list
To post a message email: Security400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: Security400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
As an Amazon Associate we earn from qualifying purchases.