lecture recording on 06 February 2025 at 18.13.52 PM

A professor, currently pursuing their doctoral degree, is in the final stage of research and is seeking participants for a survey focused on the cybersecurity job market.
The survey aims to gather information about participants' backgrounds in cybersecurity, their job applications, and rejection rates to understand the current market landscape.
Interested students can access the survey through a provided link (surveymonkey.com) and may have the opportunity for an interview via Zoom with the professor, who is appreciative of the contribution as research data.

In an enterprise network, when multiple employees simultaneously access popular websites (e.g., cnn.com), it can lead to bandwidth issues.
Repeated requests for the same content can bog down network performance.

A web cache is implemented to store frequently accessed web pages locally, reducing the need for repeated requests to the same server.
Employees can quickly access cached content without overloading the network.
Cached pages are updated periodically based on how often the source website changes its content.

Caches are configured to store content for different durations depending on website update frequency. For example, news sites may refresh every 20-30 minutes, while less dynamic sites may only refresh hourly.
When a cache reaches the end of its lifespan, a new request is made to the original server to refresh the content.

Early Internet connections were limited in bandwidth, necessitating efficient traversal and services without overwhelming network resources.
Web caching minimizes retransmission, optimizing available bandwidth.

HTTP/1.1 required sequential connections for web content, leading to inefficiencies. This could create significant delays if a large object (like an image) was encountered.
Solutions to issues like head-of-line blocking were limited in effectiveness.

HTTP/2 introduced multiplexing, allowing multiple requests and responses to be sent in parallel over a single connection, improving load times for web pages with multiple elements (text, images, etc.).
Status codes like 304 (not modified) and 200 (success) were defined for responses, maintaining functionalities from HTTP/1.1 while boosting performance.

With the rise of streaming services and mobile device usage, HTTP/3 was developed using UDP instead of TCP to reduce latency and eliminate connection overhead during data transfer.
QUIC protocol was introduced, embedding security features by default and minimizing handshake times, directly addressing security concerns while transmitting data.

QUIC supports fast, secure connections suitable for modern web applications and mobile communications, accommodating for high-speed demands of streaming services.
It allows for faster content delivery by working efficiently within a distributed infrastructure.

Email systems consist of user agents (e.g., Outlook) that connect to mail servers for sending and receiving messages.
The protocol SMTP governs communication between mail servers but has undergone less change compared to HTTP due to its reliable simplicity.

SMTP operates over port 25, pushing email data from user agents to servers.
Messages include sender and recipient headers, crucial for proper delivery and processing.

DNS translates user-friendly domain names (like Google.com) into IP addresses that are understandable by machines.
Each query to a domain entails a structured request through distributed DNS servers, including a root server for top-level domains and authoritative servers for individual domains.

Without sufficient security measures, DNS servers can be manipulated, making users susceptible to redirection to fraudulent websites (DNS spoofing).

DNSSEC was introduced to protect against such attacks by requiring authentication of requests and making it difficult for malicious actors to alter DNS settings.
Proper routing and hierarchy ensure resilient performance and redundancy within the DNS structure.

Questions were welcomed prior to concluding the lecture series, and students were informed about upcoming lab sessions.
Students are encouraged to participate in lectures and labs as an essential part of their learning experience.