CIE IGCSE | TOPIC 5

THE INTERNET AND ITS USES REVISION

Review the internet and web, browser functions, page retrieval, cookies, digital currency, security threats and protection methods. Build a focused revision list.

YOUR REVISION ROUTE

Read a summary, close your notes and explain the idea in your own words. Use the cards to identify weak points and build a revision list linked to the lessons.

5.1 | THE INTERNET AND THE WORLD WIDE WEB

The internet is the infrastructure of interconnected networks. The web is the collection of websites and pages accessed using it. Browsers, servers, DNS and protocols have different roles in obtaining a page.

5.1.1–3 | INTERNET, WEB, URL AND HTTPS

Infrastructure, service, address and protocol are different concepts
IdeaRemember
InternetCommunication infrastructure; also supports services other than the web
World Wide WebWebsites, pages and linked resources
URLA resource address: scheme, host and path
HTTPRules for web requests and responses
HTTPSHTTP through a secure connection, normally using TLS

In https://learn.example.org/courses/lesson.html, https is the scheme, learn.example.org is the host, and /courses/lesson.html is the path.

HTTPS encrypts exchanged content, protects integrity and helps authenticate the named server. It does not prove that a website’s claims are honest or conceal all connection metadata.

Revisit internet and web

5.1.4 | ALL BROWSER FUNCTIONS

The browser is application software, not the internet or a search engine
FunctionPurpose
Render HTMLProcess page structure into displayed content
Bookmarks / favouritesSave chosen addresses
HistoryRecord visited pages under applicable settings
TabsKeep multiple pages open
CookiesStore small site-related data for matching requests
NavigationBack, forward and reload
Address barShow or enter a URL; may also accept search input

A normal bookmark saves a link, not a complete offline copy. Back moves through a tab’s navigation history, not automatically to a site’s home page. Tabs can share cookies within a profile.

Revisit browser functions

5.1.5 | LOCATE, RETRIEVE AND DISPLAY

Sequence: read URL → obtain address information → connect → request resource → receive response → render.

DNS returns name information, not the lesson’s HTML
RoleContribution
DNS / domain name serverResolve the host name to suitable address information
IP addressSupport network delivery towards the server
BrowserSend requests and render received resources
Web serverProcess requests and send responses
HTMLDescribe the returned page’s structure

The path selects a resource on the host. A valid cached DNS answer may avoid a fresh full lookup. HTML can refer to separate images and stylesheets, requiring further requests.

A 404 response means a server responded but the requested resource was not found; it is not necessarily a DNS failure.

Revisit page retrieval

5.1.6 | COOKIES AND SESSIONS

Cookie lifetime and server-side session validity are separate
ConceptDistinction
CookieSmall browser-stored data sent with suitable matching requests
Session cookieNormally lasts for the browser session in the syllabus model
Persistent cookieHas an expiry or lifetime; can remain across sessions
Server-side sessionApplication state associated with related requests
Session identifierA value linking requests to stored session information

Cookies can save personal details, track preferences, support carts and recognise logins. They can contain a value or identify server-held information. A secure login need not store the raw password in a cookie.

Persistent does not mean permanent. Closing one tab need not end the browser session, and restoration behaviour varies. A server can invalidate a session even if its cookie remains.

Tracking can link visits. Cookie restrictions do not stop every possible tracking technique.

Revisit cookies

5.2 | DIGITAL CURRENCY

A digital currency exists only electronically. It can transfer value or pay for accepted goods and services. Not every digital payment uses cryptocurrency or blockchain.

5.2.1–2 | BLOCKCHAIN AND TRANSACTIONS

A blockchain is an ordered digital ledger of linked blocks. The syllabus describes a time-stamped series of records that cannot be altered. Technically, cryptographic links make unauthorised alterations detectable, while validation and consensus rules make replacement of the accepted history difficult.

Hashing is not encryption, and hashes alone do not decide the accepted history
PartPurpose
Transaction recordRecord a transfer or change
TimestampProvide associated time information
Previous-block hash referenceLink a block to earlier history
ValidationCheck authorisation and available/unspent value
ConsensusDetermine the accepted ledger history

In an invented fee-free account model, A begins with 10 units, sends B 3, B sends C 1, then A sends C 2. Final balances: A = 5, B = 2, C = 3; total = 10. B cannot then send 4.

A private key can authorise a transfer through a signature without being published. Public transaction records do not guarantee anonymity. Not all digital currency designs are decentralised.

Revisit blockchain and the worked ledger

5.3 | CYBER SECURITY

Explain the threat’s process and aim, then link a protection’s mechanism to the risk it reduces. Confidentiality, integrity and availability describe different security needs.

5.3.1 | THREATS AND THEIR AIMS

Methods can combine: a phishing message can deliver a Trojan with a ransomware payload
ThreatProcess and intended effect
Brute forceTest candidate credentials to gain access
InterceptionObtain transmitted information
DDoSMultiple sources exhaust resources and disrupt access
HackingGain unauthorised access to systems or data
VirusInfect a host file/program and replicate when it runs
WormSelf-replicate without needing a host-file attachment
TrojanDisguise malicious functions as useful software
SpywareSecretly or improperly monitor and collect information
AdwareUnwanted or deceptive advertising-related behaviour
RansomwareRestrict access and demand payment/concession
PhishingImitate a trusted source in deceptive communication
PharmingManipulate resolution/configuration towards a fake destination
Social engineeringManipulate people into unsafe disclosure or action

DDoS primarily targets availability, not necessarily data theft. A slow site alone does not prove an attack. A Trojan is defined by deception, not self-replication.

Phishing is a form of social engineering; pharming changes the route or resolution rather than simply sending a deceptive message.

Revisit security threats

5.3.2 | PROTECTION METHODS

Authentication checks identity; authorisation controls access
MethodHow it helps
Access levelsRestrict permitted actions and records
Username/passwordCheck account identity using a secret
BiometricsCompare a measured characteristic with enrolled information
Two-step verificationRequire an additional verification step
Anti-malware: anti-virus / anti-spywareDetect, block or deal with malicious software
Automatic updatesApply relevant fixes with less reliance on reminders
Check spelling and toneSpot warning signs, without assuming good writing proves authenticity
Check link URLInspect actual destination and host; verify important requests independently
FirewallFilter traffic according to rules
Privacy settingsReduce unnecessary visibility or collection
Proxy serverHandle requests through an intermediary with suitable policy controls
SSL/TLS secure-connection conceptEncrypt and protect exchanged content; authenticate the named server

The syllabus names SSL; modern secure web connections use its successor TLS. HTTPS protects transport, not the honesty of every site.

A proxy does not automatically encrypt everything or hide the user from its operator. A firewall is not a universal malware scanner. Anti-malware and updates reduce risk without guaranteeing detection or removal of every weakness.

Separate recoverable backups support recovery, but do not prevent data theft. Sync is not automatically a recoverable backup.

Revisit keeping data safe

COMMON MISTAKES

  • Confusing the internet, web, browser and search engine.
  • Making DNS responsible for displaying HTML.
  • Treating HTTPS as proof that a site is trustworthy.
  • Confusing a session cookie with server-held session state.
  • Calling every electronic payment blockchain-based.
  • Claiming hash links alone make rewriting impossible.
  • Calling all malware viruses or mixing phishing and pharming.
  • Describing one security control as complete protection.

READY TO TEST YOURSELF?

Trace a page request, compare cookie lifetimes, explain a blockchain link, identify a threat and justify a protection. Select cards that need more practice.