Read a sample: 1. Reading the Network as a Security System
A network is more than a collection of cables, wireless signals, and devices. It is a system that lets people and software reach resources. Every connection that supports legitimate work also creates a question: who or what can use that path, and under what conditions?
Consider a small accounting firm called Cedar Brook. Its employees use laptops to access shared files, a cloud-based bookkeeping application, and a network printer. A wireless network serves employees, while visitors need internet access. Some staff members work from home, and an outside technician occasionally maintains the firm’s equipment.
At first glance, Cedar Brook’s network might seem straightforward: connect the devices, provide internet access, and make sure the applications work. A security-minded view asks additional questions. Can a visitor’s phone reach the file server? Can a stolen employee password be used from an unknown device? Would the firm notice unusual connections from a laptop to many internal systems?
These questions do not require memorizing every product or protocol. They require a way to read the network as a security system: identify what matters, understand what could go wrong, and choose controls that fit the paths and risks involved.
Security decisions begin with assets: things an organization values and needs to protect. An asset can be a physical device, but it can also be information, a service, an account, or the ability to perform a business process.
At Cedar Brook, important assets include client financial records, employee credentials, the shared file service, and the laptops used to access that service. The internet connection matters too, because losing it could interrupt access to the cloud application. Even an administrator account is an asset: it provides authority over systems that support the business.
Not every asset has the same importance. A public brochure on the firm’s website is intended to be read by anyone, so its secrecy may not matter. Its accuracy still matters; an unauthorized change to payment instructions could harm clients. Client financial records, by contrast, need both privacy and accuracy. The booking system must also be available when staff need to serve clients.
This distinction leads to three familiar security objectives:
- Confidentiality means information is accessible only to authorized parties.
- Integrity means information and systems are protected against improper modification or destruction, and changes can be trusted.
- Availability means authorized users can access information and services when needed.
These objectives are often called the CIA triad. They are useful because they turn a vague requirement such as “secure the server” into questions that can guide control selection.
If an employee sends a client record over an exposed connection, confidentiality is a primary concern. If an attacker changes bank details in that record, integrity is at risk. If ransomware makes the file service unusable, availability is affected, and integrity and confidentiality may be affected as well.
A single incident can threaten more than one objective. Likewise, a control can support several objectives without solving all of them. Encryption can help protect confidentiality and, when used with appropriate integrity protections, help detect tampering in transit. It does not by itself ensure that the service is available or that the person requesting the data is authorized to receive it.
Security terminology becomes easier to apply when each term answers a different question.
A threat is a potential cause of harm. Threats can include a criminal attempting to steal records, an employee making a mistake, malware, or a power failure. A threat actor is an individual or group that acts, such as an attacker using stolen credentials.
A vulnerability is a weakness that could be exploited or otherwise contribute to harm. An unpatched network appliance, an unnecessarily exposed management interface, and a poorly configured access rule are examples. A vulnerability can exist even if no attacker has discovered it.
An exploit is a method or action used to take advantage of a vulnerability. For example, an attacker might use a known software flaw to execute commands on an unpatched appliance. The flaw is the vulnerability; the attacker is the threat actor; the action that takes advantage of the flaw is the exploit.
Risk describes the possibility of loss or harm when a threat affects an asset, often by exploiting a vulnerability. Risk assessment considers both the likelihood of an event and its potential impact. It does not require a precise numerical score to be useful.
Suppose Cedar Brook’s file server contains sensitive client records and is reachable from the visitor wireless network. The records and server are assets. The unnecessary network reachability is a weakness in the design. A malicious visitor is one possible threat actor. If that person can exploit another weakness in the server or obtain valid credentials, the resulting impact might include exposure or alteration of records.
This example also shows why context matters. Merely being able to reach a server does not automatically grant access to its files. Authentication and permissions may still stop a visitor. Nevertheless, unnecessary reachability gives an attacker an opportunity to probe services or attempt logins that could have been avoided.
The attack surface is the set of points where an attacker might interact with or attempt to enter a system. On a network, it includes exposed services, remote access interfaces, wireless access, management interfaces, and other reachable paths. It also includes less obvious opportunities, such as an employee opening a malicious attachment that initiates an outbound connection.