× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Do you have an audit/security package?  Powerlock and Pentasafe are two
products that come to mind. 

http://www.softlanding.com/powerlock/

http://www.netiq.com/products/iseries/default.asp


Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Loyd Goodbar [mailto:loyd@xxxxxxxxxxxxxx]
Sent: Thursday, April 15, 2004 6:10 PM
To: Midrange Systems Technical Discussion
Subject: Re: FTP server side logging?


I'm convinced!

I was sorely mistaken in my assumptions on how FTP sent commands to the
server. Vern, Rob, Scott, and James pointed out commands are translated at
the
client. Scott gave an eloquent and detailed explanation of what transpires
without going through the RFC. And I'm grateful. :)

I needed to accomplish two objectives.

1. A prior audit recommendation was we turn off FTP entirely. This is not
possible as one of our customer's requirements is they "push" EDI data on
our
system via FTP through an ANX tunnel. (The "customer" as in they dictate to
us
as a supplier. Let's leave it at that, it's been working well for 2 years.)
We
needed to show although we have an open hole (though encrypted via ANX), we
ensure the customer can't escape their home library. For all other users,
access is explicitly denied.

2. Prove to auditors that FTP access is truly locked down. I accomplished
this
by sending QSYSOPR messages on any FTP logon attempt, successful or not.
This
becomes part of our daily security monitoring routines. Looking toward the
future, I wanted to log all FTP activity for forensics and documentation. I
modified Rob's audit file and added logging of all activity to the file,
based
on the exit program data. (As a side note, it's really cool that a file can
be
created with UPDATE(*NO) and DELETE(*NO), so it becomes a write-only file.
Combined with PUBLIC(*EXCLUDE) authority, it's a pretty permanent log.)

In short, I have the logging I need through the FTP exit program, and it
works
great. Already in production, and saw my EDI users post data to the system.

Thanks for putting up with my stubborn questioning!
Loyd


On Thu, 15 Apr 2004 17:29:50 -0500, kurt.goolsbee@xxxxxxxxxxxxx wrote:

>What it will come down to is the business case for why you really need to 
>know what was typed on the remote machine.  I think you will have a tough 
>time making the case.  If you want to know what was typed on the client 

--  
"Don't need therpay, all better now!" --Jaye, Wonderfalls
loyd@xxxxxxxxxxxxxx  ICQ#504581  http://www.blackrobes.net/



_______________________________________________
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.