Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Secure Software Development: Misuse Cases & Checking for Vulnerabilities, Slides of Software Engineering

An overview of secure software development, focusing on the application of misuse cases and checking for known vulnerabilities. Topics covered include requirement and use cases, architecture and design, risk analysis, code tests and test results, feedback from the field, abuse cases, security requirements, software vendor accountability, and checking for known vulnerabilities. Misuse cases are discussed in detail, including their extension of use case diagrams, representation of actions the system should prevent, and the importance of building security in from the ground up.

Typology: Slides

2012/2013

Uploaded on 04/26/2013

sharad_984
sharad_984 🇮🇳

4.5

(13)

146 documents

1 / 9

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Secure Software Development
Docsity.com
pf3
pf4
pf5
pf8
pf9

Partial preview of the text

Download Secure Software Development: Misuse Cases & Checking for Vulnerabilities and more Slides Software Engineering in PDF only on Docsity!

Secure Software Development

Application of Touchpoints

Requirement andUse cases Architectureand Design Test Plans Code (^) Test ResultsTests and Feedback fromthe Field

5. Abuse cases 6. Security Requirements 2. Risk Analysis

External Review

4. Risk-Based Security Tests 1. Code Review (Tools) 2. Risk Analysis 3. Penetration Testing 7. Security Operations

Software Vendor Accountability

  • Proper implementation of security features
  • Looking for known security flaws
  • Passing third party validation
  • Source code analysis

Checking for Known Vulnerabilities

  • Need tool
  • Possible attacks and attack types
  • How the software behaves if something goes WRONG
  • What motivates an attacker?

Misuse Cases

  • Analyze system design and requirements
    • Assumptions
    • Failure of assumptions
    • Attack patterns
  • Software that is used also going to be attacked
  • What can a bad guy do and how to react to malicious use

Misuse Case Development

  • Team work – software developers and security experts
  • Identifying and documenting threats
  • Creating anti-requirements: how the system can be abused
  • Creating attack model
    • Select attack pattern relevant to the system
    • Include anyone who can gain access to the system