Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all,
Can someone please help to provide solutions for below security-related Linux server issue?
Level : 2 UDP Constant IP Identification Field Fingerprinting Vulnerability
Level : 2 TCP Sequence Number Approximation Based Denial of Service
Level : 2 Operating System Detected
Level : 2 Host Uptime Based on TCP TimeStamp Option
Currently we have two name servers and both also having the above same issue.
Thanks in advance for your help
Take each vulnerability, and search for it on Google, and read about them. Where does this "information" come from? Does it, an audit report??, come with other supporting information? It's bizarre to merely present four sentences without any context and expect a reply... you *must* have backup information to have this in the first place.
One of those was actually previously discussed on the LQ forums (I just checked one of them). They offered far more supporting information that this OP did, also.
Distribution: Solaris 9 & 10, Mac OS X, Ubuntu Server
Posts: 1,197
Rep:
Looks to me like one of those audit situations where the higher ups call in some security auditor who runs scans of all the servers and submits a report. The higher ups pay good money, don't understand any of it, and then just say, "fix it." Sometimes it actually matters, sometimes it doesn't. The auditors typically dump a lot of information with little context or explanation.
I've taken care of this stuff on Solaris systems using the NSA security guides. The Solaris guide was a collaboration between Sun and the NSA. There are also Windows and Linux guides and application software guides. See http://www.nsa.gov/ia/guidance/secur...es/index.shtml. Select Operating Systems from the left. It shows Red Hat Linux, but much of that should be applicable to other distributions.
When I work through the Solaris guide, I don't necessarily do everything they suggest. Some of it I see as inappropriate to my environment. You're the sysadmin, you choose (unless your boss overrides your choice).
I believe they're actually the results of a QualysGuard PCI scan. Some scans are done in-house while some are done by 3rd parties. Qualys (and most other tools, including such tools as Nessus) actually adds quite a bit research/remediation/mitigation data into their scan results. The OP may be leaving out those details or the auditors may've not given him those details...I don't know. Not all managers are clueless regarding these audits and the steps involved in remediation of scan findings. Sure, they won't know the intimate details, as most may not have worked in a technical field for years, but still, I've seen more than one manager call out either a dumb auditor or a dumb sysadmin.
In my experience, the system owner may not necessarily have a choice in whether or not he/she addresses the findings. I've worked at places that have management backing the scanning process (this is actually essential), but also have seen the system owners play a key part in mitigation or at least justifying why they can't/won't patch a particular system.
I believe they're actually the results of a QualysGuard PCI scan. Some are done in-house while some are done by 3rd parties. Qualys (and most other tools, including such tools as Nessus) actually adds quite a bit research/remediation/mitigation data into their scan results. The OP may be leaving out those details or the auditors may've not given him those details...I don't know. Not all managers are clueless regarding these audits and the steps involved in remediation of scan findings. Sure, they won't know the intimate details, as most may not have worked in a technical field for years, but still, I've seen more than one manager call out either a dumb auditor or a dumb sysadmin.
In my experience, the system owner may not necessarily have a choice in whether or not he/she addresses the findings. I've worked at places that have management back the scanning process (this is actually essential), but also have seen the system owners play a key part in mitigation or at least justifying why they can't/won't patch a particular system.
Seems so. I googled one and found an amusing blog post of some sysadmin slagging off the test results. Fun.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.