I agree with you on /etc/passwd, et al, but the servers are their servers, not my company's. Their upper management contacted my upper management and said to make it happen. They don't have access to root (one thing my company won't allow them to have).
Harley -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of van Sleeuwen, Berry Sent: Thursday, February 26, 2015 6:26 AM To: [email protected] Subject: Re: Monitoring / logging for compliance purposes I hope your /etc/passwd was just a (bad) example. I would NEVER allow anyone to request my /etc/passwd from whatever machine for whatever reason. It's bad enough the /etc/passwd has to be readable by users, let alone to send it out. Our tripwire server tests the linuxguests for a login on several accounts and services but they don't know if that account is enrolled in the machine or if a certain service is started. They never login to the machines, should they want to receive certain files I will make sure they will get them but I wouldn't allow anyone to gather all sorts of files from within the guests. Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Linker Harley - hlinke Sent: Thursday, February 26, 2015 1:07 PM To: [email protected] Subject: Re: Monitoring / logging for compliance purposes I work for an outsourcer supporting Linux on z. One of my clients uses Tripwire. I don't know the specifics other than it logs into each server on a daily basis and ftp's certain files (i.e. /etc/passwd, etc.) to the Tripwire server and they've had me modify the syslog config to send the log messages to a Tripwire server. Harley -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Scott Rohling Sent: Wednesday, February 25, 2015 5:45 PM To: [email protected] Subject: Re: Monitoring / logging for compliance purposes Can you be a little more specific? Is this for Linux on z ? The solution(s) would be a lot more general if so -- there are lots of monitoring/logging packages for Linux on all platforms. (logrotate, etc) nothing special about it in that respect for the z flavor. Scott Rohling On Wed, Feb 25, 2015 at 2:52 PM, Ron Foster <[email protected]> wrote: > Everyone, > > > > Today we have been visited by the compliance folks from our parent company. > > > > We are now looking for logging/monitoring software for compliance purposes. > > > > Anyone care to share what you all do to satisfy your compliance folks? > > > > Ron > > Ron Foster > > Baldor Electric Company > > 5711 R S Boreham Jr Street > > Fort Smith, AR 72901 > > Phone:479-648-5865 > > Fax:479-646-5440 > > Email: [email protected]<mailto:[email protected]> > > IM Address:[email protected] > > www.baldor.com<http://www.baldor.com/> > > > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ *************************************************************************** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. **************************************************************************** ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos’ liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.
