When it comes to security, context is king. In our recent podcast with the team at The New Stack, we explored the importance of context when it comes to security. This post is a more in-depth analysis of some of these concepts we discussed.
To understand the impact of context, let’s consider an everyday use case: The simple callerID. You get a phone call, and you look at a phone number. Potentially, your phone has a local directory (let’s call it a context cache) and it maps the number to a name, and based on this mapping you decide whether to answer the call or not, or you can check the log later to figure out who called you. Indeed phones are becoming more intelligent, and they are trying to determine this mapping by looking at your email and other local information. This process is efficient enough to skip lots of unwanted conversations.