Read a sample: 1. What a Cybersecurity Risk Review Can Do
A cybersecurity risk review begins with a business question: What could interfere with work that matters, and what should we do about it?
The question sounds simple, but answering it requires more than a list of security products. A scheduling application may have a strong password policy, for example, while the only person who knows how to restore its data is unavailable. A supplier may protect its systems carefully, but an outage could still prevent your organization from serving customers. A shared account may make a busy team more efficient while making it difficult to tell who changed an important record.
A review brings those practical details into view. It connects technology to the work it supports, considers credible ways that work could be harmed, and gives decision-makers a basis for choosing what to address. The first review does not need to cover every system or predict every incident. It needs to be clear enough that someone can understand the reasoning, challenge an assumption, and take a useful next step.
This chapter introduces the building blocks of that work. It also introduces a fictional organization that will appear throughout the book, so you can see how an initial concern develops into a documented risk decision.
Organizations face more potential cybersecurity problems than they can address at once. Even a small organization may rely on email, shared files, cloud applications, laptops, outside service providers, and a handful of people with specialized knowledge. Each dependency creates questions worth asking, but not every question has the same urgency.
A cybersecurity risk review helps organize those questions. At its most useful, it shows:
- What business activity is being reviewed and why it matters.
- Which assets and dependencies support that activity.
- What plausible events could affect those assets.
- What consequences could follow for the organization.
- Which safeguards are already in place and what is known about them.
- Which risks need a decision, who can make it, and what happens next.
The output is not simply a declaration that an organization is “secure” or “insecure.” Security is not a fixed state established by completing a worksheet. Systems change, people change roles, suppliers change services, and safeguards can fail or be used differently than intended. A review captures a reasoned view at a particular point in time and provides a way to revisit it.
That view can support several kinds of decisions. A manager might approve a recovery test, assign an owner to an important application, or ask for a comparison of account-access options. A team might discover that it does not yet know enough to rate a risk confidently and make gathering evidence its next action. Even deciding to defer an improvement can be useful if the decision, its rationale, and its owner are recorded.
A first review can make dependencies visible, expose gaps in ownership, and turn vague concerns into scenarios people can discuss. It can also help an organization focus limited time on issues with meaningful consequences.
It cannot, by itself, prove that an environment is free of weaknesses. Interviewing an application administrator is not the same as testing every configuration. Reviewing a written backup procedure is not the same as restoring data from a backup. Seeing that a control exists is not necessarily evidence that it is operating effectively.
An initial review is also different from several related activities:
- An asset inventory identifies and describes resources. A risk review uses that information to consider what could happen to them.
- A vulnerability assessment looks for weaknesses, often with technical tools. Its findings can inform a risk review, but a weakness matters differently depending on what it exposes and what the consequences could be.
- A penetration test attempts to demonstrate whether selected weaknesses can be exploited within an agreed scope. It can provide valuable evidence, but it does not describe every business risk.
- An audit assesses evidence against defined criteria. A risk review may use audit results, but its purpose here is to support decisions about uncertain future events.
These activities can overlap. A review might recommend a vulnerability assessment where technical evidence is missing, or an audit finding might prompt a closer look at a business process. None is automatically a substitute for the others.
The boundary of the review matters just as much as its name. If the team examines one scheduling process, it should not imply that every department and system has been assessed. A useful report states what was included, what was left out, and what the reviewers could not verify.
Risk terminology can feel abstract until the terms are connected to a real activity. The distinctions below will help you describe a concern without mixing up its cause, consequence, and possible remedy.
An asset is something of value to the organization that supports its objectives. It might be information, an application, a device, an account, a service, a physical resource, or specialized knowledge. An asset does not have to be owned outright. A cloud service can be essential to your work even though a supplier operates it.
A threat is a potential cause of harm. A threat may involve a malicious actor, an accidental action, a technical failure, or another event that could adversely affect an asset. “An employee accidentally deletes a shared file” and “an attacker uses stolen credentials” describe different threat events.
A vulnerability is a weakness that…