All-in-One Guides:Web application security -- How to prevent attacks
Web application security -- How to prevent attacks
Prevention techniques when gathering requirements
Security features, like other features in software, are initiated in the requirements elicitation and analysis phase. Learn how to use threat modeling and misuse cases, among other techniques, to determine security features that ought to be included.
-
Threat modeling key to pro-active security
01 Mar 2006
Article - The best way to ensure software is secure is to build security into the software development life cycle, industry experts say. Design-time threat modeling is pivotal, but it needs to be constrained by an understanding of the business risks involved.
-
Writing software requirements that address security issues
Tip - Experts always say you need to bake security into the development lifecycle. To do that, you need to take a hard look at the security requirements written for the software. Kevin Beaver offers some advice on what you should consider during this critical...
-
Software Security Engineering: A Guide for Project Managers -- Chapter 3, Requirements Engineering f
Tip - Software security requirements engineering is a critical part of the software development lifecycle. This free book chapter explains how to approach requirements engineering for a secure SDLC.
-
The essentials of Web application threat modeling
Tip - A critical part of Web application security is mapping out what's at risk -- or threat modeling. Kevin Beaver outlines the essential steps to get you started and help you identify where your application vulnerabilities may be.
-
Threat modeling enhanced with misuse cases
Tip - Misuse cases capture all the possible attacks on an application, as well as mitigation steps. Anurag Agarwal explains how they can help architects correct design flaws, help developers understand a hacker's approach and write more secure code, and help...
-
Getting started with Web application misuse cases
Tip - When developing applications it isn't enough to think about how they will be used. You must also consider how they will be misused -- or abused -- so that you can prevent attacks. Kevin Beaver gives some examples of Web application weak spots that your...