4.1 What Happens When Networks Break or Fail?

Networks don't just carry cat videos and emails. They carry hospital records, power grid signals, and billion-dollar transactions. So when something goes wrong, whether that's a hacker sneaking in or the whole system crashing, the effects can ripple way beyond just "the Wi-Fi is slow." This topic is all about spotting when a network has been compromised and understanding what happens to real organizations when their connections fail.

The CIA Triad: The Foundation of Secure Networks

When people in cybersecurity talk about keeping a network safe, they almost always come back to three ideas. Together, these three form the CIA triad, and they're the foundation of secure and reliable network communication.

• Confidentiality: data are reached only by authorized individuals, systems, or processes. Think of it like a locked diary. Only people with the key get to read it.
• Integrity: data are correct, trustworthy, and unaltered. If someone sneaks in and changes a grade from a C to an A, integrity is broken.
• Availability: authorized entities can actually get to the data and services they need. A bank's website being down means availability is broken, even if nothing was stolen or changed.

Here's the tricky part: these three things often break at the same time. A ransomware attack, for example, might steal data (confidentiality), encrypt and corrupt files (integrity), and lock users out of their systems (availability) all in one shot. That's why breaches tend to hit harder than people expect.

Investigating an Incident

When something goes wrong, you can't just shrug and reboot. Grasping an incident's full scope means figuring out three things:

1. What occurred
2. Who was hit
3. How data or services were affected

To piece that together, investigators dig through a bunch of different sources:

• Access logs (who logged in, when, and from where)
• Alerts raised by firewalls or network monitoring tools
• Error reports from systems and applications
• Files that are missing or corrupted
• Network outages or slowdowns that were reported

Each of these sources gives you a different puzzle piece. Access logs might show a login from Russia at 3 a.m. Firewall alerts might show a huge spike in outbound traffic. Error reports might reveal a program crashing right when the suspicious login happened. Put those pieces together and you start to see the full picture.

Signs of a Confidentiality Breach

A confidentiality compromise leaves systems open to sensitive data being exposed or stolen. Basically, information that was supposed to be private isn't private anymore.

Watch for these signs:

• Access by parties lacking authorization. Someone's account shows activity in a database they shouldn't be touching.
• Network traffic that reveals exfiltration of sensitive data. "Exfiltration" is just a fancy word for data being smuggled out. If you see gigabytes of data leaving your network at 2 a.m. headed to a sketchy IP address, that's exfiltration.
• Credentials that have been exposed. Usernames and passwords showing up on a data leak site, or an employee's login getting posted somewhere.
• Unusual activity involving sensitive data. A payroll file being opened 400 times in an hour when it's normally opened twice a week.

A real example: in a data breach at a healthcare company, you might see one employee's login suddenly pulling thousands of patient records they've never needed before. That's a classic confidentiality red flag.

Signs of an Integrity Breach

An integrity compromise means systems may hold false or inaccurate data. The scary thing is that integrity breaches can be invisible. Everything looks fine, but the data is quietly wrong.

Signs to look for:

• Data altered without authorization. Account balances change, student grades shift, inventory counts don't match.
• Log data containing inconsistencies. Logs with gaps, duplicate entries, or timestamps that don't make sense. Attackers often try to edit logs to cover their tracks.
• Software installed without authorization. New programs appearing on systems that no admin approved. This could be malware or a backdoor.
• Data that has become corrupted. Files that won't open, databases throwing errors, or records that contain garbled text.

Imagine a bank where one day the transaction logs show a $500 transfer, but the next day they show $5,000. If no one authorized the change, that's a serious integrity issue.

Signs of an Availability Breach

An availability compromise means systems go out of service for periods of time that were not expected. This is the type of breach users notice fastest, because they literally can't do their work.

Signs include:

• Being unable to reach systems, networks, or resources. The website won't load, the shared drive won't mount, the app times out.
• Connections that are slow or dropped. Pages taking forever, video calls freezing, downloads dying mid-transfer.
• Network traffic arriving in an unexpectedly high volume. A classic sign of a Distributed Denial of Service (DDoS) attack, where attackers flood the network to overwhelm it.
• Error messages appearing frequently. Lots of "server not responding" or "503 service unavailable" messages piling up.

When a gaming company's servers get hit with a DDoS attack on launch day, millions of players see login errors and connection drops. That's availability under attack.

Why Dependable Connectivity Matters

Network connectivity underpins essential work: communicating with coworkers, reaching data, and providing services to customers. When that connectivity isn't dependable, employees or users can lose access to the systems they need to do their jobs. That lost access leads to delays, mistakes, and lost productivity.

But the impact isn't always the same. How much a loss of connectivity affects an organization varies depending on when the disruption happens and which type of system is hit.

Timing Matters

An outage during peak activity hits way harder than one during a quiet stretch. If Amazon's checkout system goes down for 10 minutes on a random Tuesday afternoon, that's bad. If it goes down for 10 minutes on Black Friday, that's catastrophic. Same outage, wildly different impact.

Low-usage periods (overnight, weekends, holidays for some industries) are when IT teams usually schedule maintenance, because fewer people are affected.

The System Type Matters Too

Not all systems are equal. When critical infrastructure gets disrupted, the consequences can be severe no matter what time it is. Think:

• Water treatment and distribution systems
• Power grids
• Emergency response networks (911, fire, police dispatch)

If a 911 dispatch system goes down at 3 a.m., it's still a disaster. There's no "safe" time for those systems to fail.

Certain sectors are especially sensitive to connectivity issues:

• Healthcare: Hospitals rely on networks for electronic health records, imaging systems, and medication orders. A network outage can literally endanger patients.
• Military: Command, communication, and surveillance systems need to stay online. Outages can compromise missions and safety.
• Food supply chain: Logistics, refrigeration monitoring, and ordering systems all depend on connectivity. Disruptions can lead to spoiled food and shortages.

Long-Term Consequences of Unreliable Networks

A one-time hiccup is annoying but manageable. Network outages that are extended or repeated, though, can cause serious long-term damage. The CED calls out three big ones:

1. Financial Loss

Every minute a system is down can mean missed transactions or lower productivity. For an e-commerce site, that's lost sales. For a factory, it's workers getting paid to stand around. For a bank, it's fees refunded and transfers delayed. These costs add up fast, and some companies have reported losing millions per hour during major outages.

2. Harm to Reputation

If a company becomes known for being unreliable or for leaking customer data, it can deter investors and customers. People remember when their bank's app was down for three days, or when their personal info got leaked. Rebuilding that trust takes years, and some companies never fully recover.

3. Declining Public Trust

This one hits hardest for critical services and public institutions. When a government agency, hospital, or utility company fails repeatedly, people stop believing those institutions can handle their responsibilities. That erosion of public trust has consequences well beyond any single outage. It can affect how people vote, what services they're willing to use, and whether they cooperate with public health or safety measures in the future.

So when you hear about "just" a network outage, remember: there's often a lot more at stake than a loading screen. The CIA triad gives you a framework for spotting what's gone wrong, and understanding the real-world impact helps you see why keeping networks dependable is such a big deal.