Skip to main content

Threat Modeling

Humans have and will always be using techniques we now call Threat Modeling. The circumstances we are in and history is full of threat modeling techniques employed at and effectively used to counter an  adversary. The adversary has multitude of forms and attacks utilizes any vector for effectively neutralizing your efforts to counter the adversary.

So what do we do when we say threat modeling. Is threat an adversary? There are tomes written on the approach towards an adversary. Here in this blog, I will term "Threat Modeling" as something akin to understanding the adversary in terms of the threat he brings to the table and the varied tools (Armaments) in his disposal, his ability to understand your weaknesses and exploit it. All this put together helps the incumbent to understand the posture he has taken viz the adversary and therefore understands the various actions and reactions thereof.

The activity to list all the threats, countermeasures, weaknesses and appropriate actions and reactions of the adversary and the subsequent changes in the action as a consequence of a countermeasure are all studied and we get ready to take on the adversary. This activity of self realization can be simplified and call it "Threat Modeling"

Comments

Popular posts from this blog

Malware Damage - It is real and you need to be ready ...

  Malware, short for "malicious software," is any software intentionally designed to cause harm to computer systems, networks, or devices. Malware can take many forms, including viruses, trojan horses, worms, ransomware, spyware, and adware, among others. The dangers of malware are numerous, and it is crucial to protect yourself from malware to avoid serious consequences, such as: Data theft: Malware can be designed to steal personal information, such as bank account details, social security numbers, and login credentials. Once this information is stolen, it can be used for identity theft, financial fraud, and other malicious activities. System damage: Some malware can damage your computer system, causing it to crash or malfunction. This can result in lost data, system downtime, and costly repairs. Financial loss: Malware can also be used to extort money from victims. For example, ransomware can lock down a victim's computer and demand payment in exchange for the decrypti...

The Finger Knows, even if your brain does not - Passwords

Was reading an interesting article, now that I have lost the link, I may not have it here, though I would fill that in once I get hands on it. This article was how the fingers knows what you are typing even though your eyes reading the content says you typed in wrong. This was done in a research that talks about how they introduced typos, some of the typos were introduced even when it was typed proper and some typos were corrected randomly. The conclusion of the study was that, the finger paused a second, when it typed fine, but the eyes looking at the screen, saying you got it wrong. The pause is because of the auto recognition of the fact by the fingers when you make a typo or that you are sure that you got the correspondence between the eyes and the fingers. Reading the article, made me wonder, have we not always remembered our passwords for different sites. Many a times I have had the opportunity to go to a website and even without thinking for a moment, the fingers go and hav...

A Roadmap to move from Cloud to In premise - The reverse migration -- Is Cloudflation at myth?

 Cloudflation as a term is being used and talks on the spiralling cost of cloud bills for an organization. The easily available and provisioning options leads to workloads that run for no reasons, orphaned accounts and a gamut of costs that are accrued by multiple departments without much of an oversight. There is a trend to reduce the workloads and have a semblance of order. It is imperative that we have plans that helps to reverse the migration to cloud and bring back some of the workloads that might work cheaper to run local. Is there a roadmap to achieve this goal? A few pointers in this direction A roadmap for moving from the cloud to in-premise computing should include the following steps: Assess current workloads: Assess the current workloads that are running on the cloud and determine which workloads would be most suitable for in-premise computing. Identify in-premise infrastructure: Identify the in-premise infrastructure that will be needed to run the identified workloads....