Basics of Network and Cyber Security
Open in the Padhaiko app1.1 Introduction to Network and Cyber Security
Modern organizations rely on interconnected computer networks, cloud platforms, and mobile endpoints to store, process, and transmit critical information. Every connection that enables productivity also introduces an attack surface—the sum of all points (open ports, web forms, wireless links, user accounts, and physical interfaces) through which an unauthorized party can attempt to enter or extract data.
Network Security and Cyber Security
- Network Security: The set of policies, architectures, protocols, and controls (such as firewalls, VPNs, IDS/IPS, and TLS) designed to protect data in transit across wired and wireless communication links and to safeguard the underlying network infrastructure against unauthorized access, misuse, modification, or denial.
- Cyber Security: The broader discipline of protecting all digital assets—networks, hosts, applications, cloud workloads, data at rest, and human users—against cyber threats across cyberspace, encompassing technical defenses, risk management, incident response, governance, and legal compliance.
| Aspect | Network Security | Cyber Security |
|---|---|---|
| Primary Scope | Data in transit, communication channels, routers, switches, and network perimeters | Entire digital ecosystem: networks, endpoints, applications, data at rest/in use, and people |
| Core Controls | Firewalls, ACLs, VPNs, TLS/IPsec, IDS/IPS, NAC, DNS security | All network controls plus cryptography, endpoint protection, IAM, patching, SIEM, SOC, and policies |
| Typical Threats Addressed | Packet sniffing, ARP spoofing, MITM, DoS/DDoS, port scanning, rogue APs | Malware, ransomware, phishing, SQL injection, insider threats, zero-day exploits, data breaches |
| Relationship | A foundational subset of cyber security focused on connectivity and traffic | The overarching umbrella covering technical, operational, and governance security |
Effective security follows Defense in Depth (layered security): instead of relying on a single perimeter firewall, multiple independent layers (physical, network perimeter, host/OS, application, data/cryptography, and user awareness) ensure that if one control fails, subsequent layers contain the breach.
1.2 Basic security requirements: Confidentiality, Integrity, Availability
The foundational model of information and network security is the CIA Triad: Confidentiality, Integrity, and Availability. Every security requirement, mechanism, and policy is built to uphold one or more of these three properties.
The CIA Triad
- Confidentiality: Ensures that sensitive information is not disclosed or made available to unauthorized individuals, entities, or processes.
- Key aspects: Data secrecy (protecting content via encryption) and privacy (preventing unauthorized traffic analysis or personal data exposure).
- Mechanisms: Symmetric/asymmetric encryption (AES, RSA), TLS/VPN tunnels, access control lists (ACLs), and masking.
- Integrity: Ensures that data and system resources are accurate, complete, and trustworthy, and have not been altered, inserted, deleted, or replayed in an unauthorized or undetected manner.
- Key aspects: Data integrity (messages and files remain unmodified) and system integrity (OS/application binaries perform intended functions without tampering).
- Mechanisms: Cryptographic hash functions (SHA-256), Message Authentication Codes (HMAC), digital signatures, and file integrity monitoring.
- Availability: Ensures that authorized users have timely, reliable, and uninterrupted access to systems, networks, and information whenever required.
- Mechanisms: Redundancy (RAID, failover clusters), load balancing, DDoS mitigation, regular backups, UPS power, and timely patching.
| Property | Example Breach / Attack | Primary Countermeasure |
|---|---|---|
| Confidentiality | Packet sniffing on unencrypted Wi-Fi; database leak of customer records | Encryption at rest (AES) and in transit (TLS 1.3), strict ACLs |
| Integrity | Attacker alters a bank transfer amount in transit; tampering with system binaries | HMAC / Digital signatures, TLS integrity tags, cryptographic checksums |
| Availability | Distributed Denial of Service (DDoS) flooding a web server; ransomware locking files | Rate limiting, CDN/scrubbing centers, offline immutable backups |
1.3 Security threats and attacks
Asset, Vulnerability, Threat, Exploit, and Attack
- Asset: Any hardware, software, data, service, or reputation of value to an organization.
- Vulnerability: A weakness or flaw in system design, implementation, configuration, or human behavior that can be exploited to violate security policy.
- Threat: A potential circumstance or agent capable of exploiting a vulnerability and causing harm to an asset.
- Exploit: A specific technique, payload, or piece of code that takes advantage of a vulnerability.
- Attack: An intentional, realized action by a threat actor that attempts to bypass security controls to compromise confidentiality, integrity, or availability.
Following RFC 4949 and ITU-T X.800 (Stallings), security attacks are classified along two major axes:
1. Passive vs. Active Attacks
| Aspect | Passive Attacks | Active Attacks |
|---|---|---|
| Nature | Eavesdropping on or monitoring transmissions without altering data | Modifying data streams, injecting false traffic, or disrupting operations |
| CIA Impact | Violates Confidentiality only | Violates Integrity, Availability, and/or Authenticity |
| Detection vs. Prevention | Very hard to detect (no trace left on the wire); focus is on prevention (encryption) | Easier to detect via anomalies/logs; hard to prevent completely, so focus is on detection and recovery |
| Standard Examples | Release of message contents (sniffing plaintext email/HTTP); Traffic analysis (observing packet frequency, size, and endpoints even when encrypted) | Masquerade (impersonation), Replay (retransmitting captured valid packets), Modification of messages, Denial of Service (DoS) |
2. Threat Categories by Information Flow
| Category | Target Requirement | Mechanism of Harm | Example |
|---|---|---|---|
| Interruption | Availability | An asset is destroyed, disabled, or becomes unreachable | Cutting a fiber link, DoS flood, power sabotage |
| Interception | Confidentiality | An unauthorized party gains read access to an asset | Wiretapping, packet sniffing, unauthorized file copying |
| Modification | Integrity | An unauthorized party tampers with an asset | Altering packets in MITM, changing database grades |
| Fabrication | Authenticity / Integrity | An unauthorized party inserts counterfeit objects into the system | Forged email/ARP replies, injecting fake database rows |
1.4 Security services and mechanisms
The ITU-T X.800 Security Architecture defines a systematic framework linking what protection is needed (Security Services) to how it is implemented (Security Mechanisms).
Security Services (X.800)
- Authentication: Assures that a communicating entity is the one it claims to be.
- Peer Entity Authentication: Verifies identities of communicating parties during a connection (e.g., mutual TLS handshake).
- Data Origin Authentication: Verifies the source of a received data unit in connectionless communication (does not by itself protect against replay).
- Access Control: Prevents unauthorized use of a resource by enforcing who may read, write, or execute what.
- Data Confidentiality: Protects transmitted data from passive eavesdropping:
- Connection Confidentiality (entire stream on a session), Connectionless Confidentiality (single datagram), Selective-Field Confidentiality (specific fields), and Traffic-Flow Confidentiality (hiding traffic patterns).
- Data Integrity: Assures that data received are exactly as sent by an authorized entity, without modification, insertion, deletion, or replay (with or without recovery).
- Non-Repudiation: Prevents either party from denying a past communication:
- Non-repudiation, Origin: Proof that the sender actually sent the message.
- Non-repudiation, Destination: Proof that the intended recipient actually received the message.
- Availability Service: Protects a system to ensure its resources remain accessible and usable on demand.
Security Mechanisms (X.800)
- Specific Security Mechanisms (implemented in specific protocol layers):
- Encipherment: Using mathematical algorithms to transform plaintext into unintelligible ciphertext.
- Digital Signature: Appending cryptographic data derived from the sender's private key to prove origin and integrity.
- Access Control: Enforcing resource permissions (ACLs, capability lists, RBAC).
- Data Integrity: Appending checksums, cryptographic hashes, or MACs to detect tampering.
- Authentication Exchange: Challenge–response protocols or credential exchanges to verify identity.
- Traffic Padding: Inserting dummy bits/packets into gaps to defeat traffic analysis.
- Routing Control: Selecting physically or cryptographically trusted network paths for sensitive traffic.
- Notarization: Using a trusted third party (TTP) to record and certify properties like timestamp, origin, or delivery.
- Pervasive Security Mechanisms (not tied to any single service or protocol layer): Trusted Functionality, Security Labels, Event Detection, Security Audit Trails, and Security Recovery.
| Security Service | Primary Supporting Mechanisms |
|---|---|
| Peer Entity / Data Origin Authentication | Encipherment, Digital Signature, Authentication Exchange |
| Access Control | Access Control Lists (ACLs), RBAC, Security Labels |
| Data Confidentiality | Encipherment, Routing Control, Traffic Padding (for traffic-flow) |
| Data Integrity | Data Integrity (MAC/Hash), Encipherment, Digital Signature |
| Non-Repudiation | Digital Signature, Data Integrity, Notarization |
| Availability | Authentication Exchange (rate-limited), Routing Control, Event Detection |
1.5 Risk management and vulnerabilities
No system can achieve zero risk at finite cost. Risk management is the ongoing process of identifying vulnerabilities and threats, estimating their business impact, and selecting cost-effective controls to bring risk within an acceptable threshold (risk appetite).
Common Vulnerability Categories
- Software & Design Flaws: Buffer overflows, SQL injection, improper input validation, race conditions, and unpatched CVEs.
- Configuration & Operational Weaknesses: Default vendor passwords, open cloud storage buckets, unnecessary open ports, missing TLS, and overly permissive firewall rules.
- Human & Procedural Weaknesses: Susceptibility to phishing, password reuse, lack of security awareness, and missing change-control checks.
Qualitative vs. Quantitative Risk Analysis
Qualitatively, risk is expressed as an interplay of threat, vulnerability, and asset impact:
In quantitative risk analysis, monetary estimates are computed using standard metrics:
Quantitative Risk Metrics
- Asset Value (): Total monetary value of the asset (hardware, data, and operational value).
- Exposure Factor (): Percentage ( to , or to ) of the asset's value lost if a specific threat occurs.
- Single Loss Expectancy (): Expected monetary loss from a single occurrence of the threat:
- Annualized Rate of Occurrence (): Expected number of times the threat occurs per year (e.g., once in 4 years gives ).
- Annualized Loss Expectancy (): Expected yearly monetary loss due to that threat:
- Cost–Benefit Analysis () of a Safeguard: Net annual savings after paying the Annualized Cost of Safeguard () to reduce from to :
A control is financially justified when .
Risk Treatment Strategies
Once risk is assessed, management chooses one of four responses:
- Risk Mitigation (Reduction): Deploy technical or administrative controls (e.g., patching, MFA, firewalls) to lower likelihood or impact. The remaining risk after controls is called residual risk.
- Risk Transfer (Sharing): Shift financial consequences to a third party via cyber insurance or managed-service SLAs.
- Risk Avoidance: Discontinue the risky activity or decommission the vulnerable legacy service.
- Risk Acceptance: Acknowledge a low or economically non-viable risk and monitor it without extra expenditure.
Quantitative Risk Analysis and Safeguard Cost-Benefit
An organization's e-commerce database server has an Asset Value () of . A ransomware incident causes an Exposure Factor () of and is estimated to occur once every . Management is evaluating an endpoint detection and backup control costing per year that reduces the expected occurrence rate to once every (keeping unchanged). Compute , , , and , and determine whether the safeguard is financially justified.
Compute the Single Loss Expectancy (): With and :
Compute and :
Compute the Cost–Benefit Analysis (): With Annualized Cost of Safeguard :
Since , the safeguard yields a net saving of per year and should be deployed.
; ; ; . The safeguard is financially justified.
1.6 Cyber Security Frameworks (NIST, ISO/IEC 27001)
Cyber security frameworks give organizations a structured, repeatable vocabulary and set of controls to manage risk, align security with business goals, and demonstrate compliance.
1. NIST Cybersecurity Framework (CSF)
Developed by the US National Institute of Standards and Technology, the NIST CSF organizes cyber security activities into core outcome functions. Traditionally structured around five core functions (with Govern added as a sixth overarching function in NIST CSF 2.0):
- Govern (CSF 2.0): Establish organizational cyber security strategy, roles, policies, and risk oversight.
- Identify: Understand assets, systems, data flows, vulnerabilities, and business risk context.
- Protect: Implement technical and procedural safeguards (access control, awareness training, data encryption, protective technology) to limit impact.
- Detect: Continuously monitor networks and logs to discover anomalies and security events promptly.
- Respond: Take action upon a detected incident (response planning, communications, analysis, containment, mitigation).
- Recover: Restore impaired capabilities and services, apply lessons learned, and communicate recovery status.
2. ISO/IEC 27001
ISO/IEC 27001 is the leading international, certifiable standard for establishing, implementing, maintaining, and continually improving an Information Security Management System (ISMS).
- Risk-Based ISMS & PDCA Cycle: ISO/IEC 27001 operates on the Plan–Do–Check–Act (PDCA) continual-improvement model:
- Plan: Define ISMS scope, policy, risk assessment, and risk treatment plan.
- Do: Implement selected controls and operational procedures.
- Check: Monitor, measure, conduct internal audits, and perform management reviews.
- Act: Take corrective actions to close non-conformities and improve the ISMS.
- Annex A & Statement of Applicability (SoA): Annex A provides a catalog of security controls (grouped in ISO/IEC 27001:2022 into Organizational, People, Physical, and Technological controls). The Statement of Applicability (SoA) documents which Annex A controls are applicable, justified, and implemented.
| Aspect | NIST Cybersecurity Framework (CSF) | ISO/IEC 27001 |
|---|---|---|
| Nature | Voluntary, outcome-focused risk management framework | International, auditable management system standard (ISMS) |
| Certification | No formal accredited certification | Formal third-party certification available |
| Core Structure | Core Functions (Govern, Identify, Protect, Detect, Respond, Recover), Tiers, Profiles | Clauses 4–10 (PDCA management requirements) + Annex A controls + SoA |
| Typical Usage | Rapid maturity benchmarking, executive risk communication, aligning technical controls | Demonstrating formal governance and compliance to regulators, partners, and customers |
Classifying Attacks and Selecting X.800 Services (Exam Model)
Analyze the following three incidents using X.800 attack classifications, identify the compromised CIA property, and specify the appropriate X.800 security service and mechanism to counter each: (a) An attacker captures unencrypted login packets on a campus LAN. (b) An attacker intercepts an online payment request and changes the payee account number before forwarding it. (c) An attacker captures a valid authentication token and resends it an hour later to gain access.
Analyze Incident (a) — Unencrypted Packet Capture:
- Attack Type: Passive attack (release of message contents / interception).
- CIA Impact: Violates Confidentiality.
- Countermeasure: Data Confidentiality service implemented via the Encipherment mechanism (e.g., TLS encrypting the session).
Analyze Incident (b) — Altering Payee Account Number:
- Attack Type: Active attack (modification of messages).
- CIA Impact: Violates Integrity.
- Countermeasure: Data Integrity service (and Data Origin Authentication) implemented via Data Integrity mechanisms (HMAC) or Digital Signatures.
Analyze Incident (c) — Resending a Valid Authentication Token:
- Attack Type: Active attack (replay attack).
- CIA Impact: Violates Authenticity (and threatens Confidentiality/Integrity of the target account).
- Countermeasure: Peer Entity / Data Origin Authentication and Data Integrity (with replay detection) implemented via Authentication Exchange incorporating nonces, sequence numbers, or strict timestamps.
(a) Passive interception Confidentiality Data Confidentiality + Encipherment. (b) Active modification Integrity Data Integrity + HMAC/Digital Signature. (c) Active replay Authenticity Authentication Exchange with nonces/timestamps.
Mapping a Security Program to NIST CSF and ISO 27001 PDCA
A university IT department wants to secure its student portal. It inventories all servers, enforces MFA, deploys a SIEM to alert on brute-force logins, isolates compromised hosts within 15 minutes, and restores databases from daily backups. Map each action to the NIST CSF core functions and explain how the cycle maps onto ISO/IEC 27001 PDCA.
Map each technical control to NIST CSF Core Functions:
- Server inventory: Identify (asset management).
- Enforcing MFA: Protect (identity management and access control).
- SIEM alerting on brute-force logins: Detect (anomalies and continuous monitoring).
- Isolating compromised hosts: Respond (mitigation and containment).
- Restoring databases from backups: Recover (recovery planning and restoration).
Connect to the ISO/IEC 27001 PDCA cycle:
- Plan: Inventory assets, assess risks on the student portal, and document chosen controls (MFA, SIEM, backups) in the risk treatment plan and SoA.
- Do: Deploy and operate MFA, SIEM rules, isolation runbooks, and daily backups.
- Check: Review SIEM alerts, test backup restoration, and run internal ISMS audits.
- Act: Tune detection rules and strengthen access controls after drills or incidents to close gaps.
The five actions map cleanly onto Identify Protect Detect Respond Recover in NIST CSF, while ISO/IEC 27001 governs their planning, execution, audit, and continual improvement through the PDCA cycle.
Exercises
A research server worth faces a hardware/data corruption threat with an Exposure Factor () of and an Annualized Rate of Occurrence () of . A high-availability clustering solution costs and lowers to while keeping unchanged. Calculate , , , and , and state your recommendation.
Compute Single Loss Expectancy ():
Compute Annualized Loss Expectancy before and after the safeguard:
Compute Cost–Benefit Analysis ():
Because , implementing the safeguard is cost-effective.
; ; ; . Deploy the safeguard.
Define the CIA Triad and explain how each property differs from the others, giving one concrete network security attack and one countermeasure for each.
Define Confidentiality, Integrity, and Availability:
- Confidentiality keeps data secret from unauthorized observers (attack: sniffing unencrypted HTTP traffic; countermeasure: TLS encryption).
- Integrity protects data from unauthorized modification or forgery (attack: MITM tampering with a routing update or transaction payload; countermeasure: HMAC or digital signatures).
- Availability guarantees timely access to resources by legitimate users (attack: SYN flood DDoS exhausting server sockets; countermeasure: SYN cookies, rate limiting, and upstream scrubbing).
Explain the distinction: Confidentiality concerns who can read data, Integrity concerns whether data is genuine and unaltered, and Availability concerns whether the system and data remain reachable when needed. A system can preserve confidentiality (encrypted data) while still losing integrity (corrupted ciphertext) or availability (flooded link).
Confidentiality (secrecy vs. sniffing, countered by encryption), Integrity (accuracy/non-tampering vs. MITM alteration, countered by HMAC/signatures), and Availability (timely access vs. DDoS, countered by redundancy/rate limiting).
Distinguish between passive and active attacks under ITU-T X.800, explaining why passive attacks are harder to detect and naming two subtypes of each.
Compare Passive and Active Attacks:
- Passive attacks monitor or eavesdrop on transmissions without altering packet contents or disrupting the link. Because the communication proceeds normally and leaves no modification artifact on the channel, passive attacks are very difficult to detect; defense therefore emphasizes prevention via encryption and traffic padding. Subtypes: release of message contents and traffic analysis.
- Active attacks alter data streams, inject fabricated messages, or disrupt service. Because they change state, cause checksum/signature failures, or degrade service, they are easier to detect; defense combines prevention, detection, and recovery. Subtypes: masquerade, replay, modification of messages, and denial of service (any two).
Passive attacks (release of message contents, traffic analysis) compromise confidentiality without altering data, making detection hard and requiring encryption. Active attacks (masquerade, replay, modification, DoS) alter data or availability, making detection feasible via integrity checks and monitoring.
An asset valued at suffers with . Two mutually exclusive controls are proposed: Control A costs and lowers to ; Control B costs and lowers to . Compare their values and select the better investment.
Compute and :
Evaluate Control A and Control B:
Although Control B yields lower residual loss, Control A delivers a higher net annual benefit ( vs. ).
and ; Control A is the better financial investment.
Compare the NIST Cybersecurity Framework (CSF) and ISO/IEC 27001, and describe the four phases of the PDCA cycle in an ISO/IEC 27001 ISMS.
Compare NIST CSF and ISO/IEC 27001:
- NIST CSF is a voluntary, outcome-based framework organized around Core Functions (Govern, Identify, Protect, Detect, Respond, Recover), Implementation Tiers, and Profiles. It excels at rapid gap assessment and technical alignment without formal certification.
- ISO/IEC 27001 is a certifiable international management system standard requiring a formal ISMS, risk assessment, risk treatment, Statement of Applicability (SoA), and Annex A controls.
Describe the PDCA Cycle in an ISMS:
- Plan: Establish ISMS scope, security policy, risk assessment methodology, and risk treatment plan.
- Do: Implement and operate the selected Annex A security controls and train personnel.
- Check: Monitor security metrics, conduct internal audits, and perform management reviews.
- Act: Execute corrective and preventive actions to remediate gaps and continually improve the ISMS.
NIST CSF provides flexible outcome functions (Govern, Identify, Protect, Detect, Respond, Recover) without certification, whereas ISO/IEC 27001 defines a certifiable ISMS governed by Annex A controls and the Plan–Do–Check–Act (PDCA) continual improvement cycle.