Slashdot Mirror

← Back to Stories (view on slashdot.org)

U.S. Navy Works To Improve Linux Security

Posted by timothy on from the gnu-linux dept.

MrPhiles writes "Just saw an article at Washington Technology talking about how the Navy is developing a Secure Auditing tool for Linux. I think it's cool that government agencies are taking steps to obtain credentials necessary for open source use in high-security environments."

3 of 20 comments (clear)

  1. Re:Great but by rritterson · · Score: 5, Informative

    It's not quite the same, obviously. The Navy software engineers can easily tweak and fix any holes they find. With Windows you are limited to the framework MS provides and the hope that they will fix any problems discovered.

    The NSA released documents on how to secure WinXP and Win2K server not too long ago- it was even posted on /.

    --
    -Ryan
    AUWYHSTOT (Acronyms are Useless When You Have to Spell Them Out Too)
  2. Re:what is the kernel lacking? by Beryllium+Sphere(tm) · · Score: 4, Informative

    >Would one of ya'all gurus please explain this?

    Attend, my son :-)

    The key word seems to be "forensic". They want to replace syslog with something sufficiently tamper-resistant to persuade a judge that it's good enough for legal evidence. There are already some clever hacks for this, such as hiding the real syslog process and leaving a fake one around for an intruder to disable or corrupt.

  3. Re:what is the kernel lacking? by ctr2sprt · · Score: 2, Informative
    There are a lot of things that can be meant by "auditing." At its most sensitive, you can audit all accesses to certain system resources (files, syscalls, device node accesses, that sort of thing), and at a more standard level you can audit failed accesses to system resources. Some of this is implemented in some way - "bad root login on tty1" - but usually when people talk about system security auditing, they are talking about a unified framework for controlling auditing of the entire system (the parts relevant to security, at least). The "unified" part is especially important because frequently you want to analyze the audit trail using automated tools, kind of like Snort and ACID, rather than viewing each entry individually. If you have 50 different programs auditing things in 50 different ways, that makes system-wide analysis much more difficult.

    This isn't the sort of thing normal people will want or need on their Linux systems, but in some environments (military, government) it's really important. And you could, of course, use it to create a honeypot, if you're into that sort of thing.