Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is the OSI Model?

The OSI model describes network communication as seven layers. Real networks do not implement it, but it remains the vocabulary defenders use to place attacks and controls.

Illustration for the cybersecurity term OSI Model
Home / Blog / Cybersecurity Terms / What Is the OSI Model?
17 November 2026

What Is the OSI Model?

What Is the OSI Model?

The Open Systems Interconnection model, standardised as ISO/IEC 7498-1, divides network communication into seven layers, each providing a service to the one above it. It was developed as a blueprint for an actual protocol suite that lost to TCP/IP, so nothing you run implements it. What survives is the vocabulary: when an engineer says a problem is at layer two, or a product is described as a layer seven firewall, this is the reference being used, and it remains the most convenient way to place attacks and controls against each other.

The Seven Layers, With Their Security Dimension

LayerFunctionTypical attacksControls
7 ApplicationProtocols users interact with: HTTP, SMTP, DNSInjection, broken access control, phishingWAF, secure coding, email authentication
6 PresentationEncoding, encryption, compressionTLS downgrade, padding oracles, deserialisationModern cipher policy, safe parsers
5 SessionEstablishing and managing dialoguesSession hijacking, fixationSecure cookies, session timeouts, rebinding
4 TransportTCP and UDP, ports, reliabilitySYN floods, port scanning, reflectionSYN cookies, rate limiting, stateful filtering
3 NetworkIP addressing and routingIP spoofing, BGP hijacking, ICMP abuseIPsec, ingress filtering, RPKI
2 Data linkFrames, MAC addresses, switchingARP spoofing, VLAN hopping, rogue DHCP802.1X, DHCP snooping, dynamic ARP inspection
1 PhysicalCables, radio, signallingTapping, jamming, cable accessPhysical security, fibre monitoring

Why Defenders Still Use It

Three reasons, all practical.

It separates concerns. TLS protects data at layers five and six and above; it does nothing about a forged frame at layer two. An engineer who understands this does not propose HTTPS as a remedy for ARP spoofing, which is a conversation that happens more often than it should.

It structures defence in depth. An attack that passes one layer may be caught at another. A volumetric flood is handled at layers three and four by upstream scrubbing; an application-layer flood that mimics real users needs layer seven rate limiting. Buying one and assuming it covers the other is a recurring and expensive mistake.

It speeds diagnosis. Working from the bottom up — link established, address assigned, route present, port reachable, handshake completing, application responding — isolates a fault far faster than guessing. The same discipline applies to a security incident: establishing which layer the anomaly sits at narrows the candidate causes immediately.

There is a fourth use that gets less attention: the model is a decent audit checklist. Walk a network design layer by layer and ask what authenticates, what encrypts, and what logs at each one. Most organisations find a confident answer at layers three, four, and seven, and silence at layers one and two — no port authentication, no switch hardening, no record of which device plugged into which socket. That silence is where an attacker with building access begins.

Where the Model Breaks Down

Be clear about this, because treating the model as literal truth causes its own confusion.

Layers five and six barely exist in practice. TLS is habitually called a layer six protocol, but it runs over TCP and carries session semantics, so it spans four, five, and six depending on how you squint. QUIC is worse for the model: it is a transport protocol that includes its own cryptographic handshake and runs over UDP, deliberately crossing three layers at once.

The real internet uses the four-layer TCP/IP model, which maps onto OSI only loosely. And modern security tooling ignores layers entirely: an identity-aware proxy makes decisions using user identity, device posture, and request content simultaneously.

Treat the model as a map rather than the territory. It is useful for placing a control and for making sure nothing has been left uncovered, and it stops being useful the moment someone argues about whether a product is layer four or layer seven instead of about what it actually inspects.

When we scope an engagement we describe coverage in these terms for exactly that reason — it makes gaps visible. Our Penetration Test Services cover the stack from the switch port upwards.

FAQ – Frequently Asked Questions

Why Learn the OSI Model if Networks Use TCP/IP?

Because it is the shared vocabulary. Firewall capabilities, load balancer modes, attack categories, and product datasheets are all described in OSI layer terms even though no implementation follows the model. It also gives a systematic order for troubleshooting and a checklist for making sure controls exist at every level rather than clustering at the application.

Which Layer Does TLS Belong To?

There is no clean answer, which is itself instructive. TLS is commonly placed at layer six because it handles encryption, but it runs on top of TCP, manages sessions, and in the case of QUIC incorporates the transport itself. The practical question is not which layer it occupies but what it protects: data in transit between two endpoints, not frames on the local network.

What Is a Layer 7 Attack?

An attack against the application protocol rather than the network beneath it. HTTP floods that issue expensive, legitimate-looking requests, SQL injection, and API abuse are all layer seven. They matter because network-level defences see valid traffic and let it through, so they require application-aware controls such as a web application firewall and request rate limiting.

Does the OSI Model Still Apply to Cloud Environments?

The layering concept does, though you no longer control the lower layers. A cloud provider owns the physical and data link layers, you configure the network layer through virtual networks and security groups, and you own everything above. The model is still useful for deciding which controls are yours under the shared responsibility model.

Related Terms

You May Be Interested In These

What Is Diffie-Hellman Key Exchange?

Cybersecurity Terms

17 November 2026

What Is Diffie-Hellman Key Exchange?

Read More
What Are SPI and I2C?

Cybersecurity Terms

17 November 2026

What Are SPI and I2C?

Read More
What Is Network Access Control?

Cybersecurity Terms

17 November 2026

What Is Network Access Control?

Read More