TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------
Chris:
I would approach the problem from the other direction. Create a unique
custom signature for each sensor and then send a packet that violates that
signature past each of your sensors every 6 hours. Config RealSecure to
email an alert for each violation. You might as well use the alert feature
rather than create your own.
Ken Stephens, CISSP
Sr. Security Manager
Computer Sciences Corporation
One Tower Lane, Suite 400
Oakbrook Terrace, IL 60181
Voice: 630.990.6207
Fax: 630.990.6369
"Coffey,
Christopher To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
S." cc: "Riffel, Steve"
<[EMAIL PROTECTED]>
<Christopher. Subject: Realsecure "Heartbeat" system
Coffey
@mail.va.gov>
Sent by:
owner-issforu
m
01/15/02
07:02 AM
TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any
problems!
----------------------------------------------------------------------------
Hello,
I'm looking for a solution to an interesting problem. Our management has
tasked us with building a system to verify the "operational status" of our
ISS RealSecure network sensors. Some type of Heartbeat system that every 6
hours would "Ping" all our network sensors and verify they are operational,
and send us some type of "all is well" email ? Has anyone developed a
system like this ??? We have 11 operational network sensors and I'm at a
loss on how to do this, any and all help would be appreciated. thanks in
advance.
Christopher Coffey
Network Security Officer
Austin Automation Center - VA
[EMAIL PROTECTED]
(512)326-6039
