1. Encryption (keeps data secret)

HTTPS uses Transport Layer Security (TLS) to encrypt the data between your browser and the website.

• Even if an attacker intercepts the data, it looks like unreadable gibberish
• Sensitive info (passwords, credit card details) stays private

Without HTTPS: attacker can read everything
With HTTPS: attacker sees encrypted nonsense

2. Authentication (proves the website is real)

HTTPS uses SSL/TLS certificates issued by trusted organizations called Certificate Authority (CAs).

• These certificates verify that the website is legitimate
• Your browser checks the certificate before connecting

Prevents attackers from impersonating real websites

3. Data Integrity (prevents tampering)

HTTPS ensures that:

• Data cannot be changed during transmission
• If an attacker tries to modify anything, the connection breaks or shows a warning

Stops attackers from injecting malicious content

4. Secure Handshake (key exchange)

When you visit an HTTPS site:

1. Your browser and server perform a TLS handshake
2. They agree on encryption methods
3. They securely exchange keys

This process often uses public-key cryptography:

• A public key (shared openly)
• A private key (kept secret by the server)

Ensures only the intended server can decrypt the data

HTTPS greatly reduces MITM risk, but it’s not foolproof if:

• You ignore browser warnings
• A device is already compromised
• Attackers use advanced tricks (like fake certificates)

How it works (simple idea)

Imagine you’re sending a message to a website:

You → (attacker intercepts) → Website

The attacker places themselves “in the middle” and can:

• Read your data (like passwords, messages)
• Modify the data
• Steal sensitive information

Step-by-step process

1. Interception
   The attacker gains access to your connection
   (often through unsecured public Wi-Fi)
2. Eavesdropping
   They monitor the data being sent (e.g., login credentials)
3. Manipulation (optional)
   They may alter the communication
   (e.g., redirect you to a fake website)

Common types of MITM attacks

• Wi-Fi eavesdropping – Fake or unsecured Wi-Fi networks
• ARP spoofing – Attacker links their device to your IP address
• DNS spoofing – Redirects you to fake websites
• Session hijacking – Steals your active login session

A MITM attack is like someone secretly listening to—and possibly changing—a private conversation between you and another party.

How ransomware works (step-by-step)

1. Infection

Ransomware usually enters a system through:

• Phishing emails (malicious attachments or links)
• Downloading unsafe software
• Visiting compromised websites
• Exploiting system vulnerabilities

2. Installation

Once inside, the ransomware installs itself silently on your device without your knowledge.

3. Encryption or Locking

The malware then:

• Encrypts your files (documents, photos, databases), or
• Locks your entire system

Encryption means your files become unreadable without a special decryption key.

4. Ransom Demand

After locking your data, you’ll see a message like:

• “Your files are encrypted”
• “Pay X amount (often in cryptocurrency) to get them back”

5. Payment Pressure

Attackers often:

• Set deadlines
• Threaten to delete data
• Sometimes threaten to leak sensitive information

Types of ransomware

• Crypto ransomware – encrypts files
• Locker ransomware – locks the device
• Double extortion – encrypts data and threatens to leak it

1. Malware (Malicious Software)

Malware is any software designed to harm or exploit systems.

Common types:

• Viruses – attach to files and spread when opened
• Worms – spread automatically across networks
• Ransomware – locks your data and demands payment
• Spyware – secretly monitors your activity
• Trojans – disguise themselves as legitimate programs

2. Phishing Attacks

Phishing tricks people into revealing sensitive information like passwords or bank details.

Examples:

• Fake emails pretending to be from banks
• Messages with malicious links
• Fake login pages

3. Man-in-the-Middle (MitM) Attacks

In these attacks, a hacker secretly intercepts communication between two parties.

Example:

• Using public Wi-Fi to steal login details while you browse

4. Denial-of-Service (DoS) Attacks

These attacks overload a system or website so it crashes or becomes unavailable.

• DoS – from a single source
• DDoS (Distributed DoS) – from many systems at once

5. Password Attacks

Attackers try to gain access by cracking passwords.

Methods include:

• Brute force (trying many combinations)
• Dictionary attacks (common passwords)
• Credential stuffing (using leaked passwords)

6. Social Engineering

Instead of hacking systems, attackers manipulate people.

Examples:

• Pretending to be IT support
• Asking for OTPs or passwords
• Creating fake urgency to trick victims

7. Insider Threats

Threats that come from inside an organization.

• Disgruntled employees
• Careless staff exposing data
• Misuse of access privileges

8. Advanced Persistent Threats (APTs)

These are long-term, targeted attacks where hackers secretly stay inside a system to steal data over time.

9. Zero-Day Exploits

Attacks that target unknown vulnerabilities—before developers can fix them.

10. Supply Chain Attacks

Hackers attack a trusted third-party service to indirectly access their target.

At its core, cybersecurity is about keeping three things safe (often called the CIA triad):

• Confidentiality – making sure sensitive information is only accessed by the right people
• Integrity – ensuring data isn’t altered or tampered with
• Availability – making sure systems and data are accessible when needed

What does cybersecurity protect against?

Cybersecurity defends against threats like:

• Hacking (unauthorized access to systems)
• Malware (malicious software like viruses, ransomware)
• Phishing (tricking people into revealing sensitive info)
• Data breaches (leaking or stealing confidential data)

Where is cybersecurity used?

It’s used everywhere digital systems exist:

• Personal devices (phones, laptops)
• Businesses and banks
• Government systems
• Online services (email, social media, cloud storage)

Why TCP optimization matters

TCP (Transmission Control Protocol) ensures data reaches the user reliably, but plain TCP can be slow because of:

• High latency (long distances between client and server)
• Packet loss (retransmissions delay content delivery)
• Inefficient connection setups (handshakes, multiple connections)

TCP optimization reduces these delays so websites, APIs, and streaming services feel faster.

How Cloudflare optimizes TCP

1. Edge Termination
   • TCP connections are terminated at Cloudflare’s edge servers near the user.
   • Traffic from the edge to your origin can use optimized internal routes.
2. TCP Multiplexing
   • Multiple client connections are consolidated into fewer connections to the origin.
   • Reduces load and latency while improving server efficiency.
3. TCP Fast Open (TFO)
   • Allows sending data during the TCP handshake, reducing the time for new connections.
4. Advanced Congestion Control
   • Cloudflare can dynamically adjust packet sending rate based on network conditions to reduce retransmissions and delays.
5. Packet Loss Mitigation
   • Uses forward error correction (FEC) and smart retransmission strategies to recover lost packets faster.
6. HTTP/3 and QUIC
   • While technically not TCP, Cloudflare encourages HTTP/3 over QUIC as an alternative:
     • QUIC is built on UDP but offers TCP-like reliability with faster connection setup.
     • Greatly reduces latency on lossy or high-latency networks.

Why TCP optimization matters

TCP (Transmission Control Protocol) ensures reliable delivery of data, but it can be slow in certain situations:

• High latency networks (e.g., international traffic)
• Packet loss or unstable connections
• Multiple small requests leading to repeated handshakes

Without optimization, users may experience slow page loads, buffering, or timeouts.

How Akamai optimizes TCP

1. Edge Termination
   • Akamai terminates TCP connections at edge nodes, close to the user.
   • This avoids long-distance TCP round-trips between the user and your origin server.
2. TCP Multiplexing
   • Many small user connections are combined into fewer persistent connections to the origin.
   • Reduces load on the origin server and improves response times.
3. TCP Fast Open
   • Reduces latency for new connections by sending data during the initial handshake.
4. Intelligent Congestion Control
   • Dynamically adjusts the flow of packets based on network conditions.
   • Avoids unnecessary delays or dropped packets.
5. Packet Loss Recovery
   • Detects and recovers from lost packets faster than standard TCP, improving perceived speed.

Key Features

1. Automatic Image Optimization

• Converts images into modern, efficient formats like WebP or AVIF
• Resizes and compresses images based on device, screen size, and network conditions
• Reduces load times without degrading visual quality

2. Automatic Video Optimization

• Converts videos into adaptive streaming formats like HLS or DASH
• Adjusts bitrate and resolution dynamically depending on user bandwidth
• Supports on-the-fly transcoding so the right version is delivered to each device

3. Edge Processing

• Image & Video Manager works at Akamai’s edge nodes, meaning media is optimized closer to the user, reducing latency
• No need to pre-process every version of an image or video at origin

4. Responsive Media Delivery

• Detects user device, screen size, and connection speed to serve the best version automatically
• Helps improve performance scores on tools like Google PageSpeed Insights

5. Integration with Akamai Properties

• You can configure media optimization rules as part of your property
• Works seamlessly with caching, security, and delivery rules already applied via Akamai

Benefits

• Faster load times – optimized images/videos load more quickly on all devices
• Reduced bandwidth costs – smaller files reduce data usage
• Global consistency – users everywhere get the best version of content
• Automatic updates – new images/videos are optimized in real-time without manual intervention

It’s the central unit for managing your web presence on the Akamai Intelligent Edge Platform.

Key points about a property

1. It represents your application or website
   • Example: www.test.com or api.test.com
   • Each property corresponds to a set of rules for how traffic is handled.
2. Contains configuration rules
   • Caching rules: How content is cached at edge nodes (e.g., static files vs. dynamic content)
   • Security rules: WAF, bot mitigation, DDoS protection, TLS settings
   • Performance optimizations: Compression, image optimization, redirects
   • Edge logic: EdgeWorkers scripts or other custom behaviors
3. Assigned a hostname
   • Properties are accessed via Akamai hostnames (e.g., www.example.com.edgesuite.net)
   • Your DNS points to this hostname to route traffic through Akamai’s edge network.
4. Managed through Akamai Control Center
   • Akamai’s web interface or API allows you to create, update, and deploy property configurations.

Think of them as the “local branches” of the internet that handle requests before they ever reach the origin server.

Key characteristics of edge nodes

1. Geographically distributed
   • There are thousands of Akamai edge nodes worldwide, located in ISPs, data centers, and major internet hubs.
   • The closer a node is to a user, the faster it can serve content.
2. Caching content
   • Stores static files like images, videos, or web pages to avoid repeated requests to the origin server.
3. Running edge logic
   • Some nodes can execute code (e.g., using Akamai EdgeWorkers) for personalization, authentication, or other tasks at the edge.
4. Security enforcement
   • Edge nodes can inspect traffic and block malicious requests (DDoS protection, bot mitigation, WAF rules) before they reach your server.
5. Intelligent routing
   • Edge nodes direct traffic to the fastest or most available path, balancing loads across the network.

How edge nodes fit into the Akamai Intelligent Edge Platform

• The platform is the network + software + analytics.
• The edge nodes are the physical servers that carry out the platform’s functions:
  • Delivering content
  • Securing traffic
  • Running edge computing tasks
  • Optimizing performance