Systems Security

students, imagine a school network where students submit assignments, teachers store grades, and everyone uses the same internet connection 📱💻. If one person steals passwords, installs malware, or changes files without permission, the whole system can be affected. That is why systems security matters. In IB Computer Science HL, systems security is part of System Fundamentals because a computer system is not only hardware and software, but also the people, data, and procedures that keep it working safely.

In this lesson, you will learn how to:

• explain the main ideas and terminology behind systems security,
• apply IB Computer Science HL reasoning to security situations,
• connect security to system architecture, data management, and ethics,
• and summarize why security is essential in real systems.

By the end, students, you should be able to describe common threats, explain how organizations protect systems, and support your answers with real-world examples.

What systems security means

Systems security is the protection of computer systems from unauthorized access, damage, theft, or disruption. A secure system tries to keep data and services available to the right people at the right time. In practice, security is often described using three key goals called the CIA triad:

• Confidentiality means information is only seen by authorized users.
• Integrity means data is accurate and has not been changed improperly.
• Availability means systems and data are accessible when needed.

These ideas are easy to remember, but they are also deeply connected. For example, a hospital database must keep patient records confidential, accurate, and available 24/7. If a ransomware attack locks access to records, availability is damaged. If someone edits test results, integrity is damaged. If personal health data is leaked, confidentiality is damaged.

Security also depends on knowing the difference between a threat, a vulnerability, and an attack. A threat is anything that could cause harm, such as malware or a dishonest employee. A vulnerability is a weakness in the system, such as a weak password or outdated software. An attack is the actual attempt to exploit that weakness. students, this distinction is important in IB questions because you may need to identify not only what went wrong, but also why it was possible.

Common threats and attacks

Computer systems face many different kinds of threats. Some are technical, while others involve human behavior. Understanding these helps you explain why security controls are needed.

One major threat is malware, short for malicious software. Malware includes viruses, worms, trojans, spyware, and ransomware. A virus attaches itself to a file or program and spreads when the file is run. A worm can spread across networks on its own. A trojan looks useful but hides harmful code. Spyware secretly gathers information. Ransomware encrypts files and demands payment for access.

Another common threat is phishing 🎣. Phishing uses fake emails, websites, or messages to trick users into giving away passwords, credit card numbers, or other sensitive data. For example, a message that looks like it came from a bank may ask a user to “verify” a login. If the user enters details into the fake site, the attacker gains access.

There are also attacks that target the way a system is built. A brute-force attack tries many password combinations until one works. A denial-of-service attack attempts to overload a server so legitimate users cannot connect. A man-in-the-middle attack intercepts communication between two parties. If data is sent without encryption on an unsafe network, an attacker may read or alter it.

Human error is also a security risk. Someone might reuse passwords, leave a device unlocked, or accidentally send private data to the wrong person. In many cases, the weakest part of a system is not the hardware or software but the people using it.

Security controls and how they protect systems

To reduce risk, organizations use security controls. These are methods that prevent attacks, detect problems, or help recover after an incident. In IB Computer Science HL, it is useful to group controls by purpose.

Preventive controls try to stop security problems before they happen. Examples include strong passwords, multi-factor authentication, encryption, secure software design, firewalls, and access control lists. A password is a secret value, but by itself it may not be enough. Multi-factor authentication adds another step, such as a code from a phone, making it harder for an attacker to log in.

Detective controls identify suspicious activity. Examples include intrusion detection systems, log files, antivirus alerts, and security monitoring. A company may not stop every attack, but it should be able to notice unusual behavior, such as repeated failed logins or large data transfers at odd times.

Corrective controls help restore systems after a problem. Backups are a very important example. If files are lost, encrypted by ransomware, or accidentally deleted, a backup allows recovery. Disaster recovery plans and patching procedures also belong here because they help fix weaknesses and restore normal operation.

Encryption is one of the most important security tools. It changes readable data into a coded form using an algorithm and a key. If encrypted data is intercepted, it is much harder to understand without the key. For example, online banking uses encryption so that account details cannot be easily read by outsiders. In IB terms, encryption supports confidentiality.

Authentication and authorization are often confused, students, but they are different. Authentication checks who a user is. Authorization checks what that user is allowed to do. A student logging into the school portal is authenticated with a password, but they are not authorized to edit teacher-only grade records. Access control depends on this difference.

Security policies, procedures, and user behavior

Systems security is not only about software settings. It also depends on policy and practice. A security policy is a set of rules an organization follows to protect its systems and data. Policies may cover password strength, acceptable use, data retention, device management, and what to do if a breach occurs.

For example, a school might require students to change passwords regularly, lock screens when leaving devices unattended, and never share accounts. A business might restrict USB storage devices or require employees to update software promptly. These rules reduce the chance of accidental leaks or unauthorized access.

Procedures matter too. A secure organization may train staff to spot phishing emails, report suspicious links, and verify unusual requests by phone or in person. This matters because attackers often rely on social engineering, which means manipulating people rather than breaking the technology directly.

A practical example is a finance office receiving an email asking for an urgent payment change. If employees follow a verification procedure, they can confirm the request using a trusted phone number before sending money. This simple step can prevent fraud.

Security in the wider System Fundamentals topic

Systems security connects to many other parts of System Fundamentals. In system architecture, security features may be built into hardware and software layers. For example, a firewall can filter network traffic, and a processor may support secure boot features that help verify trusted software starts correctly.

In data representation, security may involve hashing. A hash function turns data into a fixed-length value. If even one bit changes, the hash usually changes too. This is useful for checking whether files have been altered. Passwords are often stored as hashes rather than in plain text, so the original password is not directly exposed.

In computer performance and management, security affects speed and reliability. Encryption, real-time scanning, and logging can use resources, which may slow a system slightly. However, these costs are often necessary to protect important data. Organizations must balance performance and security carefully.

Security also links to ethics and social impact. Protecting user data is part of responsible computing. Poor security can lead to identity theft, financial loss, privacy violations, and reputational damage. At the same time, strong security must respect legal and ethical boundaries. For example, monitoring employee devices may improve safety, but it should be done transparently and according to policy.

students, IB Computer Science HL often expects you to explain trade-offs. A system with maximum security may be harder to use, while a very convenient system may be less secure. Real-world design requires balance.

How to apply IB-style reasoning

When answering exam questions about systems security, start by naming the threat or control clearly, then explain how it works, and finally link it to the system outcome. This structure helps you earn marks because it shows understanding, not just memorization.

For example, if asked why multi-factor authentication improves security, you could explain that it requires more than one proof of identity, so a stolen password alone is not enough for access. That improves confidentiality and reduces unauthorized access.

If asked how backups help after a ransomware attack, you could explain that backups allow the organization to restore data without paying the attacker. This supports availability and reduces the impact of data loss.

If asked to compare a firewall and antivirus software, note that a firewall controls network traffic while antivirus scans files and processes for known malware. They protect against different parts of the threat landscape, so they are often used together.

In longer responses, always connect the control to the threat it reduces. For instance, encryption protects against data interception, access control limits who can view or edit files, and user training reduces phishing success. This is the kind of clear reasoning that IB Computer Science HL values.

Conclusion

Systems security is about protecting computer systems, data, and users from harm. It includes understanding threats such as malware, phishing, and unauthorized access, as well as using controls like encryption, authentication, firewalls, backups, and policies. It also connects strongly to other parts of System Fundamentals because security affects architecture, data handling, performance, and ethics.

students, the key idea is that security is not a single tool. It is a combination of technology, procedures, and responsible human behavior. A strong system protects confidentiality, integrity, and availability while still being practical to use. That balance is central to real computing systems and to success in IB Computer Science HL.

Study Notes

• Systems security protects computer systems from unauthorized access, damage, theft, and disruption.
• The CIA triad means confidentiality, integrity, and availability.
• A threat is a possible cause of harm, a vulnerability is a weakness, and an attack is an attempt to exploit it.
• Common threats include malware, phishing, brute-force attacks, denial-of-service attacks, and man-in-the-middle attacks.
• Malware includes viruses, worms, trojans, spyware, and ransomware.
• Security controls can be preventive, detective, or corrective.
• Encryption protects confidentiality by making data unreadable without the correct key.
• Authentication proves identity; authorization determines access rights.
• Security policies and user training are essential because human behavior is often the weakest link.
• Backups support recovery and help protect availability after data loss or ransomware.
• Hashing can help detect changes to data and store passwords more safely.
• Systems security connects to architecture, data representation, performance, management, ethics, and social impact.
• IB-style answers should name the issue, explain how it works, and link it to the security goal it affects.