Skip to content

Update README.md #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,17 +2,17 @@
Data flow diagrams, also called DFDs or threat modeling diagrams.

## Goal
Many people have presented various different ways to craft data flow diagrams over the years. This is an attempt to both be precise about what this defninition of a "v3 DFD" is, and also to encourage people to think about diagramming techniques themselves as something that, like code, can be specified and evolved over time, and labeled with a version.
Many people have presented various different ways to craft data flow diagrams over the years. This is an attempt to both be precise about what this definition of a "v3 DFD" is, and also to encourage people to think about diagramming techniques themselves as something that, like code, can be specified and evolved over time, and labeled with a version.

### Symbols/Elements used

| Element | Symbol | Discussion |
|---------|--------|------------|
| External entity| <img src ="icons/rectangle.png" width=50 height=50> | A sharp-cornered rectangle. Anything outside your control. Examples include people and systems run by other organizations or even divisions. For example, Joe's mobile phone, the Mint data aggregators (assuming you're modeling from a bank's perspective.). If you're modeling Mint, then the bank's systems would be external entities.
| External entity| <img src ="icons/rectangle.png" width=50 height=50> | A sharp-cornered rectangle. Anything outside your control. Examples include people and systems run by other organizations or even divisions. For example, Joe's mobile phone, the Mint data aggregators (assuming you're modeling from a bank's perspective). If you're modeling Mint, then the bank's systems would be external entities.
| Process| <img src ="icons/rounded-rectangle.png" width=50 height=50> | A rounded rectangle. Any running code, including compiled, scripts, shell commands, SQL stored procedures, et cetera.
| Data store| <img src ="icons/cylinder-256.png" width=50 height=50> | A drum. Anywhere data is stored, including files, databases, shared memory, S3, cookies, et cetera.
| Data flows| <img src ="icons/arrow.png" width=50 height=50> | An arrow. All the ways that processes can talk to data stores or each other.
| Trust boundary | . . . | A closed shape drawn with a dashed or dotted line. Usually a box.
| Trust boundary | . . . | A closed shape drawn with a dashed or dotted line to denote difference realms of the level of trust. Usually a box.



Expand Down