Once upon a time,
A woman asked me this question while I was cashiering at a local grocery chain.
It was a bit of a funny story, with me looking a bit dumbstruck, as she read the message on the EMV back to me, “Please wait for cashier… But what does it mean??” It still makes me chuckle a little at what seemed so obvious to me had her completely baffled. Granted though I was, and still am, a bit lost at her confusion, she taught me a very valuable lesson. Nothing is universally understood.
When you think about communication in this world, we take a lot for granted. We frequently are so used to our cultural, situational, and even job biases, we forget that perhaps what we assume to be universally “grokked” may not be so unidirectional. This is why I have always loved to use diagrams. For me, diagramming and other data visualization methods allow for clearer more concise communication and if done correctly can eliminate ambiguity and literally show what is meant.
I have decided to do a small series of info posts, which teach some basic concepts about diagrams used security analysts, and system auditors, to help understand a computer information system.
Wheather it be a cloud or a data center, there are some basic rules to creating a good diagram. Throughout this series of posts, I will be coming back to the following statement “But what does it mean?”
Every diagram you create, should begin and end with that question. First, as a query to determine what should be in the diagram to best show a system. Then lastly, does the diagram serve its intended purpose to explain what it means to explain.
Next up in the series will be Authorization Boundary Diagrams.
- We will discuss how to create them.
- What are the required elements.
- And what they will mean to your security decisions.