Not all session spoofing is alike, and therefore it needs to be responded to differently according to the urgency associated with the event. For example, a session might be spoofed, but this session is not in the middle of any purchasing, and therefore the potential financial loss to either the website or the consumer is extremely low. Another session is spoofed in the middle of making over $1,000 in purchases, and therefore the potential financial loss to the parties involved is substantial.
You can build some common logic into your search, based upon given values, to increase the urgency associated with an event. In the following example, we bring together the website access and web application logs to enhance ...
