PadhaikoAll subjects

Basics of Network and Cyber Security

Network and Cyber Security (ENCT 463)

Open in the Padhaiko app

1.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.

Definition

Network Security and Cyber Security

AspectNetwork SecurityCyber Security
Primary ScopeData in transit, communication channels, routers, switches, and network perimetersEntire digital ecosystem: networks, endpoints, applications, data at rest/in use, and people
Core ControlsFirewalls, ACLs, VPNs, TLS/IPsec, IDS/IPS, NAC, DNS securityAll network controls plus cryptography, endpoint protection, IAM, patching, SIEM, SOC, and policies
Typical Threats AddressedPacket sniffing, ARP spoofing, MITM, DoS/DDoS, port scanning, rogue APsMalware, ransomware, phishing, SQL injection, insider threats, zero-day exploits, data breaches
RelationshipA foundational subset of cyber security focused on connectivity and trafficThe 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.

Definition

The CIA Triad

  1. 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.
  2. 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.
  3. 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.
CIA Triad Violations and Countermeasures
PropertyExample Breach / AttackPrimary Countermeasure
ConfidentialityPacket sniffing on unencrypted Wi-Fi; database leak of customer recordsEncryption at rest (AES) and in transit (TLS 1.3), strict ACLs
IntegrityAttacker alters a bank transfer amount in transit; tampering with system binariesHMAC / Digital signatures, TLS integrity tags, cryptographic checksums
AvailabilityDistributed Denial of Service (DDoS) flooding a web server; ransomware locking filesRate limiting, CDN/scrubbing centers, offline immutable backups

1.3 Security threats and attacks

Definition

Asset, Vulnerability, Threat, Exploit, and Attack

Following RFC 4949 and ITU-T X.800 (Stallings), security attacks are classified along two major axes:

1. Passive vs. Active Attacks

AspectPassive AttacksActive Attacks
NatureEavesdropping on or monitoring transmissions without altering dataModifying data streams, injecting false traffic, or disrupting operations
CIA ImpactViolates Confidentiality onlyViolates Integrity, Availability, and/or Authenticity
Detection vs. PreventionVery 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 ExamplesRelease 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

Four Basic Categories of Security Attacks
CategoryTarget RequirementMechanism of HarmExample
InterruptionAvailabilityAn asset is destroyed, disabled, or becomes unreachableCutting a fiber link, DoS flood, power sabotage
InterceptionConfidentialityAn unauthorized party gains read access to an assetWiretapping, packet sniffing, unauthorized file copying
ModificationIntegrityAn unauthorized party tampers with an assetAltering packets in MITM, changing database grades
FabricationAuthenticity / IntegrityAn unauthorized party inserts counterfeit objects into the systemForged 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)

  1. 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).
  2. Access Control: Prevents unauthorized use of a resource by enforcing who may read, write, or execute what.
  3. 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).
  4. Data Integrity: Assures that data received are exactly as sent by an authorized entity, without modification, insertion, deletion, or replay (with or without recovery).
  5. 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.
  6. Availability Service: Protects a system to ensure its resources remain accessible and usable on demand.

Security Mechanisms (X.800)

Mapping X.800 Security Services to Mechanisms
Security ServicePrimary Supporting Mechanisms
Peer Entity / Data Origin AuthenticationEncipherment, Digital Signature, Authentication Exchange
Access ControlAccess Control Lists (ACLs), RBAC, Security Labels
Data ConfidentialityEncipherment, Routing Control, Traffic Padding (for traffic-flow)
Data IntegrityData Integrity (MAC/Hash), Encipherment, Digital Signature
Non-RepudiationDigital Signature, Data Integrity, Notarization
AvailabilityAuthentication 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

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:

Definition

Quantitative Risk Metrics

A control is financially justified when .

Risk Treatment Strategies

Once risk is assessed, management chooses one of four responses:

  1. 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.
  2. Risk Transfer (Sharing): Shift financial consequences to a third party via cyber insurance or managed-service SLAs.
  3. Risk Avoidance: Discontinue the risky activity or decommission the vulnerable legacy service.
  4. Risk Acceptance: Acknowledge a low or economically non-viable risk and monitor it without extra expenditure.
Example 1

Quantitative Risk Analysis and Safeguard Cost-Benefit (6 marks)

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.

Answer:

; ; ; . 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):

  1. Govern (CSF 2.0): Establish organizational cyber security strategy, roles, policies, and risk oversight.
  2. Identify: Understand assets, systems, data flows, vulnerabilities, and business risk context.
  3. Protect: Implement technical and procedural safeguards (access control, awareness training, data encryption, protective technology) to limit impact.
  4. Detect: Continuously monitor networks and logs to discover anomalies and security events promptly.
  5. Respond: Take action upon a detected incident (response planning, communications, analysis, containment, mitigation).
  6. 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).

AspectNIST Cybersecurity Framework (CSF)ISO/IEC 27001
NatureVoluntary, outcome-focused risk management frameworkInternational, auditable management system standard (ISMS)
CertificationNo formal accredited certificationFormal third-party certification available
Core StructureCore Functions (Govern, Identify, Protect, Detect, Respond, Recover), Tiers, ProfilesClauses 4–10 (PDCA management requirements) + Annex A controls + SoA
Typical UsageRapid maturity benchmarking, executive risk communication, aligning technical controlsDemonstrating formal governance and compliance to regulators, partners, and customers
Example 2

Classifying Attacks and Selecting X.800 Services (Exam Model) (6 marks)

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.
Answer:

(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.

Example 3

Mapping a Security Program to NIST CSF and ISO 27001 PDCA (5 marks)

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.
Answer:

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

Question 1

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.

Answer:

; ; ; . Deploy the safeguard.

Question 2

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).

Answer:

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).

Question 3

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).
Answer:

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.

Question 4

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. ).

Answer:

and ; Control A is the better financial investment.

Question 5

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.
Answer:

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.

Cryptography →