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 ISSForum
[Top] [All Lists]

RE: [ISSForum] problem with system scanner log file

Subject: RE: [ISSForum] problem with system scanner log file
Date: Mon, 18 Apr 2005 13:50:14 +0100
Dawne,

The Logit action causes an event to be written to the system's application
eventlog.  $file is used to include the name of the Policy that was run.

I have pasted below the help text for Logit, I hope this helps.

Configuring the Logit Action
----------------------------
As supplied with System Scanner, the command for the logit action is as
follows:

logevent /i W /f "$file"

logevent procedure
This is the procedure logevent followed by two parameters:

/i (importance), which currently shows the value W (warning)

/f (the policy that triggered the event), followed by the substitution
variable that will be replaced with the name of the file when the action
occurs.

In this example, you will change the importance to information, and add the
name of the destination host (the host the log file you want to write to
resides on) and the message text that you want to appear in the log.

The parameter for destination host is /d.

The parameter for message text is /m.

Therefore, you should edit the command to read:

logevent /i I /d hostname /f "$file" /m "The example event will be logged."

This is the procedure logevent followed now by four parameters:

/i is the importance, now I for Information

/d is the destination hostname. You must replace the word hostname with the
name of the destination host.

/f is the policy that triggered the alert, still using the substitution
variable

/m is the message text. You should replace the text in quotation marks with
text that is logical for the alert you are creating.

Nick Connor
Assuria Limited

-----Original Message-----
From: issforum-bounces@iss.net [mailto:issforum-bounces@iss.net]On
Behalf Of dawne
Sent: 15 April 2005 06:42
To: issforum@iss.net
Subject: [ISSForum] problem with system scanner log file


hey there!
using system scanner 4.2.5 console and 4.2 agents. When I do a scheduled
scan, I want to log a message on a specified computer. this is the command i
used :
logevent /i I /d com1 /f "$file" /m "scheduled scan started"

tried to change "$file" to a local directory "D:\...." because at first i
assumed that the file will automatically be logged in the console log file,
however it was not. Anyway, no log was logged in the D:\..... directory
either!

why so?

thanks!

 Yahoo! Messenger
- Log on with your mobile phone!
_______________________________________________
ISSForum mailing list
ISSForum@iss.net

TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to
https://atla-mm1.iss.net/mailman/listinfo/issforum

To contact the ISSForum Moderator, send email to mod-issforum@iss.net

The ISSForum mailing list is hosted and managed by Internet Security
Systems, 6303 Barfield Road, Atlanta, Georgia, USA 30328.

_______________________________________________
ISSForum mailing list
ISSForum@iss.net

TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to 
https://atla-mm1.iss.net/mailman/listinfo/issforum

To contact the ISSForum Moderator, send email to mod-issforum@iss.net

The ISSForum mailing list is hosted and managed by Internet Security Systems, 
6303 Barfield Road, Atlanta, Georgia, USA 30328.

<Prev in Thread] Current Thread [Next in Thread>