SUPERIOR-PAPERS.COM essay writing company is the ideal place for homework help. If you are looking for affordable, custom-written, high-quality and non-plagiarized papers, your student life just became easier with us. Click the button below to place your order.

Order a Similar Paper Order a Different Paper

The assignment is based off the lab so both need to be done by same person ? the power point is the answer the last question in assignment 3


ISEC 620 Homework 3

Please review the chapters about attack trees and attack libraries:

Attack Trees:

Attack Libraries (CAPEC and OWASP Top Ten attack libraries):

Attack trees are an essential method for threat assessment. It evaluates the security of a system from an attacker perspective. The root node represents the attacks’ goal, and the remaining leaves indicate sub-goals or attack methods.

In this homework, you are expected to provide an attack tree for the system you threat-modeled in the lab. The goal of the attacks is to steal information from the password-protected blog website.

Question 1

Provide a report that includes your analysis. The report should consist of (but not limited to) the following items:

1. Initial attack interfaces and a short description of why they can be the starting point for attacks

2. Attack tree

a. Sub-goals

b. The nodes of the tree (Please use AND, OR functions appropriately)

Question 2

Map the sub-goals and attack methods with the attack libraries given in the second reading

Question 3 – Weekly Learning and Reflection 

In two to three paragraphs of prose (i.e., sentences, not bullet lists) using APA style citations if needed, summarize and interact with the content that was covered this week in class. In your summary, you should highlight the major topics, theories, practices, and knowledge that were covered. Your summary should also interact with the material through personal observations, reflections, and applications to the field of study. In particular, highlight what surprised, enlightened, or otherwise engaged you. Make sure to include at least one thing that you’re still confused about or ask a question about the content or the field. In other words, you should think and write critically not just about what was presented but also what you have learned through the session. Questions asked here will be summarized and answered anonymously in the next class.

ISEC 620 Lab 3: Threat Modeling


In the previous lab, you created a Kanban Board. One of the tasks you created in Module-2 should be to perform threat modeling for the blog website you have been developing for your customer. You decided to perform threat modeling after the vulnerability management team discovered a critical vulnerability on the web service.

The blog site is in the staging environment. It will be migrated to the production environment in the Azure cloud next month. The blog site will eventually serve as an information sharing and collaboration portal for authenticated users. It will use an SQL database at the backend.

As the project manager, you want to see the Data Flow Diagram (DFD) that shows the communications between various entities and to perform threat modeling with your team to explore threats and suggest countermeasures.


Please read the following articles:

A short introduction to Microsoft’s STRIDE (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege) threat modeling approach:

A short case:

A detailed case, learn more about the approach to threat modeling in this article:

You will use Microsoft Threat Modeling Tool in this lab. Familiarize yourself with the tool by reviewing this page:

Lab Environment

Access to Microsoft Threat Modeling Tool:

1) If you want to run it on your Windows machine, you can download it from and run the tool on your personal computer.

2) Alternatively, you can reserve the Windows 10 instance in the Netlab environment ( Please refer to the Netlab Reservation Instructions for access details.

Instructions & Questions

1. Double click the Microsoft Threat Modeling 2016 icon on the desktop.

2. Click the Browse button and select the Azure Cloud Services file.

3. Click the Create A Model.

4. Please refer to the “Microsoft Threat Modeling Tool 2016 Guidance” section of this document to get guidance on using the threat modeler tool.

Part 1: Create a Data Flow Diagram

There is no single solution for this lab. After carefully reading the description given in the introduction section of this lab instruction, draw a DFD that shows Data stores, Processes, Interactors, Data flows, and Trust boundaries. Take the screenshot of the DFD.

Part 2: Review Threats

1. Switch to analysis view

2. Review all of the threats that are automatically devised by the tool

3. Add two more threats.

Take a screenshot of the new threats.

Part 3: Devise Mitigations and Change Threat Properties

1. For the threats you added, change the status to Mitigated and fill out the “Possible Mitigations” section.

2. Choose one threat, change the status to “Not Applicable”. Fill out the justification section.

3. Choose another threat, change the status to “Need Investigation”. Adjust the severity level and write a justification for it.

Take the screenshots that show the result of your actions.

Part 4: Reporting

1. Click the Reports menu and “Create Full Report”.

2. Review the downloaded report.

Part 5: Project Management

1. Log into your Azure Board and create a task for the threat that needs investigation.

2. Take the screenshot of the Azure board showing the tasks.

Submit the Full Report and screenshots.

Microsoft Threat Modeling Tool 2016 Guidance

The below figure shows how to switch to analysis view.

In the analysis view, you see some generic threats, as shown below.

Right-click on the objects you created (Sample objects: “Request”, “Response,” and Trust Boundaries). You will see the “Add User-defined Threat” option.

Once you click on “Add User-defined Threat”, the threat list will show the new threat (1).

Fill out the details of the new threat (2).

Software Assurance Maturity Model


  • Review of existing secure SDLC efforts
  • Understanding the model
  • Applying the model
  • Exploring the model’s levels and activities
  • SAMM and the real world

By the end, you’ll be able to…

  • Evaluate an organization’s existing software security practices
  • Build a balanced software security assurance program in well-defined iterations
  • Demonstrate concrete improvements to a security assurance program
  • Define and measure security-related activities throughout an organization

Review of existing secure SDLC efforts


  • Comprehensive, Lightweight Application Security Process
  • Centered around 7 AppSec Best Practices
  • Cover the entire software lifecycle (not just development)
  • Adaptable to any development process
  • Defines roles across the SDLC
  • 24 role-based process components
  • Start small and dial-in to your needs

Microsoft SDL

  • Built internally for MS software
  • Extended and made public for others
  • MS-only versions since public release


  • Gary McGraw’s and Cigital’s model

Lessons Learned

  • Microsoft SDL
  • Heavyweight, good for large ISVs
  • Touchpoints
  • High-level, not enough details to execute against
  • Large collection of activities, but no priority ordering
  • ALL: Good for experts to use as a guide, but hard for non-security folks to use off the shelf

Drivers for a Maturity Model

  • An organization’s behavior changes slowly over time
  • Changes must be iterative while working toward long-term goals
  • There is no single recipe that works for all organizations
  • A solution must enable risk-based choices tailor to the organization
  • Guidance related to security activities must be prescriptive
  • A solution must provide enough details for non-security-people
  • Overall, must be simple, well-defined, and measurable

Therefore, a viable model must…

  • Define building blocks for an assurance program
  • Delineate all functions within an organization that could be improved over time
  • Define how building blocks should be combined
  • Make creating change in iterations a no-brainer
  • Define details for each building block clearly
  • Clarify the security-relevant parts in a widely applicable way (for any org doing software dev)

Understanding the model

SAMM Business Functions

  • Start with the core activities tied to any organization performing software development
  • Named generically, but should resonate with any developer or manager

SAMM Security Practices

  • From each of the Business Functions, 3 Security Practices are defined
  • The Security Practices cover all areas relevant to software security assurance
  • Each one is a ‘silo’ for improvement

Under each Security Practice

  • Three successive Objectives under each Practice define how it can be improved over time
  • This establishes a notion of a Level at which an organization fulfills a given Practice
  • The three Levels for a Practice generally correspond to:
  • (0: Implicit starting point with the Practice unfulfilled)
  • 1: Initial understanding and ad hoc provision of the Practice
  • 2: Increase efficiency and/or effectiveness of the Practice
  • 3: Comprehensive mastery of the Practice at scale

Check out this one…

Per Level, SAMM defines…

  • Objective
  • Activities
  • Results
  • Success Metrics
  • Costs
  • Personnel
  • Related Levels

Approach to iterative improvement

  • Since the twelve Practices are each a maturity area, the successive Objectives represent the “building blocks” for any assurance program
  • Simply put, improve an assurance program in phases by:

Select security Practices to improve in next phase of assurance program

Achieve the next Objective in each Practice by performing the corresponding Activities at the specified Success Metrics

Applying the model

Conducting assessments

  • SAMM includes assessment worksheets for each Security Practice

Assessment process

  • Supports both lightweight and detailed assessments
  • Organizations may fall in between levels (+)

Creating Scorecards

  • Gap analysis
  • Capturing scores from detailed assessments versus expected performance levels
  • Demonstrating improvement
  • Capturing scores from before and after an iteration of assurance program build-out
  • Ongoing measurement
  • Capturing scores over consistent time frames for an assurance program that is already in place

Roadmap templates

  • To make the “building blocks” usable, SAMM defines Roadmaps templates for typical kinds of organizations
  • Independent Software Vendors
  • Online Service Providers
  • Financial Services Organizations
  • Government Organizations
  • Organization types chosen because
  • They represent common use-cases
  • Each organization has variations in typical software-induced risk
  • Optimal creation of an assurance program is different for each

Building Assurance Programs

Case Studies

  • A full walkthrough with prose explanations of decision-making as an organization improves
  • Each Phase described in detail
  • Organizational constraints
  • Build/buy choices
  • One case study exists today, several more in progress using industry partners

Exploring the model’s levels and activities

The SAMM 1.0 release

SAMM and the real world

SAMM history

  • Beta released August 2008
  • 1.0 released March 2009
  • Originally funded by Fortify
  • Still actively involved and using this model
  • Released under a Creative Commons Attribution Share-Alike license
  • Donated to OWASP and is currently an OWASP project

The OpenSAMM Project

  • Dedicated to defining, improving, and testing the SAMM framework
  • Always vendor-neutral, but lots of industry participation
  • Open and community driven
  • Targeting new releases every 6-12 months
  • Change management process
  • SAMM Enhancement Proposals (SEP)

Future plans

  • Mappings to existing standards and regulations (many underway currently)
  • PCI, COBIT, ISO-17799/27002, ISM3, etc.
  • Additional roadmaps where need is identified
  • Additional case studies
  • Feedback for refinement of the model
  • Translations into other languages

Other “modern” approachs

  • Microsoft SDL Optimization Model
  • Fortify/Cigital Building Security In Maturity Model (BSIMM)

SDL Optimization Model

  • Built by MS to make SDL adoption easier


  • Framework derived from SAMM Beta
  • Based on collected data from 9 large firms

Quick re-cap on using SAMM

  • Evaluate an organization’s existing software security practices
  • Build a balanced software security assurance program in well-defined iterations
  • Demonstrate concrete improvements to a security assurance program
  • Define and measure security-related activities throughout an organization

Got stuck with a writing task? We can help! Use our paper writing service to score better grades and meet your deadlines.

Get 15% discount for your first order

Order a Similar Paper Order a Different Paper