Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

Re: Windows Compliance Check Problems

Subject: Re: Windows Compliance Check Problems
Date: Thu, 25 Jan 2007 15:16:43 -0500
i have a support request in for the same thing :)

On 1/25/07, Mike Forrester <mikef@pocketlint.com> wrote:

I'm hoping someone can figure out something that I'm missing when trying to get the Windows compliance checks working (UNIX works fine).

Nessus Server:
CentOS 4.4
Nessus 3.0.3 (RedHat ES4 rpm)
Nessus Direct Feed

Nessus Client:
Fedora Core 6
NessusClient 1.0.2

Policy Info (brief):
Plugins:
Windows Compliance Checks Plugin - enabled
Enable dependencies at runtime - enabled
Silent dependencies - enabled

Crendentials:
SMB account - specified (local admin)
SMB password - specified
SMB domain - specified

Target selection:
Target: Single Windows XP SP2 host

Prefs:
Windows Compliance Checks:
Policy file #1: federal_nsa_microsoft_xp_user_right_assignment.audit
Policy file #2: federal_audit_microsoft_windows_os_guideline.audit

I get the following error in nessusd.dump every time I try to run a scan:

[26363](compliance_check.nbin:0x161a) A non-authenticated script
attempted to use an authenticated function - returning NULL
[26363](compliance_check.nbin:0x161a)
script_get_preference_file_location: script is not authenticated!

I've tried both domain and local authenticated accounts (just local
Admin, not domain).  I get entries in the Security event log for two
successful login for whatever test account I use plus a couple others
(administrator and nessus+random number).  When I enable Windows checks
that check policy requiring a login, they work just fine.

Any ideas on what I'm missing?

Thanks,
Mike
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus




-- Doug Nordwall Unix, Network, and Security Administrator Noise proves nothing. Often a hen who has merely laid an egg cackles as if she laid an asteroid. -- Mark Twain
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
<Prev in Thread] Current Thread [Next in Thread>