Sponsored Content
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Security Event Management (SEM) with CEP (Part 3) - Trends in Cyberspace Post 302124610 by Linux Bot on Monday 2nd of July 2007 01:48:13 AM
Old 07-02-2007
Security Event Management (SEM) with CEP (Part 3) - Trends in Cyberspace

Security Event Management (SEM) with CEP (Part 3) - Trends in Cyber Attacks, Threats and Vulnerabilities
Life in our web browser-based world is more dangerous than first meets the eye.*** I don’t mention this to sound the alarm bells.* It is, however, important to understand why organizations need sophisticated event-driven cybertools to catch criminals before they do harm to us.* For example,* look at the next two*charts from IBM*that show critical vulnerabilities for Internet Explorer (34 total)*and Firefox (64 total) in 2006.

Image

Image
The two charts above are just two examples of the unseen*daily risks we face*while*working*and playing in cyberspace - and the risk increases daily as our lives become more dependent on the net, as illustrated by the graphic below.
Image
We can easily see from IBM’s graphic (superimposed with my curve)*that the number of cyberspace vulnerabilities*have been*increasing exponentially since 2000.* This trend continues today and is expected to get worse.*** This was the motivation for my 2000 CACM paper on next generation intrusion detection systems (which also applies to fraud detection as well as other detection-oriented event processing applications).**
Security event management*is an*event-driven* set of technologies envisioned*to make our lives more secure in cyberspace.** In my next post in the series, Security Event Management (SEM) with CEP (Part 4), I will discuss the promise of SEM and SEM functionality.* I will then explain why current SEM implementations fall far short of the earlier SEM hype and how CEP can help.
Copyright © 2007 by Tim Bass, All Rights Reserved.


More...
 
emsweb(1M)																emsweb(1M)

NAME
emsweb - starts the HP-UX Event Monitoring Service tool (a Web interface) SYNOPSIS
[ ] [ ] DESCRIPTION
The HP-UX Event Monitoring Service tool ( ) is used to monitor resource instances and manages requests created on these instances. The HP-UX Event Monitoring Service tool provides both Web-based and terminal user interface. The Web-based interface is launched through the HP System Management Homepage. Superuser privileges are required to access the HP-UX Event Monitoring Service tool. A user who does not have superuser privileges has read-only access to the requests area in the HP-UX Event Monitoring Service tool and cannot modify requests. An attempt will be made to connect to a Mozilla/Netscape Web browser running on the X server defined by the DISPLAY environment variable. If a running Mozilla/Netscape client is found, it will be used, otherwise a new Mozilla/Netscape session will be initiated. This will only happen if the Mozilla/Netscape process is running in the same system as that referenced by the DISPLAY variable, unless the -F option is used. Note: By default, the HP-UX Event Monitoring Service tool (emsweb) invokes the Mozilla Web browser. If you want to support any other browser (Netscape), set the $BROWSER environment variable as shown below: The terminal user interface is invoked if any of the following conditions are true: o The command is invoked with the option. o The environment variable is not set. The Web-based interface is launched if all the following conditions are true: o The command is invoked with option. o The environment variable is set. o The command is available on the system. If the Web-based interface cannot be launched, invokes the terminal user interface. Options recognizes the following options: Forces a client browser to be used in less secure ways. The option forces the client browser to be used or started, even when the X-traffic between the X-server and the Mozilla browser is not secure. Use this option only when you are sure the network traffic between the host where Mozilla is running and the host in the DISPLAY variable is secure. If cannot start the Web browser, the terminal interface is started. When the HP-UX Event Monitoring Service Web interface is invoked by SAM, the option is used. If a privileged user (root) executes the command with the option, a temporary login bypass key is generated. The bypass key enables the user to access the Web interface without having to provide login information again. When the HP-UX Event Monitoring Service Web interface is invoked by SAM, the option is used. Opens the terminal interface for managing requests created to monitor resource instances regardless of the current setting of the environment variable. You can also start the HP-UX Event Monitoring Service tool using one of the following methods: o Invoke and select the Event Monitoring Service (character mode) functional area to launch the terminal user interface and the Event Monitoring Service (Web-based Interface) to launch the Web-based tool o Invoke the HP-UX Event Monitoring Service tool Web interface by typing the URL in the address bar of your browser, where hostname is the name of the server o Launch the HP-UX Systems Insight Manager on the server and select the Event Monitoring Service tool from the Configure -> HP-UX Configuration menu Online Help After the HP-UX Event Monitoring Service tool is started, the online help provides details on how to use the tool. RETURN VALUES
Upon completion, emsweb returns one of the following values: o 0 Successful o 1 An error occurred AUTHOR
was developed by Hewlett-Packard. SEE ALSO
emscli(1M), resls(1), resdata(1) emsweb(1M)
All times are GMT -4. The time now is 06:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy