session prediction (credential/session prediction)
Session prediction, also called credential/session prediction, is a method of surreptitiously
obtaining data (called a session ID)
about an authorized visitor to a Web site. The session ID is normally stored within a cookie or URL.
Session IDs enables user tracking on a Web site. The session ID can also provide automatic
authentication for future visits to that site or associated sites. If a cracker obtains
session ID data, he can conduct an attack, such as session
hijacking or session
replay.
Session prediction and hijacking typically occur while a legitimate user is interacting with an
affected Web site. The legitimate user may or may not be able to detect the intrusion, depending on
his or her level of technical knowledge, and on the nature of the attack. If a Web site does not
respond in the normal or expected way to user input, or if it stops responding altogether for an
unknown reason, session prediction or hijacking may be taking place.
This was last updated in March 2006
Email Alerts
Register now to receive SearchSoftwareQuality.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy
More News and Tutorials
-
Software consultant Nari Kannan describes how agile practices and work can be scaled appropriately for success in large organizations. Using lean thinking, reduction of waste, and appropriately organizing work and people, agile can be successfully adapted, regardless of the size of the organization.
-
Undiscovered software glitches in complex systems are common, and one of the primary drivers is the loss of mainframe knowledge of a retiring workforce. Software glitches are lurking in many large systems, particularly mainframe systems, and the COBOL programmers that understand the code best are retiring, according to Jeff Papows, author of the new book, "Glitch - The hidden impact of faulty software." Papows describes how faulty software caused a huge charge to debit card holder's account and why such mistakes are on the rise in this interview. Papows notes the three most pressing drivers for software glitches: loss of intellectual knowledge, market consolidation and the ubiquity of technology
-
Karen Johnson suggests a variety of ways that testers can gain additional skills and experience, including social networking and open source testing.
-
Articles
-
Resources from around the Web
