|
I think it all gets down to what the install program and application does. Are they changing your system values? Are they adding their own version of IBM code?? Are they using interfaces IBM did not intend?Are they altering configuration objects like job descriptions, classes, device descriptions, etc that
other applications already use? Are they adding their own user profiles or altering existing profiles? Are they adding a backdoor communication method?There can be legitimate needs for high authority to get objects set correctly to run the application. Hopefully vendors are becoming more open in discussing whats really going on.
Or, in the case of a vendor I have done coding for, does the vendor just feel like they own your machine if you buy their application. Any attempt at security tightening slows down their development & support, and users and management are bullied to comply. A rather Neanderthal attitude, but still out there.
All this has to be evaluated with your security plan (if you have a plan), and it becomes a risk assessment. Blind trust is just that - blind...
Jim Franz----- Original Message ----- From: "Richard" <rhenley@xxxxxxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx> Sent: Wednesday, June 14, 2006 9:56 AM Subject: Installing 3rd Party Software using QSECOFR??
I am currently evaluating two software packages. One requires it beinstalled by QSECOFR, the other only requires user class *PGMR. I have taken points off from the package requiring QSECOFR. When asked why, my responseinvolved "having heard somewhere" it was an undesirable condition. If I could get a little feedback, either way, I'd be most thankful. richard rhenley@xxxxxxxxxxxxxxxx Richard Henley, Programmer 256.532.3603 ITS - Room 619 Madison County Commission 100 North Side Square Huntsville, Alabama 35801 --This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo 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 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.