<commit_before>---
layout: default
title: Threat Model
type: workshop
---

## Threat Model

Organizer(s): [<NAME>](../Participants/Geoff-Hill.md)

**Who should be there**

- <NAME>
- <NAME>
- <NAME>
- <NAME>
- <NAME>
- <NAME>
- <NAME>
- Aarun (Threatmodeler owner)
- Continuum people?
- Security Compass people?

**Threat Modeling Workshop ideas**

(some can be consolidated in one workshop)

- pain of manual processes and how to optimise them
- linking threat models and sub-threat models together
- creating threat model templates for security patterns
- better threat model diffing
- integration into DevOps
- use of output by downstream systems... development, test, deployment, etc
- making the infrastructure and system (as opposed to just software) threat modeling more mature
- integration of common taxonomies that are useful across multiple sSDL tiers (not just threat modeling)
- are threat trees actually useful in live business environments
- unified input and output in a sSDL
- simplifying threat modeling for business environments
- Scaling threat models throughout an organization (central storage, versioning control, etc)<commit_msg>Updated status of proposed list<commit_after>---
layout: default
title: Threat Model
type: workshop
---

## Threat Model

Organizer(s): [<NAME>](../Participants/Geoff-Hill.md)

**Who should be there**

- <NAME>
    17/01 (2017 Jan). Cannot attend.
- <NAME>
    17/01. In discussion.
- <NAME>
    17/01. No response yet.
- <NAME>
    17/01. In discussion.
- <NAME>
    17/01. No response yet.
- <NAME>
    17/01. In discussion.
- <NAME>
    17/01. Cannot attend.
- Aarun (Threatmodeler owner)
- Continuum people?
- Security Compass people?

**Threat Modeling Workshop ideas**

(some can be consolidated in one workshop)

- pain of manual processes and how to optimise them
- linking threat models and sub-threat models together
- creating threat model templates for security patterns
- better threat model diffing
- integration into DevOps
- use of output by downstream systems... development, test, deployment, etc
- making the infrastructure and system (as opposed to just software) threat modeling more mature
- integration of common taxonomies that are useful across multiple sSDL tiers (not just threat modeling)
- are threat trees actually useful in live business environments
- unified input and output in a sSDL
- simplifying threat modeling for business environments
- Scaling threat models throughout an organization (central storage, versioning control, etc)
{'fraction_non_alphanumeric': 0.08369694565648553, 'fraction_numerical': 0.012693375644585482, 'mean_word_length': 4.013916500994036, 'pattern_counts': {'":': 0, '<': 19, '<?xml version=': 0, '>': 19, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4520612', 'n_tokens_mistral': 706, 'n_tokens_neox': 655, 'n_words': 318}