Hosting generously provided by
|
|
Writing Software Security Test Cases: Putting security test cases into your test plan
|
Part of software testing involves replicating customer use cases against a given application. These use cases are documented in a
test plan during the quality assurance phase in the development cycle to act as a checklist ensuring common use cases aren't
missed during the testing phase. People within the quality assurance community are starting to understand that checking an
application for security issues (defects) isn't just the responsibility of the security department (if one exists), or the
software architects. While typical QA Engineers don't understand the scope or inner working of specific software vulnerabilities,
they do go about testing an application in a similar fashion to how the penetration testing community does. Unlike typical
penetration testing QA has access to internal documents and insider information giving them advantages to aide in the testing of
an application. In addition to documenting customer use cases it's important to begin the process of documenting what an attacker
may attempt against your application as well and incorporating these attacker 'use cases' into a security section of your
standard test plan.
|
|
|
|
Identifying Risks in the Development Cycle
|
Identifying security defects before a product ships reduces the risk of embarrassing public exposure, the cost of repairing the defect, and the risk to your customers. Your customers will not forget being compromised via a flaw in your product, and they may try to hold you accountable. Properly performing this security validation at each phase can greatly reduce your products risk to security flaws.
|
|
|
|
Feed Injection in Web 2.0: Hacking RSS and Atom Feed Implementations
|
This is a copy of the slides I used at my Blackhat 2006 talk and a link to the paper accompying it.
(Power Point)
|
|
|
|
Fingerprinting Port 80 Attacks: A look into web server, and web application attack signatures: Part Two.
|
Part two of "Fingerprinting port80 attacks". This paper provides information on web application
attack forensics that will help you identify what an attacker might be doing. Part two covers
attacks that where not mentioned in the first paper.
|
|
|
|
Header Based Exploitation: Web Statistical Software Threats
|
This paper helps describe an attack method often overlooked
by programmers. It explains how modification of HTTP headers
can cause possible system access, cookie theft/poisoning,
tricked advertising, database injection, and other bad things
in web statistical software
|
|
|
|
Fingerprinting Port 80 Attacks: A look into web server, and web application attack signatures.
|
This is the first paper on web application attack forensics published. This paper will give you a basic
understanding of what web application attacks look like, and how they are used in real life examples.
"The paper provides a nice no-frills overview of the subject."
-
"Great analysis of Web server attacks, including log data."
-
|
|
|
|
Email Archives may allow Distributed Attacks against users and Web servers
|
"Mailing lists are often archived for later viewing on websites. The software
that archives these email messages may allow an attacker to execute commands,
include false information, cause a wide scale browser DOS, and other possibilities."
This paper covers potential uses/exploitation of this widescale problem.
|
|
|
Information contained on this website may not be copied without explicit permission.
Best Viewed with Netscape.
|
|
|
Subscribe to CGISecurity.com
|
|
|
|
|
|
The Web Security Mailing List
|
|
|
|
|
Contact us
|
Post News, get linkage!
|
|
|
|
