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
| Idea | Remember |
|---|---|
| Internet | Communication infrastructure; also supports services other than the web |
| World Wide Web | Websites, pages and linked resources |
| URL | A resource address: scheme, host and path |
| HTTP | Rules for web requests and responses |
| HTTPS | HTTP 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.
5.1.4 | ALL BROWSER FUNCTIONS
| Function | Purpose |
|---|---|
| Render HTML | Process page structure into displayed content |
| Bookmarks / favourites | Save chosen addresses |
| History | Record visited pages under applicable settings |
| Tabs | Keep multiple pages open |
| Cookies | Store small site-related data for matching requests |
| Navigation | Back, forward and reload |
| Address bar | Show 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.
5.1.5 | LOCATE, RETRIEVE AND DISPLAY
Sequence: read URL → obtain address information → connect → request resource → receive response → render.
| Role | Contribution |
|---|---|
| DNS / domain name server | Resolve the host name to suitable address information |
| IP address | Support network delivery towards the server |
| Browser | Send requests and render received resources |
| Web server | Process requests and send responses |
| HTML | Describe 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.
5.1.6 | COOKIES AND SESSIONS
| Concept | Distinction |
|---|---|
| Cookie | Small browser-stored data sent with suitable matching requests |
| Session cookie | Normally lasts for the browser session in the syllabus model |
| Persistent cookie | Has an expiry or lifetime; can remain across sessions |
| Server-side session | Application state associated with related requests |
| Session identifier | A 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.
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.
| Part | Purpose |
|---|---|
| Transaction record | Record a transfer or change |
| Timestamp | Provide associated time information |
| Previous-block hash reference | Link a block to earlier history |
| Validation | Check authorisation and available/unspent value |
| Consensus | Determine 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.
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
| Threat | Process and intended effect |
|---|---|
| Brute force | Test candidate credentials to gain access |
| Interception | Obtain transmitted information |
| DDoS | Multiple sources exhaust resources and disrupt access |
| Hacking | Gain unauthorised access to systems or data |
| Virus | Infect a host file/program and replicate when it runs |
| Worm | Self-replicate without needing a host-file attachment |
| Trojan | Disguise malicious functions as useful software |
| Spyware | Secretly or improperly monitor and collect information |
| Adware | Unwanted or deceptive advertising-related behaviour |
| Ransomware | Restrict access and demand payment/concession |
| Phishing | Imitate a trusted source in deceptive communication |
| Pharming | Manipulate resolution/configuration towards a fake destination |
| Social engineering | Manipulate 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.
5.3.2 | PROTECTION METHODS
| Method | How it helps |
|---|---|
| Access levels | Restrict permitted actions and records |
| Username/password | Check account identity using a secret |
| Biometrics | Compare a measured characteristic with enrolled information |
| Two-step verification | Require an additional verification step |
| Anti-malware: anti-virus / anti-spyware | Detect, block or deal with malicious software |
| Automatic updates | Apply relevant fixes with less reliance on reminders |
| Check spelling and tone | Spot warning signs, without assuming good writing proves authenticity |
| Check link URL | Inspect actual destination and host; verify important requests independently |
| Firewall | Filter traffic according to rules |
| Privacy settings | Reduce unnecessary visibility or collection |
| Proxy server | Handle requests through an intermediary with suitable policy controls |
| SSL/TLS secure-connection concept | Encrypt 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.
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.