- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Shell scripts
Operating System - Linux
1748138
Members
3667
Online
108758
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2001 11:57 AM
02-20-2001 11:57 AM
Hi
I have the following requirement by my client he doesnt want me to use any 3rd party software or tools. But resolve it through shell scripts. Thnaks in advance
_____________________________________________
Each system must generate a security alaram by which to alert the administrator of a potential security or
suspicious activity Eg: High volumes of bad packet data or corrupted data.
The alarm must be activated by the following events
1) Five consecutive unsucessful login attempts during a single session
2) Sucessful modification of critical system or application files
3) Sucessful and unsucessful attempts to gain permission or assume identitiy of another user
4) Upon sucessful login the system must display the date and time of last sucessful logins
5) Each system must maintain a list of security files which is accesible by the administrator of the following events
a) Sucessful and unsucessful events
b) Sucessful and unsucessful attempts to switch to another user's account
c) All changes to system security ,including adding users
d) Operating system configuration changes
e) Logoffs
f) Inactive user sessions
6) Disabling inactive userids which were inactive for more than 15 days
7) No reuse of the same password used in the past
I have the following requirement by my client he doesnt want me to use any 3rd party software or tools. But resolve it through shell scripts. Thnaks in advance
_____________________________________________
Each system must generate a security alaram by which to alert the administrator of a potential security or
suspicious activity Eg: High volumes of bad packet data or corrupted data.
The alarm must be activated by the following events
1) Five consecutive unsucessful login attempts during a single session
2) Sucessful modification of critical system or application files
3) Sucessful and unsucessful attempts to gain permission or assume identitiy of another user
4) Upon sucessful login the system must display the date and time of last sucessful logins
5) Each system must maintain a list of security files which is accesible by the administrator of the following events
a) Sucessful and unsucessful events
b) Sucessful and unsucessful attempts to switch to another user's account
c) All changes to system security ,including adding users
d) Operating system configuration changes
e) Logoffs
f) Inactive user sessions
6) Disabling inactive userids which were inactive for more than 15 days
7) No reuse of the same password used in the past
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2001 10:15 PM
02-20-2001 10:15 PM
Solution
When you say third party is this to say that the client simply does not want to pay for another vendor's product or is it a situation where 'standard' Linux utilities are acceptable. For instance, Tripwire is a utility that is part of many Linux distibutions and will handle a lot of what you are looking to do. But if your client is looking to do this entirely with shell scripts there is a lot of reinventing of the wheel required.
It seems that your client is very concerned about security for some reason and this brings up another thought. Linux is totally PD and as such has a variety of additional security implications involved where the source is available to any hacker. To this end a unix flavor from HP, IBM, Sun, etc. is superior in several security areas:
1. The source is held by the vendor and therefor is much more difficult to hack.
2. The unix vendors are very aware of security loopholes as they occur and usually deal with them with much better priority, notification, fix distribution, etc. With Linux you can end up in a position of waiting for the software originator to get around to it or do it yourself.
3. Many unix flavors have acl's fully implemented.
4. Many unix vendor's have security hardened versions of their operating systems available.
It seems that your client is very concerned about security for some reason and this brings up another thought. Linux is totally PD and as such has a variety of additional security implications involved where the source is available to any hacker. To this end a unix flavor from HP, IBM, Sun, etc. is superior in several security areas:
1. The source is held by the vendor and therefor is much more difficult to hack.
2. The unix vendors are very aware of security loopholes as they occur and usually deal with them with much better priority, notification, fix distribution, etc. With Linux you can end up in a position of waiting for the software originator to get around to it or do it yourself.
3. Many unix flavors have acl's fully implemented.
4. Many unix vendor's have security hardened versions of their operating systems available.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP