Timedora

Understanding Information-Security Risk

A practical introduction to connecting assets, threats, vulnerabilities, likelihood, impact, and safeguards when assessing information-security risk.

From Potential Harm to Reduction

Start with what could be harmed

Security is easier to reason about when you distinguish three things. An is something the organization values. Assets can be physical or intangible—for example, devices, records, software, services, intellectual property, or reputation. A is a circumstance or event that could harm an or disrupt an organization. Threats may be deliberate, accidental, or environmental. A is a weakness in a system, procedure, or control that a could exploit or trigger. These concepts are connected, but they are not interchangeable: a or weakness by itself does not tell you how much the organization faces.

concerns the possibility of harm if a exploits a . Assessing it means considering how likely the harmful event is and how serious its potential impact could be. The value of the and the safeguards already in place matter too. The assessment is a reasoned evaluation of these factors; without enough information, it does not produce a reliable numerical score.

Work through the payroll example

  1. Identify the : The company’s payroll records matter because they contain information about employees and payment details.

  2. Identify a : A phishing message is a possible in this scenario.

  3. Find a : Weak sign-in protection is a that could make an account easier to misuse.

  4. Describe the possible harm: If an attacker could use stolen credentials, they might view records or change payment details. Unauthorized viewing could affect privacy; changes could have financial consequences.

  5. Assess the : Consider how likely this event is and how serious its consequences could be. The value of the records and protections already in place also affect the assessment. The example identifies relevant factors, but does not provide enough information to calculate a numerical likelihood or score.

This reasoning makes the proposed safeguards more purposeful. Multifactor authentication adds a sign-in protection; restricted permissions limit which records or actions an account can access; staff training can help employees recognize phishing; and alerts for unusual activity can help identify suspicious account use. Each can reduce , but none guarantees that an incident will not occur. The organization should assess the remaining and decide whether more protection is needed.

Reassess as circumstances change

Safeguards should be selected and maintained in light of the that remains. Changes in threats, systems, or organizational needs can change the assessment, so protections should be reviewed and adjusted rather than treated as permanent guarantees.

The purpose is to protect information’s confidentiality (preventing unauthorized disclosure), integrity (preventing improper alteration or destruction), and availability (ensuring authorized access when needed). In the payroll example, unauthorized viewing threatens confidentiality, while unauthorized changes to payment details threaten integrity. reduction is an ongoing effort to protect what matters, not a promise that harm is impossible.

  • : A measure used to protect information or systems and reduce .